Update a cell measurement by id
Update an existing cell measurement’s metadata.
Only metadata fields can be updated (name, protocol, test_setup, notes, properties). Time series and steps data cannot be modified.
Path Parameters
Body
Model for updating an existing cell measurement. All fields optional.
1 - 255Protocol information as a dict with: name (str), ambient_temperature_degc (float), definition (dict | str - UCP or other protocol format)
Test setup: cycler, operator, lab, etc.
When the test finished (ISO 8601 with timezone). Set this to mark the measurement complete; leave null while it is still running.
Forecast of when a still-running test will finish (ISO 8601 with timezone). Distinct from end_time. Null when no estimate exists.
Free-text explanation of how estimated_end_time was derived.
When estimated_end_time was last computed (ISO 8601, tz).
Optional ID of the channel this measurement ran on.
Optional catalog program for this measurement.
Key-value measurements using Quantity format for numerics. Only for measurement_type='properties'. Example: {'thickness': {'value': 0.52, 'unit': 'mm'}}
Response
Successful Response
1 - 255Organization this measurement belongs to.
Project this measurement belongs to
Protocol information. Typical keys: 'name' (str), 'ambient_temperature_degc' (float), 'definition' (dict | str — a UCP protocol definition or another protocol format).
ISO 8601 datetime with timezone (UTC preferred) marking when the test started.
ISO 8601 datetime with timezone (UTC preferred) marking when the test finished. Leave null while the test is still running; set it once the measurement is complete. A null end_time means the cell is still considered 'on test' in the Lab view.
ISO 8601 datetime with timezone (UTC preferred) forecasting when a still-running test will finish. Distinct from end_time (the actual finish): this is an estimate. Null when no estimate has been computed yet.
Free-text explanation of how estimated_end_time was derived.
ISO 8601 datetime with timezone marking when estimated_end_time was last computed.
Physical test setup. Typical keys: 'cycler' (model), 'operator', 'lab', 'channel_number' (int).
Set to true only once step-type labels (Rest, CC charge, CV, discharge, etc.) have been manually reviewed. Server-inferred labels should leave this false.
Free-text notes about the cell measurement
What shape of data this measurement holds. Determines which fields are populated and which upload flow applies. See the class docstring.
time_series, file, properties Flat key/value measurements, populated only when measurement_type is 'properties'. Numeric values use the Quantity format. Example: {'thickness': {'value': 0.52, 'unit': 'mm'}, 'DCIR': {'value': 12, 'unit': 'mohm'}}.
Metadata about uploaded files (MIME types, dimensions, etc.)
Optional ID of the channel this measurement ran on.
Optional catalog program for this measurement (copied from a linked planned measurement when present).
User ID of the user who created this measurement
Email of the user who created this measurement
Lifecycle of server-side step processing. 'ready' once steps are available; 'pending'/'running' while the upload is being processed asynchronously; 'failed' if processing failed (see processing_error).
pending, running, ready, failed Reason step processing failed, when processing_status is 'failed'.
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