Interactive configurator: fill in RPC, ODF, and region

Generates .par, launch command, and teaching-plan JSON locally in your browser; never touches the file system or runs SAS

Published on

July 13, 2026

ImportantRead the boundaries first

This is a teaching/audit configurator, not a remote execution console.

  • Inputs are never uploaded; they are written only to the current browser's localStorage.
  • The page cannot tell whether the paths you enter exist, nor read FITS headers.
  • The configurator generates only the three profiles with direct execution evidence: XARTATOMS v1.4.1 full/resume (4.background=yes) or M31HotISM v1.3.2 accepted C (3B.background=yes). No generic mode mixing.
  • While blocking errors are non-zero, you cannot copy/download the .par or generate the launch command; you can still download the teaching-plan JSON to record the issues.
  • The teaching-plan JSON and the downloaded .par comments carry the profile ID/evidence, source revision, inventory SHA-256, and execution_authorized=false; the "Teach Hermes" export reads the same browser's builder profile.
  • Before real execution you must still complete source, geometry, camera, QPB, and output-namespace preflight in a local shell.

ESAS teaching config builder

You fill in real paths; the page only compiles them into auditable text.

Shared plan ID: initializing…

Used only in download file names; does not change science semantics.
Usually contains `odf/` and `rpc/`. Saved only in the current browser.
Fill in the exact engine you want Hermes to learn/execute, not just a version number.

The profile decides the active section and 3B/4/extra_region semantics; no more one-template-for-all-modes.

Camera
The page does not judge camera-region coverage. Compile into homogeneous batches before a real run.
Generated into `extra_region_file`; may be left blank, but must be explained in the plan.
Generated into `extra_region_list`. Different camera readiness should be split into different configs.
Preflight you have confirmed

Local-only: this page has no `fetch`, XHR, WebSocket, form action, or upload endpoint. Paths appear only in your current browser's preview / localStorage / downloaded files.

Derived paths

Status
Not yet generated

Blocking errors

  • Field checks not yet run.

Non-blocking warnings

  • Field checks not yet run.

Generated `.par` draft

Generated after filling the fields above.

Generated launch command

Generated after filling the fields above.

The command uses shell-safe single-quote escaping; the page still will not execute it.

Why a profile is more than a mode= name

The two successful chains use different active sections:

Profile active section 3B.background 4.background extra_region Evidence
XARTATOMS v1.4.1 recent [full] or [resume] no yes yes XART-E03 / ENGINE-E01
M31HotISM v1.3.2 accepted [C] yes no no HOTISM-E009 / accepted .par

So the page now generates the whole semantics set per profile, instead of mechanically copying the [full] switches into [C]. The M31HotISM legacy mask builder, linker, and verifier still embed 0112570101 exposure IDs, 92/90 mask rows, and rejected-attempt assumptions; these are acceptance evidence only and must be parameterized before migrating to a new OBSID.

Why 4.fitting=no is generated by default

This configurator discusses extraction only. Fitting should not be embedded in the same run before source/QPB/RMF/ARF and geometry have passed. The M31CGM historical redu once enabled fitting simultaneously; both the XARTATOMS recent production and M31HotISM E009 put no-fit acceptance first.

Why there is no "run" button

Cloudflare Pages is a static HTTPS site. A browser cannot safely access arbitrary local paths, nor source SAS/HEADAS. Adding a remote button that executes local commands would widen credential, path-injection, and accidental-overwrite risks.

If you ever want the web page to drive local execution, build a separate authenticated local companion service, and treat:

  • allow-listed project roots;
  • exact command schema;
  • dry-run / approval;
  • output namespace guard;
  • process log / cancel;
  • no secret in browser

as a separate security design. It is out of scope for this round of static teaching pages.

Please actually fill in a set of paths and regions you endorse, download the .par and teaching-plan JSON, then export the decision JSON on the "Teach Hermes" page. The same browser carries the builder profile ID/evidence into the decision, and ultimately forces execution_authorized=false. Then tell me: do the field names, profile, energy range, mask, and preflight match how you really work?

中文