6.3 The batch ledger

Chapter 6.3 follows chapter 6.2, The campaign boundaries and their pooling rules, and precedes chapter 6.4, The primary records and their order of precedence, within part 6, the reference part.

The batch ledger, a record that organizes the campaign runs, lists each run set, a launched group of cells, with its run identifier, date, status, project, tasks, conditions, lap profiles, model class, primary read, validity flag, tag, purpose, outcome, and boundary assignment. The authoritative records are 5. Run Sets/run_index.csv, 5. Run Sets/run_tags.json, 7. Monitoring/run_history.json, and the per-run-set folders. The history record uses the key runs, with one object for each run set and the fields run_id, date, status, valid_for_primary_analysis, summary, and link. source: operations/site-ia/A6-page-briefs.md, section X3.

The tag key decodes the batch labels and links them to the shakedown findings. The per-run-set folders supply the detailed records behind each ledger entry. The table preserves the source fields without replacing them with a summary or a selected subset. source: operations/site-ia/A6-page-briefs.md, section X3.

6.3.1 Ledger fields of the campaign record

run_id	date	status	project_id	task_ids	conditions	lap_profiles	model_class	primary_read	valid_for_primary_analysis
Each row in the authoritative index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index	Recorded in the index

source: run_index.csv rows by date

The index is the row-level ledger. The tag file supplies the batch label for each applicable run set, and the history file supplies the status summary and link. The per-run-set folder is the record for the detailed purpose and outcome. The ledger key carries the label decoding, with the interpretive account linked to R6. source: operations/site-ia/A6-page-briefs.md, section X3.

6.3.2 Boundary assignment of the campaign record

The automatic mode launched the run-set range 075 to 206. Each row receives its boundary assignment from the campaign boundaries and their pooling rules. The assignment travels with the row and does not change the recorded status or validity flag.

source: run_index.csv rows by date

Figure D-X3-1. The run sets of the campaign by date, model, and boundary

%% figure D-X3-1
flowchart TB
  n1["A chronological ledger figure generated from the run index and run history<br/>every run set by launch date<br/>status<br/>model class"]
  n2["tag<br/>purpose<br/>outcome<br/>boundary assignment"]
  n1 --> n2

source: operations/site-ia/A3-diagram-specification.md source: operations/site-ia/A6-page-briefs.md, section X3.

D-X3-1. Run-set chronology generated from the index and history, replacing the former timeline figure. source: operations/site-ia/A6-page-briefs.md, section X3.

Figure D-R6-1. The run sets of the campaign by date, model, and boundary

%% figure D-R6-1
flowchart TB
  subgraph runsets["Run sets"]
    n1_1["5. Run Sets/run_index.csv"] --> n1_2["run_id"]
    n1_2 --> n1_3["date"]
    n1_3 --> n1_4["status"]
  end
  subgraph status["Status"]
    n2_1["model_class"] --> n2_2["valid_for_primary_analysis"]
    n2_2 --> n2_3["complete"]
    n2_3 --> n2_4["ended_disposition_unrecorded"]
  end
  subgraph stopped["Stopped before completion"]
    n3_1["stopped_before_completion"] --> n3_2["aborted_api_errors"]
    n3_2 --> n3_3["step"]
    n3_3 --> n3_4["step"]
  end
  subgraph completed["Completed"]
    n4_1["step"] --> n4_2["step"]
    n4_2 --> n4_3["aborted_wiring_gap"]
    n4_3 --> n4_4["step"]
  end
  subgraph tags["Tags"]
    n5_1["tags"] --> n5_2["display"]
    n5_2 --> n5_3["run_sets"]
  end
  n1_4 --> n2_1
  n2_4 --> n3_1
  n3_4 --> n4_1
  n4_4 --> n5_1
  n3_3 -- "completed_shakedown" --> n3_3_reference["reference"]
  n3_4 -- "completed_pilot" --> n3_4_reference["reference"]
  n4_1 -- "completed_smoke" --> n4_1_reference["reference"]
  n4_2 -- "completed_invalid" --> n4_2_reference["reference"]
  n4_4 -- "5. Run Sets/run_tags.json" --> n4_4_reference["reference"]

source: operations/site-ia/A3-diagram-specification.md source: operations/site-ia/A6-page-briefs.md, section X3.

D-R6-1. Registry timeline shared with the shakedown findings. source: operations/site-ia/A6-page-briefs.md, section X3.

The changelog records the generator run for the new ledger figure and the replacement of the former timeline figure.

Previous: The campaign boundaries and their pooling rules | Next: The primary records and their order of precedence

source: operations/site-ia/A6-page-briefs.md, section ### X3.