Skip to main content

Module trials

Module trials 

Source
Expand description

What was run with a version: the trials, their states and their curves.

A commit is the version and does not change. What gets tried with it grows without end — a hundred trials, three analyses, a report — and none of that can touch a commit’s hash, so it is associated with the version rather than versioned. soma writes it from the machine running the study; here it is only read, because whoever claimed a trial is its only writer and a second one would invent a race that does not exist today.

The name is the whole of the coupling. soma binds each trial to <study>/trial/<n>/<attempt>, and a study’s name is any string:

exp/<tree>/<commit>              ← that version's study
exp/<tree>/<commit>/trial/3/0    ← its fourth trial, first attempt
exp/<tree>/<commit>/said/2       ← what somebody said about that commit

A commit’s study is the prefix its journal already lives under, so the trials land beneath it with no line of soma changing: no correspondence record, no index to keep. And the store’s cost rule holds — state, point and score are in the record — so counting forty commits’ trials is one scan and only the curve is paid for when somebody asks to see it.

What cannot be said from here is which is best: whether 0.0837 is good depends on a direction that lives in the Goal handed to a sampler and is written in no record. Guessing it would be the quiet lie this tool exists not to let past, so either soma-tree.toml declares it or it is not said, and the range — true without knowing the direction — is shown instead.

Structs§

Curve
A trial’s curve, which is what costs a fetch.
Tally
What is seen of a commit’s trials without reading a single blob.
Trial
A trial, as it comes back from a scan.
Trials
The trials of one investigation, kept in a store.

Enums§

Goal
Which way is better. Not in the store: declared.
Trouble