KOPR

KOPR documentation

Light Curve Scenarios

A Light Curve Scenario is the portable Comet Analyzer workspace format for saving and restoring a complete 1..N-comet analysis workspace.

One scenario for 1..N comets

The same scenario mechanism is used for a single comet and for multi-target analysis. The file suffix is .kopr-lc.json. It belongs to the current Comet Analyzer workspace rather than to the removed Comparison workflow.

Scope: confirms one common scenario contract for 1..N targets. It does not introduce a second single-target or comparison-specific format.

Save and restore

  1. Prepare the Comet Analyzer workspace and its selected targets.
  2. Use the scenario action to write a portable .kopr-lc.json file.
  3. Open the scenario through the current Comet Analyzer workflow.
  4. Allow the complete scenario to validate before the restored state becomes active.

The restore is transactional. A failed or incomplete restore must not leave a partially replaced workspace.

Range behavior after restore

The current automatic-range policy remains authoritative after scenario restoration. Automatic X is defined by visible observations. Models, formula curves and the Bortle reference can influence automatic Y only inside that observation-defined X interval.

The Auto range command is a cached view action. It restores the current automatic view without creating a second scientific workflow.

Formula and target validation

Formula editors show the active target, but validation is atomic across all selected targets. A scenario therefore does not weaken the current draft/Refresh/Save/Analyse transaction rules or create target-local partial commits.

Compatibility boundary

wanalyzer.py and wcomparison.py are deprecated aliases. Historical Comparison material is accepted only through the one-way migration path owned by legacy_comparison_import.py. It must not be treated as an active scenario parser or a second runtime mode.