welsberr
/
ReNunney
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ReNunney/docs/MIGRATION.md

1.1 KiB
Raw Blame History

Migration

Goal

Move the current cost-of-substitution implementation into renunney in staged, low-risk steps.

Current State

Operational code still lives in:

renunney currently acts as:

  • a clean git repository,
  • a run-control wrapper,
  • a stable place for deployment and orchestration commands,
  • the eventual destination for migrated code.

Recommended Migration Order

  1. Keep orchestration running from the legacy path until real multi-host runs are stable.
  2. Migrate the orchestration modules first:
    • python/orchestration.py
    • python/run_orchestration.py
  3. Migrate Track 1 runner and API next:
    • python/run_track1.py
    • python/track1_api.py
  4. Migrate the Track 1 simulation core after the runner path is stable:
    • python/track1_reference.py
    • python/track1_threshold.py
    • python/track1_analysis.py
  5. Migrate docs and example configs last, after path references are updated.

Constraint

Do not break the ability to run current Figure 1 jobs while migrating code.