-
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
Option to include/switch reference data and a global preview table #1
Comments
Dear Sehrish, Thanks a lot for your input, highly valuable! Generally, I can say that what you suggest makes perfect sense as a further development of the workflow. And parts of your ideas have been mentioned by some other colleagues here. I will get back to you shortly with my ideas/comments on what is realistic short term etc., very busy here today. PS. You are correct about the regards, |
Hi Sigve, Thanks for the response and I look forward to hearing back from you. Regards, |
Hi Sehrish, Coming back to this:
Would appreciate your input on this. regards, |
Hi Sigve, Thanks for getting back to this. • Reference data from Hartwig is:
Also, I do appreciate the point that we need to understand what data we are going to use for presentation as it’s hard processing reference input on the fly. • Global preview: We are hoping to begin with focussing on coding regions. It would be definitely very useful to have the ability to switch to whole gene (including introns). But we can expand on this later. Happy to have your feedback on this and start looking into implementation as well - if this sounds feasible/useful to you. Regards, |
Hi Sigve
Thanks for another awesome framework. We (@umccr) are very much interested to incorporate this into our reporting.
I have looked at the github repo/code and tested it locally - it works great. We have a couple of questions/comments:
We are interested in using some of the reference data from Hartwig. Looking at the codebase, it shouldn't be a problem as the
data
directory is passed as an argument and this directory contains reference data to be used for the analysis. However, this might impact the annotations that the framework reads in from the.tsv(s)
in `cacao_utils.R for specific clinical genomic tracks?There is an optional flag
--target
, which according to my understanding refers to the targeted region in the input sample?This probably links back to point 1 i.e. feeding in one specific
bed
track (in this case) which could be joint set of various loci sources such as CIViC, CGI and OncoKb and then reading in the (optional annotations as in the code base) for this data - if this idea aligns well with your original idea of the framework?Sorry about the long commentary and thanks for your time.
Cheers,
Sehrish
The text was updated successfully, but these errors were encountered: