Correct ERA5 timestamp convention#2773
Open
AdamRJensen wants to merge 2 commits into
Open
Conversation
echedey-ls
approved these changes
Jun 4, 2026
Member
echedey-ls
left a comment
There was a problem hiding this comment.
LGTM! I'd call it a bugfix thou, also cause it probably draws more attention.
| * Clarifies how Linke turbidity values can be provided to | ||
| :py:func:`pvlib.clearsky.ineichen` via | ||
| :py:func:`pvlib.clearsky.lookup_linke_turbidity` (:issue:`2598`, :pull:`2746`) | ||
| * Documented that timestamps returned by :py:func:`~pvlib.iotools.get_era5` |
Member
There was a problem hiding this comment.
Suggested change
| * Documented that timestamps returned by :py:func:`~pvlib.iotools.get_era5` | |
| * Document that timestamps returned by :py:func:`~pvlib.iotools.get_era5` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/sphinx/source/whatsnewfor 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.See discussion in #2772.