VEP: support version 114#3209
Merged
Merged
Conversation
Contributor
|
Nice, thank you! |
vladsavelyev
added a commit
to MultiQC/test-data
that referenced
this pull request
May 28, 2025
Closed
4 tasks
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
2 participants
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.
Description of changes:
Updated the VEP MultiQC module to handle new section
[Data version]in VEP version 114 stats file.Improved type handling in the parser to avoid crashes when encountering unexpected value types in new sections in the future
Attached a generic example VEP stats file from version 114 (
VEP114_vep.txt) for use as test dataThere is example tool output for tools in the https://github.com/MultiQC/test-data repository or attached to this PR
Code is tested and works locally (including with
--strictflag)VEP114_vep.txt