Illumina NextSeq Instrument Interface
To ensure that your Illumina instrument warranty remains valid, this integration must be performed and maintained by the BaseSpace Clarity LIMS Support team as needed.
Overview of the BaseSpace Clarity LIMS ↔ Illumina NextSeq Instrument Interface
|
Image Action #
|
Description
|
|
0
|
NextSeq Run (NextSeq) 1.0 initiated in the LIMS.
|
|
1
|
|
1.
|
End Run event fires on Illumina instrument. |
|
2.
|
Instrument fires configured LIMS script. |
|
3.
|
Script writes End Run event to NAS network root folder in \gls_events . |
|
|
2
|
|
1.
|
Timer-based daemon on the LIMS server wakes up and looks for events. |
|
2.
|
Daemon discovers End Run event and processes it. |
|
3.
|
Daemon uses the supplied process run directory to locate the run folder on the NAS. |
|
4.
|
Daemon parses key information from the run folder including the Reagent Cartridge ID. |
|
5.
|
Daemon uses LIMS REST API to do the following: |
|
–
|
Populate step UDFs: Finish Date, Run Type, Status, Flowcell ID, Experiment Name, Read 1 Cycles, Index 1 Read Cycles, Index 2 Read Cycles, Read 2 Cycles, Output Folder, Run ID, Reagent Cartridge ID, PR2 Bottle ID, Chemistry, Workflow |
|
–
|
Examine list of files to collect, and attach any that are available: |
|
–
|
RunInfo.xml, RunParameters.xml, Link to Run Folder.html |
|
–
|
Run statistics are parsed from several binary InterOp files and stored (visible in the NextSeq run). |
|
–
|
Illumina Run Report invoked, generated, and attached. |
|
