-
Notifications
You must be signed in to change notification settings - Fork 23
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
Updates for pvlib 0.9.0 #121
Conversation
Pushed a sphinx fix (link) -- sorry for the scope creep, but I wanted to see what it thought of the test suite. Edit: tests all pass, although I note that the 3.7 job decided to build pandas from source for some reason 🤔 |
Thank you so much for the contribution again @kanderso-nrel ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kanderso-nrel ! LGTM
@@ -49,7 +49,7 @@ In the "full mode", ``pvfactors`` calculates the equilibrium of reflections betw | |||
Details on the "fast mode" simulations | |||
====================================== | |||
|
|||
In the "fast mode", ``pvfactors`` assumes that all incident irradiance values for the system are known except for the PV row back surfaces. So since the system to solve is now explicit (no matrix inversion needed), it runs a little bit faster than the full mode, but it is less acurrate. | |||
In the "fast mode", ``pvfactors`` assumes that all incident irradiance values for the system are known except for the PV row back surfaces. So since the system to solve is now explicit (no matrix inversion needed), it runs a little bit faster than the full mode, but it is less accurate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -335,4 +335,4 @@ | |||
|
|||
|
|||
def setup(app): | |||
app.add_stylesheet('css/custom.css') | |||
app.add_css_file('css/custom.css') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Contributors | ||
------------ | ||
* Marc Anoma (:ghuser:`anomam`) | ||
* Kevin Anderson (:ghuser:`kanderso-nrel`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@@ -555,7 +555,7 @@ def test_check_direct_shading_continuity(): | |||
|
|||
# Check expected outputs: before v1.3.0, expected output is | |||
# [20.4971271991293, 21.389095477613356], which shows discontinuity | |||
expected_out = [20.497127, 20.50229] | |||
expected_out = [20.936348, 20.942163] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to preserve the values for pvlib 0.8.0 in a comment, analogous to what was done above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, done
requirements.txt
Outdated
@@ -1,4 +1,4 @@ | |||
pvlib>=0.7.0,<0.9.0 | |||
pvlib>=0.7.0,<0.10.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kanderso-nrel The thought popped into my head last night as to if it we should require pvlib 0.9.0 as a minimum, because of the error involved in the earlier versions.
(The error appears minor in the test you fixed here, but maybe that is a false impression and/or shouldn't matter.)
@pfranz-spwr @srisukhi @loganrozanski could you please merge this PR if it looks good to you? |
Thanks for the heads up, @anomam. @campanelli-sunpower can you take a look and merge if the PR looks good? |
I do think a note somewhere about different results would be a good idea -- it's only a minor difference, but exact reproducibility is important in some contexts, and it might save some users some pain if they know to expect differences with pvlib 0.9.0+. Whether that note should go in the change log, or maybe a docstring, or maybe just the narrative docs, I'm not sure. Let me know if you want me to add something like that to this PR :) Also howdy @campanelli-sunpower, nice to see another pvlib name here! |
@kanderso-nrel (cc @anomam) Thanks for updating the comment for posterity, so that consumers will be aware of the presence of the error with earlier versions of pvlib. What are your thoughts about releasing this with a new lower limit of pvlib 0.9.0? |
I don't feel strongly one way or the other. Requiring |
@anomam What are your thoughts on requiring |
hey team @kanderso-nrel @campanelli-sunpower ! My preference would also be to set |
Requirement updated and note added :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update.
Howdy @anomam, pvlib 0.9.0 was released the other day. No changes needed in pvfactors itself, but there is one change needed to the test suite related to a bugfix in the Perez model (pvlib/pvlib-python#1239). I have updated the values here to pass with pvlib 0.9.0, but that means the test fails on older pvlib versions. Is that acceptable? I could make the test values depend on the installed pvlib version if you want the tests to pass with older pvlibs as well. I suspect CircleCI will install the latest pvlib for this PR, but we'll see what actually happens.
I also took the liberty of creating a 1.5.2 whatsnew, although a note about different irradiance values w/ pvlib 0.9.0 may be in order.
Unrelated: may want to add python 3.9 to the test matrix -- 3.10 release candidates are already available on some CIs!
cc @spaneja