Skip to content

Adding altitude lookup for Location class #1850

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

Merged
merged 11 commits into from
Jun 21, 2024

Conversation

nicomt
Copy link
Contributor

@nicomt nicomt commented Sep 11, 2023

  • Closes Altitude lookup table #1516
  • I am familiar with the contributing guidelines
  • Tests added
  • Updates entries in docs/sphinx/source/reference for API changes.
  • Adds description and name entries in the appropriate "what's new" file in 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`).
  • New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
  • Pull request is nearly complete and ready for detailed review.
  • Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

Set altitude automatically from built-in map when not specified for the Location class.
See #1547

Set altitude automatically from built-in map when not specified.
See pvlib#1547
@cwhanse cwhanse added this to the v0.10.2 milestone Sep 11, 2023
Copy link
Member

@cwhanse cwhanse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nicomt

@@ -22,6 +22,8 @@ Enhancements
* Added :py:func:`~pvlib.iam.interp` option as AOI losses model in
:py:class:`pvlib.modelchain.ModelChain` and
:py:class:`pvlib.pvsystem.PVSystem`. (:issue:`1742`, :pull:`1832`)
* Default altitude in :py:class:`pvlib.location.Location`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this considered a breaking change?
The api is technically the same, but it can cause issues downstream

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is, if the user has been omitting altitude for locations where there is data. I'm willing to live with it because the effect on air mass and other downstream variables is small.

If we want to deprecate, we could hold this PR for 10.3 and emit a warning of the future change in v10.2 instead. @kandersolar ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think what is most consistent with our versioning strategy is to wait until 0.11.0 for this (unless we consider it a bugfix, which is a stretch IMHO).

Either way I wouldn't bother with a deprecation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @kandersolar, Sounds good!
If you switch the milestone to 0.11.0 would I get a notification when it gets a release date?
I can resolve conflicts then

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately I'm not aware of a way for you to automatically get notified when we start working on 0.11.0. But anyway we will see this PR in the list and come back to it then. Thanks for the contribution :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @nicomt, we're working towards v0.11.0 now, so the time has come to dust off the PR if you're still interested :)

@@ -22,6 +22,8 @@ Enhancements
* Added :py:func:`~pvlib.iam.interp` option as AOI losses model in
:py:class:`pvlib.modelchain.ModelChain` and
:py:class:`pvlib.pvsystem.PVSystem`. (:issue:`1742`, :pull:`1832`)
* Default altitude in :py:class:`pvlib.location.Location`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think what is most consistent with our versioning strategy is to wait until 0.11.0 for this (unless we consider it a bugfix, which is a stretch IMHO).

Either way I wouldn't bother with a deprecation.

nicomt and others added 2 commits September 11, 2023 17:00
Better type definition

Co-authored-by: Kevin Anderson <[email protected]>
@kandersolar kandersolar modified the milestones: v0.10.2, 0.11.0 Sep 15, 2023
@kandersolar kandersolar requested a review from AdamRJensen June 21, 2024 16:02
@kandersolar kandersolar merged commit c6547b5 into pvlib:main Jun 21, 2024
24 of 25 checks passed
@kandersolar
Copy link
Member

Thanks @nicomt!

@nicomt
Copy link
Contributor Author

nicomt commented Jun 21, 2024

Thanks for finishing the PR @kandersolar. I tried to look at this sooner but had a busy week. I'm glad is in now 😄

@nicomt nicomt deleted the lookup_altitude3 branch June 21, 2024 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Altitude lookup table
4 participants