Skip to main content

Run Output Files

Refer to the following sections for information on the run output files available in ElemBio Cloud.

Sequencing Run Output Files

The following table defines the sequencing run output files from an AVITI System. Using the data browsing tools in ElemBio Cloud, you can access the output files from runs that use a compatible storage connection.

Braces around a file name component indicate variability. For example, the value for {tile} depends on the applicable tile number.

Directory and File NameFormatDescriptionQuantity
Root/Alignment/{read}_{tile}.alnBinary filesIndicate which polonies align to PhiX ControlOne per tile per read
Root/BaseCalls/{read}_C{cycle:000}.zipBinary filesContain base calls and associated Q scoresOne per read and cycle
Root/Filter/{tile}.filterBinary filesContain the filter status for each polonyOne per tile
Root/IndexAssignment.csvCSVRecords the results of onboard demultiplexingOne per run
Root/Location/{tile}.locBinary filesIdentify polony locations on the flow cellOne per tile
Root/RunManifest.csvCSVRecords biological sample information and analysis settingsOne per run
Root/RunManifest.jsonJSONReserved for Element processesOne per run
Root/RunParameters.jsonJSONRecords information about the run configurationOne per run
Stats/AvitiRunStats.jsonJSONRecords run metricsOne per run
Root/RunUploaded.jsonJSONThe last file transferred and marks run completionOne per run
Root/RunThumbnail.pngPNGThumbnail image for the runOne per run

Example Files

The following table provides links to examples of key output files from sequencing runs for different versions of AVITI OS.

AVITI OS VersionRun MetricsRun ParametersRun Uploaded
2.6.0AvitiRunStats.json (v2.0.0)RunParameters.json (v5.0.0)RunUploaded.json (v1.0.0)
2.5.0AvitiRunStats.json (v2.0.0)RunParameters.json (v4.0.0)RunUploaded.json (v1.0.0)

Run Metrics (AvitiRunStats.json)

The AvitiRunStats.json file contains the source information for run metrics. You can leverage the data in this file to set up the integration of metrics into another system, such as a LIMS interface.

The file defines aggregate run metrics first, followed by read and read cycle metrics. The file then defines the same metrics for each lane, including read and read cycle metrics for the lane.

Fields

The following table describes the information in the AvitiRunStats.json file.

FieldDescription
ABase composition percentage for adenine in a cycle
AverageQScoreAverage Q score for a cycle
BaseCompositionIdentifies the set of base composition measurements for a cycle
CBase composition percentage for cytosine in a cycle
CycleThe cycle number for a set of information and metrics
CyclesIdentifies the set of cycles for a read
GBase composition percentage for guanine in a cycle
I1The unassigned sequence identified in the I1 read
I2The unassigned sequence identified in the I2 read
IndexAssignmentIdentifies the set of information and metrics that describe index assignment for a lane or the entire run
IndexSamplesIdentifies the set of information and metrics for index samples and unassigned sequences
LaneThe lane number for a set of per lane metrics
LaneStatsIdentifies the sets of information and metrics for lanes
PercentAssignedReadsThe percentage of reads assigned to a sample
PercentMismatchThe percentage of polonies assigned to a sample with a mismatch
PercentOcurrenceThe occurrence rate for an unassigned sequence
PercentPhixErrorRateThe percentage of control reads that do not align to the PhiX Control Library
PercentPFThe percentage of reads that pass the quality filter process
PercentQ30The percentage of ≥ Q30 Q scores for the run, including assigned and unassigned reads
PercentQ40The percentage of ≥ Q40 Q scores for the run, including assigned and unassigned reads
PercentQ50The percentage of ≥ Q50 Q scores for the run, including assigned and unassigned reads
PFCountThe total number of reads that pass the quality filter process
PhiXAlignmentRateThe percent of reads that align to the PhiX Control Library
PolonyCountThe total number of polonies counted, either for a lane or the entire run
ReadThe read for a set of information and metrics, either R1 or R2
ReadsIdentifies a set of information and metrics for the reads, either for a lane or for the entire run
RunIDA universally unique identifier (UUID) assigned to the run and sourced from RunParameters.json
RunNameA text-based run identifier sourced from RunParameters.json
RunStatsIdentifies the set of information and metrics for the entire run
SampleNameThe name for an index sample sourced from the run manifest
TBase composition percentage for thymine in a cycle
TotalYieldThe total yield of all reads in gigabases
UnassignedSequencesIdentifies a set of unassigned index sequences, either for a lane or the entire run
VersionAVITI OS version number

Run Parameters

