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
The last row appers to be daily aggregation and it seems keeping this in the merged timeseries is not too be helpful for downstream operations.
As my understanding EOD data is adjusted to 23:00 in syscore/dateutils.syscore/dateutils.py , and hourly and eod timesries is merged with syscore.pandas.frequency.merge_with_different_freq
Perhaps we could explore refining the merge logic to avoid including daily data when hourly data is available?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When examining contract price data for
YENEUR#20241200.parquet
, I've observed a potential issue with the merging of hourly and daily data.The last row appers to be daily aggregation and it seems keeping this in the merged timeseries is not too be helpful for downstream operations.
As my understanding EOD data is adjusted to 23:00 in
syscore/dateutils.syscore/dateutils.py
, and hourly and eod timesries is merged withsyscore.pandas.frequency.merge_with_different_freq
Perhaps we could explore refining the merge logic to avoid including daily data when hourly data is available?
Beta Was this translation helpful? Give feedback.
All reactions