Question: cn.mops calling copy number 1 state as CNV using the haplocn.mops function in an haploid WGS
1
gravatar for jebet.joan
4.8 years ago by
jebet.joan10
jebet.joan10 wrote:

Hi,

I use cn.mops to detect CNVs from WGS data of an haploid genome using the haplocn.mops function . However, I obtain CNVs of copy number 1, which should not be the case since the normal should be 1. I do not get any calls of copy number 2.

Does this function still assume a normal state of 2 despite it being suggested useful for haploid genome? 

Would greatly appreciate any clarification on this.

Joan

 

 

sequencing R genome • 1.7k views
ADD COMMENTlink modified 4.5 years ago by klambauer20 • written 4.8 years ago by jebet.joan10
1
gravatar for klambauer
4.5 years ago by
klambauer20
Austria
klambauer20 wrote:

Hello Joan,

Yes, this can happen in rare cases. The reason is that the CNV calls and the integer copy numbers are made on different segments - I'll try to explain:

The CNV call joins consecutive segments with high or low signed informative/non-informative call. Let us assume that you have joined 4 segments that had: + / - / - / +. On this joined segments the integer copy numbers (CN) are called. It can happen that the probability of CN1 is slightly higher than CN2 - in this case the software returns CN2. You can check the posterior probabilities of the copy numbers for each segment, if you use "returnPosterior=TRUE".

I hope this helps - you can contact me also via email!

Regards,

Günter Klambauer

 

 

ADD COMMENTlink written 4.5 years ago by klambauer20

I am in the same situation. Could you please explain this in greater detail? I am getting many of such calls and I am not sure how to prevent this behavior. Thanks a lot.

ADD REPLYlink written 4.1 years ago by Biomonika (Noolean)3.1k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1270 users visited in the last hour