-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Clarify output variable mapping in calcparams_ functions #2405
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
Clarify output variable mapping in calcparams_ functions #2405
Conversation
…_cec, and calcparams_pvsyst
Co-authored-by: Cliff Hansen <cwhanse@sandia.gov>
Co-authored-by: Cliff Hansen <cwhanse@sandia.gov>
Co-authored-by: Cliff Hansen <cwhanse@sandia.gov>
@cwhanse I've merged your suggestions into my PR branch! |
@MaxJackson can you add yourself as a contributor to the whatsnew file? In docs/sphinx/source/whatsnew/v0.11.3.rst I don't think we need a note about this change. |
Two trailing whitespaces to remove also :) |
@cwhanse done! |
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 @MaxJackson
And for fixing the typo in the whatsnew file
remote-data
) and Milestone are assigned to the Pull Request and linked Issue.The functions
pvsystem.calcparams_desoto
,pvsystem.calcparams_cec
andpvsystem.calcparams_pvsyst
return variables which are named/labeled differently than the variables in the functions themselves. This PR adds inline comments where the return variables are initialized to help clarify exactly what calculated values are being returned.