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
Bug Description
It appears that the representative profile outputs for ReEDS may not be shifted to local time (assuming the input profiles are in UTC).
To Reproduce
Compare the 'rep_profiles_0' tables of these two files:
Specifically, compare the profile for sc_id 2726 (column 2726) in the input table to its corresponding entry in the output table (it is the representative profile for region 1 class 8, or column 4 of the output table). The comparison looks like:
Notice that, other than being scaled by 1000, the output has only shifted by -1 as compared to the input (correctly accounting for our requirement to start the arrays at 1am), while the timezone correction should be an additional shift of -8.
Expected behavior
Representative profiles are shifted to local time.
The text was updated successfully, but these errors were encountered:
Bug Description
It appears that the representative profile outputs for ReEDS may not be shifted to local time (assuming the input profiles are in UTC).
To Reproduce
Compare the 'rep_profiles_0' tables of these two files:
Specifically, compare the profile for sc_id 2726 (column 2726) in the input table to its corresponding entry in the output table (it is the representative profile for region 1 class 8, or column 4 of the output table). The comparison looks like:
Notice that, other than being scaled by 1000, the output has only shifted by -1 as compared to the input (correctly accounting for our requirement to start the arrays at 1am), while the timezone correction should be an additional shift of -8.
Expected behavior
Representative profiles are shifted to local time.
The text was updated successfully, but these errors were encountered: