Open
Conversation
No code changes required to pass testing. May want to write helper functions to abstract over some changes, depending on how other projects use this parser.
Not 100% sure this is the right thing to do - this may be intended to list only modules that are guaranteed to be present. Alternatively, split into EXPECTED and OPTIONAL modules.
Owner
|
Alas, I just had to change around the files in this repo to make it a proper package--if you could reapply and push back up, I will merge this in and go forward. Also, we'll want to tick the version number up for this, and start to do that EXPECTED/OPTIONAL split so we can do both FastQC v0.10 and v0.11. Once we have the parser working for v0.11, we will be able to start moving our pipeline to use v0.11. |
EXPECTED_MODULES are guaranteed to be present for supported versions of FastQC, OPTIONAL_MODULES may or may not be present.
New features: FastQC version 0.11.2 compatiblity
Author
|
Alright, merged in master, split out the three optional modules into |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The parser already works for FastQC v0.11 data (issue #4). There's 2 modules added, one removed (per-base GC content, which always struck me as redundant), and a few fields renamed (notably, "Filtered" -> "Sequences flagged as poor quality").
I think the LIMS will error with this change, as it's expecting all the modules in EXPECTED_MODULES to be present. It might be better to split this array into EXPECTED/OPTIONAL.