-
Notifications
You must be signed in to change notification settings - Fork 9
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
The params file format #4
Comments
Hi Rupal, Running MutSig on a cohort with a large mutation overlap between samples will yield very poor results. MutSig's background model explicitly assumes that mutations arise independently across samples, which is likely not the case when there is a substantial overlap. For example, multiple serial biopsies from the same patient will invariably share common ancestral events. In that case, violating the independence assumption will generate problematic results since passenger genes containing truncal mutations will appear to be recurrently mutated across many biopsies and show up as significant. Another common reason for substantial overlaps between samples is due to germline contamination (common germline SNPs appear as recurrent somatic mutations), or poorly filtered/QC'd somatic variant calls that contain recurrent sequencing artifacts across samples. Obviously, these would also yield poor MutSig results. I would carefully QC your mutation data before attempting to run with this option disabled. —Julian |
Hello Julian,
Yes, I do have multi-sites sequenced from same patients. Besides QCing mutations data, do you have any recommendations for running mutations from multi-site sequences?
Any other tool to detect driver and passenger mutations from your experience?
Thank you!
Rupal
From: julianhess ***@***.***>
Sent: Friday, July 16, 2021 1:38 PM
To: getzlab/MutSig2CV ***@***.***>
Cc: Rupal Hatkar ***@***.***>; Author ***@***.***>
Subject: Re: [getzlab/MutSig2CV] The params file format (#4)
EXTERNAL EMAIL:
Hi Rupal,
Running MutSig on a cohort with a large mutation overlap between samples will yield very poor results. MutSig's background model explicitly assumes that mutations arise independently across samples, which is likely not the case when there is a substantial overlap. For example, multiple serial biopsies from the same patient will invariably share common ancestral events. In that case, violating the independence assumption will generate problematic results since passenger genes containing truncal mutations will appear to be recurrently mutated across many biopsies and show up as significant.
Another common reason for substantial overlaps between samples is due to germline contamination (common germline SNPs appear as recurrent somatic mutations), or poorly filtered/QC'd somatic variant calls that contain recurrent sequencing artifacts across samples. Obviously, these would also yield poor MutSig results.
I would carefully QC your mutation data before attempting to run with this option disabled.
—Julian
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANJPLTZ2TCVBIFXPZYGZAHTTYBU6XANCNFSM5AP622QQ>.
|
I got the same issue as Rupal. I am wondering if you can kindly provide some sample maf data for our beginners to run the package. Thant would be very helpful. Best, |
It seemed to me that the option is silent in the file src/MutSig_2CV_v3_11_core.m
Best! |
Hello MutSig2CV Authors,
In the instructions for param file it says that the example file is available in test/input/params.txt. but there is no test folder.
I made a params_file.txt file stating remove_duplicate_patients = FALSE to instruct MutSig2CV to noto remove duplicate patients but it's not working and it keeps removing all the patients leaving me with no results files.
Can you please guide me? I am getting the following error:
0 patients
WARNING: MutSig is not applicable to single patients.
Error using |
Matrix dimensions must agree.
Error in add_helper_is_fields (line 19)
Error in impute_callschemes (line 12)
Error in MutSig_2CV_v3_11_core (line 296)
Error in MutSig_2CV_v3_11_wrapper (line 50)
MATLAB:dimagree
Thank you!
Rupal
The text was updated successfully, but these errors were encountered: