-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions about post-processing Tomte for Scout #175
Comments
Hello! |
Hmm, yes, OK. Makes sense. The CLGs liked seeing the list of ranked variants for our samples currently loaded as RNA-only, which I remember now is why I initially included it. Maybe we could/should also try loading the RNA-seq on top of existing DNA-seq. Then we could skip the annotation step. Thanks for making me think this through again 😅
Yes, that would be interesting for us as well.
Yes, I agree, that sounds good! I think the other bioinfs in Lund in the RNA-seq project would be interested in joining as well (@ViktorHy and @A97paupic). I'll check with them and can get back to you on Slack. |
I'll close this issue. Thanks for the discussion 😃 In conclusion:
|
Hello from Lund!
We are in process of an RNA-seq validation using Tomte, and as part of that I have been loading Tomte outputs into Scout.
At the moment, this requires several steps of post-processing beyond obtaining the results.
Currently:
(Edit: Maybe the annotation/scoring parts will not be relevant when we run this together with DNA-seq data)
Eventually, it would be nice to have this automated. Things are still under discussion, so maybe some steps will be added / removed, but I suspect we will need to do something similar also ahead.
Would it make sense to include parts of this in Tomte? If parts are very Lund-specific it might make more sense for me to set up a Lund-Tomte-postprocessing. For parts that are of general interest on the other hand, might be worth considering adding to Tomte. If so, let me know and I can splice out some concrete issues, and can also help out adding these.
The text was updated successfully, but these errors were encountered: