Campaign#
Read a campaign config, run the research loop, and read its records. See The campaign config for the config’s sections.
Running a campaign#
Run a mining campaign from its config. |
|
Every trial record of the run, why it stopped, and where the ledger is. |
|
Why the campaign stopped: |
|
Every |
|
One part of a campaign checked: its |
|
Run the |
Configuration#
Every setting of a campaign, read from one YAML file with |
|
The data the Evaluator reads. |
|
How a factor's raw values become the values that are judged ( |
|
What ranked factors are neutralised against. |
|
How the Evaluator computes the round's graph. |
|
The Gate's sandbox limits and graph constraints. |
|
What an evaluated candidate needs to be accepted. |
|
The size of a round, the planner's quotas and when the campaign stops. |
|
What the prompt context holds; the run snapshot records it at the first start, and a resume may not change it. |
|
How |
|
One role's LLM: the backend name, the model and the backend's own settings. |
|
A mechanism type a candidate's hypothesis belongs to, with the line the prompts describe it by. |
Records and run state#
Append and read the trial records of a run directory. |
|
One candidate's outcome. |
|
The events file of one run directory, appended to by a campaign; safe to use from several threads. |
|
The events in the file at |
|
The snapshot of a run directory; build it with |
|
A resume was given files that differ from the run's snapshot. |
|
A resume runs other code than the run was last opened with. |
|
The training, confirmation, validation and hold-out segments, in that order, and the purge between them. |
|
A named, inclusive date range. |
|
The templates of a campaign: the built-in ones, any of them replaced from a file. |
|
Replaced templates are wrong; the message lists every problem. |