IssueSchedule๏
IssueSchedule: when forecasts are issued and what they cover โ as data.
An energy-forecasting problemโs cadence (ziplineโs trading calendar, renamed):
each Origin is one forecast issue โ a clock time asof at which the
model acts, plus the target_index of timestamps it must forecast. Both the
event-driven and vectorized execution modes consume the same origins, so the
schedule is the single source of truth about timing.
- class emflow.problems.schedule.Origin(asof: Timestamp, target_index: DatetimeIndex, column: str | None = None)[source]๏
Bases:
objectOne forecast issue: act at
asof, forecasttarget_index.columnscopes the origin to one column of the target field โ multi-zone competitions (GEFCom2014 windโs 10 zones) score each zone separately, so each (task, zone) pair is its own origin.- target_index: DatetimeIndex๏
- column: str | None = None๏
- class emflow.problems.schedule.IssueSchedule(origin_freq, cover_start, cover_end, target_freq, origin_time=None)[source]๏
Bases:
objectGenerates
Origins over an evaluation period.Construct with one of the classmethods; call
origins()with the period to evaluate over.- classmethod hourly(horizon='1h', target_freq='1h') IssueSchedule[source]๏
One origin per hour, forecasting
asof + horizon(rolling 1-step).
- classmethod daily(at='09:00', covers=('1D', '2D'), target_freq='1h') IssueSchedule[source]๏
One origin per day at
at(UTC), coveringasof + covers[0]toasof + covers[1]attarget_freqโ the day-ahead pattern.
- classmethod single(asof, target_index) IssueSchedule[source]๏
A one-shot schedule with an explicit target index (GEFCom task style).
- classmethod explicit(origins: Sequence[Origin]) IssueSchedule[source]๏