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 On Premise Integration Package version 1.0.0.

Compatibility

Refer to Compatibility under Instruments & Integrations.

New Features

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

• Provides integration between the NovaSeq X Series instrument and on-premise Clarity LIMS.

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

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

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

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

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

Known Limitations

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

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

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

• The integration requires secondary analysis files to be present on the instrument for proper functioning of the AUTOMATED - Analysis Run step. The following instrument setting must be disabled: Permanently delete secondary analysis files from the instrument after they are transferred to the external storage and/or cloud. Refer to NovaSeq X Series On Prem Integration v1.0.0 Configuration for details.

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

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.