Period sets the exact date window a model trains on.
Connecting it
Drag a Period node off a Variables node (or connect a model directly to Variables to skip this step and use the full range).
Fields
| Field | What it controls |
|---|---|
| Name | Optional label — defaults to "Period" if left blank. Useful once a canvas has more than one period covering different windows (e.g. "Full history" vs. "Post-relaunch"). |
| Start date / End date | The window to train on. meryn pre-fills the full range your Dataset covers; narrow it to exclude anything that would distort the fit — a launch spike, a stockout, a period before you started tracking a channel consistently. |
There's nothing else to configure here — Period exists so the same Variables mapping can feed more than one date window without re-uploading or re-mapping anything.
Why "editing" a Period resets what's downstream
Changing the date range always means retraining anything connected to it, so there's no in-place edit. Clicking a configured Period gives you a confirm step that tells you how many models depend on it, then reopens the modal pre-filled with the current dates so you can adjust and resubmit — the canvas wiring itself doesn't change, only what's inside the box and everything that was trained from it.
What connects here
Upstream: Variables. Downstream: EDA, or a model node — Robyn, Meridian, or PyMC.