arrow-left

All pages
gitbookPowered by GitBook
1 of 10

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

MiSeq i100 (On-Prem)

The documents in this section support the Illumina MiSeq i100 Series integrations with on-premise Clarity LIMS setup.

MiSeq i100 On-Prem v1.1.0

The integration includes the following:

  • Preconfigured MiSeq i100 Series On-Prem Sequencing v2.0 workflow that maps to lab protocols and instrument runs.

  • Preconfigured protocols:

    • Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v2.0)

    • Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v2.0)

    • Dilute and Denature (MiSeq i100 Series On-Prem Sequencing v2.0)

    • Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v2.0)

    • AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v2.0)

    • AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v2.0)

  • Automatic validation of run setup information before sample sheet generation and planned run creation.

  • Automated planned run creation on MiSeq i100 Series instrument via Illumina Run Manager. The planned run created will be retrieved by MiSeq i100 Series Control Software and used to start a sequencing run.

  • Automated tracking of the MiSeq i100 Series sequencing run status and parsing of run metrics.

  • Automated tracking of the MiSeq i100 Series analysis run status, result summary and demultiplexing result files.

  • Support for configuration of secondary analysis with library prep kit (LPK) and index adapter kit (IAK) via Analysis Configuration Template for the planned run. The analysis is performed by DRAGEN on-premise.

  • (Optional) Preconfigured Library Prep Validation v2.3.6 workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep workflow required to produce libraries tagged with index sequences. At the end of the step, these libraries are routed to MiSeq i100 Series On-Prem Sequencing v2.0 workflow.

MiSeq i100 On-Prem v1.0.0

The integration includes the following:

  • Preconfigured MiSeq i100 Series On-Prem Sequencing v1.0 workflow that maps to lab protocols and instrument runs.

  • Preconfigured protocols:

Release Notes

Release Date: November 2025

These Release Notes describe the key changes to software components for the Clarity LIMS MiSeq i100 Series On Premise Integration Package version 1.1.0.

hashtag
Compatibility

Refer to under Instruments & Integrations.

Release Notes

Last Updated: December 2024

Release Date: December 2024

These Release Notes describe the key changes to software components for the Clarity LIMS MiSeq i100 Series On Premise Integration Package version 1.0.0.

hashtag
Compatibility

