Longqc 1.2.3#1671
Conversation
…EADME is >30 lines since examples cover important preset options.
… to main README.md.
…r. Updated dockerfile_builder to replicate Dockerfile.
…ackages to using venv to avoid any artifacts being copied over.
|
Decided on usage builder stage for main Dockerfile; we use venv for proper copying from the builder stage to the app stage, and avoid installing those extra development libraries with apt-get. |
|
Could you add a test using a PacBio BAM file? A demultiplexed HiFi read is available here: |
I added a PacBio test from the url you supplied. Unfortunately, I did run into issues 14 and 76 from longQC's issues page with some of the BAM files I tested. However, the test case I have added in a2333c9 has successfully ran, and I'll supply the stats from the output JSON below for your review. JSON output: |
|
Closes #1650 |
Pull Request (PR) checklist:
docker build --tag samtools:1.15test --target test docker-builds/build-files/samtools/1.15)docker-builds/build-files/spades/3.12.0/Dockerfile)build-files/shigatyper/2.0.1/test.sh)docker-builds/build-files/spades/3.12.0/README.md)Addition of LongQC tool version 1.2.3. Main README.md should be updated to have base information and version 1.2.3 in the versions dropdown. An MIT license is linked in the Program Licenses file. The program README.md has information as specified by the template and it's larger than 30 lines because the author included some extra examples to indicate preset / preparation kit selection.
I would like to keep this as a draft PR for now. I'm thinking of any way I can optimize the build stage, and if it's acceptable to copy over python site-packages from a builder stage.