iSeq 100 Loading
Genomics Platform
Last Updated: 11/13/2023
A step-by-step guide�
Preparing & Unboxing Your iSeq
Preparing & Unboxing Your iSeq
Preparing & Unboxing Your iSeq
iSeq Anatomy
iSeq 100 Sequencer
Flow cell
Cartridge
iSeq Intro
iSeq Chemistry
Patterned Flow Cell
Before Loading...
Flow cell
Cartridge
Loading Guide Sheet for iSeq
How to Make a Sample Sheet for iSeq
Sample Sheet Breakdown
Header section is mandatory but filling in each field is optional.
KEEP!
Manifest section is not necessary. Could delete these lines off sample sheet.
KEEP!
Reads section is mandatory
Sample Sheet Breakdown (cont.)
Setting section is not necessary.
Data section is mandatory. However, not all fields are necessary. Be sure to fill out: Sample_ID, Sample_Name, Description, I7_Index_ID, Index, I5_Index_ID, index2
Pre-run checks will take ~15 minutes. Run starts automatically after the checks are completed.
iSeq Settings
iSeq settings and options
About
System Check:
Remember to put in system test cartridge + flow cell.
System Settings
Using Express Settings will use Local Run Manager to create runs. (Different from training)
To set up runs like we do in training, please select Set up Manually and in the Local Run Manager setting choose Use Manual Mode. (Next Slide)
Set output folder to write to remote server or locally. Data is saved in two places, one copy in the output folder (defined here) and another in the local drive.
Local copy on computer. Our sequencer also writes to our remote server.
Process Management:
Can delete runs here if your computer is running out of disk space
iSeq Troubleshooting
Looking for top unknowns and re-demultiplexing
Basespace Troubleshooting → Looking for undetermined reads
>Select Analysis
OR
>Go to Projects > Select appropriate Project > FASTQ Generation….
Looking at top unknowns
Open in text editor:
Re-demultiplex with updated Sample Sheet
Examples of iSeq runs on BaseSpace
Example of a Run with Fluidic Issue (link)
Normal
Abnormal spikes
Normal
Abnormal Basecalling
PhiX Alignment and Error Rate (usually <2%)
In this case, the sequencer had a fluidic issue at cycle 105. The first 105 cycles have normal intensity and % base readouts, then becomes sporadic. Error rate on PhiX control is also a good indication of machine issues as error rate should be well under 2%.
Example of a Underclustered Run
% Occupied: 40-70%
Example a Overclustered Run
% Occupied: 97.1-98.2
Questions?
Illumina Tech Support
CZB SF Sequencing Platform