Skip to content
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

cnvpytor.utils - WARNING - Problem with fit: Runtime Error. Using mean and std instead fitting parameters! #174

Open
kaqisekuzi opened this issue Apr 3, 2023 · 4 comments

Comments

@kaqisekuzi
Copy link

          Hi @suvakov 

I sent the log file to your email.
Below is the Manhattan plot of the two samples.
Does this Manhattan plot have anything to do with the warning message?

warning message: cnvpytor.utils - WARNING - Problem with fit: Runtime Error. Using mean and std instead fitting parameters!

log file:
sample_3964_And_sample_4352.log.txt

22S04403964 manhattan global 0000
22S04404352 manhattan global 0000

Originally posted by @kaqisekuzi in #171 (comment)

@kaqisekuzi
Copy link
Author

Hi @suvakov @abyzov
Does this Manhattan plot have anything to do with the warning message?
warning message: cnvpytor.utils - WARNING - Problem with fit: Runtime Error. Using mean and std instead fitting parameters!

@suvakov
Copy link
Member

suvakov commented Apr 10, 2023

Warning message is expected due to shallow coverage (around 1x according to log files) and it is not related to Manhattan plot. Is this cancer sample (first plot)?

Thanks,
Milovan

@kaqisekuzi
Copy link
Author

@suvakov
Yes , first plot is a cancer sample.
Do these warnings have any effect on my results?
Is it possible to ignore these warning messages?

Thanks,
kaqisekuzi

@suvakov
Copy link
Member

suvakov commented Apr 13, 2023

You can safely ignore warning messages. In the first example, it's unclear what copy number 2 level refers to. Normalization is typically performed based on the mean level of autosomes, but in cancer cases, this may differ from the actual copy number 2. Our 2D caller addresses this issue by using only diploid regions for normalization based on B-allele frequency (BAF). However, this approach may not be applicable here due to the low coverage. My suggestion is to manually normalize the levels by assuming that the beginning of chromosome 1 (or any other region where you believe it is most likely to have 2 copies) has a copy number of 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants