Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update overview #202

Merged
merged 3 commits into from
Sep 23, 2020
Merged

Update overview #202

merged 3 commits into from
Sep 23, 2020

Conversation

mdeceglie
Copy link
Collaborator

I updated the docs overview to reflect our broader applications.

@kandersolar kandersolar merged commit d562f0d into feat/inverter_availability Sep 23, 2020
@mdeceglie mdeceglie deleted the overview_change branch September 23, 2020 22:41
mdeceglie added a commit that referenced this pull request Oct 1, 2020
* add is_online and tests

* improvements to is_online and tests

* add downtime_loss, tests, documentation

* update inverter sizing calculation to normalize to 1

* add tables to requirements.txt

* add explicit int conversion to make travis happy

* improve differentiation of downtime from comms outage.  improve docs

* docstring formatting updates

* make availability loss calculation more robust to mixed production and comms outages

* Add walkthrough notebook of the availability code

* Drop py2.7 from travis config and setup.py

* losses.py -> availability.py

* update with rough draft of functions from PVSC paper

* update module references

* linting

* add upper limit parameter

* reuse downtime detection logic

* remove unused pivoting functions

* add power tests

* Delete losses_test.py

* remove unnecessary return from loss_from_power

* add power tests for optional params

* various fixes to loss_from_energy

* energy tests

* tests energy method starts/ends in outage

* don't assume 15-min data; dtype fixes

* add plotting.availability_cumulative_plot

* add plotting tests

* new availability example notebook

* update sphinx docs linking

* fit init.py, fix broken test

* add quantiles parameter and test

* extend full outage detection to not require a full comms outage as well

* handle "negative production" outages

* bugfix

* add tables package to test requirements

* add tables to requirements.txt

* allow outages to be slightly negative to account for self-consumption

* add note about timeseries continuity

* switch from ineichen to haurwitz for clearsky test inputs

* Revert "add tables package to test requirements"

This reverts commit 1985101.

* Revert "add tables to requirements.txt"

This reverts commit e8e0c7b.

* rerun availability notebook

* sundry improvements from review

* good old fashioned reorganization

* docs and bugs

* add test for relative_sizes

* pv-terms compat

* more pvterms

* move plotting func to plotting module, add wrapper method

* fix starting in an outage bug

* plotting tests

* add plot func to init

* update and rerun notebook

* plot docstring example and api entry

* advertise availability in index.rst

* add suggested text to notebook

* Update rdtools/availability.py

Co-authored-by: Michael Deceglie <[email protected]>

* instrument calibration wording

* units

* raise error if calling plot before run and add accompanying test

* m -> M

* data gap rephrasing

* d->D

* rework the plotting function so it uses pandas plotting for all subplots

* rerun notebook

* Update overview (#202)

* Update overview

* reword

* heading update

* in-text citations for degradation and soiling

* rename private methods per mdeceglie's suggestion

* don't drop the tz on the results dataframe index

* Update rdtools/availability.py

Co-authored-by: Michael Deceglie <[email protected]>

* reflow docstring text for 80 char limit

* Update docstrings per review

* check for index match on input timeseries

* warn if double-counted loss is detected

* docstring updates

* clarify units

* changelog

* backticks -> single quotes in tables

* more table reformatting

* shift the end of outages back by one so the timestamp matches the last nan/zero values instead of the first positive value

* add "other uses" section to notebook and rerun

* simplify other use case section of notebook

Co-authored-by: Michael Deceglie <[email protected]>
@kandersolar kandersolar added this to the Version 2 milestone Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants