Run Field Descriptions
ElemBio Cloud displays the following information for planned, active, and historical runs.
| Field | Description |
|---|---|
| AVITI OS | The AVITI OS version operating the instrument during the run |
| Connection ID | The unique identifier that the instrument assigns to the storage connection to transfer data from the instrument |
| Created By | The name of the team member who creates the planned run |
| Expires On | The expiration date for a consumable, written as yyyy-mm-dd |
| Index 1 | The number of cycles in the Index 1 read |
| Index 2 | The number of cycles in the Index 2 read |
| Instrument:Serial Number | The instrument serial number, a 24-digit number |
| Instrument:Side | The instrument name and side, either Side A or Side B |
| Library Pools | The number of library pools in the run, either 1 or 2 |
| Library Type | The library prep workflow: Adept, Elevate, or Third Party |
| Library Structure | The structure of the input library: Circular or Linear |
| Lot Number | The manufacturing batch identifier that Element assigns to a consumable |
| Operator | The name of the person who set up the run on the instrument |
| Output Location | The URL path to the output location of the run directory, including bases files |
| Part Number | The item identified that Element assigns to the consumable |
| Read 1 | The number of cycles in Read 1 |
| Read 2 | The number of cycles in Read 2 |
| Read Order | The order of reads and indexes in the run |
| Run Description | An optional description of the run |
| Run ID | The unique identifier that AVITI OS assigns to the run |
| Run Length | The run duration in hours and minutes |
| Run Name | The name of the sequencing run |
| Scan Area | The area of the flow cell that the system images |
| Sequencing Kit | The sequencing kit type and the maximum number of supported cycles |
| Serial Number | A unique identifier for the consumable |
| Status | The current run status:
|
| Step | The current run step, which appears as "{Status} at {Cycle}/{Total Cycles}" for stopped, failed, or active runs and "Total Cycles: {Cycles}" for completed runs |
| Tags | Any tags assigned to the run |
| Time Completed | The timestamp indicating run completion, written as yyyy-mm-dd hh:mm |
| Time Created | The timestamp indicating run creation, written as yyyy-mm-dd hh:mm |
| Time Last Updated | The timestamp indicating the last run update, written as yyyy-mm-dd hh:mm |
| Time Started | The timestamp for the start of the run, written as yyyy-mm-dd hh:mm |
| Updated By | The name of the team member responsible for the last update of the planned run |
Run Statuses
| Status | Gauge Color | Description |
|---|---|---|
| Priming or Primed | Blue | The run is in setup mode. Metrics do not populate before sequencing starts. |
| Sequencing | Blue | The run is actively progressing. Metrics populate as they become available. |
| Pausing or Paused | Orange | The run is pausing or paused for flexible start. Resumption is automatic. |
| Completed | Green | The run successfully completed. The instrument completed data transfer to the selected storage location. |
| Failed | Red | The instrument encountered a critical issue during the run and cannot progress. Data analysis completed up to and including the last successfully sequenced cycle, and the instrument transferred available data to the selected storage location. |
| Stopped | Teal | A user stopped the run before it completed. Data analysis completed up to and including the last successfully sequenced cycle, and the instrument transferred all data to the selected storage location. |
Sensitive Metadata
By default, AVITI OS sends the following metadata to a secure and customer-specific ElemBio Cloud database:
- Run description
- Sample names from the run manifest, if applicable
The ElemBio Cloud database is separate from the telemetry database. Therefore, telemetry does not collect metadata. If you prefer to keep metadata on-instrument, contact Element Technical Support and request Restrict Metadata mode. When the mode is enabled, a lock appears on the run description in ElemBio Cloud and sample names are masked as numbers. The numbering reflects the order of samples in the run manifest.