arrow-left

All pages
gitbookPowered by GitBook
1 of 16

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

NovaSeq X Series (Hosted)

The Illumina NovaSeq X Series integration provides preconfigured workflows that map to established lab protocols and steps used with NovaSeq X Series sequencing instruments. The integration also supports the associated library prep kits, reagent kits, and assays used in these protocols.

NovaSeq X Series v1.2.0

The integration includes the following features:

  • Preconfigured NovaSeq X Series Sequencing v1.1 workflow that maps to lab protocols and instrument runs.

  • The following steps in the NovaSeq X Series Sequencing v1.1 preconfigured protocol:

    • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

    • Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    • Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    • Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

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

  • Automated generation of the sample sheet. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through Local run mode.

  • Automated creation of a planned run on Illumina Connected Analytics (ICA). The NovaSeq X Series Control Software retrieves the planned run for use with the Cloud run mode.

  • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics from BaseSpace Sequence Hub to Clarity LIMS.

  • Automated tracking of the NovaSeq X Series analysis run and high level analysis summary from BaseSpace Sequence Hub to Clarity LIMS.

  • Support for configuration of multiple secondary analyses with multiple library prep kits (LPKs) and index adapter kits (IAKs) for the planned run. The analysis is either performed by ICA in Cloud mode or by DRAGEN on-board the instrument in Local mode.

  • [Optional] Preconfigured Library Prep Validation v2.3.2 workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep required to produce libraries that are ready for the NovaSeq X Series Sequencing v1.1 workflow. For more information, refer to .

  • [Optional] Clarity LIMS Product Analytics (CLPA) integration that can be used with ICA. The CLPA integration installation and configuration is required. For more information, refer to .

NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting
Clarity LIMS Product Analytics Integration v1.2.0 Configuration

NovaSeq X Series v1.2.1

The integration includes the following features:

  • Preconfigured NovaSeq X Series Sequencing v1.1 workflow that maps to lab protocols and instrument runs.

  • The following steps in the NovaSeq X Series Sequencing v1.1 preconfigured protocol:

    • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

    • Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    • Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    • Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

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

  • Automated generation of the sample sheet. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through Local run mode.

  • Automated creation of a planned run on Illumina Connected Analytics (ICA). The NovaSeq X Series Control Software retrieves the planned run for use with the Cloud run mode.

  • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics from BaseSpace Sequence Hub to Clarity LIMS.

  • Automated tracking of the NovaSeq X Series analysis run and high level analysis summary from BaseSpace Sequence Hub to Clarity LIMS.

  • Support for configuration of multiple secondary analyses with multiple library prep kits (LPKs) and index adapter kits (IAKs) for the planned run. The analysis is either performed by ICA in Cloud mode or by DRAGEN on-board the instrument in Local mode.

  • [Optional] Preconfigured Library Prep Validation workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep required to produce libraries that are ready for the NovaSeq X Series Sequencing v1.1 workflow.

  • [Optional] Clarity LIMS Product Analytics (CLPA) integration that can be used with ICA. The CLPA integration installation and configuration is required. For more information, refer to .

Release Notes

Last Updated: November 2024

Release Date: September 2023

Document Version: 2

These release notes describe the key changes to software components for the Clarity LIMS NovaSeq X Series Integration Package v1.1.0.

hashtag
Compatibility

Release Notes

Last Updated: December 2024

Release Date: February 2024

Document Version: 3

These release notes describe the key changes to software components for the Clarity LIMS NovaSeq X Series Integration Package v1.2.0.

hashtag
Compatibility

Refer to Compatibility under Instruments & Integrations.

hashtag
New Features

  • Updated Java and third-party dependency libraries.

  • Updated Groovy to v3.0.7.

hashtag
Defects Fixed

  • Restricted the scope for the JWT token used in the integration.

  • Fixed issue where the SIS core service was not properly registered in systemctl.

hashtag
Known Limitations

  • This integration does not track the analysis step. You must log in to BSSH to view the cloud analysis status and results. For local analysis, the secondary analysis results are located in the external storage configured in Illumina Run Manager.

  • The Local run mode does not support custom library prep and index adapter kits.

  • The Analysis Configuration Template (ACT) names must be unique.

  • The Assign Analysis Configuration Template step expects the input samples to be unpooled libraries.

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.

  • Sample sheet and planned run generation will fail if any of the samples in the pools has been assigned QC flag in prior steps before entering the Load to Library Tube Strip step.

hashtag
Revision History

Version

Changes

2

  • Updated Compatibility section to reference Compatibility matrix table.

  • Updated Known Limitations section.

1

  • Initial release.

Refer to Compatibility under Instruments & Integrations.

hashtag
New Features

  • Supports analysis tracking at the metaworkflow level for analysis status and high level analysis summary results.

  • Supports the new 1.5B and 25B flow cell types. The B3 flow cell has been renamed to the 10B flow cell.

  • Uses the SecureString type for improving the security of values stored in the AWS param store.

  • Includes the following improvements to the NovaSeq X Series Sequencing v1.1 protocol:

    • Removes the unused Output Folder step custom field from the Load to Library Tube Strip step.

    • Renames the Library Tube barcode step custom field to Library Tube Strip Barcode in the AUTOMATED - Sequencing Run step.

hashtag
Defects Fixed

  • None

hashtag
Known Limitations

  • The analysis step tracks only the first run, but not subsequent queued runs.

  • The Local run mode does not support custom library prep and index adapter kits.

  • The Assign Analysis Configuration Template step expects the input samples to be unpooled libraries.

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.

  • Sample sheet and planned run generation will fail if any of the samples in the pools has been assigned QC flag in prior steps before entering the Load to Library Tube Strip step.

  • For BCL Convert only analysis, the high level analysis summary file is not available. User will need to manually complete the AUTOMATED - Analysis Run step upon analysis completed.

hashtag
Revision History

Version

Changes

3

  • Updated Known Issues section.

2

  • Updated Compatibility section to reference Compatibility matrix table.

  • Updated Known Limitations section.

1

  • Initial release.

Clarity LIMS Product Analytics Integration v1.3.1 Configuration

Release Notes

Last Updated: December 2024

Release Date: July 2024

Document Version: 3

These release notes describe the key changes to software components for the Clarity LIMS NovaSeq X Series Integration Package v1.2.1.

hashtag
Prerequisites

BaseSpace Sequence Hub account that has the Enterprise or Professional subscription

hashtag
Compatibility

Refer to Compatibility under Instruments & Integrations.

hashtag
Defects Fixed

  • Fixed the issue of unable to generate sample sheet and planned run when any sample in the pools has been assigned QC flag prior to entering the Load to Library Tube Strip step.

hashtag
Known Limitations

  1. The analysis step tracks only the first run, but not subsequent queued runs.

  2. The Assign Analysis Configuration Template step expects the input samples to be unpooled libraries.

hashtag
Known Issues

  1. 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.

  2. For BCL Convert only analysis, the high level analysis summary file is not available. User will need to manually complete the AUTOMATED - Analysis Run step upon analysis completed.

hashtag
Documentations

The NovaSeq X Series Integration v1.2.1 guides follows exactly that of NovaSeq X Series Integration v1.2.0 with the following updates:

  • NovaSeq X Series Integration v1.2.0 Configuration

    • NovaSeq X Series Integration Package version has been updated from v1.2.0 to v1.2.1.

  • NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting

    • NovaSeq X Series Integration Package version has been updated from v1.2.0 to v1.2.1.

triangle-exclamation

Note that there is no change in the workflow (NovaSeq X Series Sequencing v1.1)

hashtag
Revision History

Version

Changes

3

  • Updated Known Issues section - added Known Issue 2.

2

  • Updated Compatibility section to reference Compatibility matrix table.

  • Updated Known Limitations section.

1

  • Initial release.

Manual Upgrade

NovaSeq X Series Integration Package v1.3.0 includes modifications to the existing NovaSeq X Series Workflows to support these changes:

  1. Update existing containers (Library 2-tube Strip and Library 8-tube Strip)

  2. Update global field (BP Aliquot Volume (ul))

  3. Update existing automations

  4. Update Load to Library Tube Strip master step global fields

  5. Update AUTOMATED - Sequencing Run master step and step, including run metrics displayed

  6. Update AUTOMATED - Analysis Run master step

  7. Upgrade Clarity LIMS Product Analytics Integration (if enabled)

If you do not want to use the latest workflow (NovaSeq X Series Sequencing v1.2) available in IPP v2.10.0, then update your existing workflow configuration manually using the following information as required.

hashtag
1. Update Existing Containers

Library 2-tube Strip container

  1. On the Configuration tab, select Consumables

  2. Select Containers.

  3. Select the existing Library 2-tube Strip container.

Library 8-tube Strip container

Repeat the update instructions of Library 2-tube Strip container above for the existing Library 8-tube Strip container.

hashtag
2. Update Global Field (BP Aliquot Volume (ul))

circle-info

The derived sample global field BP Aliquot Volume (ul) is used in Calculate Volumes automation in Dilute and Denature step.

  1. On the configuration tab, select Custom Fields.

  2. Select Global Fields.

  3. Expand Derived Sample.

hashtag
3. Update Automations

There is a minor update of Command Line for Validate Run Setup and Create Planned Run automation, as well as, renaming of several automations to improve readability and provide more clarity of the automation function.

Update Validate Run Setup and Create Planned Run Automation

Updates to the Command Line is to improve the error message.

  1. On the configuration tab, select Automation.

  2. Select Validate Run Setup and Create Planned Run automation.

  3. Update the existing Command Line as follows. Changes are in red.

    bash -l -c "/opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} \ bash -l -c "/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 \ script:evaluateDynamicExpression \ -exp '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

[Optional] Rename Automations

  1. On the configuration tab, select Automation.

  2. Rename the automations as specified in the table below.

hashtag
4. Update Load to Library Tube Strip Step

Rename Cloud Run ID to Planned Run ID

  1. On the configuration tab, select Custom Fields.

  2. Select Master Step Fields

  3. Expand Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1).

Add Instrument Type

circle-info

New instrument type NovaSeq X is now supported.

  1. On the configuration tab, select Custom Fields.

  2. Select Master Step Fields.

  3. Expand Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1).

  1. On the configuration tab, select Lab Work.

  2. Select Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step.

  3. Under Record Details, add Instrument Type to Master Step Fields.

hashtag
5. Update AUTOMATED - Sequencing Run Step

There are configuration updates on the AUTOMATED - Sequencing Run master step and step, as well as updates to the run metrics displayed.

Update Master Step Configuration

  1. On the configuration tab, select Lab Work.

  2. Select AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) master step.

  3. Under Step Type, update Derived Sample Generation to Fixed with 1 Derived Sample generated.

Remove Unused RTA Version Master Step Field

  1. On the configuration tab, select Custom Fields.

  2. Select Master Step Fields.

  3. Expand AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1).

[Optional] Expand Sample Table By Default

  1. On the configuration tab, select Lab Work.

  2. Select AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) step.

  3. Select Record Details milestone.

Update Run Metrics

Reflect Reads PF Metrics at Run Level

  1. On the configuration tab, select Custom Fields.

  2. Select Global Fields.

  3. Add Reads PF field as specified in the image.

Reflect % PF Metrics at Run Level

  1. On the configuration tab, select Custom Fields.

  2. Select Global Fields.

  3. Add % PF field as specified in the image.

Add % Occupied

  1. On the configuration tab, select Custom Fields.

  2. Select Global Fields.

  3. Expand Container.

  1. On the configuration tab, select Lab Work.

  2. Select AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

  3. Under Record Details, add % Occupied to Table Columns.

Remove Cluster Density R1 and Cluster Density R2

  1. On the configuration tab, select Lab Work.

  2. Select AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

  3. Under Record Details, remove Cluster Density R1 and Cluster Density R2 from Table Columns.

  1. On the configuration tab, select Custom Fields.

  2. Select Global Fields.

  3. Expand Container.

hashtag
6. Update AUTOMATED - Analysis Run Master Step

Update Master Step Configuration

  1. On the configuration tab, select Lab Work.

  2. Select AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) master step.

  3. Under Step Type, update Naming Convention to {SubmittedSampleName} {AppliedReagentLabels}

Rename Library Tube Strip Barcode to App Session ID

  1. On the configuration tab, select Custom Fields.

  2. Select Master Step Fields.

  3. Expand AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1).

hashtag
7. Upgrade Clarity LIMS Product Analytics Integration (if enabled)

circle-info

The changes are due to updates on container configuration.

  1. Upgrade to Clarity LIMS Product Analytics Integration v1.4.0

  2. Restart the CLPA integration service