The RunParameters.json file contains a record of the input information for a run. When evaluating run performance or troubleshooting, you can review this file to confirm the sequencing run used the correct recipe and other parameters.

Fields

The following table describes the information in the RunParameters.json file. When applicable, the Possible Enum Values column lists the specified value options for a field.

FieldDescriptionPossible Enum Values
AdvancedSettingsIndicates if the run uses Advanced Run SettingsNot applicable
AnalysisLanesThe lanes that the run uses
  • 1
  • 2
  • 1+2
BarcodeStrThe barcode number for a consumable, which the instrument scans and identifies during consumable loadingNot applicable
BufferIdentifies a set of information that describes the buffer for the runNot applicable
ChemistryVersionThe chemistry version of the sequencing kit for the run
  • Cloudbreak for Cloudbreak
  • CloudbreakFS for Cloudbreak Freestyle
  • CloudbreakUQ for Cloudbreak UltraQ
ConsumablesIdentifies the set of information for run consumablesNot applicable
CyclesIdentifies the set of cycles for the runNot applicable
DateTimestamp for the runNot applicable
ExpirationThe expiration timestamp for a consumable, which the instrument identifies or a user inputs during consumable loadingNot applicable
ExpirationStrAn expiration ID number for a consumable, associated with the expiration dateNot applicable
FileVersionThe version of the RunParameters.json file for the runNot applicable
FlowcellIdentifies a set of information that describes the flow cell for the runNot applicable
FlowcellIDA serial number that serves as a unique identifier for the flow cellNot applicable
I1The number of cycles in the I1 readNot applicable
I2The number of cycles in the I2 readNot applicable
InstrumentNameThe name of the instrument for the runNot applicable
KitConfigurationThe total number of cycles available in the kit for the run
  • 150Cycles for a 2 x 75 kit
  • 300Cycles for a 2 x 150 kit
  • 600Cycles for a 2 x 300 kit
LibraryTypeThe structure of the input library
  • Circular
  • Linear
LotNumberThe lot number for a consumable, which the instrument identifies during consumable loading before the runNot applicable
LowDiversityIndicates if the run uses the Low-Diversity High-Multiplex option
  • true
  • false
OperatorNameThe name of the person who set up the run on the instrumentNot applicable
PartNumberThe part number for a consumable, which the instrument scans or a user inputs during consumable loadingNot applicable
PlatformVersionThe version of AVITI OS for the runNot applicable
PMGMaskA base mask used to generate the map of polonies.Not applicable
PreparationWorkflowThe library prep workflow
  • Adept
  • Elevate
  • ThirdParty
R1The number of cycles in the R1 readNot applicable
R2The number of cycles in the R2 readNot applicable
ReadOrderThe order of the reads for the runI1,I2,R1,R2 as applicable
RecipeExecutionIDA UUID for the run recipe, which governs the stages of a sequencing runNot applicable
RecipeValuesContains additional values for the recipe that the run uses, such as a filterMask valueNot applicable
RunDescriptionAn optional description for the runNot applicable
RunFolderNameThe name of the output folder that AVITI OS creates for the runNot applicable
RunIDA UUID assigned to the runNot applicable
RunNameA text-based run identifier enteredNot applicable
RunTypeThe type of AVITI System run runsSequencing
SerialNumberThe serial number for a consumable, which the instrument scans or a user inputs during consumable loadingNot applicable
SequencingCartridgeIdentifies a set of information that describes the sequencing cartridge for the runNot applicable
SideThe side of the instrument that the run uses
  • SideA
  • SideB
StorageConnectionIDA UUID for the storage connection that the run usesNot applicable
ThroughputSelectionThe output level for the run
  • High
  • Medium
  • Low
TilesIdentifies the set of tiles on the flow cell for the runNot applicable

Run Uploaded

The RunUploaded.json file indicates the completion of the run. The file contains high-level information about the run and an outcome field that confirms the run outcome. AVITI OS always transfers this file last, allowing its creation to serve as a trigger to start automated downstream analysis.

Fields

The following table defines the fields in the RunUploaded.json file. When applicable, the Possible Enum Values column lists the specified value options for a field.

FieldDescriptionPossible Enum Values
versionThe version of the RunUploaded.json fileNot applicable
instrumentThe name of the instrument for the runNot applicable
instrumentIdA UUID for the instrumentNot applicable
outcomeThe final outcome of the run
  • OutcomeCompleted
  • OutcomeStopped
  • OutcomeFailed
runTypeThe type of AVITI System runSequencing
recipeExecutionIdA UUID for the run recipe and sourced from RunParameters.jsonNot applicable
runIDA UUID assigned to the run and sourced from RunParameters.jsonNot applicable