-
Notifications
You must be signed in to change notification settings - Fork 24
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
help in describing the input #11
Comments
I found some hints to the first question in #6, "All subclonal clusters have proportion < purity" but still not sure if that is I also found that #5 talks about the |
Hi. I'm wondering if you have solved the question about the VCF input. Could you provide an input example of VCF? |
@lincj1994 @kzkedzierska I am wondering if you have solved the VCF input question. I am getting this error |
these are my dimensions
|
I fixed the error by making my vcf look similar to the one in the example repo |
@Salaheddinekacimi Hi! Would you kindly elaborate briefly on how you formatted your vcf file similar to the example? I'm getting the same dimension error as you and was wondering how to format the vcf |
Posting this if anyone else is facing the same issue. I think the dimension error occurs from the vcf format. If the vcf format is a collapsed vcf then the dimension error occurs when used as input. The expected vcf format is an expanded vcf file. |
Hi!
I am trying to use the tool but I run into a few problems and have questions regarding the inputs:
t_alt_count
andt_ref_count
but I do not have the AD/DP columns. Is that ok?readVcf
is different (my rowRanges have additional column paramRangeID) and it would be good to understand why.clonal_frequency
just a frac1_A or should that be corrected by purity?My questions are sparked by the fact that despite my best efforts the function
mutationTime
produces only NAs and plots are empty (except for copy number). Which might hint that my vcf is different than what the functions expect.I will be very grateful for suggestions and help!
The text was updated successfully, but these errors were encountered: