Cytoprofiling Run Field Descriptions
ElemBio Cloud displays the following information for planned, active, and historical cytoprofiling runs.
| Field | Description |
|---|---|
| Assigned | Percent of all reads assigned to a target |
| AVITI OS | The AVITI OS version operating the instrument during the run |
| B1-B7 | The batches in the cytoprofiling run in numerical order |
| Cell Confluency | Percent of flow cell surface area covered by cells |
| Cell Count | Number of cells identified in cell segmentation |
| 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 |
| Cytoprofiling Kit | The cytoprofiling kit type |
| Expires On | The expiration date for a consumable, written as yyyy-mm-dd |
| Instrument:Serial Number | The instrument serial number, a 24-digit number |
| Instrument:Side | The instrument name and side, either Side A or Side B |
| Lot Number | The manufacturing batch identifier that Element assigns to a consumable |
| No. Batches | The number of batches in the run |
| No. Wells | The number of wells in the flow cell 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 files |
| Part Number | The item identifier that Element assigns to the consumable |
| 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 cytoprofiling run |
| Serial Number | A unique identifier for the consumable |
| Status | The current run status: Planned runs: In Use or no status Active or historical runs: see Run Statuses |
| Step | The current run step, which appears as "{Status} at {Batch}" for stopped, failed, or active runs and "Completed" 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 |