You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once in the while, people on Slack ask about issues they encounter when running the rnaseq pipeline on prokaryotic RNA samples. Part of the confusion arises from the completely outdated documentation (separate issue #1084), but there is also room for some technical improvements to the pipeline code.
Ultimately, the goal would be to simplify running the pipeline on prokaryotic samples (e.i. those whose annotation does adhere to the canonical trinity of exon -> transcript -> gene).
I think, this could be a suitable Hackathon task for more advanced nf-core contributors:
Adapt the pipeline, primarily the prepare_genome.nf subworkflow, to handle also prokaryotic references properly. Possibly, introduce a new parameter to make the switch between eukaryotic and prokaryotic analyses.
Thanks!
The text was updated successfully, but these errors were encountered:
Description of feature
Once in the while, people on Slack ask about issues they encounter when running the rnaseq pipeline on prokaryotic RNA samples. Part of the confusion arises from the completely outdated documentation (separate issue #1084), but there is also room for some technical improvements to the pipeline code.
Ultimately, the goal would be to simplify running the pipeline on prokaryotic samples (e.i. those whose annotation does adhere to the canonical trinity of
exon -> transcript -> gene
).I think, this could be a suitable Hackathon task for more advanced nf-core contributors:
prepare_genome.nf
subworkflow, to handle also prokaryotic references properly. Possibly, introduce a new parameter to make the switch betweeneukaryotic
andprokaryotic
analyses.Thanks!
The text was updated successfully, but these errors were encountered: