The Illumina Preset Protocols (IPP) v2.7 support the integration of Clarity LIMS with established lab protocols.
The integration provides preconfigured workflows that map to lab protocols and steps, and support Illumina library prep kits, reagent kits, assays, and instruments.
This guide provides instructions and describes the components installed in the default configuration of IPP.
Installation Components
IPP Integration v2.7 is distributed as the BaseSpaceLIMS-Illumina-Preset-Protocols RPM package. The RPM package installs the following components:
The illumina-preset-protocols-installer.sh script for configuration slices.
Templates for the following uses:
Sample sheet generation
Sample placement pattern
Covid testing setup and reporting
Illumina Genomics Architecture (IGA)
Automation scripts, including scripts to support IGA and Clarity LIMS Product Analytics (CLPA) automation.
IPP Integration v2.7 contains workflows that are used to integrate the following instruments:
iScan
iSeq
MiSeq
MiniSeq
NextSeq 500/550
NextSeq 1000/2000
NovaSeq 6000
NovaSeq 6000Dx
NovaSeq X Series
The following workflows are included in the integration:
iScan v1.0
iSeq 100 v1.0
Library Prep Validation v2.3.2
MiniSeq v1.0
MiSeq Sequencing v3.2
NextSeq 500/550 Sequencing v1.1
NovaSeq 6000 v3.8
NextSeq 1000/2000 Sequencing v2.3
NovaSeqDx v1.2
NovaSeq X Series Sequencing v1.1
These workflows require ClarityLIMS-NGS-Package v5.24.0 or later so that the Template File Generator tool can be used.
Protocols and Configuration Slices
IPP Integration v2.7 provides protocols that contain configuration slices. These configuration slices are used to install other workflows and protocols.
QC_Protocols
QC_Protocols configuration component contains the qc-protocols base slice. This configuration does not contain any workflows, but it does provide the following protocols that are used by other workflows:
DNA Initial QC
Library Validation QC
RNA Initial QC
The following table shows the components that are installed with the QC_Protocols configuration.
Illumina Stranded Total RNA Prep Ligation with Ribo-Zero Plus v1.0
TruSeq Small RNA v1.0.8
TruSeq Stranded mRNA v2.1.8
Targeted_Amplicon_Protocols
TruSeq Custom Amplicon v1.0.8
Targeted_Enrichment_Protocols
Illumina DNA Prep with Enrichment (S) Tagmentation v1.1
Illumina RNA Prep with Enrichment (L) Tagmentation v1.0
Nextera Rapid Capture Custom Enrichment v2.0.9
TruSeq DNA Exome v2.0.8
TruSeq RNA
TruSeq RNA Access v2.0.8
TruSeq RNA Exome v1.0.5
TruSight_Oncology_Protocols
TruSight Oncology 500 ctDNA v1.1
TruSight Oncology 500 HT v1.1
TruSight Oncology 500 v1.1
TruSight Tumor 170 v2.0.8
IPP Integration v2.7 Package Installation
The BaseSpaceLIMS-Ilumina-Preset-Protocols RPM package provides instructions for locating and running the /opt/gls/clarity/config/illumina-preset-protocols-installer.sh bash script that launches the IPP configuration installer.
The RPM package automatically installs template files that are used with Template File Generator (TFG) and Sample Placement Helper. These template files are accessible after the applicable configuration is installed. The files are installed at the following locations:
The RPM package automatically installs the CLPA automation that is used for the CLPA integration. This automation is installed at the following location:
If this is a new Clarity LIMS installation, you must install the QC_Protocols before the preconfigured workflows. The base configuration is included in the standard installation process.
After you have selected a workflow, the installer validates the import of that workflow and provides Warning/Error details in STDOUT. This process allows you to proceed with the import or cancel it.
Prerequisites
Before installing the RPM package, make sure that the following software is installed:
Clarity LIMS v6.2 or later
NGS-Package v5.24 or later
SecretUtil v1.2. For more information, refer to Guide to Secret Management in the Clarity LIMS (Clarity & LabLink Reference Guide) documentation.
RPM Installation
On the server used for the IPP RPM installation, log in as the root user.
Use the following yum command to install the RPM:
The --enablerepo in the command line must be included to enable the repo. The Illumina Support team provides the repo file and the appropriate name to use.
yum install BaseSpaceLIMS-Illumina-Preset-Protocols --enablerepo=<< repo name info from support >>
When prompted to proceed with the RPM package installation, enter y to confirm.
Run the installer with the list operation for a list of all configuration installation options in a two-column format. The first column shows the IPP workflow identifier (or Id) that the installer uses when running the install operation. The second column shows the name of the configuration associated with the identifier.
As the glsjboss user, run the following command to view the list of IPP workflows:
/opt/gls/clarity/config/illumina-preset-protocols-installer.sh -o list
Install Operation
Use the install operation to install the configuration slices. Specify both the name of the parent item and the name of the configuration slice, separated by a period, as follows:
The all operation is a special option that is available at the top level and parent item level.
At the top level, use the operation to install every configuration package from IPP Integration v2.7. To use the all operation at this level, run the following command:
bash /opt/gls/clarity/config/illumina-preset-protocols-installer.sh -o install all
At the parent item level, use the operation to install the workflows associated with a specific parent item. For example, run the following command to install the workflows associated with the AmpliSeq_for_Illumina_Protocols parent item:
ℹ️ There is no all option available for QC_Protocols and Targeted_Amplicon_Protocols as they each contain only one configuration slice. Including all in the install command for these items generates an error.
Headless Mode
Headless mode allows the install operation to complete without prompting for input. Use this mode if you want to automate the installation. When running the installation in headless mode, the process still runs through the validation phase before importing the configuration. However, if a conflict is found, the configuration causing the conflict is skipped automatically.
Installation Validation
The IPP installer validates the configuration import. If conflicts are found during the validation, a warning message displays. This message provides the following options:
f/Import anyway
s/Skip this workflow
a/Abort
The f/Import anyway option runs the import command of the config slicer tool. It also allows the tool to handle conflicts. This option does not run the config slicer tool in importAndOverwrite mode.
The s/Skip this workflow option does not import workflows where conflicts were found, but continues to import the other selected slices.
The a/Abort option aborts all import operations. The conflicts found are captured in the log files and can be reviewed.
Track and Log the Installation
The IPP installer tracks the installation process in the installhistory table and generates log files that can be reviewed after the installation is complete.
Viewing the installhistory Table
After installation is complete, a record is stored in the installhistory table in the database.
To view the installation record, use the following command:
If a configuration slice is installed multiple times, there are multiple entries in the record. This scenario can happen during an upgrade or if there are attempts to resolve conflicts during installation. The log shows the following information for each slice:
Product — The name of the slice (e.g., IPP - LIMS 5 - TruSight_Oncology_Protocols.TruSight-Oncology-500-HT-v1.0).
Version — The version of the configuration slice that was installed (e.g., 2.0.0.25).
InstallDate — The time stamp for when the slice was installed. The date displays first (in YYYY-MM-DD format), followed by the time (in HH:MM:SS format)
Viewing the Log Files
After the configuration package is installed, the following log files are available:
ipp-installer.log
configslicer.log
omxprops.log
The ipp-installer.log file captures the output of the IPP installer tool. The name and location of this file can be changed with the command line options described previously. The default location is as follows:
The configslicer.log and omxprops.log files are raw outputs from their respective tools. These files contain more detail than the ipp-installer.log file. For example, if a conflict is identified in the ipp-installer.log file, the configslicer.log file shows the specific entry causing the conflict. Some workflow selections, such as the MiSeq and NextSeq integration workflows, import database properties in addition to a configuration slice.
By default, only the ipp-installer.log file is generated in the following directory:
When the -l operation is specified during installation, all three log files are available in the current working directory.
IPP Integration v2.7 Workflow Upgrades
There are some expected conflicts when upgrading from IPP Integration v2.6.
In IPP v2.7, new flow cell types are supported that cause a conflict with the NovaSeq X Flowcell Type derived sample custom field. The following workflows can be affected and lead to conflicts when upgrading from IPP v2.6 to v2.7:
Illumina DNA Prep (M) Tagmentation v1.0.6
Nextera Mate Pair v1.0.7
Nextera XT DNA v2.0.7
TruSeq DNA PCR-Free v2.0.7
TruSeq Nano DNA v1.0.7
Library Prep Validation v2.3.1
TruSeq ChIP-Seq v1.0.7
TruSeq Methyl Capture EPIC v2.0.8
TruSeq Small RNA v1.0.7
TruSeq Stranded mRNA v2.1.7
TruSeq Custom Amplicon v1.0.7
Nextera Rapid Capture Custom Enrichment v2.0.8
TruSeq DNA Exome v2.0.7
TruSeq RNA Exome v1.0.5
TruSeq RNA Access v2.0.7
TruSight Tumor 170 v2.0.7
To resolve these conflicts, perform the following actions:
When the expected conflicts are encountered during the IPP workflow installation, enter f to import the workflow when prompted. An example of the prompt is as follows.
Conflicts were detected between this slice and the existing configuration in the LIMS!
What would you like to do with this slice? [(f|Import anyway)|(s|Skip this workflow)|(a|Abort)]:
After the workflow is installed, resolve the conflicts as follows.
From Configuration, select the Custom Fields tab.
From the Custom Fields tab, select the Global Fields tab.
Search for NovaSeq X Flowcell Type.
For Additional Options, update the Dropdown Items with the following options:
IGA workflows require additional installation steps. For assistance, contact Illumina Technical Support. Note also that Illumina Genomics Architecture - NovaSeq Sequencing v2.1 workflow is not the same workflow as NovaSeq 6000 v3.8.
