-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Make i_x
and i_xx
SAPM parameters optional
#2433
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
Conversation
todo: edit: now done |
:py:func:`pvlib.pvsystem.sapm` directly and through | ||
:py:class:`~pvlib.pvsystem.PVSystem` and :py:class:`~pvlib.modelchain.ModelChain`. |
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.
Not super important, but is there a reason for ~
on the class reference but not the function reference?
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.
The thought was to make it clear that the change applies to both the function and class layers. If it rendered as just sapm
, it would be visually ambiguous whether it was pvlib.pvsystem.sapm
or pvlib.pvsystem.PVSystem.sapm
.
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.
LGTM
…apm` (#2435) * Update pvsystem.py * Update v0.12.1.rst * Update pvsystem.py * Update pvsystem.py * list non-required param instead, units, formatting * Update pvlib/pvsystem.py Co-authored-by: Cliff Hansen <[email protected]> * update param list (excl. param removed by #2433) * add blank line for bullet list rendering * separate C param --------- Co-authored-by: Cliff Hansen <[email protected]>
i_x
andi_xx
SAPM parameters optional #2402[ ] Updates entries indocs/sphinx/source/reference
for API changes.docs/sphinx/source/whatsnew
for all changes. Includes link to the GitHub Issue with:issue:`num`
or this Pull Request with:pull:`num`
. Includes contributor name and/or GitHub username (link with:ghuser:`user`
).remote-data
) and Milestone are assigned to the Pull Request and linked Issue.