Update Naming of Rows to Numeric.
  • Update Start at of Rows to 1.

  • Select BP Aliquot Volume (ul).
  • Update Decimal Places Displayed from 0 to 1.

  • , 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::); };' \ -exp '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::); };' \ -log {compoundOutputFileLuid1} \ -log {compoundOutputFileLuid1} \ -t true \ -t true \ && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:generate_sample_sheet -i {stepURI:v2} -u {username} -p {password} -c {compoundOutputFileLuid0} -l {compoundOutputFileLuid1}"

    Validate Sample Names, Retrieve ACT List and Register Step Started

    Assign Analysis Configuration Template

    Rename Cloud Run Id to Planned Run ID.
    Add Instrument Type field as specified in the image.
    Under Step Type, update Naming Convention to Lane {InputWellLocation:0,1}
    Delete RTA Version.
    Under Sample Table, update Sample Display Default to Expand.

    Select Save.

  • On the configuration tab, select Lab Work.

  • Select AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

  • Under Record Details, remove Reads PF R1 and Reads PF R2 from Table Columns.

  • Add Reads PF to Table Columns.

  • Select Save.

  • On the configuration tab, select Lab Work.

  • Select AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

  • Under Record Details, remove %PF R1 and %PF R2 from Table Columns.

  • Add % PF to Table Columns.

  • Add % Occupied field as specified in the image.
    Delete Cluster Density R1 and Cluster Density R2.
    Rename Library Tube Strip Barcode to App Session ID.

    Old Automation Name

    New Automation Name

    Used in Step

    Register NovaSeq X RunCompleted and Register Step Completed

    Register NovaSeq X Series Sequencing Run Completed

    AUTOMATED - Sequencing Run

    Register Step Started and Register NovaSeq X Run and Register NovaSeq X Run Association and Register NovaSeq X RunStarted

    Register NovaSeq X Series Sequencing Run Started

    AUTOMATED - Sequencing Run

    Validate Reagent Labels and Apply Selected ACT to Samples and Set Next Step

    Apply Selected ACT to Samples and Set Next Step

    Assign Analysis Configuration Template

    Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started

    Validate Flowcell Inputs, Analysis Configurations and Register Step Started

    Load to Library Tube Strip

    Validate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started

    systemctl restart clarity_upa

    Manual Upgrade

    NovaSeq X Series Integration Package v1.2.0 includes modifications to the existing NovaSeq X Series Sequencing workflows to support the following new features:

    • PhiX control included in the Dilute and Denature step instead of the Make Bulk Pool step.

    • Support for the new 1.5B and 25B flow cells.

    • Analysis tracking for the status and high level analysis result summary through the AUTOMATED - Analysis Run step (this is done at the metaworkflow level).

      âš  Analysis tracking is a new step in NovaSeq X Series protocol and cannot be added to a non-pending protocol or workflow. For analysis tracking at the metaworkflow level, do not proceed with the manual upgrade. Instead, install the NovaSeq X Series v1.2.0 Integration Package with the NovaSeq X Series Sequencing v1.1 protocol.

    • The following workflow updates are included in NovaSeq X Series Integration Package v1.2.0:

      • AUTOMATED - Sequencing Run step: Renamed the Library Tube Barcode master step custom field. This field is now named Library Tube Strip Barcode.

      • Load to Library Tube Strip step: Removed the Output Folder master step custom field.

    Use the following instructions to manually update the workflows.

    hashtag
    Prerequisites

    Illumina recommends upgrading to Illumina Preset Protocols (IPP) v2.7 to support the new features. If you do not have IPP v2.7 installed, do the following before starting the manual upgrade:

    • Install ClarityLIMS-NGS-Package-v5 RPM v5.24.

    • Replace the following files in /opt/gls/clarity/extensions/conf/driverfiletemplates:

    NovaSeqXSeries_Bulk_Pool1.csv:

    NovaSeqXSeries_Bulk_Pool2.csv:

    NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv:

    hashtag
    Add New Containers

    1. On the Configuration tab, select Consumables, and then select Containers.

    2. Add the following information to enable the Library 2-tube Strip container that supports the 1.5B flow cell:

      ℹ No action is required for the 25B flow cell. The flow cell uses the same Library 8-tube Strip as the 10B flow cell.

    hashtag
    Add New Master Step Fields

    Enable PhiX control in the Dilute and Denature step as follows.

    1. On the Configuration tab, select Custom Fields, and then select Master Step Fields.

    2. Add the following master step fields for the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step:

      Dilute and Denature (NovaSeq X Series Sequencing v1.x) Master Step Field Configuration

    hashtag
    Modify Existing Master Step Fields

    1. On the Configuration tab, select Custom Fields, and then select Master Step Fields.

    2. Modify the following master step fields:

      Make Bulk Pool (NovaSeq X Series Sequencing v1.x) Master Step Field Modifications

    hashtag
    Modify Existing Global Field

    1. On the Configuration tab, select Custom Fields, and then select Global Fields.

    2. For the NovaSeq X Flowcell Type field, update the Dropdown Items with the following values:

      ℹ A merge conflict is expected when upgrading from IPP v2.6 to v2.7 due to the changes in the NovaSeq X Flowcell Type field.

    hashtag
    Add, Configure, and Modify Automations

    Add Automation

    1. On the Configuration tab, select Automation, and then select Step Automation.

    2. On the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.x) step, add the following automation to enable new flow cell types:

      • Name: Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started

    Configure Automation Settings

    1. On the Configuration tab, select Lab Work.

    2. Configure the trigger location and style for the following automations:

      Load to Library Tube Strip (NovaSeq X Series Sequencing v1.x) Step Automation Configuration

      ℹ These configuration updates are required to enable the new flow cell types.

    Modify Step Automations

    1. On the Configuration tab, select Automation, and then select Step Automation.

    2. Select the Calculate Volumes automation that is enabled on the Make Bulk Pool (NovaSeq X Series Sequencing v1.x) step.

    3. Update the existing command line as follows.

      This modification is required to move the PhiX control from the Make Bulk Pool (NovaSeq X Series Sequencing v1.x) step to the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step. Changes are in red.

    hashtag
    Modify Existing Steps

    Enable PhiX Control

    1. On the Configuration tab, select Lab Work.

    2. Select the Make Bulk Pool (NovaSeq X Series Sequencing v1.x) step.

    3. For Control Types, remove PhiX v3.

    1. For the Record Details milestone, navigate to Step Data and remove the following fields:

      • Final Loading Volume (ul)

      • % PhiX (2.0 nM) Spike-In

    1. Select the Dilute and Denature (NovaSeq X Series v1.x) step.

    2. Select the Record Details milestone.

    3. Navigate to Step Data and add 1-2% PhiX Spike-In to Master Step Fields.

    Enable New Flow Cell Types

    1. On the Configuration tab, select Lab Work.

    2. Select the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.x) step.

    3. Select the Queue milestone.

    1. Select the Ice Bucket milestone.

    2. Navigate to Sample Table and add the NovaSeqX Flowcell Type field to Column Headers.

    3. Select the Placement milestone.

    Make Bulk Pool master step: Updated the dropdown items in the Final Loading Concentration (pM) custom field.
    For Container Name, enter Library 2-tube Strip.
  • For Rows, update the following fields:

    • Number: 2

    • Naming: Alphabetic

  • For Columns, update the following fields:

    • Number: 1

    • Naming: Numeric

    • Start at: 1

  • Additional Options and Dropdown Items

    PhiX Volume (ul)

    Numeric

    Read Only

    Decimal places displayed: 1

    1–2% PhiX Spike-In

    Toggle Switch

    Required Field

    Default: No

    Final Loading Concentration (pM)

    1. Update Dropdown Items with the following options:

      • 90

      • 140

    • Only perform this modification if the new Dropdown Items are required.

    • This modification is not required to enable support for the new flow cells or PhiX control in the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step.

    Flowcell Type

    1. Change Field Type from Text to Text Dropdown.

    2. Update Field Options as follows.

      • Read Only = No

    • This modification is required to support the new flow cells.

    Load to Library Tube Strip (NovaSeq X Series Sequencing v1.x) Master Step Field Modifications

    Field

    Modification

    Purpose/Notes

    Output Folder

    1. Remove the field.

    • If the step has been run previously and this field is used, it cannot be removed. This field does not affect the functionality of the workflow.

    • This modification is not required to enable support for the new flow cells or PhiX control in the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step.

    AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.x) Master Step Field Modifications

    Field

    Modification

    Purpose/Notes

    Library Tube Barcode

    1. Rename the field from Library Tube Barcode to Library Tube Strip Barcode.

    • If the installed NovaSeq X Series workflow is v1.1 or earlier, this modification is not required to enable support for the new flow cells or PhiX control in the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step.

    • For NovaSeq X Series workflow v1.2, this modification is required. Run event handling fails without this modification.

    1.5B
  • 10B

  • 25B

  • Channel Name: limsserver

  • Command line:

  • Automation

    Setting

    Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started

    • Trigger Location: Step

    • Trigger Style: Automatic upon entry

    Validate Input Count and Validate Analysis Configurations and Register Step Started

    • Trigger Location: Not used

    Dilute and Denature (NovaSeq X Series Sequencing v1.x) Step Automation Configuration

    ℹ This configuration update is required to enable PhiX control on the Make Bulk Pool (NovaSeq X Series Sequencing v1.x) step.

    Automation

    Setting

    Calculate Volumes

    • Trigger Location: Record Details

    • Trigger Style: Manual button

    bash -l -c "/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; }; 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 \ script:evaluateDynamicExpression \ -exp 'output.::Bulk Pool Volume (ul):: = 100 * step.::Number of Lanes to Sequence::; output.::NovaSeq X Flowcell Type:: = step.::Flowcell Type::; output.::Final Loading Concentration (pM):: = step.::Final Loading Concentration (pM)::; input.::Per Sample Volume (ul):: = 2 * output.::Bulk Pool Volume (ul):: / input.::Molarity (nM):: / output.::Number of Samples in Pool::; output.::Total Sample Volume (ul):: = 0;' -t true \ 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 (ul):: = 0 } else { output.::RSB Volume (ul):: = output.::Bulk Pool Volume (ul):: - output.::Total Sample Volume (ul):: }' -t true \ && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} script:driver_file_generator \ -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool1.csv -o 1.csv \ script:driver_file_generator \ -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool2.csv -o 2.csv \ && cat 1.csv 2.csv > {compoundOutputFileLuid0}.csv \ && /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 'output.::Number of Samples in Pool:: = ::::; output.::Total Sample Volume (ul):: = ::::; output.::Bulk Pool Volume (ul):: = ::::;' -t true \ && echo 'Calculate Volume completed successfully'"

  • Select the Calculate Volumes automation that is enabled on the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step.

  • Update the existing command line as follows.

    This modification is required to move the PhiX control from the Make Bulk Pool (NovaSeq X Series Sequencing v1.x) step to the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step and to enable support for the 1.5B and 25B flow cells. Changes are in red.

    bash -l -c "/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.::NovaSeq X Flowcell Type:: == ::10B:: || input.::NovaSeq X Flowcell Type:: == ::1.5B::) { output.::NaOH Volume (ul):: = 8.5; output.::TT2 Volume (ul):: = 127.5; output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 170 / (2 * 1000); output.::RSB Volume (ul):: = 34 - output.::BP Aliquot Volume (ul)::; if (step.::1-2% PhiX Spike-In::) { output.::PhiX Volume (ul):: = 1; output.::PhiX Concentration (pM):: = 300; } else { output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; }; } else { output.::NaOH Volume (ul):: = 14; output.::TT2 Volume (ul):: = 210; output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 280 / (2 * 1000); output.::RSB Volume (ul):: = 56 - output.::BP Aliquot Volume (ul)::; if (step.::1-2% PhiX Spike-In::) { output.::PhiX Volume (ul):: = 1.6; output.::PhiX Concentration (pM):: = 300; } else { output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; }; }' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} \ script:driver_file_generator \ -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv -o {compoundOutputFileLuid0}.csv -q true -destLIMSID {compoundOutputFileLuid0} -l {compoundOutputFileLuid1} \ && echo; echo 'Calculate Volumes completed successfully.'"

  • Select the Set Next Step automation that is enabled on the Dilute and Denature (NovaSeq X Series Sequencing v1.x) step.

  • Update the existing command line as follows.

    This modification is required to enable support for the 1.5B and 25B flow cells and future 8-tube library strips. Changes are in red.

    bash -l -c "/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.::Run Mode:: = input.::Run Mode::; output.::NovaSeq X Flowcell Type:: = input.::NovaSeq X Flowcell Type::; nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}"

  • Select the Validate Library Tube Strip Barcode automation that is enabled on the Load to Library Tube Strip Barcode (NovaSeq X Series Sequencing v1.x) step.

  • Update the existing command line as follows.

    This modification is required to enable support for the 1.5B and 25B flow cells and future 8-tube library strips. Changes are in red.

    bash -l -c "/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:validate_output_containers -l {compoundOutputFileLuid1} -r 'Library 8-tube Strip:LC[0-9]{7}-L[A-Z]{1}1' -r 'Library 2-tube Strip:LC[0-9]{7}-L[A-Z]{1}2' -max 1"

  • Navigate to Sample Table and add the NovaSeqX Flowcell Type field to Column Headers.
    Navigate to Destination Containers and add Library 2-tube Strip.

    Field Name

    Field Type

    Field

    Modification

    file-download
    356B
    NovaSeqXSeries_Bulk_Pool1.csv
    arrow-up-right-from-squareOpen
    file-download
    271B
    NovaSeqXSeries_Bulk_Pool2.csv
    arrow-up-right-from-squareOpen
    file-download
    672B
    NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv
    arrow-up-right-from-squareOpen

    Options

    Purpose/Notes

    bash -l -c "/opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} \
    script:validate_same_udf_value_for_analytes -f 'Run Mode' -f 'NovaSeq X Flowcell Type' \
    script:validate_selected_container \
    -fn 'NovaSeq X Flowcell Type' -fv '1.5B' -ct 'Library 2-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '10B' -ct 'Library 8-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '25B' -ct 'Library 8-tube Strip' && \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerRun script:validate_analysis_config script:validate_physical_logical_configurations && \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'"
    150
  • 160

  • 180

  • Custom Entries = No
  • Update Dropdown Items with the following options:

    • 1.5B

    • 10B

    • 25B

  • NovaSeq X Series v1.3.0

    The integration includes the following:

    • Preconfigured NovaSeq X Series Sequencing v1.2 workflow that maps to lab protocols and instrument runs.

    • Preconfigured protocols:

      • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2)

      • Make Bulk Pool (NovaSeq X Series Sequencing v1.2)

      • Dilute and Denature (NovaSeq X Series Sequencing v1.2)

      • Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2)

      • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2)

      • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2)

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

    • Automated generation of a samplesheet. The samplesheet will be used to start the sequencing run on NovaSeq X Series Control Software via Local run mode.

    • Automated creation of a planned run on Illumina Connected Analytics (ICA). The planned run created will be retrieved by NovaSeq X Series Control Software to start run via Cloud run mode.

    • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics from BaseSpace Sequence Hub (BSSH) into the LIMS.

    • Automated tracking of the NovaSeq X Series analysis run and high level analysis summary from BaseSpace Sequence Hub (BSSH) into the LIMS.

    • Support for configuration of multiple secondary analyses with multiple library prep kit (LPK) and index adapter kit (IAK) for the planned run. The analysis are either performed by the ICA in Cloud mode or by DRAGEN on-premise in Local mode.

    • (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 NovaSeq X Series Sequencing v1.2 workflow.

    • (Optional) Clarity LIMS Product Analytics (CLPA) integration which makes Clarity data available to the ICA service. CLPA integration installation and configuration is required. Refer to for details on configuring and using CLPA.

    User Interaction, Validation and Troubleshooting

    Last Updated: December 2024

    Release Date: September 2023

    Document Version: 2

    This section explains the user interaction for each step and how to validate the installation of the Illumina NovaSeq X Series Integration Package v1.1.0.

    The validation process involves the following actions:

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

    Clarity LIMS Product Analytics Integration v1.4 Configuration
  • 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 NovaSeq X Series Sequencing v1.0 workflow.

  • Running libraries through the NovaSeq X Series Sequencing v1.0 workflow validates the following items:

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

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

    • Automated sample sheet generation. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through the Local run mode.

    • Automated creation of a planned run in Illumina Connected Analytics (ICA). The control software retrieves the planned run. The run is started through the Cloud run mode.

    • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics into Clarity LIMS.

  • The validation steps assume that the following conditions have been met:

    • NovaSeq X Series Integration Package v1.1.0 is installed and you have imported the default Clarity LIMS configuration.

    • Analysis configuration templates (ACTs) are created in BaseSpace Sequence Hub for your run. Make sure that the index adapter kit label group is created in Clarity LIMS before selecting it in the ACT. This same label group is used in the Run Library Prep Validation v2.3.1 step. For more information on creating a reagent label group, refer to Add and Configure Labels and Label Groups in the Clarity LIMS (Clarity & LabLink Reference Guide) documentation. For the adapter sequences for your library prep kits, refer to Illumina Adapter Sequencesarrow-up-right.

    hashtag
    Analysis Configuration Template Creation in BaseSpace Sequence Hub

    You must create the Analysis Configuration Templates (ACTs) that are required for configuring secondary analysis in the NovaSeq X Series Sequencing v1.0 workflows. Create and delete ACTs in BaseSpace Sequence Hub. For instructions, refer to the BaseSpace Sequence Hub Online Help on the Illumina support sitearrow-up-right.

    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.1 and NovaSeq X Series Sequencing v1.0 workflows.

    1. On the Configuration tab, under Workflows, activate both the Library Prep Validation v2.3.1 and NovaSeq X Series Sequencing v1.0 workflows.

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

      âš  Only use alphanumeric, dash, or underscore characters in the submitted sample names. Invalid characters can cause a sample sheet validation failure in the Load to Library Tube Strip step.

    3. Assign the samples to the Library Prep Validation workflow.

    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 NovaSeq X Series Sequencing v1.0 workflow.

    Follow the steps in Library Prep Validation Protocol 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 = NovaSeq X Series

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

    hashtag
    Protocol: NovaSeq X Series Sequencing v1.0

    The NovaSeq X Series Sequencing v1.0 protocol consists of the following steps:

    • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0)

    • Make Bulk Pool (NovaSeq X Series Sequencing v1.0)

    • Dilute and Denature (NovaSeq X Series Sequencing v1.0)

    • Load To Library Tube Strip (NovaSeq X Series Sequencing v1.0)

    • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0)

    Each step contains a script to register the start time (upon step entry) and the time that the step is completed (upon step exit). This information is published to CLPA through ICA. These scripts are used only for CLPA support and can be incorporated as part of an automation that performs other functions.

    hashtag
    Step 1: Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.0 protocol. The samples are queued for the Assign Analysis Configuration Template (NovaSeq X Series 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 to start the Validate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started automation.

      The automation checks that the sample names do not use restricted characters and are within character limits and retrieves the list of ACTs that you can select. The automation also registers the start time of the step by publishing messages to CLPA through ICA. The part of the script for start time registration is used only for CLPA support.

    4. Select the applicable ACT to assign to the samples. The index adapter kit specified by the ACT must correspond with the label group used in .

    5. [Optional] Under Step Details, select Retrieve ACT Information to trigger the Retrieve ACT Information automation.

      This automation retrieves ACT information (e.g., Library Prep Kit, Index Adapter Kit, Reference Genome, and so on) and populates the fields in Clarity LIMS. These details are saved to the ACTMetadata.csv file that you can download. If you are not sure of the analysis configuration before starting the sequencing and analysis run, refer to the details in the file.

    6. 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 validates that the indexes applied to the libraries are valid for the selected ACT and assigns samples to it. All samples added to the Ice Bucket (mentioned above) are assigned to this ACT.

    7. Select Finish Step.

    To use multiple ACTs in a single run, repeat 2–7 for each ACT. For step 2, only add samples that are being assigned to that ACT into the Ice Bucket.

    hashtag
    Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.0)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.0 protocol. The samples are queued for the Make Bulk Pool (NovaSeq X Series 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.

    4. 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).

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

    1. [Optional] Create a new lot. For more information, refer to Add and Configure Reagent Kits and Lots in the Clarity LIMS (Clarity & LabLink Reference Guide) documentation.

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

      • Number of Lanes to Sequence — Used in volume calculations, to make sure that the volumes are sufficient for the number of times the pool is sequenced. This field is applied to all pools in the step.

      • 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. This field is prepopulated with the configured default value (200 ul), but can be edited if more volume is required.

      • Minimum Per Sample Volume (ul) — The minimum volume for each sample. This field is prepopulated with the configured default value (2 ul) 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.

      • % PhiX (2.0nM) Spike-In — The value entered in this field is used to calculate the volume of PhiX spike-in required.

      • Flowcell Type — This is a read-only field configured with the default value of B3.

    3. 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 fields. The automation is applied to control samples when they are indexed and molarity is specified. It also generates the calculation file in a CSV format which is available for download under Files placeholder section below.

    4. In the Sample Details table, select the pool next to the sample name to view details on the pool composition.

    1. 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 Dilute and Denature (NovaSeq X Series Sequencing v1.0) step.

    2. Select Finish Step.

    hashtag
    Step 3: Dilute and Denature (NovaSeq X Series Sequencing v1.0)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.0 protocol. The pool of samples queued for the Dilute and Denature (NovaSeq X Series Sequencing v1.0) displays.

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

    3. [Optional] On the Ice Bucket screen, set the number of derivatives to create (placed into the library tube strip) and select Begin Work.

      • On entry to the step, the Validate Inputs Flowcell Type and Register Step Started automation is triggered. This automation makes sure that the configured flow cell type is valid. The automation also registers the start time of the step by publishing messages to CLPA through ICA. The portion of the script used for start time registration is used only for CLPA support.

      • On entry to the Record Details screen, the Calculate Volumes automation is triggered. This automation sets the following values:

        • BP Aliquot Volume (ul)

    4. On the Record Details screen, the Reagent Lot Tracking section tracks the NaOH, Resuspension Buffer, and TT2 reagents used in the step. To add and activate reagent lots, refer to Add and Configure Reagent Kits and Lots in the .

    5. On the Record Details screen, perform the following actions:

      1. In the Reagent Lot Tracking section, select from the active lots displayed in each drop-down list.

      2. In the Sample Details table, the BP aliquot, RSB, NaOH, and TT2 reagent volume values are auto populated and read-only.

    6. In the Files area, download the Calculation File (CSV) and open it and view details on the RSB, NaOH, and TT2 volumes to add per working pool.

    7. Select Next Steps.

    8. Select Finish Step.

    hashtag
    Step 4: Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.0 protocol. The pool of samples are queued for the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step.

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

    3. On the Ice Bucket screen, select Begin Work to trigger the Validate Analysis Configurations and Register Step Started automation.

      Validate Analysis Configurations automation performs the following basic checks on the analysis configuration for each pool:

      • Pooled samples are within the maximum configuration limit.

      • Pooled samples have the sample type of analysis (Cloud or Local).

      • Pooled samples that have the same secondary analysis also have the same analysis version and settings.

      Register Step Started automation registers the start time of the step by publishing messages to CLPA through ICA. The portion of the script used for start time registration is used only for CLPA support.

    4. On the Placement screen, do as follows.

      1. Drag the pool into the Library 8-tube Strip in the Placed Samples area on the right.

      2. Scan or type the barcode of the Library 8-tube Strip into the Library 8-tube Strip container name field.

    5. 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 is from the ACT associated with the samples and no further analysis configuration is required. Refer to the following table for details.

      Fields Displayed on Record Details Screen of Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) Step

    6. 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.

      • Clarity consolidates sample/library information, run and analysis configuration details and send them to ICA to create a planned run and samplesheet for Cloud run mode.

    7. Select Next Steps.

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

    8. Select Finish Step to advance the pooled samples to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step. For more information on how to start the sequencing run for different run modes, refer to .

    9. To use multiple ACTs in a single run, repeat steps 1–3 for each ACT. The pool of samples (for different ACTs) are then queued for the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step to be added to the Ice Bucket.

    hashtag
    Step 5: AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0)

    This protocol contains the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step. This step is fully automated.

    triangle-exclamation

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

    The integration starts the step automatically and data from the run is parsed back into Clarity LIMS. 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

    • Output Folder

    • Current Read

    • Current Cycle

    • Library Tube Barcode

    • Flow Cell ID

    • Flow Cell Side

    • Flow Cell Type

    • Flow Cell Part Number

    • Flow Cell Lot Number

    • Flow Cell Expiration Date

    • Instrument ID

    • Instrument Type

    • Instrument Control Software Version

    • Sequencing Log

    chevron-rightSample Details Tablehashtag

    Summary metrics populate the following global custom fields:

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    • % Error Rate R1

    • % Error Rate R2

    • Yield (Gb) R1

    • Yield (Gb) R2

    • Reads PF R1

    • Reads PF R2

    • %PF R1

    • %PF R2

    • % Aligned R1

    • % Aligned R2

    • % Phasing R1

    • % Phasing R2

    • % Prephasing R1

    • % Prephasing R2

    • Intensity Cycle 1 R1

    • Intensity Cycle 1 R2

    • Cluster Density R1

    • Cluster Density R2

    hashtag
    Troubleshooting

    If an automation trigger does not appear to run its corresponding scripts, refer to the Troubleshooting Automation section in the Clarity LIMS (API & Database) documentation.

    hashtag
    Automated Step Does Not Start

    If the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step does not start, Clarity LIMS is likely not receiving sequencing run events from BaseSpace Sequence Hub correctly. Check for the following issues:

    1. Make sure that the NovaSeq X Control Software is configured properly as follows.

      1. Before you start the run, in the NovaSeq X Control Software, select the appropriate BaseSpace Sequence Hub region in the Hosting location drop-down list.

      1. Under Run Settings, check the boxes next to Cloud run monitoring and Cloud run storage.

      If there are issues after modifying the configuration settings on the NovaSeq X Control Software, contact Illumina Support.

    hashtag
    Automated Step Starts, But Does Not Complete

    If the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step starts, but does not complete, do as follows.

    1. Log in to Clarity LIMS and use one of the following methods to open the in-progress step:

      1. In Lab View, find the step in the Recent Activities pane.

      2. Search for the step in Clarity LIMS using the library tube strip barcode 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.

    hashtag
    Validate Analysis Configuration Automation Check Fails

    The Validate Analysis Configuration automation check is in the Make Bulk Pool (upon pooling) and Load to Library Tube Strip (upon step entry) steps. 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:

    • The analysis configuration after library pooling or during the planned run creation exceeds the configuration limit.

      Resolve this error as follows.

      • If the error occurs on the Make Bulk Pool step, reduce the number of analysis configurations for a pool. To reduce the number, reorganize the samples for the pooling step (eg, by pooling samples that have similar configurations together).

      • If the error occurs on the Load to Library Tube step, reduce the number of analysis configurations for the planned run by reorganizing the samples for multiple runs instead of a single run.

    • ACTs of samples in the same pool or planned run must have the same run mode (Local or Cloud).

      Resolve this error as follows.

      1. Abort the step and remove samples with ACTs that have conflicting run modes from the Ice Bucket.

    • ACTs of samples in the same pool or planned run that have the same secondary analysis must have the same analysis version.

      Resolve this error as follows.

      • If the error occurs on the Make Bulk Pool step, pool the samples again. Make sure that samples with the same secondary analysis, but conflicting analysis versions, are in different pools.

    • ACTs of samples in the same pool or planned run that have the same secondary analysis must have the same analysis settings. The analysis setting fields can differ for a different secondary analysis and are configured in BaseSpace Sequence Hub when the ACT is created.

      Resolve this error as follows.

      • If the error occurs on the Make Bulk Pool step, pool the samples again. Make sure that samples with the same secondary analysis, but conflicting analysis settings, are in different pools.

    hashtag
    Revision History

    Version

    Changes

    2

    • Updated Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.1) to remove instructions on adding control. PhiX control should be added via the % PhiX (2.0nM) Spike-In step field.

    1

    • Initial release.

    NovaSeq X Series v1.1.0

    The integration includes the following features:

    • Preconfigured NovaSeq X Series Sequencing v1.0 workflow that maps to lab protocols and instrument runs.

    • The following steps in the NovaSeq X Series Sequencing v1.0 preconfigured protocol:

      • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0)

      • Make Bulk Pool (NovaSeq X Series Sequencing v1.0)

      • Dilute and Denature (NovaSeq X Series Sequencing v1.0)

      • Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0)

      • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0)

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

    • Automated generation of the sample sheet. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through Local run mode.

    • Automated creation of a planned run on Illumina Connected Analytics (ICA). The NovaSeq X Series Control Software retrieves the planned run for use with the Cloud run mode.

    • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics into Clarity LIMS.

    • Support for configuration of multiple secondary analyses with multiple library prep kits (LPKs) and index adapter kits (IAKs) for the planned run. The analysis is either performed by ICA in Cloud mode or by DRAGEN on-board the instrument in Local mode.

    • [Optional] Preconfigured Library Prep Validation v2.3.1 workflow used for validation purposes only. The workflow contains a single-step protocol that models the library prep required to produce libraries that are ready for the NovaSeq X Series Sequencing v1.0 workflow. For more information, refer to .

    • [Optional] Clarity LIMS Product Analytics (CLPA) integration that can be used with ICA. The CLPA integration installation and configuration is required. For more information, refer to .

    User Interaction, Validation and Troubleshooting

    Last Updated: December 2024

    Release Date: February 2024

    Document Version: 2

    This section explains how to validate the installation of the Illumina NovaSeq X Series Integration Package v1.2.0.

    The validation process involves the following actions:

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

    NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting
    Clarity LIMS Product Analytics Integration v1.2 Configuration

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

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

    2. 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 have the sample type of analysis (Cloud or Local).

      • Pooled samples that have the same secondary analysis also have the same analysis version and settings.

    RSB Volume (ul)

  • NaOH Volume (ul)

  • TT2 Volume (ul)

  • The automation also generates the calculation file (CSV) and attaches it to the step. This file contains information about the volume of RSB, NaOH, and TT2 to add per working pool.

  • [Optional] In the Sample Details table, select the pool icon to view details of the working pool composition.

    The working pool number is appended to the bulk pool name so that you can identify which working pools are derived from the same bulk pool.

    Select Record Details.

    After exiting the Placement screen, the Validate Library Strip Tube Barcode automation makes sure that the library tube strip barcode conforms to the barcode mask LC[0-9]{7}-LC1.

    The selected Run Mode must correspond to the ACT type. Presets

    • Local¹

    • Cloud²

    Read 1 Cycles

    Presets

    • 151

    • 101

    • 51

    Read 2 Cycles

    Presets

    • 151

    • 101

    • 51

    Index 1 Cycles

    Presets

    • 0

    • 6

    • 8

    Index 2 Cycles

    Presets

    • 0

    • 6

    • 8

    ¹ The Run/Analysis configuration is imported manually to the NovaSeq X Series instrument through a sample sheet. The sample sheet generated on this step is downloaded and imported manually by the user on NovaSeq X Control Software to start the run. The downstream secondary analysis is done using the onboard DRAGEN module.

    ² The planned run configuration is downloaded to the NovaSeq X Series Instrument Control Software to start the run. The downstream secondary analysis is done on the cloud.

    ³ 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.

    Clarity consolidates sample/library information, run and analysis configuration details and send them to ICA to generate samplesheet for Local run mode.

    Make sure that all remaining samples in the Ice Bucket have ACTs with the same run modes.

  • Select Begin Work to continue the step.

  • If the error occurs on the Load to Library Tube step, reorganize the samples for the planned run. Make sure that samples with the same secondary analysis, but conflicting analysis versions, are in different runs.

    If the error occurs on the Load to Library Tube Strip step, reorganize the samples for the planned run. Make sure that samples with the same secondary analysis, but conflicting analysis settings, are in different runs.

    Field

    Value

    Run Name

    Enter the experiment name. Only alphanumeric characters, dashes, and underscores are permitted. No spaces.

    Library Prep Protocol
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    NovaSeq X Series Integration v1.1.0 Configuration

    Run Mode

  • 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 NovaSeq X Series Sequencing v1.1 workflow.

  • Running libraries through the NovaSeq X Series Sequencing v1.1 workflow validates the following items:

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

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

    • Automated sample sheet generation. This sample sheet is used to start the sequencing run on the NovaSeq X Series Control Software through the Local run mode.

    • Automated creation of a planned run in Illumina Connected Analytics ( ICA). The control software retrieves the planned run. The run is started through the Cloud run mode.

    • Automated tracking of the NovaSeq X Series sequencing run and parsing of run statistics from BaseSpace Sequence Hub to Clarity LIMS.

    • Automated tracking of the NovaSeq X Series analysis run and high level analysis summary from BaseSpace Sequence Hub to Clarity LIMS.

  • The validation steps assume that the following conditions have been met:

    • The NovaSeq X Series Integration v1.2.0 has a valid BaseSpace Sequence Hub account with an Enterprise or Professional subscription.

    • NovaSeq X Series Integration Package v1.2.0 is installed and you have imported the default Clarity LIMS configuration.

    • Analysis configuration templates (ACTs) are created in BaseSpace Sequence Hub (BaseSpace Sequence Hub) for your run. Make sure that the index adapter kit label group is created in Clarity LIMS before selecting it in the ACT. This same label group is used in the Run Library Prep Validation v2.3.2 step. For more information on creating a reagent label group, refer to Add and Configure Labels and Label Groups in the Clarity LIMS (Clarity & LabLink Reference Guide) documentation. For the adapter sequences for your library prep kits, refer to Illumina Adapter Sequencesarrow-up-right.

    hashtag
    Analysis Configuration Template Creation in BaseSpace Sequence Hub

    You must create the Analysis Configuration Templates (ACTs) that are required for configuring secondary analysis in the NovaSeq X Series Sequencing v1.1 workflows. Create and delete ACTs in BaseSpace Sequence Hub. For instructions, refer to the BaseSpace Sequence Hub Online Help on the Illumina support sitearrow-up-right.

    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.2 and NovaSeq X Series Sequencing v1.1 workflows.

    1. On the Configuration tab, under Workflows, activate both the Library Prep Validation v2.3.2 and NovaSeq X Series Sequencing v1.1 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 Library Tube Strip step.

    3. Assign the samples to the Library Prep Validation workflow.

    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 NovaSeq X Series Sequencing v1.1 workflow.

    Follow the steps in Library Prep Validation Protocol 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 = NovaSeq X Series

    On exit from the step, the Routing Script automation is triggered. This automation assigns samples to the first step of the NovaSeq X Series Sequencing v1.1 workflow, Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1).

    hashtag
    Protocol: NovaSeq X Series Sequencing v1.1

    The NovaSeq X Series Sequencing v1.1 protocol consists of the following steps:

    • Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

    • Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    • Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    • Load To Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

    Each step contains a script to register the start time (upon step entry) and the time that the step is completed (upon step exit). This information is published to CLPA through ICA. These scripts are used only for CLPA support and can be incorporated as part of an automation that performs other functions.

    hashtag
    Step 1: Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.1 protocol. The samples are queued for the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1) step.

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

    3. On the Ice Bucket screen, select Begin Work to start the Validate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started automation.

      The automation checks that the sample names do not use restricted characters and are within character limits and retrieves the list of ACTs that you can select. The automation also registers the start time of the step by publishing messages to CLPA through ICA. The part of the script for start time registration is used only for CLPA support.

    4. Select the applicable ACT to assign to the samples. The index adapter kit specified by the ACT must correspond with the label group used in .

    5. [Optional] In Step Details, select Retrieve ACT Information to trigger the Retrieve ACT Information automation.

      This automation retrieves ACT information (e.g., Library Prep Kit, Index Adapter Kit, Reference Genome, and so on) and populates the fields in Clarity LIMS. These details are saved to the ACTMetadata.csv file that you can download. If you are not sure of the analysis configuration before starting the sequencing and analysis run, refer to the details in the file.

    6. 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 validates that the indexes applied to the libraries are valid for the selected ACT and assigns samples to it. All samples added to the Ice Bucket (mentioned above) are assigned to this ACT.

    7. Select Finish Step.

    hashtag
    Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.1 protocol. The samples are queued for the Make Bulk Pool (NovaSeq X Series Sequencing v1.1) step.

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

      ℹ If PhiX control sample is required for the run, the configuration setting shall be performed in the Step 3: Dilute and Denature with the 1–2% PhiX Spike-In toggle switch.

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

    4. 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).

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

    1. [Optional] Create a new lot. For more information, refer to Add and Configure Reagent Kits and Lots in the Clarity LIMS (Clarity & LabLink Reference Guide) documentation.

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

      • Number of Lanes to Sequence — Used in volume calculations, to make sure that the volumes are sufficient for the number of times the pool is sequenced. This field is applied to all pools in the step.

      • Final Loading Concentration (pM) — The final loading concentration of the pool in the flow cell.

      • 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. This selection affects the computation of volumes in the Calculate Volumes automation that generates the calculation file. Select from the following options:

        • 1.5B

        • 10B

    3. 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.

    4. In the Sample Details table, select the pool next to the sample name to view details on the pool composition.

    1. 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 Dilute and Denature (NovaSeq X Series Sequencing v1.1) step.

    2. Select Finish Step.

    hashtag
    Step 3: Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.1 protocol. The pool of samples queued for the Dilute and Denature (NovaSeq X Series Sequencing v1.1) displays.

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

    3. [Optional] On the Ice Bucket screen, set the number of derivatives to create (placed into the library tube strip) and select Begin Work.

      • On entry to the step, the Validate Inputs Flowcell Type and Register Step Started automation is triggered. This automation makes sure that the configured flow cell type is valid. The automation also registers the start time of the step by publishing messages to CLPA through ICA. The portion of the script used for start time registration is used only for CLPA support.

      • If PhiX is used for the run, navigate to the Record Details screen and set 1–2% PhiX Spike-In to Yes.

      Select Calculate Volumes to trigger the Calculate Volume automation. This automation sets the following values:

      • BP Aliquot Volume (ul)

      • RSB Volume (ul)

      • NaOH Volume (ul)

      • TT2 Volume (ul)

    4. On the Record Details screen, the Reagent Lot Tracking section tracks the NaOH, Resuspension Buffer, and TT2 reagents used in the step. To add and activate reagent lots, refer to Add and Configure Reagent Kits and Lots in the .

    5. On the Record Details screen, perform the following actions:

      1. In the Reagent Lot Tracking section, select from the active lots displayed in each drop-down list.

      2. In the Sample Details table, make sure that the BP aliquot, RSB, NaOH, and TT2 reagent volume values are populated. The script sets these values and they cannot be edited.

    6. In the Files area, select the Calculation File (CSV) to open it and view details on the volumes for each reagent and sample pool used for the dilute and denature process.

    7. Select Next Steps.

    8. Select Finish Step.

    hashtag
    Step 4: Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    1. In Lab View, locate the NovaSeq X Series Sequencing v1.1 protocol. The pool of samples are queued for the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step.

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

    3. On the Ice Bucket screen, select one of the following destination container types:

      • Library 8-tube Strip

      • Library 2-tube Strip

    4. Select Begin Work to trigger the Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started automations.

      • The Validate Flowcell Inputs automation ensures that the correct container is selected for the flow cell type and that the number of inputs is the same as the number of available wells on the library tube strip. The Validate Analysis Configurations automation is similar to the automation used in the Make Bulk Pool step.

      • The Register Step Started automation also registers the start time of the step by publishing messages to CLPA through ICA. The portion of the script used for start time registration is used only for CLPA support.

    5. To use multiple ACTs in a single run, repeat Steps 1–4 for each ACT.

      The pool of samples for each ACT is then queued for the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step to be added to the Ice Bucket.

    6. On the Placement screen, do as follows.

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

      2. Scan or type the barcode of the library tube strip into the container name field.

    7. 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 is from the ACT associated with the samples and no further analysis configuration is required. Refer to the following table for details.

      Fields Displayed on Record Details Screen of Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) Step

    8. 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 and sends it to ICA when the Run Mode is Cloud.

    9. Select Next Steps.

      On the Assign Next Steps screen, the next step for the pooled samples is set to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

    10. Select Finish Step to advance the pooled samples to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step. For more information on how to start the sequencing run for different run modes, refer to .

    hashtag
    Step 5: AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    This protocol contains the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step. This step is fully automated.

    triangle-exclamation

    Do not add samples to the Ice Bucket or start or complete the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step. The integration does this automatically.

    The integration starts the step automatically and data from the run is parsed back into Clarity LIMS. 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

    • Output Folder

    • Current Read

    • Current Cycle

    • Library Tube Barcode

    • Flow Cell ID

    • Flow Cell Side

    • Flow Cell Type

    • Flow Cell Part Number

    • Flow Cell Lot Number

    • Flow Cell Expiration Date

    • Instrument ID

    • Instrument Type

    • Instrument Control Software Version

    • Sequencing Log

    chevron-rightSample Details Tablehashtag

    Summary metrics populate the following global custom fields:

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    • % Error Rate R1

    • % Error Rate R2

    • Yield (Gb) R1

    • Yield (Gb) R2

    • Reads PF R1

    • Reads PF R2

    • %PF R1

    • %PF R2

    • % Aligned R1

    • % Aligned R2

    • % Phasing R1

    • % Phasing R2

    • % Prephasing R1

    • % Prephasing R2

    • Intensity Cycle 1 R1

    • Intensity Cycle 1 R2

    • Cluster Density R1

    • Cluster Density R2

    hashtag
    Step 6: AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

    This protocol contains the AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) step. This step is fully automated.

    triangle-exclamation

    Do not add samples to the Ice Bucket or start or complete the AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) step. The integration does this automatically.

    The integration starts the step automatically and data from the run is parsed back into Clarity LIMS. User interaction is not required, but you can review the stages of the step in Clarity LIMS. If the run analysis 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

    • Analysis Result Location

    • Log

    After the analysis is complete, download the demultiplexing results and analysis results summary files from the file placeholders. Retrieve detailed analysis results from ICA.

    The demultiplexing results file contains the following demultiplexing statistics for each sample:

    • Number of reads

    • Number of perfect index reads

    • Number of mismatch index reads

    The analysis result summary file provides a summary of what analysis workflows were performed. This file also identifies the total number of samples analyzed and how many were completed or failed for each analysis.

    At this point, the entire NovaSeq X Series 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 Clarity LIMS (API & Database) documentation.

    hashtag
    Automated Step Does Not Start

    If the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step does not start, Clarity LIMS is likely not receiving sequencing run events from BaseSpace Sequence Hub correctly. Check for the following issues:

    1. Make sure that the NovaSeq X Control Software is configured properly as follows.

      1. Before you start the run, in the NovaSeq X Control Software, select the appropriate BaseSpace Sequence Hub region in the Hosting location drop-down list.

      1. Under Run Settings, check the boxes next to Cloud run monitoring and Cloud run storage.

      If there are issues after using the configuration settings on the NovaSeq X Control Software, contact Illumina Support.

    hashtag
    Automated Step Starts, But Does Not Complete

    If the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step starts, but does not complete, do as follows.

    1. Log in to the default user account and use one of the following methods to open the in progress step in Clarity LIMS:

      1. In Lab View, find the step in the Recent Activities pane.

      2. Search for the step in Clarity LIMS using the library tube strip barcode 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.

    hashtag
    Error When Creating Planned Runs

    If you receive an error when creating a planned run, check the log message in the Load to Library Tube Strip 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 and only select the ACTs that are compatible with the planned run.

    hashtag
    Validate Analysis Configuration Automation Check Fails

    The Validate Analysis Configuration automation check is in the Make Bulk Pool (upon pooling) and Load to Library Tube Strip (upon step entry) steps. If a failure happens, an error message displays and the step can be aborted, or you might be prevented from continuing the step. For NovaSeq X Series Integration v1.2, the configuration limits for the Cloud and Local modes are as follows.

    • Cloud — Maximum of seven applications and genome configurations (and, if needed, the BCL Convert Only application). Cloud mode also allows up to eight different library prep kits for each application and genome configuration.

    • Local — Maximum of three applications and genome configurations (and, if needed, the BCL Convert Only application). Local mode also allows up to eight different library prep kits for each application and genome configuration.

    This check can fail for the following reasons:

    • The analysis configuration after library pooling or during the planned run creation exceeds the configuration limit.

      Resolve this error as follows.

      • If the error occurs on the Make Bulk Pool step, reduce the number of analysis configurations for a pool. To reduce the number, reorganize the samples for the pooling step (eg, by pooling samples that have similar configurations together).

      • If the error occurs on the Load to Library Tube step, reduce the number of analysis configurations for the planned run by reorganizing the samples for multiple runs instead of a single run.

    • ACTs of samples in the same pool or planned run must have the same run mode (Local or Cloud).

      Resolve this error as follows.

      1. Abort the step and remove samples with ACTs that have conflicting run modes from the Ice Bucket.

    • ACTs of samples in the same pool or planned run that have the same secondary analysis must have the same analysis version.

      Resolve this error as follows.

      • If the error occurs on the Make Bulk Pool step, pool the samples again. Make sure that samples with the same secondary analysis, but conflicting analysis versions, are in different pools.

    • ACTs of samples in the same pool or planned run that have the same secondary analysis must have the same analysis settings. The analysis setting fields can differ for a different secondary analysis and are configured in BaseSpace Sequence Hub when the ACT is created.

      Resolve this error as follows.

      1. If the error occurs on the Make Bulk Pool step, pool the samples again. Make sure that samples with the same secondary analysis, but conflicting analysis settings, are in different pools.

    hashtag
    Revision History

    Version

    Changes

    2

    • Updated Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    1

    • Initial release.

    Type a custom value

    Type a custom value

    Type a custom value³

    Type a custom value³

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

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

    2. 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 have the sample type of analysis (Cloud or Local).

      • Pooled samples that have the same secondary analysis also have the same analysis version and settings.

    25B
  • PhiX Volume (ul) and Concentration (pM) (if there is a PhiX spike-in)

  • The automation also generates the calculation file (CSV) and attaches it to the step. This file contains information about the volume of RSB, NaOH, and TT2 to add per working pool. If there is a PhiX spike-in, the file also contains information on the PhiX volume and concentration.

  • [Optional] In the Sample Details table, select the pool icon to view details of the working pool composition.
    Select Record Details.

    After exiting the Placement screen, the Validate Library Strip Tube Barcode automation makes sure that the library tube strip barcode conforms to the barcode mask. For the Library 8-tube Strip, the barcode mask is LC[0-9]{7}-L[A-Z]{1}1 and an error message displays if the barcode does not match. For the Library 2-tube Strip, the barcode mask is LC[0-9]{7}-L[A-Z]{1}2.

    Presets

    • Local¹

    • Cloud²

    âš  The selected Run Mode must correspond to the ACT type.

    Read 1 Cycles

    Presets

    • 151

    • 101

    • 51

    Read 2 Cycles

    Presets

    • 151

    • 101

    • 51

    Index 1 Cycles

    Presets

    • 0

    • 6

    • 8

    Index 2 Cycles

    Presets

    • 0

    • 6

    • 8

    ¹ The Local run mode generates the sample sheet. The Run/Analysis configuration is imported manually to the NovaSeq X Series instrument through the sample sheet. The sample sheet is downloaded and imported manually by the user on NovaSeq X Control Software to start the run. The downstream secondary analysis is done using the onboard DRAGEN module.

    ² The Cloud run mode sends the Run/Analysis configuration to ICA. This configuration is downloaded to the NovaSeq X Series instrument through ICA to start the run. The downstream secondary analysis is done in the cloud.

    ³ 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.

    Generates the sample sheet and attaches it to the placeholder in the Files area on the Record Details screen for all Run Mode types.

    Make sure that all remaining samples in the Ice Bucket have ACTs with the same run modes.

  • Select Begin Work to continue the step.

  • If the error occurs on the Load to Library Tube step, reorganize the samples for the planned run. Make sure that samples with the same secondary analysis, but conflicting analysis versions, are in different runs.

    If the error occurs on the Load to Library Tube step, reorganize the samples for the planned run. Make sure that samples with the same secondary analysis, but conflicting analysis settings, are in different runs.

    Field

    Description

    Run Name

    Enter the experiment name. Only alphanumeric characters, dashes, and underscores are permitted. No spaces.

    Library Prep Protocol
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    NovaSeq X Series Integration v1.2.0 Configuration

    Run Mode

    Type a custom value

    Type a custom value

    Type a custom value³

    Type a custom value³

    Configuration

    The Illumina NovaSeq X Series Integration Package v1.1.0 supports the integration of Clarity LIMS to Illumina NovaSeq X series instruments.

    For user interactions for each step and instructions on validating and troubleshooting the Illumina NovaSeq X Series Integration, refer to NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting.

    triangle-exclamation

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

    circle-info

    The Illumina Universal Sample Identifier is a global field that is imported with the Library Prep Validation v2.3.1 and NovaSeq X Series Sequencing v1.0 workflows. Illumina Universal Sample Identifier is a text field that is reserved for CLPA support. The field is optional and not required for this integration.

    hashtag
    Prerequisites and Assumptions

    hashtag
    Analysis Configuration Template

    The NovaSeq X Series Sequencing v1.0 workflow uses analysis configuration templates (ACTs) to configure secondary analysis for planned runs. Required ACTs must be created using BSSH. The ACT names must be unique. The index adapter kit (the label group in Clarity LIMS) selected in the ACT is created in Clarity LIMS. The same label group must be used in the library preparation step. For more information, refer to .

    triangle-exclamation

    Make sure that ACT names created in BaseSpace Sequence Hub do not have leading or trailing spaces. Otherwise, Clarity LIMS can have issues with recognizing the ACT names.

    hashtag
    Samples

    Samples must go through the library preparation and quantification process before they enter the NovaSeq X Series Sequencing v1.0 workflow. It is assumed that the following steps have completed before samples are assigned to the workflow:

    • Samples have been accessioned into Clarity LIMS.

    • Samples have been run through QC and library prep.

    • Samples have the Molarity (nM) global field set to a value. This value is required for the Calculate Volumes automation in the Make Bulk Pool step. For more information on sample accessioning, refer to Sample Accessioning and Upload and Modify Samples in the Getting Started section of the .

    You can assign samples to workflows automatically, using a routing script, or manually—from the Projects & Samples dashboard. Refer to Assign and Process Samples in the .

    hashtag
    Workflows, Protocols, and Steps

    The NovaSeq X Series Integration Package v1.1.0 includes the following workflows:

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

    • NovaSeq X Series Sequencing v1.0

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

    hashtag
    Library Prep Validation v2.3.1 Workflow

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

    Purpose:

    • Included for validation purposes only, this protocol models the library prep steps required to advance samples to the NovaSeq X Series Sequencing v1.0 workflow.

    hashtag
    NovaSeq X Series Sequencing v1.0 Workflow

    chevron-rightProtocol 1: NovaSeq X Series Sequencing v1.0hashtag

    Purpose:

    • This protocol models the lab processes of run setup for starting a NovaSeq X Series sequencing run.

    Steps:

    hashtag
    Validation Workflow

    The Library Prep Validation v2.3.1 workflow allows for validation of the system after installation is complete. For details, refer to .

    hashtag
    Step 1: Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0)

    The Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0) step uses ACTs to configure secondary analysis for samples. Each ACT contains details related to the secondary analysis (eg, index adapter kit to use, reference genome setting, and so on). You can select an ACT from a list and assign samples to it. A planned run can have multiple ACTs and this step must be repeated for each ACT that is required for the run. For more information on creating ACTs and assigning samples to them, refer to .

    The following automations are configured on this step:

    • Validate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started²

    • Retrieve ACT Information

    • Validate Reagent Labels and Apply Selected ACT to Samples and Set Next Step

    ¹ These automations are required for CLPA support only.

    ² These automations are required for the NovaSeq X Series Sequencing v1.0 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.0 workflows.

    chevron-rightValidate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started Automationhashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that submitted sample names contain only alphanumeric, dash, and underscore characters.

    chevron-rightRetrieve ACT Information Automationhashtag

    Automatically triggered when you select Retrieve ACT Information on the Record Details screen, this automation completes the following actions:

    • Retrieves the details of the selected ACT and populates the step custom fields (eg, Analysis Version, Library Prep Kit, and so on).

    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 completes the following actions:

    • Checks that the molarity of all samples is specified.

    chevron-rightRegister Step Completed Automationhashtag

    Automatically triggered on exit of the step, this automation registers completion time of the step by publishing messages to CLPA through ICA.

    hashtag
    Master Step Fields

    The following table lists the configuration details for fields that are defined on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0) step.

    Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0) step.

    Global Field Configuration (Configured on Derived Sample)

    hashtag
    Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.0)

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

    The following automations are configured on this step:

    • Register Step Started¹

    • Validate Analysis Configurations

    • Calculate Volumes

    • Set Next Step

    ¹ These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.0 workflows.

    chevron-rightRegister Step Started Automationhashtag

    Automatically triggered on entry to the step, this automation registers the start time of the step by publishing messages to CLPA through ICA.

    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 are within the maximum configuration limit.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you select Calculate Volumes on the Record Details screen, this automation completes the following actions:

    • Proceeds if the sample has molarity values.

    • 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.

    chevron-rightRegister Pools & Register Step Completed Automationhashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the pool and library information used by the Clarity LIMS workflow. Samples in the pool are assumed to have gone through library prep.

    hashtag
    Master Step Fields

    The following table lists configuration details for the fields that are defined on the Make Bulk Pool (NovaSeq X Series Sequencing v1.0) step.

    Make Bulk Pool (NovaSeq X Series Sequencing v1.0) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Make Bulk Pool (NovaSeq X Series Sequencing v1.0) step.

    Global Custom Fields Configuration (Configured on Derived Sample)

    hashtag
    Step 3: Dilute and Denature (NovaSeq X Series Sequencing v1.0)

    The Dilute and Denature (NovaSeq X Series Sequencing v1.0) step allows you to dilute pooled samples with the addition of RSB.

    The following automations are configured on this step:

    • Validate Inputs Flowcell Type and Register Step Started²

    • Calculate Volumes

    • Set Next Step

    • Register Step Completed¹

    ¹ These automations are required for CLPA support only.

    ² These automations are required for the NovaSeq X Series Sequencing v1.0 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.0 workflows.

    chevron-rightValidate Inputs Flowcell Type and Register Step Startedhashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the specified flow cell type is valid.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you enter the Record Details screen, this automation completes the following actions:

    • Checks that the NovaSeq X Flowcell Type is B3 and sets NaOH Volume (ul) and TT2 Volume (ul) field values to 10 and 150.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step.

    chevron-rightRegister Step Completed Automationhashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Dilute and Denature (NovaSeq X Series Sequencing v1.0) step.

    Global Field Configuration (Configured on Derived Sample)

    hashtag
    Step 4: Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0)

    The Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step allows you to scan the library tube strip barcode into Clarity LIMS. Then, you can place the working pools into the library tube strip used in the NovaSeq X Series run. This step also does the following actions:

    • Validates the run setup and analysis information.

    • Generates the sample sheet file.

    • Creates a planned run on ICA, depending on the selected run mode.

    chevron-rightValidate Input Count and Validate Analysis Configurations and Register Step Started¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the number of input pools is the same as the number of tubes in the library tube strip.

    chevron-rightValidate Library Tube Strip Barcode Automationhashtag

    Automatically triggered on the Placement screen, this automation validates the library tube strip barcode to make sure that it conforms to the barcode mask LC[0-9]{7}-LC1.

    chevron-rightValidate Run Setup and Create Planned Run Automationhashtag

    Automatically triggered after a selection 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 in ICA, depending on the run mode.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.0 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.0 workflows.

    hashtag
    Master Step Fields

    The following table shows the master step fields that are configured on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step. These fields are required for sample sheet generation and planned run creation in ICA.

    Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) Master Step Field Configurationn

    hashtag
    Step 5: AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0)

    The AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step is fully automated. The integration starts the step, adds samples to the Ice Bucket, and completes the step. Data from the run is parsed back to Clarity LIMS. In this step, pooled samples in the library tube strip are sequenced on the NovaSeq X Series instrument.

    chevron-rightRegister Step Started & Register NovaSeq X Run & Register NovaSeq X Run Association & Register NovaSeq X RunStarted Automation¹hashtag

    Automatically triggered at the beginning of the step, this automation completes the following actions:

    • Registers the start time of the step.

    chevron-rightRegister NovaSeq X RunCompleted & Register Step Completed Automation¹hashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the sequencing run completion time, run status, and run metrics. This script requires the Cloud Run ID custom field from the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step.

    ¹ These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.0 workflows.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step.

    Clarity LIMS Master Step Field Information

    Other Clarity LIMS Master Step Fields

    hashtag
    Global Fields

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

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    • % Error Rate R1

    • % Error Rate R2

    At the end of the step, the pools of samples are automatically removed from the step. The step completes automatically when Run Status is RunCompletedSuccessfully.

    hashtag
    How the Integration Works

    The following information summarizes how the NovaSeq X Series integration works.

    • After the Validate Run Setup and Create Planned Run automation is triggered on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step, the run parameters entered in the Run Details screen are sent to ICA. The analysis configuration parameters from the selected ACTs are also sent to ICA. ICA validates the run and analysis configuration. If the validation fails, ICA sends an error message to Clarity LIMS. If the validation passes, ICA generates the sample sheet and sends it back to Clarity LIMS. ICA also creates the planned run based on the selected run mode (eg, Local or Cloud).

      • For the Local run mode, the sample sheet is generated and stored in Clarity LIMS. This sample sheet contains the run and analysis configuration information required to start the run on the NovaSeq X Series instrument.

    triangle-exclamation

    If a planned run with the same sample name and project name (case-insensitive) has been created previously in ICA, 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 NovaSeq X Series Instrument

    The following sections outline the steps to start a Clarity LIMS cloud or local run on the NovaSeq X Series instrument.

    hashtag
    Run Mode Configuration

    . Select Cloud run storage options under Run Settings.

    hashtag
    Start a Sequencing Run in Local Run or Cloud Run Modes

    You can start the sequencing run in BSSH for both the Local and Cloud modes. Make sure that you log in using the account that was used during the NovaSeq X Series integration package setup. You must also import the sample sheet created from the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.0) step for the Local Run Mode.

    chevron-rightStart a Sequencing Run in Local Run Modehashtag

    Follow instructions to start a sequencing run with local secondary analysis in .

    chevron-rightStart a Sequencing Run in Cloud Run Modehashtag

    Follow instructions to start a sequencing run with cloud secondary analysis in .

    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.

    Reagent Kits

    • Buffer Cartridge

    • Lyophilization Cartridge

    • NaOH

    • Reagent Cartridge

    Container Types

    • Library 8-Tube Strip

    • Tube This integration supports the library 8-tube strip with the barcode in the LC[0-9]{7}-LC1 format (eg, LC1234567-LC1).

    Control Types

    • PhiX v3

    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.

    The protocol contains a single step - Library Prep Validation v2.3.1. After this step, a routing script sends the samples to the first step of the NovaSeq X Series Sequencing v1.0 workflow (Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.0)).

    Steps:

    1. Library Prep Validation v2.3.1

    Assign Analysis Configuration Template (NovaSeq X Series 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 so that samples use valid labels.

  • Make Bulk Pool (NovaSeq X Series Sequencing v1.0)

    • The Calculate Volumes script assists with pooling samples and adding resuspension buffers and reagents.

    • The Validate Analysis Configurations automation validates the ACT of pooled samples to make sure that the secondary analysis configurations remain valid after pooling.

  • Dilute and Denature (NovaSeq X Series Sequencing v1.0)

    • The Calculate Volumes script helps denature and dilute samples from step 2 to the final loading concentration.

  • Load To Library Tube Strip (NovaSeq X Series Sequencing v1.0)

    • The library pools from step 3 are ready to be loaded to the NovaSeq X Series library tube strip.

    • Validates run and analysis information.

    • Generates the sample sheet and creates the planned run, depending on the run mode.

  • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0)

    • The step is fully automated and starts and completes automatically after the sequencing run is started and completed on the instrument side.

    • The sequencing run metadata (eg, run configuration, primary run metrics, and so on) are recorded automatically.

    • The integration does this step automatically. Do not add samples to the Ice Bucket or start or complete the step.

  • Register Step Completed¹
    Retrieves the list of ACTs that were created in BSSH.
  • Registers the start time of the step by publishing messages to CLPA through the ICA.

  • Saves the details into a file that is available to download. This file is stored in the Analysis Configuration Metadata file placeholder.
    Checks that all samples are indexed and for invalid indexes. The indexes applied are the same as the selected ACT.
  • Assigns the selected ACT to all samples in the step.

  • Sets the next step for samples to ADVANCE, which advances them to the next step in the protocol (Make Bulk Pool (NovaSeq X Series Sequencing v1.0)).

  • Text

    Read Only

    Reference Genome

    Text

    Read Only

    Secondary Analysis Mode

    Text

    Read Only

  • Register Pools & Register Step Completed¹

  • Pooled samples have the same type of analysis (eg, Cloud or Local).
  • Pooled samples that have the same secondary analysis also have the same analysis version (eg, v3.8.4) and analysis settings (eg, Map/Align Output Format = CRAM).

  • Uses the Bulk Pool Volume (ul) field and Number of Lanes to Sequence (x100) for the B3 flow cell type to calculate volumes needed for the 2 nM intermediate library pools.

  • Copies the Final Loading Concentration (pM) and 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.

  • If PhiX is used for a planned run (eg, a value for % PhiX (2.0 nM) Spike-In is specified), sets the PhiX Volume (ul).

  • Calculates the adjusted per sample volume for the pools.

  • 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 NovaSeqXSeries_Bulk_Pool1.csv and NovaSeqXSeries_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, Total Sample Volume (ul), and Bulk Pool Volume (ul) to null before exiting the step.

  • Sets the next step for samples to ADVANCE, which advances them to the Dilute and Denature (NovaSeq X Series Sequencing v1.0) step.

    Registers completion time of the step.

    This automation completes this action by publishing messages to CLPA through ICA.

    Flowcell Type

    Text

    • Required Field

    • Read Only

    • Default = B3

    Minimum Per Sample Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed = 2

    • Default = 2

    Number of Lanes to Sequence

    Numeric

    • Required Field

    • Range = 1–10

    • Decimal places displayed = 0

    PhiX Volume (ul)

    Numeric

    • Read Only

    • Hidden

    • Decimal places displayed = 1

    • Used for Calculate Volume script when there is PhiX spike-in.

    âš  Do not remove, rename, or modify this field as it can cause the integration to break.

    Registers the start time of the step by publishing messages to CLPA through ICA.
    Computes BP Aliquot Volume (ul) and RSB Volume (ul) required for the dilution of pools to the required final loading concentration.
  • Generates a single CSV file that contains information about the reagents volume required to dilute the working pools. The generated file is stored in the Calculation File placeholder in the Files section.

  • TT2 Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Performs basic checks on the secondary analysis configuration of the samples in the same planned run. The following checks are included in this script:
    • Secondary analysis configuration of samples in a planned run is within maximum configuration limit.

    • Samples in a planned run have the same type of analysis (eg, Cloud or Local).

    • Samples in the same pools that have the same secondary analysis (eg, Illumina DRAGEN Enrichment) also have the same analysis settings (eg, Map/Align Output Format = CRAM) and the same analysis version (eg, v3.8.4).

  • Registers the start time of the step by publishing messages to CLPA through ICA.

  • Run Name can only contain alphanumeric, dash, underscore, or period characters. Do not use spaces.
  • Run Name cannot 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. If you are in Cloud run mode, the automation creates the planned run in ICA. The sample sheet is attached to the step.

  • There is a backend validation of the sample sheet content in ICA. This validation makes sure that the sample sheet is valid to set up a Local mode run and that it is ready for use with DRAGEN applications.

    For more information on sample name character restrictions, refer to NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting.

    Output Folder

    Text

    Read 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 1–251

    • Presets

      • 51

    Read 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–251

    • Presets

      • 51

    Run Mode

    Text Dropdown

    Required Field

    Presets

    • Local

    • Cloud

    Run Name

    Text

    Required Field

    Registers the NovaSeq X Series sequencing run configuration.
  • Registers the association of the sequencing run with the samples by linking the Instrument Run ID with the sample ID.

  • Registers the time that the sequencing run started. This automation completes these actions by publishing messages to CLPA through ICA.

  • Registers the completion time of the step. This automation completes these actions by publishing messages to CLPA through ICA.

    Flow Cell ID

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the SerialNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Lot Number

    • RunParameters.xml

    • LotNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the LotNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Part Number

    • RunParameters.xml

    • PartNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the PartNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Side

    • RunParameters.xml

    • Side

    • Visible on Record Details screen.

    Flow Cell Type

    • RunParameters.xml

    • FlowCellType

    • Visible on Record Details screen.

    Instrument Control Software Version

    • RunParameters.xml

    • SystemSuiteVersion

    • Visible on Record Details screen.

    Instrument ID

    • RunParameters.xml

    • InstrumentSerialNumber

    • Visible on Record Details screen.

    Instrument Type

    • RunParameters.xml

    • InstrumentType

    • Visible on Record Details screen.

    Output Folder

    • RunParameters.xml

    • OutputFolder

    • Visible on Record Details screen.

    Library Tube Barcode

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the SerialNumber field under the ConsumableInfo field for SampleTube Type.

    Library Tube Lot Number

    • RunParameters.xml

    • LotNumber

    • Hidden

    • Corresponds to the value of the LotNumber field under the ConsumableInfo field for SampleTube Type.

    Run End Time

    • RunCompletionStatus.xml

    • RunEndTime

    • Hidden

    Run Name

    • RunParameters.xml

    • ExperimentName

    • Visible on Record Details screen.

    • Received from the message sent to the integration service.

    Hidden

    Run Start Time

    • Received from the message sent to the integration service.

    Hidden

    Yield (Gb) R1

  • Yield (Gb) R2

  • Reads PF R1

  • Reads PF R2

  • %PF R1

  • %PF R2

  • % Aligned R1

  • % Aligned R2

  • % Phasing R1

  • % Phasing R2

  • % Prephasing R1

  • % Prephasing R2

  • Intensity Cycle 1 R1

  • Intensity Cycle 1 R2

  • Cluster Density R1

  • Cluster Density R2

  • For the Cloud run mode, the planned run is created in ICA. The planned run contains the run and analysis configuration information required to start the run on the instrument. The sample sheet is generated and stored in Clarity LIMS for reference purposes.
  • When the sequencing run starts on the instrument, the NovaSeq X Series Control Software notifies BSSH. BSSH monitors the run and uses the Stratus Integration Service (SIS) to notify Clarity LIMS. The events are processed and the integration service retrieves the run information from BSSH. This information is used to populate the custom fields in the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step.

  • Other run events follow the same information flow. When sequencing is complete, the control software uploads the sequencing run data (primary metrics) and associated files to ICA. Then, Clarity LIMS retrieves the primary metrics and uses them to populate the fields in the Sample Details table (eg, % Error Rate R1). The custom fields (eg, Run Status, Current Read, and so on) on the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.0) step are updated using the run related information. If the sequencing run is successfully completed, the step automatically completes.

  • The analysis results are not tracked. You must log in to BSSH to retrieve the cloud analysis results. For local analysis, the secondary analysis results are found 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.

  • Resuspension Buffer (RSB)

  • TT2

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

  • The library tube strip barcode must be unique. There must not be multiple library tube strip containers with the same name in the 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 (NovaSeq X Series Sequencing v1.0) step must not be manually started or completed. This step is fully automated and the sequencing service does not update samples correctly if they have been manually started.

  • For the automated run to start successfully, you must select Validate Run Setup and Create Planned Run in the Load to Library Tube step.

  • Field Name

    Field Type

    Options

    Analysis Configuration Template

    Text Dropdown

    Required Field

    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

    Molarity (nM)

    Numeric

    Decimal places displayed = 2

    ACT Name

    Text

    Read Only

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    % PhiX (2.5 nM) Spike-In

    Numeric

    • Range = 0–100

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    Final Loading Volume (ul)

    Numeric

    • Required Field

    • Default = 200

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Decimal places displayed = 0

    • Presets

      • 225

      • 400

    RSB Volume (ul)

    Numeric

    • Read Only

    • Decimal places displayed = 2

    NovaSeq X Flowcell Type

    Text

    • Required Field

    • Read Only

    • Default = B3

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    BP Aliquot Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 0

    NaOH Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    RSB Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Cloud Run ID

    Text

    Read Only

    • Hidden

    • Used for creating a planned run in ICA.

    âš  Do not remove, rename, or modify this field as it can cause the integration to break.

    Index 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Index 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Field Name

    Source File

    Corresponding Field in Source File

    Additional Information

    Current Cycle

    • RunCompletionStatus.xml

    • CompletedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field.

    Current Read

    • RunCompletionStatus.xml

    • RunParameters.xml

    • CompletedReads

    • PlannedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field in RunCompletionStatus.xml and PlannedReads field in RunParameters.xml.

    Flow Cell Expiration Date

    • RunParameters.xml

    • ExpirationDate

    • Visible on Record Details screen.

    • Corresponds to the value in the ExpirationDate field under the ConsumableInfo field for FlowCell Type.

    Field Name

    Description

    Additional Information

    Run Status

    • Presets

      • RunStarted

      • RunCompletedSuccessfully

      • RunAbortedByUser

      • RunErroredOut

    • Set by the integration service.

    Visible on Record Details screen.

    Sequencing Log

    • Set by the integration service during the sequencing run.

    Visible on Record Details screen.

    BaseSpace Run ID

    • Received from the message sent to the integration service.

    Hidden

    ICA Project ID

    • Received from the message sent to the integration service.

    Hidden

    NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting
    NovaSeq X Series Integration v1.1.0 User Interaction, Validation and Troubleshooting
    Configure the run modearrow-up-right
    https://support-docs.illumina.com/IN/NovaSeqX/Content/IN/NovaSeqX/StartManual.htmarrow-up-right
    https://support-docs.illumina.com/IN/NovaSeqX/Content/IN/NovaSeqX/StartPlannedRun.htmarrow-up-right
    configured to ensure unique derived sample names

    Library Prep Kit

    Instrument Run ID

    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:assign_act -i {stepURI:v2} -u {username} -p {password} -a '{udf:Analysis Configuration Template}' -l {compoundOutputFileLuid1}
    nextStep = ::ADVANCE:
    if (step.::Flowcell Type:: == ::B3::) { output.::Bulk Pool Volume (ul):: = 100 * step.::Number of Lanes to Sequence::; }; output.::NovaSeq X Flowcell Type:: = step.::Flowcell Type::; output.::Final Loading Concentration (pM):: = step.::Final Loading Concentration (pM)::;
    input.::Per Sample Volume (ul):: = 2 * output.::Bulk Pool Volume (ul):: / input.::Molarity (nM):: / output.::Number of Samples in Pool::;
    if (step.hasValue(::% PhiX (2.0nM) Spike-In::)) { step.::PhiX Volume (ul):: = step.::% PhiX (2.0nM) Spike-In:: / 100 * step.::Final Loading Volume (ul)::; };
    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 (ul):: = 0 } else { output.::RSB Volume (ul):: = output.::Bulk Pool Volume (ul):: - output.::Total Sample Volume (ul):: }' -t true \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool1.csv -o 1.csv \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool2.csv -o 2.csv \
    && cat 1.csv 2.csv > {compoundOutputFileLuid0}.csv \
    -exp 'output.::Number of Samples in Pool:: = ::::; output.::Total Sample Volume (ul):: = ::::; output.::Bulk Pool Volume (ul):: = ::::;' -t true
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv -o {compoundOutputFileLuid0}.csv -q true -destLIMSID {compoundOutputFileLuid0} -l {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    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/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:generate_sample_sheet -i {stepURI:v2} -u {username} -p {password} -c {compoundOutputFileLuid0} -l {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 -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/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/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    if (!input.hasValue(::Molarity (nM)::)) { return; };
    /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 -h false -exp 'if (!input.hasValue(::NovaSeq X Flowcell Type::)){fail(::Invalid Flowcell Type custom field value. Please make sure all input samples have a value assigned for Flowcell Type custom field.::)}' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /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:validateSampleCount -min 8 -max 8
    /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:validate_output_containers -l {compoundOutputFileLuid1} -r 'Library 8-tube Strip:LC[0-9]{7}-LC1' -max 1
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_list -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_info -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_indexes -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_physical_logical_configurations -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool script:validate_analysis_config -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar script:validate_same_analyte_udf_value_for_all_inputs -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -f 'Run Mode' -perPool true
    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::;'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/pooling.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    /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.::NovaSeq X Flowcell Type:: == ::B3::) { output.::NaOH Volume (ul):: = 10; output.::TT2 Volume (ul):: = 150; }; output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 200 / (2 * 1000); output.::RSB Volume (ul):: = 40 - output.::BP Aliquot Volume (ul)::;'
    /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.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_physical_logical_configurations -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerRun script:validate_analysis_config -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerRun && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar script:validate_same_analyte_udf_value_for_all_inputs -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -f 'Run Mode' -perPool false
    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 and underscores. Run Name must start with alphanumeric, a dash or an underscore::);}
    output.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/register_novaseqxseries_run.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_associate_seqrun.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_completed.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    101
  • 151

  • 101
  • 151

  • Release Notes

    Last Updated: December 2024

    Release Date: December 2024

    These release notes describe the key changes to software components for the Clarity LIMS NovaSeq X Series Integration Package v1.3.0.

    hashtag
    Prerequisites

    • BaseSpace Sequence Hub account that has the Enterprise or Professional subscription

    hashtag
    Compatibility

    Refer to under Instruments & Integrations.

    hashtag
    New Features & Updates

    1. Updates on automations:

      • Register NovaSeq X RunCompleted and Register Step Completed

      • Register Step Started and Register NovaSeq X Run and Register NovaSeq X Run Association and Register NovaSeq X RunStarted

    circle-info

    Refer to for details on changes in automations, configuration and run metrics. Manual upgrade instructions from NovaSeq X Series Sequencing v1.1 workflow to v1.2 workflow are provided in .

    hashtag
    Known Limitations

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

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

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

    hashtag
    Known Issues

    1. 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.

    2. For BCL Convert only analysis, the high level analysis summary information is not available. Upon analysis successfully completed, an empty file is being attached at the AUTOMATED - Analysis Run step and the step is automatically completed.

    hashtag
    Documentations

    The NovaSeq X Series Integration v1.3.0 User Interaction, Validation and Troubleshooting guide follows exactly that of with the following updates:

    • Version updates:

      • NovaSeq X Series Integration Package version updated to v1.3.0.

      • NovaSeq X Series Sequencing workflow version updated to v1.2.

    Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started
  • Validate Reagent Labels and Apply Selected ACT to Samples and Set Next Step

  • Validate Run Setup and Create Planned Run

  • Validate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started

  • Updates on configuration:

    • Library 2-tube Strip and Library 8-tube Strip containers

    • BP Aliquot Volume (ul) derived sample global field

  • In the Load to Library Tube Strip step,

    • the master step field Cloud Run ID has been renamed to Planned Run ID.

    • a new step field Instrument Type is added.

  • In the AUTOMATED - Sequencing Run step,

    • the Derived Sample Generation configuration setting has been updated to Fixed with 1 Derived Sample generated.

    • removed unused RTA Version step field.

    • under Record Details milestone, the sample table is now expanded by default and run metrics in Sample Details table have been updated.

  • In the AUTOMATED - Analysis Run step,

    • the Library Tube Strip Barcode hidden master step field has been replaced with the App Session ID hidden field.

    • the Naming Convention under Step Type has been updated to {SubmittedSampleName}{AppliedReagentLabels}.

    • under Record Details milestone, the sample table is now expanded by default.

  • Library Prep Validation workflow version updated to v2.3.5.
  • Automation name update:

    • Validate Flowcell Inputs and Validate Analysis Configurations and Register Step Started automation updated to Validate Flowcell Inputs, Analysis Configurations and Register Step Started

  • Updates of run metrics displayed in Sample Details table of AUTOMATED - Sequencing Run step. Refer to NovaSeq X Series Integration v1.3.0 Configuration for the updated metrics.

  • Update of analysis configuration supported. Refer to Set Up Secondary Analysis in NovaSeq X Series documentationarrow-up-right for limits of the number of analysis application and reference genome combinations supported.

  • Compatibility
    NovaSeq X Series Integration v1.3.0 Configuration
    NovaSeq X Series Integration v1.3.0 Manual Upgrade
    NovaSeq X Series Integration v1.2.0

    Configuration

    The Illumina NovaSeq X Series Integration Package v1.3.0 supports the integration of Clarity LIMS to Illumina NovaSeq X series instruments.

    triangle-exclamation

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

    hashtag
    Prerequisites and Assumptions

    • The NovaSeq X Series Integration v1.3.0 requires a valid BaseSpace Sequence Hub account with an Enterprise or Professional subscription.

    • The required analysis configuration templates (ACTs), have been created on BaseSpace Sequence Hub.

      âš  ACT names created in BaseSpace Sequence Hub must not have leading or trailing spaces.

    hashtag
    Workflows, Protocols, and Steps

    The NovaSeq X Series Integration Package v1.3.0 includes the following workflows:

    • NovaSeq X Series Sequencing v1.2

    • 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 prep steps required to advance samples to the NovaSeq X Series Sequencing v1.2 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.

    hashtag
    NovaSeq X Series Sequencing v1.2 Workflow

    chevron-rightProtocol 1: NovaSeq X Series Sequencing v1.2hashtag

    Purpose:

    • This protocol models the lab processes of run setup for starting a NovaSeq X Series sequencing and secondary analysis run.

    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.

    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
    Step 1: Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2)

    The Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2) step uses ACTs to configure secondary analysis for samples. Each ACT contains details related to the secondary analysis (e.g., index adapter kit to use, reference genome setting, and so on). You can select an ACT from a list and assign samples to it. A planned run can have multiple ACTs and this step must be repeated for each ACT that is required for the run.

    chevron-rightValidate Sample Names, Retrieve ACT List and Register Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that submitted sample names contain only alphanumeric, dash, and underscore characters.

    chevron-rightRetrieve ACT Information Automationhashtag

    Automatically triggered when you select Retrieve ACT Information on the Record Details screen, this automation completes the following actions:

    • Retrieves the details of the selected ACT and populates the step custom fields (e.g., Analysis Version, Library Prep Kit, and so on).

    chevron-rightApply Selected ACT to Samples and Set Next Step Automationhashtag

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

    • Checks that the molarity of all samples is specified.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.2 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.2 workflows.

    hashtag
    Master Step Fields

    The following table lists the configuration details for fields that are defined on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2) step.

    Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2) step.

    Global Field Configuration (Derived Sample)

    hashtag
    Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.2)

    Samples are pooled in the Make Bulk Pool (NovaSeq X Series Sequencing v1.2) step. You can manually create working pools based on the final loading concentration required.

    chevron-rightRegister Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation registers the start time of the step. This automation completes this action by publishing messages to CLPA through ICA.

    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 are within the maximum configuration limit.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you select Calculate Volumes on the Record Details screen, this automation completes the following actions:

    • Proceeds if the sample has molarity values.

    • 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.

    chevron-rightRegister Pools and Register Step Completed Automation¹hashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the pool and library information used by the Clarity LIMS workflow. Samples in the pool are assumed to have gone through library preparation.

    ¹These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.2 workflows.

    hashtag
    Master Step Fields

    The following table lists configuration details for the fields that are defined on the Make Bulk Pool (NovaSeq X Series Sequencing v1.2) step.

    Make Bulk Pool (NovaSeq X Series Sequencing v1.2) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Make Bulk Pool (NovaSeq X Series Sequencing v1.2) step.

    Global Custom Fields Configuration (Derived Sample)

    hashtag
    Step 3: Dilute and Denature (NovaSeq X Series Sequencing v1.2)

    The Dilute and Denature (NovaSeq X Series Sequencing v1.2) step allows you to dilute pooled samples with the addition of RSB.

    chevron-rightValidate Inputs Flowcell Type and Register Step Started¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the specified flow cell type is valid.

      âš  This script is required for the NovaSeq X Series Sequencing v1.2 workflow to function properly.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you select Calculate Volumes on the Record Details screen, this automation completes the following actions based on the NovaSeq X Flowcell Type selected:

    • Sets the NaOH Volume (µl) and TT2 Volume (µl) field values.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.2 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.2 workflows.

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Dilute and Denature (NovaSeq X Series Sequencing v1.2) step.

    Global Field Configuration (Derived Sample)

    hashtag
    Step 4: Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2)

    The Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step allows you to scan the library tube strip barcode into Clarity LIMS. Then, you can place the working pools into the library tube strip used in the NovaSeq X Series run. This step also does the following actions:

    • Validates the run setup and analysis information.

    • Generates the sample sheet file.

    • Creates a planned run on Illumina Connected Analytics (ICA), depending on the selected run mode.

    chevron-rightValidate Flowcell Inputs, Analysis Configurations and Register Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the selected destination container types on the Load to Library Tube Strip step matches the selected flow cell type of the samples. The 1.5B flow cell is compatible with the library 2-tube strip and the 10B and 25B flow cells are compatible with the library 8-tube strip.

    chevron-rightValidate Library Tube Strip Barcode Automationhashtag

    Automatically triggered on the Placement screen, this automation validates the library tube strip barcode to make sure that it conforms to the barcode mask LC[0-9]{7}-LC1 for the library 8-tube strip and LC[0-9]{7}-L[A-Z]2 for the library 2-tube strip.

    chevron-rightValidate Run Setup and Create Planned Run Automationhashtag

    Automatically triggered after a selection 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 in ICA, depending on the run mode.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2) step.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.2 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.2 workflows.

    hashtag
    Master Step Fields

    The following table shows the master step fields that are configured on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step. These fields are required for sample sheet generation and planned run creation in ICA.

    Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) Master Step Field Configuration

    hashtag
    Step 5: AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2)

    triangle-exclamation

    Do not add samples to the Ice Bucket or start and complete the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2) step. The integration does this automatically.

    Data from the run is parsed back to Clarity LIMS. In this step, pooled samples in the library tube strip are sequenced on the NovaSeq X Series instrument.

    chevron-rightRegister NovaSeq X Series Sequencing Run Started Automation¹hashtag

    Automatically triggered at the beginning of the step, this automation completes the following actions:

    • Registers the start time of the step.

    chevron-rightRegister NovaSeq X Series Sequencing Run Completed Automation¹hashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the sequencing run completion time, run status, and run metrics. This script requires the Planned Run ID custom field from the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step.

    ¹ These automations are required for CLPA support only.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2) step.

    Clarity LIMS Master Step Field Information

    Other Clarity LIMS Master Step Fields

    hashtag
    Global Fields

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

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    • % Error Rate R1

    • % Error Rate R2

    At the end of the step, the pools of samples are automatically removed from the step. The step completes automatically when Run Status is RunCompletedSuccessfully.

    hashtag
    Step 6: AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2)

    triangle-exclamation

    Do not add samples to the Ice Bucket or start and complete the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2) 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 in Illumina Connected Analytics (ICA). There are no automations associated with this step.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2) step.

    AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2) Master Step Field Information

    hashtag
    How the Integration Works

    The following information summarizes how the NovaSeq X Series integration works.

    • After the Validate Run Setup and Create Planned Run automation is triggered on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step, the run parameters entered in the Run Details screen are sent to Illumina Connected Analytics (ICA). The analysis configuration parameters from the selected ACTs are also sent to ICA. ICA validates the run and analysis configuration. If the validation fails, ICA sends an error message to Clarity LIMS. If the validation passes, ICA generates the sample sheet and sends it back to Clarity LIMS. ICA also creates the planned run based on the selected run mode (e.g., Local or Cloud).

      • For the Local run mode, the sample sheet is generated and stored in Clarity LIMS. This sample sheet contains the run and analysis configuration information required to start the run on the NovaSeq X Series instrument.

    triangle-exclamation

    If a planned run with the same sample name and project name (case-insensitive) has been created previously, 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 NovaSeq X Series Instrument

    The following sections outline the steps to start a Clarity LIMS cloud or local run on the NovaSeq X Series instrument.

    chevron-rightRun Mode Configurationhashtag
    1. In the NovaSeq X Series Control Software, log in to the instrument using an account that has permissions for configuring settings.

    2. On the menu, select Settings, then select Cloud settings.

    chevron-rightStart a Sequencing Run in Local Run or Cloud Run Modeshashtag

    Start a Sequencing Run in Local Run Mode

    1. Log in with the BaseSpace Sequence Hub account and select the workgroup used during the NovaSeq X Series integration package installation.

    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.

    Reagent Kits

    • Buffer Cartridge

    • Lyophilization Cartridge

    • NaOH

    • Reagent Cartridge

    Container Types

    • Library 2-Tube Strip

    • Library 8-Tube Strip

    • Tube

    This integration supports the library 8-tube strip with the barcode in the LC[0-9]{7}-L[A-Z]1 format. The integration also supports the library 2-tube strip with the barcode in the LC[0-9]{7}-L[A-Z]2 format.

    Control Types

    • PhiX v3

    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.

    The index adapter kit configured in the ACT must be created as label group in Clarity LIMS and used in the library preparation step for indexing the samples.
  • Samples must go through the library preparation and quantification process before they enter the NovaSeq X Series Sequencing v1.2 workflow. It is assumed that the following steps have completed before samples are assigned to the workflow:

    • Samples have been accessioned into Clarity LIMS.

    • Samples have been run through QC and library prep.

    • Samples have the Molarity (nM) global field set to a value.

      This value is required for the Calculate Volumes automation in the Make Bulk Pool step.

    âš  Sample and library names must use only alphanumeric, dash, or underscore characters.

    For more information on sample accessioning, refer to Sample Accessioning and Upload and Modify Samples in the Getting Started section of the .

    You can assign samples to workflows automatically, using a routing script, or manually—from the Projects & Samples dashboard. Refer to Assign and Process Samples in the .

  • 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 NovaSeq X Series Sequencing v1.2 workflow (Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2)).

    Steps:

    1. Library Prep Validation v2.3.5

    Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2)

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

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

  • Make Bulk Pool (NovaSeq X Series Sequencing v1.2)

    • The Calculate Volume script assists with pooling samples and adding resuspension buffers and reagents.

    • The Validate Analysis Configurations automation validates the ACT of pooled samples to make sure that the secondary analysis configurations remain valid after pooling.

  • Dilute and Denature (NovaSeq X Series Sequencing v1.2)

    • The Calculate Volume script helps denature and dilute samples from step 2 to the final loading concentration.

  • Load To Library Tube Strip (NovaSeq X Series Sequencing v1.2)

    • The library pools from step 3 are ready to be loaded to the NovaSeq X Series library tube strip.

    • Validates run and analysis information.

    • Generates the sample sheet and creates the planned run, depending on the run mode.

  • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2)

    • The step is fully automated and starts and completes automatically after the sequencing run is started and completed on the instrument side.

    • The sequencing run metadata (e.g., run configuration, primary run metrics, and so on) are recorded automatically.

  • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2)

    • The step is fully automated and starts and completes automatically after the analysis run is started and completed in ICA.

    • The analysis run metadata (eg, status and high level analysis summary) 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.

    Retrieves the list of ACTs that were created in BaseSpace Sequence Hub.
  • Registers the start time of the step by publishing messages to CLPA through the ICA.

  • Saves the details into a file that is available to download. This file is stored in the Analysis Configuration Metadata file placeholder.
    Checks that all samples are indexed and for invalid indexes. The indexes applied are the same as the selected ACT.
  • Assigns the selected ACT to all samples in the step.

  • Sets the next step for samples to ADVANCE, which advances them to the next step in the protocol (Make Bulk Pool (NovaSeq X Series Sequencing v1.2)).

  • Text

    Read Only

    Reference Genome

    Text

    Read Only

    Secondary Analysis Mode

    Text

    Read Only

    Pooled samples have the same type of analysis (e.g., Cloud or Local).
  • Pooled samples that have the same secondary analysis also have the same analysis version (e.g., v3.8.4) and analysis settings (e.g., Map/Align Output Format = CRAM).

  • Uses the Bulk Pool Volume (ul) field and Number of Lanes to Sequence (x100) to calculate volumes needed for the 2 nM intermediate library pools.

  • Copies the Final Loading Concentration (pM) and 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 adjusted per sample volume for the pools.

  • 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 NovaSeqXSeries_Bulk_Pool1.csv and NovaSeqXSeries_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, Total Sample Volume (ul), and Bulk Pool Volume (ul) to null before exiting the step.

  • Sets the next step for samples to ADVANCE, which advances them to the Dilute and Denature (NovaSeq X Series Sequencing v1.2) step.

    Registers the completion time of the step.

    This automation completes this action by publishing messages to CLPA through ICA.

    Number of Lanes to Sequence

    Numeric

    • Required Field

    • Range: 1–10

    • Decimal places displayed: 0

    Registers the start time of the step by publishing messages to CLPA through ICA.

    Computes the BP Aliquot Volume (µl) and RSB Volume (µl) required for the dilution of pools to the required final loading concentration.

    ℹ The BP Aliquot Volume value is rounded up to the nearest µl. The value in the calculation file, however, is reflected with up to two decimal places.

  • Sets the PhiX Volume (µl) and PhiX Concentration (µl) if there is a PhiX spike-in.

  • Generates a single CSV file that contains information about the reagents volume required to dilute the working pools. The generated file is stored in the Calculation File placeholder in the Files section.

  • TT2 Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Performs basic checks on the secondary analysis configuration of the samples in the same planned run. The following checks are included in this script:
    • Secondary analysis configuration of samples in a planned run is within maximum configuration limit.

    • Samples in a planned run have the same type of analysis (e.g., Cloud or Local).

    • Samples in the same pools that have the same secondary analysis (e.g., Illumina DRAGEN Enrichment) also have the same analysis settings (e.g., Map/Align Output Format = CRAM) and the same analysis version (e.g., v3.8.4).

    âš  This script is required for the NovaSeq X Series Sequencing v1.2 workflow to function properly.

  • Registers the start time of the step by publishing messages to CLPA through ICA.

  • Run Name can only contain alphanumeric, dash, underscore, or period characters. Do not use spaces.
  • Run Name cannot 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 in ICA. The sample sheet is attached to the step.

  • There is a backend validation of the sample sheet content in ICA. This validation makes sure that the sample sheet is valid to set up a Local mode run and that it is ready for use with DRAGEN applications.

    Read 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 1–251

    • Presets

      • 51

    Read 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–251

    • Presets

      • 51

    Run Mode

    Text Dropdown

    • Required Field

    • Presets

      • Local

      • Cloud

    Run Name

    Text

    • Required Field

    Instrument Type

    Text

    • Read Only

    Registers the NovaSeq X Series sequencing run configuration.
  • Registers the association of the sequencing run with the samples by linking the Instrument Run ID with the sample ID.

  • Registers the time that the sequencing run started.

  • This automation completes these actions by publishing messages to CLPA through ICA.

    Registers the completion time of the step.

    This automation completes these actions by publishing messages to CLPA through ICA.

    Flow Cell ID

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the SerialNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Lot Number

    • RunParameters.xml

    • LotNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the LotNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Part Number

    • RunParameters.xml

    • PartNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the PartNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Side

    • RunParameters.xml

    • Side

    • Visible on Record Details screen.

    Flow Cell Type

    • RunParameters.xml

    • FlowCellType

    • Visible on Record Details screen.

    Instrument Control Software Version

    • RunParameters.xml

    • SystemSuiteVersion

    • Visible on Record Details screen.

    Instrument ID

    • RunParameters.xml

    • InstrumentSerialNumber

    • Visible on Record Details screen.

    Instrument Type

    • RunParameters.xml

    • InstrumentType

    • Visible on Record Details screen.

    Output Folder

    • RunParameters.xml

    • OutputFolder

    • Visible on Record Details screen.

    Library Tube Strip Barcode

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the SerialNumber field under the ConsumableInfo field for SampleTube Type.

    Library Tube Lot Number

    • RunParameters.xml

    • LotNumber

    • Hidden

    • Corresponds to the value of the LotNumber field under the ConsumableInfo field for SampleTube Type.

    Run End Time

    • RunCompletionStatus.xml

    • RunEndTime

    • Hidden

    Run Name

    • RunParameters.xml

    • ExperimentName

    • Visible on Record Details screen.

    • Received from the message sent to the integration service.

    Hidden

    Run Start Time

    • Received from the message sent to the integration service.

    Hidden

    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

  • For the Cloud run mode, the planned run is created in ICA. The planned run contains the run and analysis configuration information required to start the run on the instrument. The sample sheet is generated and stored in Clarity LIMS for reference purposes.
  • When the sequencing run starts on the instrument, the NovaSeq X Series Control Software notifies BaseSpace Sequence Hub. BaseSpace Sequence Hub monitors the run and notifies Clarity LIMS via the integration service. The events are processed and the integration service retrieves the run information from BaseSpace Sequence Hub. This information is used to populate the custom fields in the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.2) step.

  • Other run events follow the same information flow. When sequencing is complete, the control software uploads the sequencing run data (primary metrics) and associated files to ICA. Then, Clarity LIMS 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 (NovaSeq X Series Sequencing v1.2) 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 (NovaSeq X Series Sequencing v1.2) step. You must log in to BaseSpace Sequence Hub to retrieve the cloud analysis results. For local analysis, 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.

  • In Run Settings, select the Cloud run storage checkbox.

  • For Hosting location, select the applicable location from the drop-down options.

  • [Optional] For Private domain name, enter the domain name according to the workgroup that was configured with the NovaSeq X Series integration package.

  • Select Save.

  • Import the sample sheet created in the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.2) step. Refer to information on creating a local run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.
  • When the sample sheet is selected, the contents are validated. After the validation passes, select Next.

  • Select Save As Planned.

    Run and analysis data is parsed and auto-populates in the list of runs. For more information on planning a NovaSeq X Series run, refer to the Plan a NovaSeq X Series Run section of the BaseSpace Sequence Hub Online Help at help.basespace.illumina.comarrow-up-right and the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

  • Start the run. Refer to information on starting a planned run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

  • Start a Sequencing Run in Cloud Run Mode

    To start a sequencing run in cloud run mode, refer to information on starting a planned run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

    Resuspension Buffer (RSB)

  • TT2

  • All submitted samples must have an associated secondary analysis that is configured using the analysis configuration template (ACT). The ACT must be configured on BaseSpace Sequence Hub before starting the Assign Analysis Configuration Template step. The ACT names must be unique.

  • The library tube strip barcode must be unique. There must not be multiple library tube strip containers with the same name in the 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 (NovaSeq X Series Sequencing v1.2) and AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.2) steps must not be manually started or completed. These steps are fully automated and the sequencing service does not update samples correctly if they have been manually started.

  • For the automated run to start successfully, you must select Validate Run Setup and Create Planned Run in the Load to Library Tube step.

  • Field Name

    Field Type

    Options

    Analysis Configuration Template

    Text Dropdown

    Required Field

    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

    Molarity (nM)

    Numeric

    Decimal places displayed = 2

    ACT Name

    Text

    Read Only

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Dropdown Items

      • 90

      • 140

      • 150

      • 160

      • 180

    • Range from 0

    • Decimal places displayed: 0

    Flowcell Type

    Text

    • Required Field

    • Dropdown Items

      • 1.5B

      • 10B

      • 25B

    Minimum Per Sample Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed: 2

    • Default: 2

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Decimal places displayed: 0

    • Dropdown Items

      • 225

      • 400

    RSB Volume (ul)

    Numeric

    • Read Only

    • Decimal places displayed: 2

    NovaSeq X Flowcell Type

    Text Dropdown

    • Required Field

    • Read Only

    • Dropdown Items

      • 1.5B

      • 10B

      • 25B

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    BP Aliquot Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 1

    NaOH Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    RSB Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Planned Run ID

    Text

    • Read Only

    • Hidden

    ℹ Used for creating a planned run in ICA.

    Index 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Index 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Field Name

    Source File

    Corresponding Field in Source File

    Additional Information

    Current Cycle

    • RunCompletionStatus.xml

    • CompletedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field.

    Current Read

    • RunCompletionStatus.xml

    • RunParameters.xml

    • CompletedReads

    • PlannedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field in RunCompletionStatus.xml and PlannedReads field in RunParameters.xml.

    Flow Cell Expiration Date

    • RunParameters.xml

    • ExpirationDate

    • Visible on Record Details screen.

    • Corresponds to the value in the ExpirationDate field under the ConsumableInfo field for FlowCell Type.

    Field Name

    Description

    Additional Information

    Run Status

    • Presets

      • RunStarted

      • RunCompletedSuccessfully

      • RunAbortedByUser

      • RunErroredOut

    • Set by the integration service.

    Visible on Record Details screen.

    Sequencing Log

    • Set by the integration service during the sequencing run.

    Visible on Record Details screen.

    BaseSpace Run ID

    • Received from the message sent to the integration service.

    Hidden

    ICA Project ID

    • Received from the message sent to the integration service.

    Hidden

    Field Name

    Description

    Additional Information

    Analysis Status

    • Presets

      • Started

      • Completed

      • Failed

      • NeedsAttention

      • Stopped

      • TimedOut

      • CompletedWithErrors

    • Set by the integration service.

    Visible on Record Details screen.

    Analysis Result Location

    • Received from the message sent to the integration service.

    Visible on Record Details screen.

    App Session ID

    • Identified by the integration service using information from RunParameters.xml.

    Hidden

    configured to ensure unique derived sample names

    Library Prep Kit

    Instrument Run ID

    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 'NovaSeq X Series' \
    --WORKFLOW 'NovaSeq X Series v1.2' \
    --STEP 'Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.2)' \
    --INPUTS_OR_OUTPUTS 'OUTPUTS'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:assign_act -i {stepURI:v2} -u {username} -p {password} -a '{udf:Analysis Configuration Template}' -l {compoundOutputFileLuid1}
    nextStep = ::ADVANCE:
    output.::Bulk Pool Volume (ul):: = 100 * step.::Number of Lanes to Sequence::; output.::NovaSeq X Flowcell Type:: = step.::Flowcell Type::; output.::Final Loading Concentration (pM):: = step.::Final Loading Concentration (pM)::;
    input.::Per Sample Volume (ul):: = 2 * output.::Bulk Pool Volume (ul):: / input.::Molarity (nM):: / output.::Number of Samples in Pool::;output.::Total Sample Volume (ul):: = 0;' -t true
    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 (ul):: = 0 } else { output.::RSB Volume (ul):: = output.::Bulk Pool Volume (ul):: - output.::Total Sample Volume (ul):: }' -t true \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool1.csv -o 1.csv \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool2.csv -o 2.csv \
    && cat 1.csv 2.csv > {compoundOutputFileLuid0}.csv \
    -exp 'output.::Number of Samples in Pool:: = ::::; output.::Total Sample Volume (ul):: = ::::; output.::Bulk Pool Volume (ul):: = ::::;' -t true
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    bash -l -c "/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.::NovaSeq X Flowcell Type:: == ::10B:: || input.::NovaSeq X Flowcell Type:: == ::1.5B::) {
        output.::NaOH Volume (ul):: = 8.5;
        output.::TT2 Volume (ul):: = 127.5;
        output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 170 / (2 * 1000);
        output.::RSB Volume (ul):: = 34 - output.::BP Aliquot Volume (ul)::;
        if (step.::1-2% PhiX Spike-In::) { 
            output.::PhiX Volume (ul):: = 1; output.::PhiX Concentration (pM):: = 300; 
        }else { 
            output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; 
        };
    } else {
        output.::NaOH Volume (ul):: = 14;
        output.::TT2 Volume (ul):: = 210;
        output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 280 / (2 * 1000);
        output.::RSB Volume (ul):: = 56 - output.::BP Aliquot Volume (ul)::;
        if (step.::1-2% PhiX Spike-In::) { 
            output.::PhiX Volume (ul):: = 1.6; output.::PhiX Concentration (pM):: = 300; 
        }
        else { 
            output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; 
        };
    }'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv -o {compoundOutputFileLuid0}.csv -q true -destLIMSID {compoundOutputFileLuid0} -l {compoundOutputFileLuid1} \
    && echo; echo 'Calculate Volumes completed successfully.'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    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/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:generate_sample_sheet -i {stepURI:v2} -u {username} -p {password} -c {compoundOutputFileLuid0} -l {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 -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/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/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    if (!input.hasValue(::Molarity (nM)::)) { return; };
    /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 -h false -exp 'if (!input.hasValue(::NovaSeq X Flowcell Type::)){fail(::Invalid Flowcell Type custom field value. Please make sure all input samples have a value assigned for Flowcell Type custom field.::)}' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} \
    script:validate_same_udf_value_for_analytes -f 'Run Mode' -f 'NovaSeq X Flowcell Type' \
    script:validate_selected_container \
    -fn 'NovaSeq X Flowcell Type' -fv '1.5B' -ct 'Library 2-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '10B' -ct 'Library 8-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '25B' -ct 'Library 8-tube Strip'
    /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:validate_output_containers -l {compoundOutputFileLuid1} -r 'Library 8-tube Strip:LC[0-9]{7}-L[A-Z]1' -r 'Library 2-tube Strip:LC[0-9]{7}-L[A-Z]2' -max 1
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_list -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_info -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_indexes -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_physical_logical_configurations -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool script:validate_analysis_config -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar script:validate_same_analyte_udf_value_for_all_inputs -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -f 'Run Mode' -perPool true
    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::;'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/pooling.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /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.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerRun script:validate_analysis_config script:validate_physical_logical_configurations
    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::);}
    output.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/register_novaseqxseries_run.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_associate_seqrun.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_completed.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    101
  • 151

  • 101
  • 151

  • Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation

    Configuration

    The Illumina NovaSeq X Series Integration Package v1.2.0 supports the integration of Clarity LIMS to Illumina NovaSeq X series instruments.

    For instructions on validating and troubleshooting the Illumina NovaSeq X Series Integration, refer to NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting.

    triangle-exclamation

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

    hashtag
    Prerequisites and Assumptions

    triangle-exclamation

    The NovaSeq X Series Integration v1.2.0 requires a valid BaseSpace Sequence Hub account with an Enterprise or Professional subscription.

    hashtag
    Analysis Configuration Template

    The NovaSeq X Series Sequencing v1.1 workflow uses analysis configuration templates (ACTs) to configure secondary analysis for planned runs. Required ACTs must be created using BaseSpace Sequence Hub. The ACT names must be unique. The index adapter kit (the label group in Clarity LIMS) selected in the ACT is created in Clarity LIMS. The same label group must be used in the library preparation step. For more information, refer to .

    triangle-exclamation

    Make sure that ACT names created in BaseSpace Sequence Hub do not have leading or trailing spaces. Otherwise, Clarity LIMS can have issues with recognizing the ACT names.

    hashtag
    Samples

    Samples must go through the library preparation and quantification process before they enter the NovaSeq X Series Sequencing v1.1 workflow. It is assumed that the following steps have completed before samples are assigned to the workflow:

    • Samples have been accessioned into Clarity LIMS.

    • Samples have been run through QC and library prep.

    • Samples have the Molarity (nM) global field set to a value.

      This value is required for the Calculate Volumes automation in the Make Bulk Pool step.

    triangle-exclamation

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

    For more information on sample accessioning, refer to Sample Accessioning and Upload and Modify Samples in the Getting Started section of the .

    You can assign samples to workflows automatically, using a routing script, or manually—from the Projects & Samples dashboard. Refer to Assign and Process Samples in the .

    hashtag
    Workflows, Protocols, and Steps

    The NovaSeq X Series Integration Package v1.2 includes the following workflows:

    • NovaSeq X Series Sequencing v1.1

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

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

    hashtag
    Library Prep Validation v2.3.2 Workflow

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

    Purpose:

    • Included for validation purposes only, this protocol models the library prep steps required to advance samples to the NovaSeq X Series Sequencing v1.1 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
    NovaSeq X Series Sequencing v1.1 Workflow

    chevron-rightProtocol 1: NovaSeq X Series Sequencing v1.1hashtag

    Purpose:

    • This protocol models the lab processes of run setup for starting a NovaSeq X Series sequencing and secondary analysis run.

    Steps:

    hashtag
    Validation Workflow

    The Library Prep Validation v2.3.2 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 .

    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
    Step 1: Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

    The Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1) step uses ACTs to configure secondary analysis for samples. Each ACT contains details related to the secondary analysis (e.g., index adapter kit to use, reference genome setting, and so on). You can select an ACT from a list and assign samples to it. A planned run can have multiple ACTs and this step must be repeated for each ACT that is required for the run. For more information on creating ACTs and assigning samples to them, refer to .

    chevron-rightValidate Sample Names and Retrieve Analysis Configuration Template List and Register Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that submitted sample names contain only alphanumeric, dash, and underscore characters.

    chevron-rightRetrieve ACT Information Automationhashtag

    Automatically triggered when you select Retrieve ACT Information on the Record Details screen, this automation completes the following actions:

    • Retrieves the details of the selected ACT and populates the step custom fields (e.g., Analysis Version, Library Prep Kit, and so on).

    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 completes the following actions:

    • Checks that the molarity of all samples is specified.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.1 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.1 workflows.

    hashtag
    Master Step Fields

    The following table lists the configuration details for fields that are defined on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1) step.

    Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1) step.

    Global Field Configuration (Derived Sample)

    hashtag
    Step 2: Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    Samples are pooled in the Make Bulk Pool (NovaSeq X Series Sequencing v1.1) step. You can manually create working pools based on the final loading concentration required.

    chevron-rightRegister Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation registers the start time of the step. This automation completes this action by publishing messages to CLPA through ICA.

    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 are within the maximum configuration limit.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you select Calculate Volumes on the Record Details screen, this automation completes the following actions:

    • Proceeds if the sample has molarity values.

    • 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.

    chevron-rightRegister Pools & Register Step Completed Automation¹hashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the pool and library information used by the Clarity LIMS workflow. Samples in the pool are assumed to have gone through library preparation.

    ¹These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.1 workflows.

    hashtag
    Master Step Fields

    The following table lists configuration details for the fields that are defined on the Make Bulk Pool (NovaSeq X Series Sequencing v1.1) step.

    Make Bulk Pool (NovaSeq X Series Sequencing v1.1) Master Step Field Configuration

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Make Bulk Pool (NovaSeq X Series Sequencing v1.1) step.

    Global Custom Fields Configuration (Derived Sample)

    hashtag
    Step 3: Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    The Dilute and Denature (NovaSeq X Series Sequencing v1.1) step allows you to dilute pooled samples with the addition of RSB.

    chevron-rightValidate Inputs Flowcell Type and Register Step Started¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the specified flow cell type is valid.

      âš  This script is required for the NovaSeq X Series Sequencing v1.1 workflow to function properly.

    chevron-rightCalculate Volumes Automationhashtag

    Automatically triggered when you select Calculate Volumes on the Record Details screen, this automation completes the following actions based on the NovaSeq X Flowcell Type selected:

    • Sets the NaOH Volume (µl) and TT2 Volume (µl) field values.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.1 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.1 workflows.

    hashtag
    Global Fields

    The following table lists the global custom fields that are configured to display on the Dilute and Denature (NovaSeq X Series Sequencing v1.1) step.

    Global Field Configuration (Derived Sample)

    hashtag
    Step 4: Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    The Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step allows you to scan the library tube strip barcode into Clarity LIMS. Then, you can place the working pools into the library tube strip used in the NovaSeq X Series run. This step also does the following actions:

    • Validates the run setup and analysis information.

    • Generates the sample sheet file.

    • Creates a planned run on Illumina Connected Analytics (ICA), depending on the selected run mode.

    chevron-rightValidate Flowcell Inputs and Validate Analysis Configurations and Register Step Started Automation¹hashtag

    Automatically triggered on entry to the step, this automation completes the following actions:

    • Checks that the selected destination container types on the Load to Library Tube Strip step matches the selected flow cell type of the samples. The 1.5B flow cell is compatible with the library 2-tube strip and the 10B and 25B flow cells are compatible with the library 8-tube strip.

    chevron-rightValidate Library Tube Strip Barcode Automationhashtag

    Automatically triggered on the Placement screen, this automation validates the library tube strip barcode to make sure that it conforms to the barcode mask LC[0-9]{7}-LC1 for the library 8-tube strip and LC[0-9]{7}-L[A-Z]2 for the library 2-tube strip.

    chevron-rightValidate Run Setup and Create Planned Run Automationhashtag

    Automatically triggered after a selection 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 in ICA, depending on the run mode.

    chevron-rightSet Next Step Automationhashtag

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

    • Copies the Run Mode from input to output.

    • Sets the next step for samples to ADVANCE, advancing them to the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

    chevron-rightRegister Step Completed Automation²hashtag

    Automatically triggered on exit of the step, this automation registers the completion time of the step by publishing messages to CLPA through ICA.

    ¹ These automations are required for the NovaSeq X Series Sequencing v1.1 workflows and contain additional logic needed for CLPA support. If you would like to remove support for CLPA, contact Illumina Support.

    ² These automations are required for CLPA support only.

    All remaining automations are required for the NovaSeq X Series Sequencing v1.1 workflows.

    hashtag
    Master Step Fields

    The following table shows the master step fields that are configured on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step. These fields are required for sample sheet generation and planned run creation in ICA.

    Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) Master Step Field Configuration

    hashtag
    Step 5: AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    The AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step is fully automated. The integration starts the step, adds samples to the Ice Bucket, and completes the step. Data from the run is parsed back to Clarity LIMS. In this step, pooled samples in the library tube strip are sequenced on the NovaSeq X Series instrument.

    triangle-exclamation

    Do not add samples to the Ice Bucket or start and complete the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step. The integration does this automatically.

    chevron-rightRegister Step Started & Register NovaSeq X Run & Register NovaSeq X Run Association & Register NovaSeq X RunStarted Automation¹hashtag

    Automatically triggered at the beginning of the step, this automation completes the following actions:

    • Registers the start time of the step.

    chevron-rightRegister NovaSeq X RunCompleted & Register Step Completed Automation¹hashtag

    Automatically triggered on exit of the step, this automation completes the following actions:

    • Registers the sequencing run completion time, run status, and run metrics. This script requires the Cloud Run ID custom field from the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step.

    ¹ These automations are required for CLPA support only.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

    Clarity LIMS Master Step Field Information

    Other Clarity LIMS Master Step Fields

    hashtag
    Global Fields

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

    • % Bases >=Q30 R1

    • % Bases >=Q30 R2

    • % Error Rate R1

    • % Error Rate R2

    At the end of the step, the pools of samples are automatically removed from the step. The step completes automatically when Run Status is RunCompletedSuccessfully.

    hashtag
    Step 6: AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

    The AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) step is fully automated. The integration starts and completes the step 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 in Illumina Connected Analytics (ICA). There are no automations associated with this step.

    triangle-exclamation

    Do not add samples to the Ice Bucket or start and complete the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step. The integration does this automatically.

    hashtag
    Master Step Fields

    The following tables show the master step fields that are configured on the AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) step.

    triangle-exclamation

    Do not modify the names of the master step fields. Modifications cause the integration to break.

    AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) Master Step Field Information

    hashtag
    How the Integration Works

    The following information summarizes how the NovaSeq X Series integration works.

    • After the Validate Run Setup and Create Planned Run automation is triggered on the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step, the run parameters entered in the Run Details screen are sent to Illumina Connected Analytics (ICA). The analysis configuration parameters from the selected ACTs are also sent to ICA. ICA validates the run and analysis configuration. If the validation fails, ICA sends an error message to Clarity LIMS. If the validation passes, ICA generates the sample sheet and sends it back to Clarity LIMS. ICA also creates the planned run based on the selected run mode (e.g., Local or Cloud).

      • For the Local run mode, the sample sheet is generated and stored in Clarity LIMS. This sample sheet contains the run and analysis configuration information required to start the run on the NovaSeq X Series instrument.

    triangle-exclamation

    If a planned run with the same sample name and project name (case-insensitive) has been created previously in ICA, 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 NovaSeq X Series Instrument

    The following sections outline the steps to start a Clarity LIMS cloud or local run on the NovaSeq X Series instrument.

    chevron-rightRun Mode Configurationhashtag
    1. In the NovaSeq X Series Control Software, log in to the instrument using an account that has permissions for configuring settings.

    2. On the menu, select Settings, then select Cloud settings.

    chevron-rightStart a Sequencing Run in Local Run or Cloud Run Modeshashtag

    Start a Sequencing Run in Local Run Mode

    1. Log in with the BaseSpace Sequence Hub account and select the workgroup used during the NovaSeq X Series integration package installation.

    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.

    Reagent Kits

    • Buffer Cartridge

    • Lyophilization Cartridge

    • NaOH

    • Reagent Cartridge

    Container Types

    • Library 2-Tube Strip

    • Library 8-Tube Strip

    • Tube

    This integration supports the library 8-tube strip with the barcode in the LC[0-9]{7}-L[A-Z]1 format. The integration also supports the library 2-tube strip with the barcode in the LC[0-9]{7}-L[A-Z]2 format.

    Control Types

    • PhiX v3

    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.

    .
  • The protocol contains a single step - Library Prep Validation v2.3.2. After this step, a routing script sends the samples to the first step of the NovaSeq X Series Sequencing v1.1 workflow (Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)).

  • Steps:

    1. Library Prep Validation v2.3.2

    Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)

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

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

  • Make Bulk Pool (NovaSeq X Series Sequencing v1.1)

    • The Calculate Volume script assists with pooling samples and adding resuspension buffers and reagents.

    • The Validate Analysis Configurations automation validates the ACT of pooled samples to make sure that the secondary analysis configurations remain valid after pooling.

  • Dilute and Denature (NovaSeq X Series Sequencing v1.1)

    • The Calculate Volume script helps denature and dilute samples from step 2 to the final loading concentration.

  • Load To Library Tube Strip (NovaSeq X Series Sequencing v1.1)

    • The library pools from step 3 are ready to be loaded to the NovaSeq X Series library tube strip.

    • Validates run and analysis information.

    • Generates the sample sheet and creates the planned run, depending on the run mode.

  • AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1)

    • The step is fully automated and starts and completes automatically after the sequencing run is started and completed on the instrument side.

    • The sequencing run metadata (eg, run configuration, primary run metrics, and so on) are recorded automatically.

    âš  Do not add samples to the Ice Bucket or start or complete the step. The integration does this automatically.

  • AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1)

    • The step is fully automated and starts and completes automatically after the analysis run is started and completed in ICA.

    • The analysis run metadata (eg, status and high level analysis summary) are recorded automatically.

    âš  Do not add samples to the Ice Bucket or start or complete the step. The integration does this 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.

    Retrieves the list of ACTs that were created in BaseSpace Sequence Hub.
  • Registers the start time of the step by publishing messages to CLPA through the ICA.

  • Saves the details into a file that is available to download. This file is stored in the Analysis Configuration Metadata file placeholder.
    Checks that all samples are indexed and for invalid indexes. The indexes applied are the same as the selected ACT.
  • Assigns the selected ACT to all samples in the step.

  • Sets the next step for samples to ADVANCE, which advances them to the next step in the protocol (Make Bulk Pool (NovaSeq X Series Sequencing v1.1)).

  • Text

    Read Only

    Reference Genome

    Text

    Read Only

    Secondary Analysis Mode

    Text

    Read Only

    Pooled samples have the same type of analysis (e.g., Cloud or Local).
  • Pooled samples that have the same secondary analysis also have the same analysis version (e.g., v3.8.4) and analysis settings (e.g., Map/Align Output Format = CRAM).

  • Uses the Bulk Pool Volume (ul) field and Number of Lanes to Sequence (x100) to calculate volumes needed for the 2 nM intermediate library pools.

  • Copies the Final Loading Concentration (pM) and 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 adjusted per sample volume for the pools.

  • 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 NovaSeqXSeries_Bulk_Pool1.csv and NovaSeqXSeries_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, Total Sample Volume (ul), and Bulk Pool Volume (ul) to null before exiting the step.

  • Sets the next step for samples to ADVANCE, which advances them to the Dilute and Denature (NovaSeq X Series Sequencing v1.1) step.

    Registers the completion time of the step.

    This automation completes this action by publishing messages to CLPA through ICA.

    Number of Lanes to Sequence

    Numeric

    • Required Field

    • Range: 1–10

    • Decimal places displayed: 0

    Registers the start time of the step by publishing messages to CLPA through ICA.

    Computes the BP Aliquot Volume (µl) and RSB Volume (µl) required for the dilution of pools to the required final loading concentration.

    ℹ The BP Aliquot Volume value is rounded up to the nearest µl. The value in the calculation file, however, is reflected with up to two decimal places.

  • Sets the PhiX Volume (µl) and PhiX Concentration (µl) if there is a PhiX spike-in.

  • Generates a single CSV file that contains information about the reagents volume required to dilute the working pools. The generated file is stored in the Calculation File placeholder in the Files section.

  • TT2 Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Performs basic checks on the secondary analysis configuration of the samples in the same planned run. The following checks are included in this script:

    • Secondary analysis configuration of samples in a planned run is within maximum configuration limit.

    • Samples in a planned run have the same type of analysis (e.g., Cloud or Local).

    • Samples in the same pools that have the same secondary analysis (e.g., Illumina DRAGEN Enrichment) also have the same analysis settings (e.g., Map/Align Output Format = CRAM) and the same analysis version (e.g., v3.8.4).

    âš  This script is required for the NovaSeq X Series Sequencing v1.1 workflow to function properly.

  • Registers the start time of the step by publishing messages to CLPA through ICA.

  • Run Name can only contain alphanumeric, dash, underscore, or period characters. Do not use spaces.
  • Run Name cannot 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 in ICA. The sample sheet is attached to the step.

  • There is a backend validation of the sample sheet content in ICA. This validation makes sure that the sample sheet is valid to set up a Local mode run and that it is ready for use with DRAGEN applications.

    For more information on sample name character restrictions, refer to NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting.

    Read 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 1–251

    • Presets

      • 51

    Read 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–251

    • Presets

      • 51

    Run Mode

    Text Dropdown

    • Required Field

    • Presets

      • Local

      • Cloud

    Run Name

    Text

    • Required Field

    Registers the NovaSeq X Series sequencing run configuration.
  • Registers the association of the sequencing run with the samples by linking the Instrument Run ID with the sample ID.

  • Registers the time that the sequencing run started.

  • This automation completes these actions by publishing messages to CLPA through ICA.

    Registers the completion time of the step.

    This automation completes these actions by publishing messages to CLPA through ICA.

    Flow Cell ID

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the SerialNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Lot Number

    • RunParameters.xml

    • LotNumber

    • Visible on Record Details screen.

    • Corresponds to the value in the LotNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Part Number

    • RunParameters.xml

    • PartNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the PartNumber field under the ConsumableInfo field for FlowCell Type.

    Flow Cell Side

    • RunParameters.xml

    • Side

    • Visible on Record Details screen.

    Flow Cell Type

    • RunParameters.xml

    • FlowCellType

    • Visible on Record Details screen.

    Instrument Control Software Version

    • RunParameters.xml

    • SystemSuiteVersion

    • Visible on Record Details screen.

    Instrument ID

    • RunParameters.xml

    • InstrumentSerialNumber

    • Visible on Record Details screen.

    Instrument Type

    • RunParameters.xml

    • InstrumentType

    • Visible on Record Details screen.

    Output Folder

    • RunParameters.xml

    • OutputFolder

    • Visible on Record Details screen.

    Library Tube Strip Barcode

    • RunParameters.xml

    • SerialNumber

    • Visible on Record Details screen.

    • Corresponds to the value of the SerialNumber field under the ConsumableInfo field for SampleTube Type.

    Library Tube Lot Number

    • RunParameters.xml

    • LotNumber

    • Hidden

    • Corresponds to the value of the LotNumber field under the ConsumableInfo field for SampleTube Type.

    Run End Time

    • RunCompletionStatus.xml

    • RunEndTime

    • Hidden

    Run Name

    • RunParameters.xml

    • ExperimentName

    • Visible on Record Details screen.

    RTA Version

    • Not used

    • Not used

    • Hidden

    • Received from the message sent to the integration service.

    Hidden

    Run Start Time

    • Received from the message sent to the integration service.

    Hidden

    Yield (Gb) R1

  • Yield (Gb) R2

  • Reads PF R1

  • Reads PF R2

  • %PF R1

  • %PF R2

  • % Aligned R1

  • % Aligned R2

  • % Phasing R1

  • % Phasing R2

  • % Prephasing R1

  • % Prephasing R2

  • Intensity Cycle 1 R1

  • Intensity Cycle 1 R2

  • Cluster Density R1

  • Cluster Density R2

  • For the Cloud run mode, the planned run is created in ICA. The planned run contains the run and analysis configuration information required to start the run on the instrument. The sample sheet is generated and stored in Clarity LIMS for reference purposes.
  • When the sequencing run starts on the instrument, the NovaSeq X Series Control Software notifies BaseSpace Sequence Hub. BaseSpace Sequence Hub monitors the run and notifies Clarity LIMS via the integration service. The events are processed and the integration service retrieves the run information from BaseSpace Sequence Hub. This information is used to populate the custom fields in the AUTOMATED - Sequencing Run (NovaSeq X Series Sequencing v1.1) step.

  • Other run events follow the same information flow. When sequencing is complete, the control software uploads the sequencing run data (primary metrics) and associated files to ICA. Then, Clarity LIMS 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 (NovaSeq X Series Sequencing v1.1) 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 (NovaSeq X Series Sequencing v1.1) step. You must log in to BaseSpace Sequence Hub to retrieve the cloud analysis results. For local analysis, 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.

  • In Run Settings, select the Cloud run storage checkbox.

  • For Hosting location, select the applicable location from the drop-down options.

  • [Optional] For Private domain name, enter the domain name according to the workgroup that was configured with the NovaSeq X Series integration package.

  • Select Save.

  • Import the sample sheet created in the Load to Library Tube Strip (NovaSeq X Series Sequencing v1.1) step. Refer to information on creating a local run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.
  • When the sample sheet is selected, the contents are validated. After the validation passes, select Next.

  • Select Save As Planned.

    Run and analysis data is parsed and auto-populates in the list of runs. For more information on planning a NovaSeq X Series run, refer to the Plan a NovaSeq X Series Run section of the BaseSpace Sequence Hub Online Help at help.basespace.illumina.comarrow-up-right and the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

  • Start the run. Refer to information on starting a planned run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

  • Start a Sequencing Run in Cloud Run Mode

    To start a sequencing run in cloud run mode, refer to information on starting a planned run in the NovaSeq X Plus Product Documentation on the NovaSeq X Plus Sequencing System support sitearrow-up-right.

    Resuspension Buffer (RSB)

  • TT2

  • All submitted samples must have an associated secondary analysis that is configured using the analysis configuration template (ACT). The ACT must be configured on BaseSpace Sequence Hub before starting the Assign Analysis Configuration Template step. The ACT names must be unique.

  • The library tube strip barcode must be unique. There must not be multiple library tube strip containers with the same name in the 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 (NovaSeq X Series Sequencing v1.1) and AUTOMATED - Analysis Run (NovaSeq X Series Sequencing v1.1) steps must not be manually started or completed. These steps are fully automated and the sequencing service does not update samples correctly if they have been manually started.

  • For the automated run to start successfully, you must select Validate Run Setup and Create Planned Run in the Load to Library Tube step.

  • Field Name

    Field Type

    Options

    Analysis Configuration Template

    Text Dropdown

    Required Field

    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

    Molarity (nM)

    Numeric

    Decimal places displayed = 2

    ACT Name

    Text

    Read Only

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Dropdown Items

      • 90

      • 140

      • 150

      • 160

      • 180

    • Range from 0

    • Decimal places displayed: 0

    Flowcell Type

    Text

    • Required Field

    • Dropdown Items

      • 1.5B

      • 10B

      • 25B

    Minimum Per Sample Volume (ul)

    Numeric

    • Required Field

    • Decimal places displayed: 2

    • Default: 2

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Final Loading Concentration (pM)

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Decimal places displayed: 0

    • Dropdown Items

      • 225

      • 400

    RSB Volume (ul)

    Numeric

    • Read Only

    • Decimal places displayed: 2

    NovaSeq X Flowcell Type

    Text Dropdown

    • Required Field

    • Read Only

    • Dropdown Items

      • 1.5B

      • 10B

      • 25B

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    BP Aliquot Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 0

    NaOH Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    RSB Volume (ul)

    Numeric

    Read Only

    Decimal places displayed = 2

    Field Name

    Field Type

    Options

    Additional Options and Dropdown Items

    Cloud Run ID

    Text

    • Read Only

    • Hidden

    ℹ Used for creating a planned run in ICA.

    Index 1 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Index 2 Cycles

    Numeric Dropdown

    • Required Field

    • Custom Entries

    • Range = 0–20

    • Presets

      • 0

      • 6

      • 8

    Field Name

    Source File

    Corresponding Field in Source File

    Additional Information

    Current Cycle

    • RunCompletionStatus.xml

    • CompletedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field.

    Current Read

    • RunCompletionStatus.xml

    • RunParameters.xml

    • CompletedReads

    • PlannedReads

    • Visible on Record Details screen.

    • Calculated based on the CompletedReads field in RunCompletionStatus.xml and PlannedReads field in RunParameters.xml.

    Flow Cell Expiration Date

    • RunParameters.xml

    • ExpirationDate

    • Visible on Record Details screen.

    • Corresponds to the value in the ExpirationDate field under the ConsumableInfo field for FlowCell Type.

    Field Name

    Description

    Additional Information

    Run Status

    • Presets

      • RunStarted

      • RunCompletedSuccessfully

      • RunAbortedByUser

      • RunErroredOut

    • Set by the integration service.

    Visible on Record Details screen.

    Sequencing Log

    • Set by the integration service during the sequencing run.

    Visible on Record Details screen.

    BaseSpace Run ID

    • Received from the message sent to the integration service.

    Hidden

    ICA Project ID

    • Received from the message sent to the integration service.

    Hidden

    Field Name

    Description

    Additional Information

    Analysis Status

    • Presets

      • Started

      • Completed

      • Failed

      • NeedsAttention

      • Stopped

      • TimedOut

      • CompletedWithErrors

    • Set by the integration service.

    Visible on Record Details screen.

    Analysis Result Location

    • Received from the message sent to the integration service.

    Visible on Record Details screen.

    Library Tube Strip Barcode

    • Identified by the integration service using information from RunParameters.xml.

    Hidden

    NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    Clarity LIMS (Clarity & LabLink Reference Guide) documentation
    NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting
    NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting
    configured to ensure unique derived sample names

    Library Prep Kit

    Instrument Run ID

    NovaSeq X Series Integration v1.2.0 User Interaction, Validation and Troubleshooting
    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 'NovaSeq X Series' \
    --WORKFLOW 'NovaSeq X Series v1.1' \
    --STEP 'Assign Analysis Configuration Template (NovaSeq X Series Sequencing v1.1)' \
    --INPUTS_OR_OUTPUTS 'OUTPUTS'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:assign_act -i {stepURI:v2} -u {username} -p {password} -a '{udf:Analysis Configuration Template}' -l {compoundOutputFileLuid1}
    nextStep = ::ADVANCE:
    output.::Bulk Pool Volume (ul):: = 100 * step.::Number of Lanes to Sequence::; output.::NovaSeq X Flowcell Type:: = step.::Flowcell Type::; output.::Final Loading Concentration (pM):: = step.::Final Loading Concentration (pM)::;
    input.::Per Sample Volume (ul):: = 2 * output.::Bulk Pool Volume (ul):: / input.::Molarity (nM):: / output.::Number of Samples in Pool::;output.::Total Sample Volume (ul):: = 0;' -t true
    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 (ul):: = 0 } else { output.::RSB Volume (ul):: = output.::Bulk Pool Volume (ul):: - output.::Total Sample Volume (ul):: }' -t true \
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool1.csv -o 1.csv \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Bulk_Pool2.csv -o 2.csv \
    && cat 1.csv 2.csv > {compoundOutputFileLuid0}.csv \
    -exp 'output.::Number of Samples in Pool:: = ::::; output.::Total Sample Volume (ul):: = ::::; output.::Bulk Pool Volume (ul):: = ::::;' -t true
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    bash -l -c "/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.::NovaSeq X Flowcell Type:: == ::10B:: || input.::NovaSeq X Flowcell Type:: == ::1.5B::) {
        output.::NaOH Volume (ul):: = 8.5;
        output.::TT2 Volume (ul):: = 127.5;
        output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 170 / (2 * 1000);
        output.::RSB Volume (ul):: = 34 - output.::BP Aliquot Volume (ul)::;
        if (step.::1-2% PhiX Spike-In::) { 
            output.::PhiX Volume (ul):: = 1; output.::PhiX Concentration (pM):: = 300; 
        }else { 
            output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; 
        };
    } else {
        output.::NaOH Volume (ul):: = 14;
        output.::TT2 Volume (ul):: = 210;
        output.::BP Aliquot Volume (ul):: = input.::Final Loading Concentration (pM):: * 280 / (2 * 1000);
        output.::RSB Volume (ul):: = 56 - output.::BP Aliquot Volume (ul)::;
        if (step.::1-2% PhiX Spike-In::) { 
            output.::PhiX Volume (ul):: = 1.6; output.::PhiX Concentration (pM):: = 300; 
        }
        else { 
            output.::PhiX Volume (ul):: = ::::; output.::PhiX Concentration (pM):: = ::::; 
        };
    }'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/DriverFileGenerator.jar -i {stepURI:v2} -u {username} -p {password} \
    script:driver_file_generator \
    -t /opt/gls/clarity/extensions/conf/driverfiletemplates/NovaSeqXSeries_Dilute_Denature_Calculate_Volumes.csv -o {compoundOutputFileLuid0}.csv -q true -destLIMSID {compoundOutputFileLuid0} -l {compoundOutputFileLuid1} \
    && echo; echo 'Calculate Volumes completed successfully.'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    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/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:generate_sample_sheet -i {stepURI:v2} -u {username} -p {password} -c {compoundOutputFileLuid0} -l {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 -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/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/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -s 'com/illumina/upa/scripts/common/step_started.groovy'
    if (!input.hasValue(::Molarity (nM)::)) { return; };
    /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 -h false -exp 'if (!input.hasValue(::NovaSeq X Flowcell Type::)){fail(::Invalid Flowcell Type custom field value. Please make sure all input samples have a value assigned for Flowcell Type custom field.::)}' -log {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} \
    script:validate_same_udf_value_for_analytes -f 'Run Mode' -f 'NovaSeq X Flowcell Type' \
    script:validate_selected_container \
    -fn 'NovaSeq X Flowcell Type' -fv '1.5B' -ct 'Library 2-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '10B' -ct 'Library 8-tube Strip' \
    -fn 'NovaSeq X Flowcell Type' -fv '25B' -ct 'Library 8-tube Strip'
    /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:validate_output_containers -l {compoundOutputFileLuid1} -r 'Library 8-tube Strip:LC[0-9]{7}-L[A-Z]1' -r 'Library 2-tube Strip:LC[0-9]{7}-L[A-Z]2' -max 1
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_list -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1}
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:retrieve_act_info -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_indexes -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -a '{udf:Analysis Configuration Template}'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar script:validate_physical_logical_configurations -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool script:validate_analysis_config -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerPool && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/ngs-common/v5/EPP/ngs-extensions.jar script:validate_same_analyte_udf_value_for_all_inputs -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -f 'Run Mode' -perPool true
    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::;'"
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/pooling.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    /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.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::' -log {compoundOutputFileLuid1}
    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 and underscores. Run Name must start with alphanumeric, a dash or an underscore::);}
    output.::Run Mode:: = input.::Run Mode::; nextStep = ::ADVANCE::
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_started.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/register_novaseqxseries_run.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_associate_seqrun.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_started.groovy'
    /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/novaseqxseries/novaseqxseries_seqrun_completed.groovy' && /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/unified-product-analytics/automation/unified-product-analytics-automation.jar script:executeUPAAutomationScript -i {stepURI:v2} -u {username} -p {password} -s 'com/illumina/upa/scripts/common/step_completed.groovy'
    101
  • 151

  • 101
  • 151

  • /opt/gls/clarity/bin/java -jar /opt/gls/clarity/extensions/SIS/SISServices/extensions/automation/novaseqxseries-automation.jar -i {stepURI:v2} -u {username} -p {password} -l {compoundOutputFileLuid1} -m PerRun script:validate_analysis_config script:validate_physical_logical_configurations