Clearer QC messages

Patch changes:

• Fixed travis integration issue
• Updated QC messages in unidentified index handler to be clearer about which index it is referring to

v1.5 reagents adjustements to NovaSeq

Patch changes:

• Minor adjustments of NovaSeq QC thresholds to account for the v1.5 reagents.

Default config update and fixing docs (with bumped version number)

New release since version number never was incremented in the last one

Patch updates:

• Bioconda information added to README
• Docs building fixes
• Updated some QC thresholds in the default config

Default config update and fixing docs

Patch updates:

• Bioconda information added to README
• Docs building fixes
• Updated some QC thresholds in the default config

Update interop requirement

Patch release:

• Fixed problem where NovaSeq SP couldn't be run #88

New feature: Use closest read length

It is possible to instruct CheckQC to use the closest read length if the read length of the run is not found in the config. In case of a tie between two read lengths, the longer read length (with stricter QC criteria) will be used.

Usage:
$ checkqc --use-closest-read-length <RUNFOLDER>

This parameter can be supplied to the webservice as a query argument:
curl -s -w'\n' localhost:9999/qc/170726_D00118_0303_BCB1TVANXX?useClosestReadLength | python -m json.tool

New feature: Downgrade errors

It is now possible to downgrade errors to warnings for specific handlers. Prior to evaluating the QC criteria, the config will be updated so that warning threshold = error threshold and error threshold = unknown. Read more about usage in the docs.

New feature: Index white-list

It is now possible to specify white-list indexes that only cause warnings even if they occur above the significance level.

Small QC config update

Patch:
Updated Q30 threshold for hiseqx_v2.

QC critera for NovaSeq SP 101 bp

Patch:
QC criteria for NovaSeq SP, read length 101 bp, have been added to the default config.