Refer to under Instruments & Integrations.

Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)
  • Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

  • Dilute and Denature (MiSeq i100 Series On-Prem Sequencing v1.0)

  • Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

  • AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)

  • AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

  • Automatic validation of run setup information before sample sheet generation and planned run creation.

  • Automated planned run creation on MiSeq i100 Series instrument via Illumina Run Manager. The planned run created will be retrieved by MiSeq i100 Series Control Software and used to start a sequencing run.

  • Automated tracking of the MiSeq i100 Series sequencing run status and parsing of run metrics.

  • Automated tracking of the MiSeq i100 Series analysis run status, result summary and demultiplexing result files.

  • Support for configuration of secondary analysis with library prep kit (LPK) and index adapter kit (IAK) via Analysis Configuration Template for the planned run. The analysis is performed by DRAGEN on-premise.

  • (Optional) Preconfigured Library Prep Validation v2.3.5 workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep workflow required to produce libraries tagged with index sequences. At the end of the step, these libraries are routed to MiSeq i100 Series On-Prem Sequencing v1.0 workflow.

  • hashtag
    New Features
    • Create planned runs without analysis (Generate BCLs only).

    • Added support for MiSeq i100 50M and 100M flow cell types.

    • Added support for MiSeq i100 2 x 500 bp kit for 25M flow cell.

    • Sequencing run metrics are now displayed per-run and per-lane in the AUTOMATED - Sequencing Run step.

    hashtag
    Enhancement

    • Both indexed and pooled libraries are now supported as input for the MiSeq i100 v2.0 sequencing protocol.

    • The Make Bulk Pool and Calculate Volumes automation scripts have been updated to align with the latest MiSeq i100 Series System Sequencing Protocolarrow-up-right

    • When configurations of existing planned runs are updated, apply updates to existing planned runs instead of creating new planned runs with updated configurations.

    hashtag
    Known Limitations

    • Tracks only the analysis configured with the planned run. Does not track analysis requeue or analysis triggered externally with the same planned run.

    • The integration does not support pools with samples assigned with Analysis Configuration Templates from different instruments.

    hashtag
    Known Issues

    • On the Make Bulk Pool step, the log displays a warning when the Calculate Volume automation is triggered and at least one pool consists of multiple inputs. This issue is caused by the output custom field being reset multiple times at the end of the automation. This issue does not affect the Calculate Volume automation functionality.

    • Planned runs configured with no analysis will be deleted from MiSeq i100 Series Control Software v1.1.0 upon restarting of the Control Software or power cycling of the instrument. Refer to MiSeq i100 Series Sequencing v2.0 Workflow User Interaction, Validation and Troubleshooting for details.

    Compatibility
    hashtag
    New Features

    Features provided with this release of the integration package are as follows.

    • Provides integration between the MiSeq i100 Series instrument and on-premise Clarity LIMS.

    • Supports creation of planned run with secondary analysis configuration and generation of v2 sample sheet via Illumina Run Manager on instrument.

    • Supports automated tracking of the sequencing run and parsing of run metrics for on-premise Clarity LIMS.

    • Supports automated tracking of local analysis for analysis status and demultiplexing results.

    • New MiSeq i100 Series On-Prem Sequencing v1.0 workflow available from Illumina Preset Protocols v2.10.

    hashtag
    Known Limitations

    • Tracks only the analysis configured with the planned run. Does not track analysis requeue or analysis triggered externally with the same planned run.

    • The Assign Analysis Configuration Template step does not support pooled libraries.

    • The integration does not support --bcl-sampleproject-subdirectories option of BCL Convert.

    • The integration does not support pools with samples assigned with Analysis Configuration Templates from different instruments.

    hashtag
    Known Issues

    • On the Make Bulk Pool step, the log displays a warning when the Calculate Volume automation is triggered and at least one pool consists of multiple inputs. This issue is caused by the output custom field being reset multiple times at the end of the automation. This issue does not affect the Calculate Volume automation functionality.

    Compatibility

    Installation

    The Illumina MiSeq i100 Series On-Prem Integration Package v1.0.0 supports the integration of Clarity LIMS to MiSeq i100 Series instruments that are on-premise via Illumina Run Manager.

    hashtag
    Prerequisites

    chevron-rightPrerequisite 1: Clarity LIMS v6.2 or later with SecretUtil v1.5.0.12 or laterhashtag

    Installation

    The Illumina MiSeq i100 Series On-Prem Integration Package v1.1.0 supports the integration of Clarity LIMS to MiSeq i100 Series instruments that are on-premise via Illumina Run Manager.

    hashtag
    Prerequisites

    chevron-rightPrerequisite 1: Clarity LIMS v6.2 or later with SecretUtil v1.5.0.12 or laterhashtag

    The MiSeq i100 Series On-Prem integration v1.0 relies on secret management util version 1.5.0.12 or later to store the access token to Illumina Run Manager and its related secrets.

    ℹ If using Vault, ensure that the appropriate ACL policies are added. Refer to Authentication ACL Policies under On-Premise Deployments > Configure Your HashiCorp Vault in Clarity LIMS (Clarity & LabLink Reference Guide) documentation.

    chevron-rightPrerequisite 2: Illumina Run Manager Integration Service v1.0.0 or laterhashtag

    Illumina Run Manager Integration Service v1.0 or later is required for this integration.

    chevron-rightPrerequisite 3: Illumina Preset Protocols (IPP) v2.10 with NGS Commons Package v5.25.0 or laterhashtag

    Illumina Preset Protocols (IPP) v2.10 package contains the workflow configuration and template files required to enable the MiSeq i100 Series On-Prem workflow to run properly.

    Install the workflow configurations below on the same server on which you intend to install the MiSeq i100 Series On-Prem integration.

    • MiSeq i100 Series On-Prem Sequencing v1.0 workflow

    • Library Prep Validation v2.3.5 workflow (optional, but recommended)

    NGS Commons Package v5.25.0 or later is required for Step Automation to work properly.

    hashtag
    Installation Steps

    Steps:

    1. Install / Upgrade Clarity LIMS

    2. Install and Configure Illumina Run Manager Integration Service

    3. Install MiSeq i100 Series On-Prem Integration RPM

    4. Install Illumina Preset Protocols (IPP) v2.10 RPM and Import Required IPP Workflows.

    hashtag
    Step 1: Install / Upgrade Clarity LIMS

    Install or upgrade to Clarity LIMS v6.2 or later. If you are using an older version of Clarity LIMS, please contact Illumina Support ([email protected]) to schedule for upgrade.

    hashtag
    Step 2: Install and Configure Illumina Run Manager Integration Service

    Install and configure Illumina Run Manager Integration Service v1.0, please refer to Illumina Run Manager v1.0.0 Installation for details.

    hashtag
    Step 3: Install MiSeq i100 Series On-Prem Integration RPM

    Install ClarityLIMS-MiSeqi100Series-OnPremise RPM using yum or your preferred package manager.

    Example with YUM:

    Example with RPM:

    hashtag
    Step 4: Install Illumina Preset Protocols (IPP) v2.10 and Import Required IPP Workflows

    Install BaseSpaceLIMS-Illumina-Preset-Protocols RPM using yum or your preferred package manager.

    Example with YUM:

    Example with RPM:

    Upon successful installation of IPP v2.10.0, install the following workflow configurations:

    • MiSeq i100 Series On-Prem Sequencing v1.0 workflow

    • (Optional) Library Prep Validation v2.3.5 workflow

    For detailed options and steps on how to install IPP workflows and protocols, Installer Parameters and Operations section of Illumina Preset Protocols v2.10 Installation and User Configuration.

    The MiSeq i100 Series On-Prem integration v1.1.0 relies on secret management util version 1.5.0.12 or later to store the access token to Illumina Run Manager and its related secrets.

    ℹ If using Vault, ensure that the appropriate ACL policies are added. Refer to Authentication ACL Policies under On-Premise Deployments > Configure Your HashiCorp Vault in Clarity LIMS (Clarity & LabLink Reference Guide) documentation.

    chevron-rightPrerequisite 2: Illumina Run Manager Integration Service v1.1.0 or laterhashtag

    Illumina Run Manager Integration Service v1.1.0 or later is required for this integration.

    chevron-rightPrerequisite 3: Illumina Preset Protocols (IPP) v2.11 with NGS Commons Package v5.25 or laterhashtag

    Illumina Preset Protocols (IPP) v2.11 package contains the workflow configuration and template files required to enable the MiSeq i100 Series On-Prem workflow to run properly.

    Install the workflow configurations below on the same server on which you intend to install the MiSeq i100 Series On-Prem integration.

    • MiSeq i100 Series Sequencing v2.0 workflow

    • Library Prep Validation v2.3.6 workflow (optional, but recommended)

    NGS Commons Package v5.25 or later is required for Step Automation to work properly.

    hashtag
    Installation Steps

    Steps:

    1. Install / Upgrade Clarity LIMS

    2. Install and Configure Illumina Run Manager Integration Service

    3. Install MiSeq i100 Series On-Prem Integration RPM

    4. Install Illumina Preset Protocols (IPP) v2.11 RPM and Import Required IPP Workflows.

    hashtag
    Step 1: Install / Upgrade Clarity LIMS

    Install or upgrade to Clarity LIMS v6.2 or later. If you are using an older version of Clarity LIMS, please contact Illumina Support ([email protected]) to schedule for upgrade.

    hashtag
    Step 2: Install Illumina Run Manager Integration Service

    Refer to Illumina Run Manager v1.1.0 Installation for details.

    hashtag
    Step 3: Install MiSeq i100 Series On-Prem Integration RPM

    Install ClarityLIMS-MiSeqi100Series-OnPremise RPM using yum or your preferred package manager.

    Example with YUM:

    Example with RPM:

    hashtag
    Step 4: Install Illumina Preset Protocols (IPP) v2.11 and Import Required IPP Workflows

    Install BaseSpaceLIMS-Illumina-Preset-Protocols RPM using yum or your preferred package manager.

    Example with YUM:

    Example with RPM:

    Upon successful installation of IPP v2.11, install the following workflow configurations:

    • MiSeq i100 Series Sequencing v2.0 workflow

    • (Optional) Library Prep Validation v2.3.6 workflow

    For detailed options and steps on how to install IPP workflows and protocols, Installer Parameters and Operations section of Illumina Preset Protocols v2.11 Installation and User Configuration.

    yum install ClarityLIMS-MiSeqi100Series-OnPremise
    rpm -i ClarityLIMS-MiSeqi100Series-OnPremise-{version}.86_64.rpm
    yum install BaseSpaceLIMS-Illumina-Preset-Protocols
    rpm -i BaseSpaceLIMS-Illumina-Preset-Protocols-{version}.86_64.rpm
    yum install ClarityLIMS-MiSeqi100Series-OnPremise
    rpm -i ClarityLIMS-MiSeqi100Series-OnPremise-{version}.86_64.rpm
    yum install BaseSpaceLIMS-Illumina-Preset-Protocols
    rpm -i BaseSpaceLIMS-Illumina-Preset-Protocols-{version}.86_64.rpm

    Configuration

    The Illumina MiSeq i100 Series On-Prem Integration Package v1.1.0 supports the integration of Clarity LIMS to Illumina MiSeq i100 Series sequencer connected to the Illumina Run Manager platform on premise.

    For instructions on validating and troubleshooting the MiSeq i100 Sequencing v2.0 workflow for the integration, refer to MiSeq i100 Series Sequencing v2.0 Workflow User Interaction, Validation and Troubleshooting.

    triangle-exclamation

    The configuration provided in this integration has been established to support MiSeq i100 Series lab processes. Any configuration changes to protocols or workflows (including renaming protocols, steps, and fields) could break the integration.

    hashtag
    Prerequisites and Assumptions

    hashtag
    Analysis Configuration Template

    The MiSeq i100 Series Sequencing v2.0 workflow uses analysis configuration templates (ACT) to configure secondary analysis for the planned runs. It is assumed that the required ACTs for your run has been pre-created using Illumina Run Manager UI. Please make sure that the index adapter kit (label group on Clarity) selected in the ACT has already been created on Clarity LIMS. The same label group shall be used in the library preparation step. Names of ACT must be unique. Please refer to the for details on creating ACT on Illumina Run Manager User Interface (UI).

    triangle-exclamation

    Clarity LIMS trims all leading and trailing spaces from the ACT names and ACTs created in Illumina Run Manager UI with names containing leading and/or trailing spaces may not be recognized properly on Clarity. Please ensure that the ACT do not have leading and/or trailing spaces.

    hashtag
    Samples

    It is assumed that samples that enter the MiSeq i100 Series Sequencing v2.0 workflow have gone through library preparation and quantification processes before they are assigned to the workflow:

    • Samples have been accessioned into Clarity LIMS.

    • Sample and library names must contain only alphanumeric, dash, or underscore characters.

    • Samples have been run through QC and library prep.

    hashtag
    Workflows, Protocols, and Steps

    The MiSeq i100 Series On-Premise Integration Package v1.1.0 includes the following workflows:

    • Library Prep Validation v2.3.6 (optional, but recommended for validation purposes)

    The following describes the protocols and steps included in these workflows.

    hashtag
    Library Prep Validation v2.3.6 Workflow

    chevron-rightProtocol 1: Library Prep Validation v2.3.6hashtag

    Purpose:

    • Included for validation purposes only, this protocol models the library preparation steps required to advance samples to the MiSeq i100 Series Sequencing v2.0 workflow. For details, refer to .

      ℹ This workflow can be replaced by other custom library preparation workflows. Routing of libraries from the custom workflow to the MiSeq i100 Series Sequencing protocol can be enabled in the master step with the

    hashtag
    MiSeq i100 Series Sequencing v2.0 Workflow

    chevron-rightProtocol 1: MiSeq i100 Series Sequencing v2.0hashtag

    Purpose:

    • This protocol models the lab processes of run setup for starting a MiSeq i100 Series sequencing and secondary analysis run on premise.

    Steps:

    hashtag
    Validation Workflow

    The Library Prep Validation v2.3.6 workflow allows for validation of the system after installation is complete. This workflow can be replaced by other custom library preparation workflows.

    Configure a custom library preparation workflow as follows.

    1. Select Configuration, then select Lab Work.

    2. Add a Routing Script automation to the last Master Step of the library preparation workflow.

    3. Select Configuration, then select Automation.

    hashtag
    How the Integration Works

    The following information summarizes how the MiSeq i100 Series On-Premise Integration works.

    • After the 'Validate Run Setup and Create Planned Run' automation is triggered on the Load to Dry Cartridge step, the run parameters entered in the Run Details screen and the sample informations are sent to Illumina Run Manager. Illumina Run Manager validates the run and analysis configuration before the planned run is created, the automation also generates the sample sheet and attaches it to the step. In the event of incomplete information or misconfiguration on the planned run, an error will be displayed on the automation banner and details of the error will be logged in the automation log file.

    • When the sequencing run starts on the instrument, the MiSeq i100 Series Control Software notifies the Illumina Run Manager integration. The events are processed and the integration service retrieves the run information from MiSeq i100 Illumina Run Manager. This information is used to populate the custom fields in the AUTOMATED - Sequencing Run step.

    triangle-exclamation

    If a planned run with the same sample name and project name (case-insensitive) has been created previously in Illumina Run Manager, the sample sheet generated from the 'Validate Run Setup and Create Planned Run' automation can reflect the original case of the previous sample name. This can cause validation errors for analysis configurations with sample-level settings. To resolve this issue, change the sample name or the project name on Clarity LIMS and run the automation again.

    hashtag
    Start a Sequencing Run on MiSeq i100 Series Instrument

    To start a planned run, refer to information on .

    hashtag
    Enabling Planned Run Generation for Samples Having Duplicate Name with Different Indexes

    The library preparation workflow of the samples must be before routing the samples through the library preparation workflow.

    hashtag
    Rules and Constraints

    • The workflow configuration contains several validation checks. To make sure that the calculations work properly, it is important that you do not disable any of this validation logic. The validation checks determine the following information:

      • Which samples, and how many, can enter each step together.

      • Which samples, and how many, can be pooled together.

    Samples have the Molarity (nM) global field set to a valid value (required for the 'Calculate Volumes' automation in the Make Bulk Pool step).
    available in the NGS package.

    âš  The label group (index adapter kit) used for library preparation must be the same as the index adapter kit specified in the ACT that is being used. For more information, refer to MiSeq i100 Series Sequencing v2.0 Workflow User Interaction, Validation and Troubleshooting.

  • The protocol contains a single step - Library Prep Validation v2.3.6. After this step, a routing script sends the samples to the first step of the MiSeq i100 Series Sequencing v2.0 workflow.

  • Steps:

    1. Library Prep Validation v2.3.6

    Assign Analysis Configuration Template (MiSeq i100 Series Sequencing v2.0)

    • The secondary analysis of samples is configured using the ACT.

    • The labels applied to the samples are validated against the selected ACT to ensure that samples use valid labels.

  • Make Bulk Pool (MiSeq i100 Series Sequencing v2.0)

    • Samples are pooled and resuspension buffers and reagents are added with the help of the 'Calculate Volumes' automation.

    • ACT of pooled samples are validated with Validate Analysis Configurations automation to ensure that the secondary analysis configurations remain valid after pooling.

  • Load To Dry Cartridge (MiSeq i100 Series Sequencing v2.0)

    • The library pools from step 2 are now ready to be loaded to the MiSeq i100 Series dry cartridge.

    • Run and analysis information is validated.

    • Samplesheet is generated and planned run is created on MiSeq i100 Illumina Run Manager.

  • AUTOMATED - Sequencing Run (MiSeq i100 Series Sequencing v2.0)

    • This is a fully-automated step that is started and completed automatically once the sequencing run is started and completed on the instrument side.

    • All the sequencing run metadata e.g. run configuration, primary run metrics etc. are recorded automatically.

  • AUTOMATED - Analysis Run (MiSeq i100 Series Sequencing v2.0)

    • This is a fully-automated step that is started and completed automatically once the analysis run is started and completed on DRAGEN on premise.

    • All the analysis run metadata e.g. status and demultiplexing result files are recorded automatically.

  • Create a new Routing Script automation and update it as follows.

    1. For Channel Name, enter limsserver.

    2. For Command Line, enter the following script:

    3. For Automation Use, select the custom library preparation workflow.

    Other run events follow the same information flow. When sequencing is complete, the control software uploads the sequencing run data (primary metrics). Then, Illumina Run Manager integration retrieves the primary metrics and uses them to populate the fields in the Sample Details table (e.g., % Error Rate R1). The custom fields (e.g., Run Status, Current Read, and so on) on the AUTOMATED - Sequencing Run step are updated using the run related information. If the sequencing run is successfully completed, the step automatically completes.
  • The integration tracks the analysis events and results in the AUTOMATED - Analysis Run step. The secondary analysis results are in the external storage configured in Illumina Run Manager. The external storage information is found in the External Storage for Analysis Results configuration settings in Illumina Run Manager.

  • For all submitted samples that require analysis, they must have an associated secondary analysis that is configured using the analysis configuration template (ACT). The ACT must be configured on MiSeq i100 Illumina Run Manager before starting the Assign Analysis Configuration Template step. The ACT names must be unique.

  • Assign Analysis Configuration Template step does not support pool library as input.

  • The dry cartridge barcode must be unique. There must not be multiple dry cartridge containers with the same name in the Clarity LIMS system.

  • Reagent labels, or indexes, must be unique.

  • One library pool can only contain one library or control with no label/index.

  • The AUTOMATED - Sequencing Run and AUTOMATED - Analysis Run steps must not be manually started or completed. These steps are fully automated and the integration service does not update samples correctly if they have been manually started.

  • For the automated run to start successfully, you must click 'Validate Run Setup and Create Planned Run' in the Load to Dry Cartridge step and the automation must be ran successfully.

  • MiSeq i100 Sequencing 2.0 Workflow User Interaction, Validation and Troubleshooting
    MiSeq i100 Series Sequencing v2.0
    MiSeq i100 Series Sequencing v2.0 Workflow User Interaction, Validation and Troubleshooting
    starting a planned run in the Illumina support site.arrow-up-right
    configured to ensure unique derived sample names
    routing script
    bash -l -c "/opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -u {username} -p {password} -i {stepURI:v2} -l {compoundOutputFileLuid0} script:changeWorkflow \
    \
    --FIELD_NAME 'Sequencing Instrument' \
    --FIELD_VALUE 'MiSeq i100 Series' \
    --WORKFLOW 'MiSeq i100 Series Sequencing v2.0' \
    --STEP 'Assign Analysis Configuration Template (MiSeq i100 Series Sequencing v2.0)' \
    --INPUTS_OR_OUTPUTS 'OUTPUTS'"

    User Interaction, Validation and Troubleshooting

    This section explains how to validate the installation of the Illumina MiSeq i100 Series On-Prem Integration Package v1.0.0.

    The validation process involves the following actions:

    • Running samples through the Library Prep Validation v2.3.5 workflow.

      • The workflow contains a single-step protocol that models the library prep required to produce libraries tagged with index sequences. At the end of the step, these libraries are routed to MiSeq i100 Series On-Prem Sequencing v1.0 workflow.

    • Running libraries through the MiSeq i100 Series On-Prem Sequencing v1.0 workflow validates the following items:

      • Successful sequential step advancement of samples through the steps of the workflow.

        • Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)

    The validation steps assume the following conditions have been met:

    • Integration package has been successfully installed. Refer to .

    • Analysis configuration templates (ACTs) are created in Illumina Run Manager for your run.

    • Index Adapter Kit used in selected ACT is created as label group in Clarity LIMS.

      ℹ For more information on creating a reagent label group, refer to Add and Configure Labels and Label Groups in the

    hashtag
    Analysis Configuration Template Creation in Illumina Run Manager

    MiSeq i100 Series On-Prem Sequencing v1.0 workflow requires Analysis Configuration Templates (ACTs) for configuring secondary analysis.

    Create these ACTs in Illumina Run Manager (IRM) UI:

    1. Select Analysis Configuration Templates from the dropdown list of the IRM UI menu icon

    2. Select Add analysis template to create and add a new ACT.

    3. Fill up details of the ACT and select Save.

    For details, refer to the Illumina Run Manager help documentation on Illumina support site.

    hashtag
    Activate Workflow, Create Project, Add and Assign Samples

    The following steps set up Clarity LIMS in preparation for running samples through the Library Prep Validation v2.3.5 and MiSeq i100 Series On-Prem Sequencing v1.0 workflows.

    1. On the Configuration tab, under Workflows, activate both the Library Prep Validation v2.3.5 and MiSeq i100 Series On-Prem Sequencing v1.0 workflows.

    2. On the Projects and Samples screen, create a project and add samples to it.

      âš  Sample and library names must use only alphanumeric, dash, or underscore characters. Invalid characters can cause a sample sheet validation failure in the Load to Dry Cartridge step.

    hashtag
    Library Prep Protocol

    This single-step protocol models the library prep required to produce libraries tagged with index sequences that are ready for the MiSeq i100 Series On-Prem Sequencing v1.0 workflow.

    Follow the steps in to run the Library Prep Validation workflow with the following:

    • Label Group = same as the Index Adapter Kit selected in the ACT that is being used

    • Sequencing Instrument = MiSeq i100 Series On-Prem

    On exit from the step, the Routing Script automation is triggered. This automation assigns samples to the first step of the MiSeq i100 Series On-Prem Sequencing v1.0 workflow, Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0).

    hashtag
    Protocol: MiSeq i100 Series On-Prem Sequencing v1.0

    The MiSeq i100 Series On-Prem Sequencing v1.0 protocol consists of the following steps:

    • Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)

    • Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

    • Load To Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

    hashtag
    Step 1: Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)

    1. In Lab View, locate the MiSeq i100 Series On-Prem Sequencing v1.0 protocol. The samples are queued for the Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    2. Add the samples to the Ice Bucket and start the step. The Validate Sample Names automation is triggered upon step started, and validates the sample names.

    3. Select the connected MiSeq i100 instrument to integrate with.

    hashtag
    Step 2: Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

    1. In Lab View, locate the MiSeq i100 Series On-Prem Sequencing v1.0 protocol. The samples are queued for the Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    2. Add the samples to the Ice Bucket and select View Ice Bucket.

    3. On the Ice Bucket screen, select Begin Work.

    1. On the Record Details screen, navigate to the Reagent Lot Tracking section to track the lot information used in the step.

      [Optional] Create a new lot. For more information, refer to Add and Configure Reagent Kits and Lots in the .

    2. In the Step Details area, complete the following fields:

    hashtag
    Step 4: Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

    1. In Lab View, locate the MiSeq i100 Series On-Prem Sequencing v1.0 protocol. The pool of samples are queued for the Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    2. Add the pool to the Ice Bucket and select View Ice Bucket.

      âš  Only single pool is allowed at this step.

    hashtag
    Step 5: AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    triangle-exclamation

    Do not add samples to the Ice Bucket or start or complete the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step. The integration does this automatically.

    User interaction is not required, but you can review the stages of the step in Clarity LIMS.

    hashtag
    Review Run Data

    Read summary metrics are recorded for the library pool. After the run is complete, open the step and review these metrics in the Step Details section and the Sample Details table.

    chevron-rightStep Details Sectionhashtag

    The following values populate the master step fields:

    • Run Name

    • Run Status

    chevron-rightSample Details Tablehashtag

    Summary metrics populate the following global custom fields:

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    hashtag
    Step 6: AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    triangle-exclamation

    Do not add samples to the Ice Bucket or start or complete the AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0) step. The integration does this automatically.

    User interaction is not required, but you can review the stages of the step in Clarity LIMS. If the run analysis tracking is successful, the integration completes the step automatically.

    hashtag
    Review Analysis Data

    After the analysis run is complete, open the step and review the following values in the Step Details section:

    • Analysis Status - Status of the analysis run

    • Analysis Result Location - Location of the secondary analysis data. This field is empty if transfer of secondary analysis data to an external location is disabled.

    • Log - Log message when integration handling the event from IRM

    File placeholder:

    • Demultiplexing results file - demultiplexing statistics for each sample

    circle-info

    Retrieve detailed analysis results from Illumina Run Manager.

    At this point, the entire MiSeq i100 Series On-Prem Integration workflow is fully validated.

    hashtag
    Troubleshooting

    If an automation trigger does not appear to run its corresponding scripts, refer to the Troubleshooting Automation section in the .

    hashtag
    Validate Analysis Configuration Automation Check Fails

    The Validate Analysis Configuration automation check is in the Make Bulk Pool (upon pooling) step. If a failure happens, an error message displays and the step can be aborted, or you might be prevented from continuing the step.

    This check can fail for the following reasons:

    • Pooled samples assigned with the same secondary analysis application must have the same analysis version (e.g. v3.8.4) and settings (e.g. Map/Align Output Format = CRAM).

      Resolve this error as follows.

    hashtag
    Error When Creating Planned Runs

    If you receive an error when creating a planned run, check the log message in the Load to Dry Cartridge step to identify the issue. If you cannot correct the issue, contact Illumina Support.

    Incompatible Analyses in a Planned Run

    Only compatible analysis versions should be combined in a single planned run. When incompatible analysis versions are combined, an error log message displays. An example of the error log message is shown below.

    To resolve this error, check the ACTs that were used for the run. Create a new planned run with ACTs that have the same analysis and analysis versions.

    hashtag
    Automated Step Does Not Start

    If the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step does not start, Clarity LIMS is likely not receiving sequencing run events from Illumina Run Manager correctly. Check for the following issues:

    • The instrument must be reflected as Connected and Active in the Illumina Run Manager Integration UI. Reconnect the instrument if the status reflects otherwise.

    • The container must be queued at the AUTOMATED - Sequencing Run step. It should not be in the ice bucket or in the previous step.

    If the issues remain, contact Illumina Support.

    hashtag
    Automated Step Starts, But Does Not Complete

    If the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step starts, but does not complete, do as follows.

    1. Log in to the default user account and search for the in progress step in Clarity LIMS using the container name as the search term.

    2. On the Record Details screen, the Sequencing Log multiline text field contains logging information.

      If unable to reach the Record Details screen, or if the Sequencing Log field does not contain enough information to resolve the issue, contact Illumina Support. Provide the relevant information from the troubleshooting steps already performed.

    Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

  • Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

  • AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)

  • AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

  • Automated creation of a planned run on Illumina Run Manager (IRM).

    • Automatic validation of run setup information before planned run creation.

    • Automated generation of sample sheet as part of the planned run creation.

  • Automated tracking of the MiSeq i100 Series sequencing run and parsing of run statistics from Illumina Run Manager into the LIMS.

  • Automated tracking of the MiSeq i100 Series analysis run and demultiplexing result files from Illumina Run Manager into the LIMS.

  • . For the adapter sequences for your library prep kits, refer to
    .
  • This same label group must be used in the Library Prep Validation v2.3.5 step or your custom library prep step.

  • Required DRAGEN analysis application is installed locally on instrument.

  • The MiSeq i100 Series instrument to be integration is connected successfully via Illumina Run Manager UI.

  • Assign the samples to the Library Prep Validation workflow.
    AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)
  • AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

  • On Record Details screen, select 1. Retrieve ACT List to retrieve the list of ACTs created on Illumina Run Manager.
  • Select the applicable ACT to assign to the samples. The samples must be indexed with the index adapter kit configured in the selected ACT.

  • [Optional] Select 2. Retrieve ACT Information to trigger the automation.

    The Retrieve ACT Information automation retrieves the details of the selected ACT. High level information e.g., Library Prep Kit, Index Adapter Kit, Reference Genome etc. are populated on the step fields. For more details, refer to the ACTMetadata.csv file in the file placeholder section.

  • Select Next Steps to assign the ACT to the samples.

    This action triggers the Validate Reagent Labels and Apply Selected ACT to Samples and Set Next Step automation. This automation

    • ensures every sample has Molarity (nM) UDF value greater than zero

    • validates that the indexes applied to the libraries are valid for the selected ACT

    • assigns all samples in this step to the selected ACT

  • Select Finish Step.

  • Create a pool of samples as follows.
    1. On the Pooling screen, create a pool by dragging samples into the Pool Creator.

    1. Enter a name for your pool or accept the default name (Pool #1).

    1. [Optional] If multiple pools are required, select the plus sign (+) next to Pool Creator to create a pool.

    ℹ Only a single pool is allowed in the Load to Dry Cartridge step for each run. Create multiple pools if required for subsequent runs.

    1. [Optional] To remove a pool, select the X in the top right corner of the pool.

  • Select Record Details to trigger the Validate Analysis Configurations automation.

    This automation performs the following checks on the analysis configuration for each pool:

    • Pooled samples are within the maximum configuration limit.

    • Pooled samples assigned with the same secondary analysis application must have the same analysis version (e.g. v3.8.4) and settings (e.g. Map/Align Output Format = CRAM).

  • [Optional] In the Sample Details table, select the pool next to the sample name to view details on the pool composition.

  • [Optional] % PhiX (100pM) Spike-In — The percentage of PhiX spike-in.
  • Final Loading Concentration (pM) — The final loading concentration of the pool in the flow cell.

  • Final Loading Volume (ul) — The final loading volume of the pool in the flow cell.

  • Bulk Pool Volume (ul) — The bulk pool volume is used in the Calculate Volumes script to determine RSB volumes required for pooling.

  • Minimum Per Sample Volume (ul) — The minimum volume for each sample. This field is prepopulated with the configured default value (2 µl) and can be edited. If the per sample volume is below the value set in this field, the Calculate Volumes script applies a rounding factor to affected samples so that the volume reaches the minimum volume.

  • Flowcell Type — The flow cell type that the run uses. Select from the following options:

    • 5M

    • 25M

  • Select Calculate Volumes to trigger the Calculate Volumes automation.

    This automation calculates the volumes required for each library to form a pool that has the concentration and volume specified in the Step Details field. It also generates the calculation file in a CSV format and attaches it to the step. Select the file name to download it.

  • Select Next Steps to trigger the Set Next Step automation.

    This automation sets the next step for samples to ADVANCE, which moves them to the Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) step.

  • Select Finish Step.

  • On the Ice Bucket screen, select the destination container type:
    • MiSeq i100 Series Dry Cartridge

  • Select Begin Work to trigger the Validate Single Pool automation.

    • The Validate Single Pool automation ensures that only one pool is selected for loading to the dry cartridge in this step.

  • On the Placement screen, do as follows.

    1. Drag the pool into the Placed Samples area on the right.

    2. Scan or type the barcode of the dry cartridge into the container name field.

    3. Select Record Details.

    After exiting the Placement screen, the Validate Dry Cartridge Barcode automation makes sure that the dry cartridge barcode conforms to the barcode mask. The barcode mask is SC[0-9]{7}-SC3.

  • The fields displayed on the Record Details screen are used to create the planned run and generate the sample sheet.

    The analysis related information for the planned run comes from the ACT associated with the samples. Refer to the following table for details.

    Fields Displayed on Record Details Screen of Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) Step

    Field

    Description

    Run Name

    Experiment name.

    • Only alphanumeric characters, dashes, periods, spaces and underscores are permitted.

    • Maximum of 255 characters

    Run Mode

    ¹ The Local run mode sends the Run/Analysis configuration to Illumina Run Manager. This configuration is downloaded to the MiSeq i100 Series instrument through Illumina Run Manager to start the run. The downstream secondary analysis is done on premise.

    ² The custom value must correspond to the longest index sequence of the samples in the pools in the library tube strip. Otherwise, the planned run creation fails and an error message displays.

  • Select Validate Run Setup and Create Planned Run to trigger the automation script. The script performs the following actions:

    • Validates the parameters entered on the Record Details screen.

    • Creates the planned run on Illumina Run Manager.

    • Generates the sample sheet and attaches it to the placeholder in the Files area on the Record Details screen.

  • Select Next Steps.

    On the Assign Next Steps screen, the next step for the pooled samples is set to the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step.

  • Select Finish Step to advance the pooled samples to the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step. For more information on how to start the sequencing run for different run modes, refer to MiSeq i100 Series On-Prem Integration v1.0.0 Configuration.

  • Output Folder

  • Current Read

  • Current Cycle

  • Dry Cartridge Barcode Serial Number

  • Dry Cartridge Expiration Date

  • Wet Cartridge Expiration Date

  • Wet Cartridge Serial Number

  • Flow Cell ID

  • Flow Cell Type

  • Instrument ID

  • Instrument Type

  • Instrument Control Software Version

  • Sequencing Log

  • Refer to MiSeq i100 Series On-Prem Integration v1.0.0 Configuration for details of the fields.

    % Error Rate R1

  • % Error Rate R2

  • Yield (Gb) R1

  • Yield (Gb) R2

  • Reads PF

  • % PF

  • % Aligned R1

  • % Aligned R2

  • % Occupied

  • % Phasing R1

  • % Phasing R2

  • % Prephasing R1

  • % Prephasing R2

  • Intensity Cycle 1 R1

  • Intensity Cycle 1 R2

  • Pool the samples again. Make sure that samples with conflicting secondary analysis application, analysis versions or analysis settings, are in different pools.
    MiSeq i100 Series On-Prem Integration v1.0.0 Installation
    Library Prep Validation Protocol
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    Clarity LIMS (API & Database) documentation
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    Illumina Adapter Sequencesarrow-up-right

    Presets

    • Local (Default)¹

    Read 1 Cycles

    Presets

    • 151

    • 101

    • 51

    • Type a custom value

    Read 2 Cycles

    Presets

    • 151

    • 101

    • 51

    • Type a custom value

    Index 1 Cycles

    Presets

    • 0

    • 6

    • 8

    • Type a custom value²

    Index 2 Cycles

    Presets

    • 0

    • 6

    • 8

    • Type a custom value²

    Configuration

    The Illumina MiSeq i100 Series On-Prem Integration Package v1.0.0 supports the integration of Clarity LIMS to Illumina MiSeq i100 Series sequencer connected to the Illumina Run Manager platform on premise.

    For instructions on validating and troubleshooting the Illumina MiSeq i100 Series On-Premise Integration, refer to MiSeq i100 Series On-Premise Integration v1.0.0 User Interaction, Validation and Troubleshooting.

    triangle-exclamation

    The configuration provided in this integration has been established to support MiSeq i100 Series lab processes. Any configuration changes to protocols or workflows (including renaming protocols, steps, and fields) could break the integration.

    hashtag
    Prerequisites and Assumptions

    hashtag
    Analysis Configuration Template

    The MiSeq i100 Series On-Prem Sequencing v1.0 workflow uses analysis configuration templates (ACT) to configure secondary analysis for the planned runs. It is assumed that the required ACTs for your run has been pre-created using Illumina Run Manager UI. Please make sure that the index adapter kit (label group on Clarity) selected in the ACT has already been created on Clarity LIMS. The same label group shall be used in the library preparation step. Names of ACT must be unique. Please refer to the for details on creating ACT on Illumina Run Manager User Interface (UI).

    triangle-exclamation

    Clarity LIMS trims all leading and trailing spaces from the ACT names and ACTs created in Illumina Run Manager UI with names containing leading and/or trailing spaces may not be recognized properly on Clarity. Please ensure that the ACT do not have leading and/or trailing spaces.

    hashtag
    Samples

    It is assumed that samples that enter the MiSeq i100 Series On-Prem Sequencing v1.0 workflow have gone through library preparation and quantification processes before they are assigned to the workflow:

    • Samples have been accessioned into Clarity LIMS.

    • Sample and library names must contain only alphanumeric, dash, or underscore characters.

    • Samples have been run through QC and library prep.

    hashtag
    Workflows, Protocols, and Steps

    The MiSeq i100 Series On-Premise Integration Package v1.0.0 includes the following workflows:

    • MiSeq i100 Series On-Prem Sequencing v1.0

    • Library Prep Validation v2.3.5 (optional, but recommended for validation purposes)

    The following describes the protocols and steps included in these workflows.

    hashtag
    Library Prep Validation v2.3.5 Workflow

    chevron-rightProtocol 1: Library Prep Validation v2.3.5hashtag

    Purpose:

    • Included for validation purposes only, this protocol models the library preparation steps required to advance samples to the MiSeq i100 Series On-Prem Sequencing v1.0 workflow.

      âš  The label group (index adapter kit) used for library preparation must be the same as the index adapter kit specified in the ACT that is being used. For more information, refer to

    hashtag
    MiSeq i100 Series On-Prem Sequencing v1.0 Workflow

    chevron-rightProtocol 1: MiSeq i100 Series On-Prem Sequencing v1.0hashtag

    Purpose:

    • This protocol models the lab processes of run setup for starting a MiSeq i100 Series sequencing and secondary analysis run on premise.

    Steps:

    hashtag
    Validation Workflow

    The Library Prep Validation v2.3.5 workflow allows for validation of the system after installation is complete. This workflow can be replaced by other custom library preparation workflows. For details, refer to .

    [Optional] Configure a custom library preparation workflow. Routing of libraries from the custom workflow to the MiSeq i100 Series On-Premise Sequencing protocol can be enabled in the master step with the available in the NGS package.

    hashtag
    Step 1: Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)

    In this step, secondary analyses are configured for the samples using ACTs. Each ACT contains details related to a particular secondary analysis (e.g., index adapter kit to use, reference genome setting). At this step, the user selects an ACT from a list of pre-constructed ACTs and assigns samples to it. A planned run can involve multiple ACTs and users have to repeat Step 1 for each ACT that is required for the planned run. For more information on creating ACTs and assigning samples to them, refer to .

    chevron-rightValidate Sample Names Automationhashtag

    Automatically triggered on entry of the step, this automation validates that the sample names contain only alphanumeric, dash and underscore characters.

    chevron-right1. Retrieve ACT List Automationhashtag

    Triggered when you select '1. Retrieve ACT List' button on the Record Details screen, this automation retrieves the list of ACTS that has been created using Illumina Run Manager UI.

    chevron-right2. Retrieve ACT Information Automationhashtag

    Triggered when you select '2. Retrieve ACT Information' button on the Record Details screen, this automation:

    • Retrieves the details of the selected ACT and populates the step UDFs (e.g., Analysis Version, Library Prep Kit, Index Adapter Kit, Reference Genome)

    chevron-rightValidate Reagent Labels and Apply Selected ACT to Samples and Set Next Step Automationhashtag

    Automatically triggered on exit of the Record Details screen, this automation:

    • Checks that the molarity of all samples are specified

    hashtag
    Master Step Fields

    The following table lists the configuration details for custom fields that are defined on the Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0) Master Step Field Configuration

    hashtag
    Global Fields

    The following lists the global custom fields that are configured to display on the Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0) step. See Global Fields section for detail configuration.

    • Molarity (nM)

    • ACT Name

    hashtag
    Step 2: Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

    Samples are pooled in the Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0) step. You can manually create working pools based on the final loading concentration required.

    chevron-rightValidate Analysis Configurations Automationhashtag

    Automatically triggered on exit of the Pooling screen, this automation performs analysis configuration validity and checks each pool for the following characteristics:

    • Pooled samples assigned with the same secondary analysis application must have the same analysis version (e.g. v3.8.4) and settings (e.g. Map/Align Output Format = CRAM).

    chevron-rightCalculate Volumes Automationhashtag

    Triggered when you select 'Calculate Volumes' button on the Record Details screen, this automation completes the following actions:

    • Checks to ensure all samples have molarity values assigned.

    • Uses Number of Samples in Pool to calculate the volumes needed for the 2 nM intermediate library pools.

    chevron-rightSet Next Step Automationhashtag

    Automatically triggered on exit of the Record Details screen, this automation completes the following actions:

    • Proceeds only if the sample has a molarity value.

    • Copies the Run Mode from input to output.

    hashtag
    Master Step Fields

    The following table lists configuration details for the custom fields that are defined on the Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0) Master Step Field Configuration

    hashtag
    Global Fields

    The following lists the global custom fields that are configured to display on the Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0) step. See Global Fields section for detail configuration.

    • Final Loading Concentration (pM)

    • RSB Volume (ul)

    • MiSeq i100 Series Flowcell Type

    hashtag
    Step 4: Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

    In this step, the user scans the dry cartridge barcode into the LIMS, and then manually places the working pools into the dry cartridge to be used in the MiSeq i100 Series run. In addition, this step validates the run setup and analysis information and generates samplesheet file and/or creates a planned run on instrument's Illumina Run Manager UI.

    chevron-rightValidate Single Pool Automationhashtag

    Automatically triggered on entry to the step, this automation checks only single pool is use to start the step.

    chevron-rightValidate Dry Cartridge Barcode Automationhashtag

    Automatically triggered on exit of the Placement screen, this automation validates the dry cartridge barcode to ensure it conforms to the barcode mask SC[0-9]{7}-SC3.

    chevron-rightValidate Run Setup and Create Planned Run Automationhashtag

    Triggered when you select 'Validate Run Setup and Create Planned Run' on the Record Details screen, this automation completes the following actions:

    • Validates the parameters entered on the Record Details screen. These parameters are used to set up the run, generate the sample sheet file, and create the planned run on Illumina Run Manager.

    chevron-rightSet Next Step Automationhashtag

    Automatically triggered on exit of the Record Details screen, this automation completes the following actions:

    • Sets the next step for samples to ADVANCE, advancing them to the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    hashtag
    Master Step Fields

    The following table shows the master step fields that are configured on the Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) step. These fields are required for sample sheet generation and planned run creation in Illumina Run Manager.

    Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) Master Step Field Configuration

    hashtag
    Step 5: AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    triangle-exclamation

    Do not add samples to the Ice Bucket, start or complete the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step. The integration will do this automatically.

    In this step, the pooled samples in the dry cartridge are sequenced on the MiSeq i100 Series instrument.

    There are no automation associated to this step.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    Master Step Field Information

    All the fields above are Read-Only Text field, except Sequencing Log is a Read-Only Multiline Text.

    hashtag
    Global Fields

    The following global custom fields are used to capture the run metrics in Clarity LIMS:

    • % Aligned R1

    • % Aligned R2

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    At the end of the step, the pools of samples are automatically route to next step.

    hashtag
    Step 6: AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    triangle-exclamation

    Do not add samples to the Ice Bucket or start and complete the AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Analysis v1.0) step. The integration does this automatically.

    Data from the analysis is parsed back to Clarity LIMS. In this step, the secondary analysis configured using the Analysis Configuration Template (ACT) is performed on DRAGEN on-premise.

    There are no automation associated to this step.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0) Master Step Field Information

    All the fields above are Read-Only Text field, except Log is a Read-Only Multiline Text.

    hashtag
    How the Integration Works

    The following information summarizes how the MiSeq i100 Series On-Premise Integration works.

    • After the 'Validate Run Setup and Create Planned Run' automation is triggered on the Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) step, the run parameters entered in the Run Details screen and the sample informations are sent to Illumina Run Manager. Illumina Run Manager validates the run and analysis configuration before the planned run is created, the automation also generates the sample sheet and attaches it to the step. In the event of incomplete information or misconfiguration on the planned run, an error will be displayed on the automation banner and details of the error will be logged in the automation log file.

    • When the sequencing run starts on the instrument, the MiSeq i100 Series Control Software notifies the Illumina Run Manager integration. The events are processed and the integration service retrieves the run information from MiSeq i100 Illumina Run Manager. This information is used to populate the custom fields in the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    triangle-exclamation

    If a planned run with the same sample name and project name (case-insensitive) has been created previously in Illumina Run Manager, the sample sheet generated from the 'Validate Run Setup and Create Planned Run' automation can reflect the original case of the previous sample name. This can cause validation errors for analysis configurations with sample-level settings. To resolve this issue, change the sample name or the project name on Clarity LIMS and run the automation again.

    hashtag
    Start a Sequencing Run on MiSeq i100 Series Instrument

    To start a planned run, refer to information on .

    hashtag
    Enabling Planned Run Generation for Samples Having Duplicate Name with Different Indexes

    The library preparation workflow of the samples must be before routing the samples through the library preparation workflow.

    hashtag
    Components Installed

    The following sections describe the components (files, properties, reagent categories / label groups, reagent kits, and containers) that are installed by default as part of this integration.

    Global Fields

    Container Global Fields

    Derived Sample Global Fields

    Reagent Kits

    • MiSeq i100 Series Dry Cartridge

    • MiSeq i100 Series Library Denature (KLD)

    • MiSeq i100 Series Wet Cartridge

    Container Types

    • MiSeq i100 Series Dry Cartridge

    Instrument Types

    • MiSeq i100 Series

    hashtag
    Rules and Constraints

    • The workflow configuration contains several validation checks. To make sure that the calculations work properly, it is important that you do not disable any of this validation logic. The validation checks determine the following information:

      • Which samples, and how many, can enter each step together.

      • Which samples, and how many, can be pooled together.

    Samples have the Molarity (nM) global field set to a valid value (required for the 'Calculate Volumes' automation in the Make Bulk Pool step).
    .
  • The protocol contains a single step - Library Prep Validation v2.3.5. After this step, a routing script sends the samples to the first step of the MiSeq i100 Series On-Prem Sequencing v1.0 workflow.

  • Steps:

    1. Library Prep Validation v2.3.5

    Assign Analysis Configuration Template (MiSeq i100 Series On-Prem Sequencing v1.0)

    • The secondary analysis of samples is configured using the ACT.

    • The labels applied to the samples are validated against the selected ACT to ensure that samples use valid labels.

  • Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0)

    • Samples are pooled and resuspension buffers and reagents are added with the help of the 'Calculate Volumes' automation.

    • ACT of pooled samples are validated with Validate Analysis Configurations automation to ensure that the secondary analysis configurations remain valid after pooling.

  • Load To Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0)

    • The library pools from step 2 are now ready to be loaded to the MiSeq i100 Series dry cartridge.

    • Run and analysis information is validated.

    • Samplesheet is generated and planned run is created on MiSeq i100 Illumina Run Manager.

  • AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    • This is a fully-automated step that is started and completed automatically once the sequencing run is started and completed on the instrument side.

    • All the sequencing run metadata e.g. run configuration, primary run metrics etc. are recorded automatically.

  • AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0)

    • This is a fully-automated step that is started and completed automatically once the analysis run is started and completed on DRAGEN on premise.

    • All the analysis run metadata e.g. status and demultiplexing result files are recorded automatically.

  • Saves the details into a file stored in the Analysis Configuration Metadata file placeholder, which is available for user to download.
    Checks that all samples are indexed, indexes are the same as the selected ACT.
  • Assign the ACT ID, ACT Name, Run Mode and Instrument ID to all the samples in the step.

  • Sets the next step for samples to ADVANCE, advancing them to the next step in the protocol - Make Bulk Pool (MiSeq i100 Series On-Prem Sequencing v1.0).

  • Text

    Read Only

    Reference Genome

    Text

    Read Only

    Secondary Analysis Mode

    Text

    Read Only

  • Calculate the Final Loading Concentration (pM)

  • Copies Flowcell Type from the step inputs to the step outputs.

  • Calculates the per sample volume required for each library to make a 2 nM intermediate library pool and sets the total sample volume to zero.

  • Calculates the PhiX Spike-in volume if specified.

  • Calculates the adjusted per sample volume for the pools if any of the calculated volume is lesser than the value specified in Minimum Per Sample Volume (ul) step UDF.

  • Uses the Total Sample Volume (ul) to calculate the RSB volume (ul) required to top up the pools that are needed to create the 2 nM intermediate library pools. The RSB volume is saved to the file in the Calculation File placeholder in the Files section.

  • Uses the MiSeqi100Series_Bulk_Pool1.csv and MiSeqi100Series_Bulk_Pool2.csv template files to generate a single CSV file. This file contains information about the pools and the samples that they contain. The generated file is stored in the Calculation File placeholder in the Files section.

  • Resets the Number of Samples in Pool to null before exiting the step.

  • Sets the next step for samples to ADVANCE, advancing them to the Load to Dry Cartridge (MiSeq i100 Series On-Prem Sequencing v1.0) step.

    Flowcell Loading Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed: 2

    • Default: 250

    Flowcell Type

    Text Dropdown

    • Required Field

    • Dropdown Items

      • 5M

      • 25M

    Minimum Per Sample Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed: 2

    • Default: 2

    Run Name may only contain alphanumeric, dash, underscore or period characters. Spaces are not permitted.

  • Run Name shall not exceed 255 characters.

  • Checks the Index 1 Cycles and Index 2 Cycles field values. If Index 2 Cycles is greater than 0, the Index 1 Cycles value must be greater than 0 or an error can occur.

  • Generates the sample sheet and creates the planned run on Illumina Run Manager. The sample sheet is attached to the step.

  • Planned Run ID

    Text

    • Read Only

    • Hidden, use to store created planned run id

    Read 1 Cycles

    Numeric Dropdown

    • Required Field

    • Allow Custom Entries

    • Range: 1 – 301

    • Presets

      • 101

    Read 2 Cycles

    Numeric Dropdown

    • Required Field

    • Allow Custom Entries

    • Range: 0 – 301

    • Presets

      • 101

    Run Mode

    Text

    • Read Only

    • Default: Local

    Run Name

    Text

    • Required Field

    Version of the instrument control software.

    Instrument ID

    Unique identification for the instrument.

    Instrument Run ID

    Unique identification for the instrument sequencing run.

    Instrument Type

    Type of the instrument, either MiSeqi100 or MiSeqi100Plus.

    Output Folder

    Output folder path for the sequencing run data.

    Run End Time

    Time completed for the sequencing run.

    Run Name

    Run name user configured for the sequencing run.

    Run Start Time

    Time started for the sequencing run.

    Run Status

    Status of the sequencing run.

    Sequencing Log

    Log messages by the Illumina Run Manager integration while handling the sequencing event from instrument.

    Wet Cartridge Expiration Date

    Wet cartridge expiration data.

    Wet Cartridge Serial Number

    Wet cartridge Serial Number.

    % Error Rate R1

  • % Error Rate R2

  • % Occupied

  • % Phasing R1

  • % Phasing R2

  • % Prephasing R1

  • % Prephasing R2

  • % PF

  • Intensity Cycle 1 R1

  • Intensity Cycle 1 R2

  • Reads PF

  • Yield (Gb) R1

  • Yield (Gb) R2

  • Other run events follow the same information flow. When sequencing is complete, the control software uploads the sequencing run data (primary metrics). Then, Illumina Run Manager integration retrieves the primary metrics and uses them to populate the fields in the Sample Details table (e.g., % Error Rate R1). The custom fields (e.g., Run Status, Current Read, and so on) on the AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) step are updated using the run related information. If the sequencing run is successfully completed, the step automatically completes.
  • The integration tracks the analysis events and results in the AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0) step. The secondary analysis results are in the external storage configured in Illumina Run Manager. The external storage information is found in the External Storage for Analysis Results configuration settings in Illumina Run Manager.

  • Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Error Rate R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Occupied

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % PF

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Phasing R1

    Numeric

    • Read Only

    • Decimal Places Displayed: 3

    % Phasing R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 3

    % Prephasing R1

    Numeric

    • Read Only

    • Decimal Places Displayed: 3

    % Prephasing R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 3

    Intensity Cycle 1 R1

    Numeric

    • Read Only

    Intensity Cycle 1 R2

    Numeric

    • Read Only

    Reads PF

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    Yield (Gb) R1

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    Yield (Gb) R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    Numeric Dropdown

    • Required

    • Preset:

      • 225

    Instrument ID

    Text

    • Read Only

    KLD Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 1

    MiSeq i100 Series Flowcell Type

    Text Dropdown

    • Required

    • Preset:

      • 5M

    Molarity (nM)

    Numeric

    • Decimal Places Displayed: 2

    Number of Samples in Pool

    Numeric

    Per Sample Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    PhiX Concentration (pM)

    Numeric

    PhiX Volume (ul)

    Numeric

    • Decimal Places Displayed: 2

    Required Bulk Pool Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 1

    RSB Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    RSB Volume for Intermediate Pool (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 1

    Run Mode

    Text

    • Read Only

    Total Sample Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 1

    Resuspension Buffer (RSB)

    All submitted samples must have an associated secondary analysis that is configured using the analysis configuration template (ACT). The ACT must be configured on MiSeq i100 Illumina Run Manager before starting the Assign Analysis Configuration Template step. The ACT names must be unique.

  • Assign Analysis Configuration Template step does not support pool library as input.

  • The dry cartridge barcode must be unique. There must not be multiple dry cartridge containers with the same name in the Clarity LIMS system.

  • Reagent labels, or indexes, must be unique.

  • One library pool can only contain one library or control with no label/index.

  • The AUTOMATED - Sequencing Run (MiSeq i100 Series On-Prem Sequencing v1.0) and AUTOMATED - Analysis Run (MiSeq i100 Series On-Prem Sequencing v1.0) steps must not be manually started or completed. These steps are fully automated and the integration service does not update samples correctly if they have been manually started.

  • For the automated run to start successfully, you must click 'Validate Run Setup and Create Planned Run' in the Load to Dry Cartridge step and the automation must be ran successfully.

  • Field Name

    Field Type

    Options

    Analysis Configuration Template

    Text Dropdown

    Allow Custom Entries

    Application

    Text

    Read Only

    Application Version

    Text

    Read Only

    Index Adapter Kit

    Text

    Read Only

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    % PhiX (100 pM) Spike-In

    Numeric

    • Range: 0 - 100

    Bulk Pool Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed: 2

    • Default: 1

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Allow Custom Entries

    • Dropdown Items

      • 60

      • 70

      • 80

      • 90

      • 100

      • 110

      • 120

      • 130

      • 140

      • 150

      • 160

      • 170

      • 180

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Index 1 Cycles

    Numeric Dropdown

    • Required Field

    • Allow Custom Entries

    • Range: 0 – 18

    • Presets

      • 0

      • 6

      • 8

    Index 2 Cycles

    Numeric Dropdown

    • Required Field

    • Allow Custom Entries

    • Range: 0 – 18

    • Presets

      • 0

      • 6

      • 8

    Instrument

    Text

    • Read Only

    Field Name

    Description

    Current Cycle

    Current completed cycle count.

    Current Read

    Current completed reads count.

    Dry Cartridge Barcode Serial Number

    Dry Cartridge Barcode Serial Number.

    Dry Cartridge Expiration Date

    Flow Cell expiration data.

    Flow Cell ID

    Serial number of the Flow Cell.

    Flow Cell Type

    Flow Cell Type. Value can be 5M or 25M.

    Field Name

    Description

    Additional Information

    Analysis Result Location

    Analysis files final copy out location.

    Analysis Run ID

    Run ID associate with the Analysis run.

    Hidden on Record Details screen by default.

    Analysis Status

    Status for the the analysis run.

    Log

    Log messages by the Illumina Run Manager integration while handling the analysis event from instrument.

    Field Name

    Field Type

    Settings

    % Aligned R1

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Aligned R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Bases >=Q30 R1

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    % Bases >=Q30 R2

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    Field Name

    Field Type

    Settings

    ACT ID

    Text

    • Read Only

    ACT Name

    Text

    • Read Only

    Adjusted Per Sample Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    Bulk Pool Volume (ul)

    Numeric

    • Read Only

    • Decimal Places Displayed: 2

    MiSeq i100 Series On-Premise Integration v1.0.0 User Interaction, Validation and Troubleshooting
    MiSeq i100 Series On-Premise Integration v1.0.0 User Interaction, Validation and Troubleshooting
    routing script
    MiSeq i100 Series On-Premise Integration v1.0.0 User Interaction, Validation and Troubleshooting
    starting a planned run in the Illumina support site.arrow-up-right
    configured to ensure unique derived sample names

    Library Prep Kit

    Instrument Control Software Version

    % Error Rate R1

    Final Loading Concentration (pM)

    MiSeq i100 Series On-Premise Integration v1.0.0 User Interaction, Validation and Troubleshooting
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/miseqi100series-onprem/automation/miseqi100series-onprem-automation.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}' -n 'INSTRUMENT_USED' --derivedSampleInstrumentIdUdf 'Instrument ID' script:validate_indexes script:assign_act
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:evaluateDynamicExpression -t false -h false -exp 'nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}
    output.::Required Bulk Pool Volume (ul):: = (step.::Final Loading Concentration (pM):: / 1000) * step.::Final Loading Volume (ul):: / 4 ;
        output.::MiSeq i100 Series Flowcell Type:: = step.::Flowcell Type::;
    input.::Per Sample Volume (ul):: = 4 * step.::Bulk Pool Volume (ul):: / input.::Molarity (nM):: / output.::Number of Samples in Pool::;
        output.::Bulk Pool Volume (ul):: = step.::Bulk Pool Volume (ul)::;
        output.::Total Sample Volume (ul):: = 0;
    if (step.hasValue(::% PhiX (100 pM) Spike-In::) && step.::% PhiX (100 pM) Spike-In:: > 0) { output.::PhiX Concentration (pM):: = 100; output.::PhiX Volume (ul):: = 4 * output.::Required Bulk Pool Volume (ul):: * (step.::% PhiX (100 pM) Spike-In:: / 100) / (output.::PhiX Concentration (pM):: / 1000); } else { output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; }
    script:calculate_multipool_adjusted_per_sample_volume -t
    script:evaluateDynamicExpression \
      -exp 'if (output.hasValue(::Total Sample Volume (ul)::)) { output.::Total Sample Volume (ul):: = output.::Total Sample Volume (ul):: + input.::Adjusted Per Sample Volume (ul)::; } else { output.::Total Sample Volume (ul):: = input.::Adjusted Per Sample Volume (ul)::; }' -t true \
      script:evaluateDynamicExpression \
      -exp 'if (output.::Total Sample Volume (ul):: > output.::Bulk Pool Volume (ul)::) { output.::RSB Volume for Intermediate Pool (ul):: = 0 } else { output.::RSB Volume for Intermediate Pool (ul):: = output.::Bulk Pool Volume (ul):: - output.::Total Sample Volume (ul):: }' -t true \
      script:evaluateDynamicExpression \
        -exp 'if (output.::Bulk Pool Volume (ul):: < output.::Required Bulk Pool Volume (ul)::) { output.::RSB Volume (ul):: = output.::Required Bulk Pool Volume (ul):: - output.::Bulk Pool Volume (ul)::; } else { output.::RSB Volume (ul):: = 0.1 * step.::Final Loading Volume (ul):: - output.::Required Bulk Pool Volume (ul)::; } ; output.::KLD Volume (ul):: = 0.9 * step.::Final Loading Volume (ul)::; output.::Final Loading Concentration (pM):: = step.::Final Loading Concentration (pM)::;' -t true
    script:driver_file_generator \
        -t /opt/gls/clarity/extensions/conf/driverfiletemplates/MiSeqi100Series_Bulk_Pool1.csv -o 1.csv \
        script:driver_file_generator \
        -t /opt/gls/clarity/extensions/conf/driverfiletemplates/MiSeqi100Series_Bulk_Pool2.csv -o 2.csv \
        script:driver_file_generator \
        -t /opt/gls/clarity/extensions/conf/driverfiletemplates/MiSeqi100Series_Bulk_Pool3.csv -o 3.csv \
        && cat 1.csv 2.csv 3.csv > {compoundOutputFileLuid0}.csv
    -exp 'output.::Number of Samples in Pool:: = ::::;' -t true
    'if (!step.::Run Name::.matches(::[a-zA-Z0-9-_]+[a-zA-Z0-9-_. ]*::)) { fail(::Run Name contains prohibited characters. Please check to make sure Run Name only contains alphanumeric characters, spaces, dashes, periods and underscores. Run Name must start with alphanumeric, a dash or an underscore::); }; 
    if (step.::Run Name::.length() > 255) { fail(::Run Name shall not exceed 255 characters.::); };
    if (step.::Index 2 Cycles:: > 0 && step.::Index 1 Cycles:: == 0) { fail(::Index 1 Cycles cannot be zero if Index 2 Cycles is non-zero::); };
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/miseqi100series-onprem/automation/miseqi100series-onprem-automation.jar  script:generate_sample_sheet -i {stepURI:v2} -u {username} -p {password} -c {compoundOutputFileLuid0} -l {compoundOutputFileLuid1} -n 'INPUT.Instrument ID' --instrumentType '{udf:Instrument Type}' --verifyIndexLength
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:evaluateDynamicExpression -exp 'submittedSamples.each { sample -> if ( !sample.name.matches( ::[A-Za-z0-9_-]+:: ) ) { fail ( ::Submitted sample :: + sample.name + :: should only have alphanumeric, dash, and underscore characters. Please rename and try again.:: ) } }' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/miseqi100series-onprem/automation/miseqi100series-onprem-automation.jar script:retrieve_act_list -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -n 'INSTRUMENT_USED' -t true
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:evaluateDynamicExpression -t false -h false -exp 'if (!input.hasValue(::Molarity (nM)::)) { fail(::The Molarity cannot be empty.::); } else if (input.::Molarity (nM):: <= 0) { fail(::The Molarity cannot be negative or zero.::); }' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:evaluateDynamicExpression -t false -h false -exp 'output.::Instrument ID:: = input.::Instrument ID::' -log {compoundOutputFileLuid1} && \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/miseqi100series-onprem/automation/miseqi100series-onprem-automation.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool -n 'INPUT.Instrument ID' script:validate_analysis_config  script:validate_physical_logical_configurations
    if (!input.hasValue(::Molarity (nM)::)) { return; };
    script:validateSampleCount -min 1 -max 1
     script:validate_output_containers -r 'MiSeq i100 Series Dry Cartridge:SC[0-9]{7}-SC3' -min 1 -max 1
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} script:evaluateDynamicExpression -t false -h false -exp 'nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/miseqi100series-onprem/automation/miseqi100series-onprem-automation.jar script:retrieve_act_info -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}' -n 'INSTRUMENT_USED'
    if (output.hasValue(::Number of Samples in Pool::)) { output.::Number of Samples in Pool:: = output.::Number of Samples in Pool:: + 1; } else { output.::Number of Samples in Pool:: = 1; }' -t true
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} -log {compoundOutputFileLuid1} \
    script:evaluateDynamicExpression -exp 'if (!input.hasValue(::Molarity (nM)::)){ return; }; output.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::;'"
    151
  • 301

  • 151
  • 301

  • 400
  • Allow custom entries

  • 25M