Versions and snapshots

Definitions change as you refine your setup. Versions and snapshots freeze a script at a point in time so collects and studies run against code you trust.

Why freeze code

A dataset is only meaningful if you know which script produced it.

Change the Definition after collecting, and old events may no longer match the new logic. Snapshots prevent that drift.

Versions

Each time you save a meaningful change, Chartnaut records a version on the definition.

Open Research → Definitions → [your definition] → Versions to see the history — who changed what, when.

Snapshots

A snapshot is a version you mark ready for Collect and Study runs.

Before your first collect:

1. Open the definition

2. Go to Versions or the snapshot control in the builder

3. Create snapshot from the current script

4. Note the snapshot name or id — collects attach to it

Studies run against events from a specific snapshot’s collects.

When to snapshot again

Create a new snapshot when logic changes materially — new conditions, different emit rules, different indicators.

After a new snapshot, recollect datasets so events match. Old datasets stay tied to old snapshots.

What good looks like

Snapshot v3-orb-volume-filter is active. Every dataset and study on the definition references that snapshot. You experiment on draft code without breaking published results.

Important distinctions

Version snapshot (Definition) = frozen setup script.

Trade snapshot (Trades) = chart image saved with a trade — unrelated.

Study run = one execution of a study on a dataset — not a code snapshot.

Next

1. Collect a dataset — run after snapshot

2. Definition Builder — where you edit before snapshot

3. Profiles — separate settings buckets per definition