Issue #501: Add simple parsing function to explode on transcript #523
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.
Before:
trio_trim_vep_vcf-20240524162149542.annotation.tsv.gz
After:
test_output.tsv.gz
Notice at loci like
chrom:chr2 pos:207647981 type:SNP inputRef:C alt:T
we no longer haveFASTKD2;FASTKD2;FASTKD2;MIR3130-1;MIR3130-2
in the refSeq.name2 field (the gene name field) andNM_001136194;NM_014929;NM_001136193;NR_036077;NR_036078
in the refSeq.name field (the transcript name field). Instead we have 5 rows, with 1 transcript/gene per row (the same is true for all of the refSeq.* fields; they are exploded relative to the refSeq.name field).