Replies: 1 comment
-
I am not sure I have much concern of tRNA... but as you suggest I would just do the two ways you have suggested. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
BACKGROUND:
I'm attempting to run the NF-Core RNAseq pipeline. Part of the pipeline runs RSEM. RSEM works off of a GTF file. GTF files have a column dedicated to feature strands. Generally, a feature is found on the
+
or the-
strand. However, the GTF file spec indicates that this column could also have a.
to indicate no strand info for a given feature. However, RSEM is written to only process a+
or-
and will throw an error when encountering any other character.I'm attempting to use the Panopea-generosa-v1.0.a4.gff3. The issue is that there are a set of annotations for tRNA that have a
.
in the strand column. This causes the pipeline to fail:QUESTION(S):
So, my question is what do you think I should do to handle this? Should I:
OR
Both of these options will allow the pipeline to proceed, but I'm not sure what the overall impacts will be for differential gene expression analysis. I'm guessing there will be no impact, as these aren't genes/mRNAs, so will likely be ignored when it comes to the actual differential gene expression analysis, but wanted to see what other people thought.
Of course, I could run the pipeline a couple with each of the proposed changes above and see how the results compare... Just so I can get the pipeline running, I'll probably do this while waiting for feedback.
Beta Was this translation helpful? Give feedback.
All reactions