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
I get an error when assigning ApparentSunEl to the DFOut column:
ValueError: cannot reindex from a duplicate axis
and I believe the reason comes from the fact that DFOut uses time as index and ApparentSunEl uses time_utc as index; and I think it raises an error because in my case time uses daylight saving and contains duplicate indices. Using ApparentSunEl.values instead should solve the issue.
The text was updated successfully, but these errors were encountered:
I'm guessing that the same thing happens with solarposition.pyephem. I don't think it should happen with solarposition.spa_python. We'll probably need .values on all of the columns.
It would be good to add a test of each method that uses duplicated labels due to DST. You could copy this test
but use a 2 element times index that occurs on the hour before and the hour of DST. You'd also copy the fixture expected_solpos_multi to create expected_solpos_dst_transition or something like that.
Old issue, but in my opinion requires no change to ephemeris. Times in data should be localized and daylight savings conflicts resolved by the user prior to this function. Maybe this is a requirement for the future pvlib.io.
In solarposition.ephemeris:
I get an error when assigning
ApparentSunEl
to theDFOut
column:and I believe the reason comes from the fact that DFOut uses
time
as index andApparentSunEl
usestime_utc
as index; and I think it raises an error because in my casetime
uses daylight saving and contains duplicate indices. UsingApparentSunEl.values
instead should solve the issue.The text was updated successfully, but these errors were encountered: