Skip to content

Clearsky functions handling tz-aware datetimes as tz-naive, contrary to user guide #2054

@yhkee0404

Description

@yhkee0404

Describe the bug
Both of the functions clearsky.lookup_linke_turbidity and irradiance.get_extra_radiation are supposed to be tz-aware in accordance with the user guide, but take the tz-aware inputs as tz-naive in their implementations and return incorrect results.
Another functions using these two functions may also have been affected by the errors; i.e. Location.get_clearsky, clearsky.ineichen, or clearsky.simplified_solis.

To Reproduce
Refer to my comprehensive analysis on the .ipynb file simulated in the same way as the user guide.
It seems too big for the browser to render because it shows me only this message: An error occurred.
In a similar situation, please download the file or clone my repository to see the content.

Expected behavior
There should be no items searched on the file by the keyword rows , each of which means errors subject to timezones.

Screenshots
For instance, on the user guide, it prints: climatological linke_turbidity = 3.329496820286459.
However, after converting the local timezone to utc, it prints on my analysis above another value: climatological linke_turbidity = 3.3247187176482633.

Versions:

  • pvlib.__version__: v0.10.5
  • pandas.__version__: 2.2.2
  • python: 3.11.9

Additional context
Almost the same as #237

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions