You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This is related to #866 which fixes the issue of coercing a TMY3 when it contained a February from a leap year, such as Greensboro, which has February 1996. See this comment
Describe the solution you'd like
It was proposed to warn users if they chose a leap year, that by convention a TMY file would only have 8760 hours, so 2/29 would not be included
Describe alternatives you've considered
Instead of raising a warning, this could be added to the docstring for read_tmy3