Understanding how instrument autolaunch analysis maps to BaseSpace projects
Last updated
Was this helpful?
Last updated
Was this helpful?
For users intending to use the cloud for FASTQ generation and DRAGEN Secondary Analysis, the data will be associated with several BaseSpace Projects.
1. SampleSheet ProjectName
When using ProjectName values in Run Planning, the FASTQ files will be written to those locations.
In the SampleSheet.csv, this will be reflected in the [Cloud_Data] section.
Once BCL Convert (and any associated downstream analysis) is completed, the FASTQ files will be associated with the ProjectName specified on BaseSpace. The project column is not required to be specified, and if left blank the FASTQ Files will be written to a BaseSpace project following the nomenclature:
2. bssh_[region]_[run ID]
For example:
bssh_use1-prod_277283070
More information about regions can be found in the BaseSpace Help center article Global Regions. The run ID corresponds to the numerical value observed in the web address bar when viewing the run.
If any DRAGEN Secondary analysis is performed, this project will also contain the DRAGEN output.
3. ICA Workflows YYYY/MM
The ICA Workflow project are created each month, and generally will be empty. However, if any cloud analysis does not complete as expected, AppSession logs files will be written to this project and can be shared with Support to investigate further.
For any feedback or questions regarding this article (Illumina Knowledge Article #8915), contact Illumina Technical Support .
