-
Notifications
You must be signed in to change notification settings - Fork 2
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
Error in returnAllowedChromsBaf -> returnBAlleleFreqs #48
Comments
Hi, could you put a piece of code
at the line 119 in this file https://github.com/imgag/ClinCNV/blob/master/somatic/bafSegmentation.R and send me the output? It should be a simple vector and its summary seems to be sensible, but R somehow thinks it is not a simple vector, I guess... |
No, don't do this, replace
with and let me know if it works! |
Hi, then I got the new error: |
in old R versions it was an acceptable code style but I think it fails with the newer ones...
Which R version do you use? Because if it is the new one I probably have to adapt the rest of the script and make a new release. |
The R version I used is 4.2.2, and I changed the code following your advice, got below error: 1] "We are reading BAF files. It may take time - especially if you have a lot of SNV positions. 2024-05-14 16:47:41" |
But I use R version 4.1.2 without any code change, it works! |
Hi @sunyihong - so it works for you now? I will debug the tool for the newest version, seems that something fundamentally changed in the language (so many conditions failed, damn), so I'll try to hunt it down, but probably not today |
Yes! Thanks!!! |
Hello, when I run somatic CNV, I got this error:
[1] "We are reading BAF files. It may take time - especially if you have a lot of SNV positions. 2024-05-14 10:40:39"
Min. 1st Qu. Median Mean 3rd Qu. Max.
0.4007 0.4545 0.4841 0.4856 0.5141 0.5988
Error in if (!is.na(potentiallyHeterozygous)) { :
the condition has length > 1
Calls: returnAllowedChromsBaf -> returnBAlleleFreqs
Execution halted
any suggestions? thank you
The text was updated successfully, but these errors were encountered: