QIAGEN powered by

System requirements

This page lists the requirements of all CLC software products, plugins and special use cases. Requirements for Biomedical Genomics Analysis plugin, CLC Single Cell Analysis Module, CLC Microbial Genomics Module vary and are listed separately below, as are special use case requirements for 3D Molecule Viewer, read mapping and de novo assembly. Please note that analysing data generated with QIAseq panels using the Biomedical Genomics Analysis require 16 GB RAM, 24 GB recommended.

QIAGEN CLC Genomics Workbench*

* Standard requirements without use of functionality in plugins

Special requirements for the 3D Molecule Viewer

Special requirements for read mapping

The numbers below give minimum and recommended memory for systems running mapping and analysis tasks. The requirements suggested are based on the genome size.

Special requirements for de novo assembly

De novo assembly may need more memory than stated above – this depends both on the number of reads, error profile and the complexity and size of the genome. See our white paper on de novo assembly for examples of the memory usage of various data sets.

Plugins and Modules

Biomedical Genomics Analysis plugin

The system requirements of Biomedical Genomics Analysis are the same as those for the CLC Genomics Workbench apart from the following:

Special requirements for QIAseq analysis

The following use cases have specific system requirements

CLC Single Cell Analysis Module

The system requirements of CLC Single Cell Analysis Module are the same as those for the CLC Genomics Workbench, apart from the following:

Most tools can be run on modest hardware such as a laptop, especially when the number of cells is under 50,000.

Special requirements for mapping reads

For mapping reads to references, we recommend using a CLC Genomics Server (see requirements below). Although a laptop with 16 GB of RAM can be used, the large number of reads are likely to lead to long runtimes when there are more than 1000 cells.

Long Read Support (beta) plugin

The system requirements of the Long Read Support (beta) plugin are the same as those for the CLC Genomics Workbench, apart from the following:


CLC Microbial Genomics Module

The system requirements of CLC Microbial Genomics Module are the same as those for QIAGEN CLC Genomics Workbench, apart from the following:

Special requirements for the Large MLST Scheme tools

The system requirements for the Large MLST Scheme tools depend on the size of the MLST schemes (both the number of alleles and the number of sequence types). A laptop with 16GB of memory is normally sufficient for 7-gene schemes or cgMLST schemes based on a moderate number of isolates. Typing or constructing larger schemes may require more memory, and in general, we recommend at least 64GB of memory when working with cg/wgMLST schemes based on more than 100 isolates.

Special requirements for the Taxonomic Profiler

he quality performance of the Taxonomic Profiler depends on the reference database used – the more complete a database, the better the quality. However, running the Taxonomic Profiler with a given database size will require at least the same amount of memory. For example, running with a 14 GB database requires at least 16 GB of RAM, and running with a 56 GB database requires a minimum of 64 GB RAM. When creating your reference database with the Download Microbial Reference Database tool, you will get a warning about the memory requirements needed for running the Taxonomic Profiler with this database.

Special requirements for De Novo Assemble Metagenome

It is recommended to have at least 16 GB RAM when running the De Novo Assemble Metagenome.

Other requirements

The PCoA 3D viewer requirements are the same as the 3D Molecule Viewer, described in the CLC Genomics Workbench requirements section above.

The Sunburst viewer makes use of JavaFX and may not work on older Linux kernels. An updated list of requirements for JavaFX can be found at http://www.oracle.com/technetwork/java/javafx/downloads/supportedconfigurations-1506746.html.

QIAGEN CLC Main Workbench

Special requirements for the 3D Molecule Viewer

QIAGEN CLC Genomics Server*

* Standard requirements without the use of functionality in plugins. For compute-intensive operations used by several plugins and modules, the recommended number of cores is 32.

Server system

Hardware requirements

CLC Network License Manager

The CLC Network License Manager does not require much processing power and only consumes a few megabytes of memory. This means that if you are putting together a dedicated server specifically for running the license manager, a modestly powered system equipped with a high number of redundant components will probably be a better investment than a system which is faster, has more memory, etc.

The system requirements for the CLC Network License Manager are:

The CLC Network License Manager is based on the LM-X License Manager 5.2.2. The list of systems above has been derived from the LM-X supported system list: https://docs.x-formation.com/display/LMX/Supported+platforms and systems we have tested on. The CLC Network License Manager will likely work on other Windows, Linux and macOS systems, but we cannot guarantee this.

Java

The QIAGEN CLC Workbenches, CLC Command Line Tools, CLC Genomics Server and the CLC Network License Manager are built using Java technology. The QIAGEN CLC software includes a JRE (Java Runtime Environment) necessary to execute the software, independent of the operating system (Windows, Mac OS X or Linux). This JRE will not interfere with existing JRE’s on your computer and will only be used to run the QIAGEN CLC software.

Mac and the Mac logo are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. Microsoft, Windows and the Windows logo are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.

Scope of requirements

All the system requirements on this page are requirements for the most recent versions of the products. For requirements for older versions, please refer to the user manual for that specific version.