跳转至

Xsuite Import and Historical Experiment Migration

简体中文 · Previous: Results and evidence · Next: Engine capabilities

Structural Xsuite Line import

vm-accelerator-studio-import-xsuite projects a resolved Xsuite Line JSON into .vmaproj and packages a canonical v0.2 structural project, import evidence, and exact source bytes. A separately reviewed expected SHA-256 is mandatory; mismatch produces no output.

./build/dev/vm-accelerator-studio-import-xsuite \
  --input resolved-line.json \
  --output imported-ring.vmaproj \
  --project-id imported-ring \
  --display-name "Imported ring structural projection" \
  --expected-sha256 <reviewed-source-sha256> \
  --project-json imported-ring.studio-project.json \
  --evidence-json imported-ring.import-evidence.json

The bounded projection accepts Marker, Drift, FirstOrderTaylorMap (length only; matrix retained in source evidence), Quadrupole, Sextupole, Bend, zero Multipole, and inactive Cavity. Nonzero relative multipoles, active RF, unknown classes, and malformed maps are rejected.

This is structural browsing/editing, not Xsuite calculation equivalence. A FirstOrderTaylorMap is represented geometrically as a drift, so calculationEquivalentToXsuiteSource=false remains mandatory. Re-running Xsuite physics still needs the original source or a future lossless model.

Historical Experiment Migration

Open an audited historical-studio-migration-audit/0.2 catalog from File → Import → Open historical migration catalog…. The workspace can filter by tier/status/ feature/duplicate/text, switch unique contents versus all file instances, map logical roots, verify exact size/SHA, show YAML read-only, attach evidence to .vmaproj, start manual reconstruction, or send historical intent/evidence to the Screening Study banner.

Historical Migration

Mapping and attaching example

For catalog paths under ssmb-new-steps/... and local root /data/ssmb-new-steps:

  1. Open the catalog and choose Map Sources.
  2. Map logical ssmb-new-steps to /data/ssmb-new-steps.
  3. Select a record and Verify Selected.
  4. Only an exact verified size/hash becomes attachable.
  5. Open or save the active project as .vmaproj, then Attach Evidence.
  6. Studio atomically saves, reopens, and verifies the package; physics revision does not change.

Mappings stay in local settings. Absolute/traversing paths, .., symlink escape, missing files, or hash mismatch fail closed.

Migration tiers

  • Bounded migration: the reviewed catalog proves a narrow safe mapping.
  • Structural project + external experiment: structure is retained while experiment semantics remain external.
  • Evidence/manual reconstruction: exact source is attached and the user explicitly rebuilds a current project.

Studio never infers circumference, harmonic, beam, RF, or lattice from filenames or old scalars; renames historical GPU work as CPU; relabels DA/FMA as generic tracking; or promotes historical results to the current revision.

The catalog's Import Xsuite action remains disabled when only a logical path exists without an independent expected SHA. A hash computed from the same local file is not independent review; after obtaining one, use the standalone structural importer.