Error: no snpdist defined

[elinejk]

Hi,
When I run detect_cnv.pl -trio using a custom pfb file for the Illumina GSA array I get the following error:

ERROR: For nextregion 22,kgp15099441,rs530422334, pos=rs5030865.1 rs78482768 kgp15099441 rs530422334 22:42529918_CYP2D6 sample1.txt sample2.txt sample3.txt: no snpdist defined!!!

In detect_cnv.pl this is:

ERROR: for nextregion $nextsubregion, pos=@nextpos @$ref_inputfile: no snpdist defined!!!

Do you have any suggestions on how to solve this?
Thanks!

[hezht3]

I also met with this issue. I wonder whether there's any suggestion on resolving this? Thanks.

[elinejk]

If I remember correctly, the error is the result of multiple SNPs with the same coordinates. Because they have the same position, PennCNV trio calling is unable to calculate the distance between the SNPs. My solution to this, while not ideal, was to change the input files so that there was only one SNP for each position

[SamGreen52]

Hello! Currently receiving this issue, was there any other additional solutions that you may have found?

[kaichop]

Try check whether all SNPs have coordinates defined in the PFB file. If not, make new signal files by including only SNPs that are defined in the PFB file.

…

On Thu, Jun 13, 2024 at 3:32 PM Sam Greenspun ***@***.***> wrote: Hello! Currently receiving this issue, was there any other additional solutions that you may have found? — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABNG3OE4VZNU54X7DXHD5ZDZHHXUHAVCNFSM6AAAAABJJAXZHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRWGYZDEMBTHE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>