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

ERROR in battenberg for XY samples only #18

Open
pumpkinpark97 opened this issue Aug 30, 2024 · 2 comments
Open

ERROR in battenberg for XY samples only #18

pumpkinpark97 opened this issue Aug 30, 2024 · 2 comments

Comments

@pumpkinpark97
Copy link

pumpkinpark97 commented Aug 30, 2024

Dear authors, @NMNS93 @elarosecadieux ,

I encountered an error when executing CAMDAC::pipeline with WGBS bam file.

The strange thing is that the Battenberg process only completes successfully for the BAM file of male patients, allowing for purity calling.

However, when the BAM file of a female patient is used as input, the Battenberg process halts after haplotyping up to chromosome 22.

The last output message is as follows:
2024-08-30 17:12:33.096258 INFO::Battenberg RUN HAPLO COMPLETE for 22

The error message is as follows:

Error in `[<-`(`*tmp*`, BAFs <= minBaf, 1, value = 1) : 
  (subscript) logical subscript too long
Calls: <Anonymous> ... withCallingHandlers -> <Anonymous> -> generate.impute.input.wgs
In addition: Warning message:
Unknown argument 'on' has been passed. 
Execution halted

Is there any way to fix this problem OR call purity without sex chromosome?

Any help is appreciated !
thanks

@elarosecadieux
Copy link
Collaborator

Hi,
@NMNS93 is the point person for CAMDAC WGBS. He is currently on holiday with little to no access to the internet. In the meantime, I will reach out to the Battenberg authors for you and see if I can implement a quick patch for this issue!
Thanks,
Lili

@NMNS93
Copy link
Collaborator

NMNS93 commented Nov 1, 2024

Thanks for raising this issue! We're currently looking into it. Please note that the WGBS tool is still in development but we expect this to be resolved with an official release in the coming months.

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

3 participants