Releases: Molmed/checkQC
Updated interop dependency for iSeq support
Bugfixes:
- Updated interop dependency for iSeq support
- iSeq support is now mentioned in README and docs
New definition of reads per sample and iSeq support
Major changes:
New definition of reads per sample
Reads per sample are now counted per sample name instead of sample ID. It allows a sample to have multiple libraries in the same lane and still be counted as one sample. For example, in a run with the following sample sheet:
Sample_ID,Sample_Name
Pool1_1,Pool1
Pool1_2,Pool1
Pool2_1,Pool2
Pool2_2,Pool2
the sum of reads for Pool1_1 and Pool1_2 will be defined as the reads for Pool1. This was not the case in previous versions of CheckQC, where each unique sample ID was considered a sample.
Minor changes:
- Support for iSeq
- Improved error handling
New definition of reads per sample
Major changes:
Reads per sample are now counted per sample name instead of sample ID. It allows a sample to have multiple libraries in the same lane and still be counted as one sample. For example, in a run with the following sample sheet:
Sample_ID,Sample_Name
Pool1_1,Pool1
Pool1_2,Pool1
Pool2_1,Pool2
Pool2_2,Pool2
the sum of reads for Pool1_1 and Pool1_2 will be defined as the reads for Pool1. This was not the case in previous versions of CheckQC, where each unique sample ID was considered a sample.
Minor changes:
Note that this is a pre-release.
v1.8.0-rc1
Bump version to 1.8.0-rc1
Minor bug fix release
This release fixes a minor bug where the error rate handler error message was odd.
Release process bug fix
The version was not properly updated in the last release (so version 1.7.0 will not be available via pypi). However v1.7.1 should fix this and contain the same updates as the previous release.
Support for Novaseq S1, S2, and S4 flowcells
CheckQC now supports Novaseq S1, S2, and S4 flowcells. Enjoy!
Automatically push new releases to PyPI
This version updates nothing user facing, but facilitates the release process of checkQC by automatically using new releases to PyPI.
Tags v1.6.0 and v1.6.1 were attempts to get this working and can be disregarded.
Remove threading from the web service
The ProcessPoolExecutor functionality has been removed from the web service, basically reducing it to running things in a blocking fashion. The problem with the ProcessPoolExecutor was that it spawned a lot of threads that were left running and wouldn't terminate properly. The most straightforward way to fix it is, for now, to remove the threading.
A Dockerfile has been added for running the web service in a container.