Estimate a planned measurement's duration from its protocol
Work out how long this planned test will take, before it runs.
Simulates the whole protocol with the cell specification’s default model and
writes the total into estimated_duration_seconds — the value scheduling
books channel windows off, which until now was always typed in by hand.
buffer_pct pads the simulated figure by that percentage before booking it,
defaulting to DEFAULT_BUFFER_PCT. A protocol whose duration is fixed by the
protocol alone is never padded.
Returns immediately with estimated_duration_status set to estimating;
the job worker fills the duration in when the simulation finishes. Poll the
plan, or watch the status. When the simulation was already run for an
identical protocol and model, the estimate comes back ready instead.
For a test that has already started, use the cell measurement’s
estimate_end_time endpoint instead: that one replays the measured steps
and forecasts only what remains.
Body
Options for a planned test's duration estimate.
The body is optional on the endpoint; omitting it takes the default margin.
0 <= x <= 100Response
Successful Response
A planned measurement row returned by the API.
1 - 255Lifecycle state for a planned measurement.
requested, scheduled, in_progress, completed, cancelled Cell specification the requester wants tested (set at request time).
Cell instance this future measurement will run on.
Channel reserved for this measurement, once scheduled.
Named protocol (experiment_template) this measurement will run. Required on create; a planned measurement must name a protocol.
Optional catalog program (Formation, Cycling, …) for this test request.
Planned physical setup.
When setup/run is planned to start.
When this planned measurement is expected to release the channel.
Expected run duration before scheduled times exist.
x >= 1Operator setup duration before the test starts.
x >= 0Operator teardown duration after the test finishes.
x >= 0Free-text planning notes.
Lifecycle of a duration estimate computed by a background simulation.
Used by both estimates: a planned test's total duration
(planned_measurements.estimated_duration_*) and a running test's
remaining duration (cell_measurements.estimated_end_time_*). One enum
because the lifecycle is identical -- only what is being estimated differs.
estimating while the job is in flight, ready once a value came from
it, failed with the reason in the accompanying note. None means no
estimate was ever requested.
estimating, ready, failed