Closed sebcomarmond closed 5 years ago
Hi @sebcomarmond,
Thank you for reporting this issue. I am not able to reproduce this error and I'm not sure what could be causing it.
Does the error still occur if you run dmrseq on a single chromosome or some other smaller subset of your BSseq object? If so, would you be able to send me the example subset object as an .rds file so that I can track down the problem? You can send via email to keegan@jimmy.harvard.edu. If the object is too large to send over email, I can provide a dropbox link for you to use.
Best, Keegan
Hi @sebcomarmond,
Thank you for sending me the example bsseq objects. I was able to reproduce the error and track down the issue. The bug was due to not properly combining nearby block segments while paying attention to different chromosomes/contigs and I've just pushed a fix. Following the fix, I am able to run dmrseq successfully on the example objects.
The new version is available on Github immediately, and on Bioc release and devel in the next day or so. Please try it out and let me know if it remedies the issue for you on the full set.
Best, Keegan
Hi @kdkorthauer ,
Thanks a lot for your help. After implementing the updated version of dmrseq from Github, the problem was solved even when working on a bigger dataset.
Best regards, Sebastien
Hi @kdkorthauer,
I am running some tests with
simDMRs
to find which parameters to use so as to increase the number of detected DMRs within my dataset. However, I meet with the following error message every time I try to setBlock=TRUE
no matter theblockSize
I try.The dataset consists of triplicates for two different conditions. To run the simulation, a
bs.null
object was created containing only the control samples.Except from the creation of the
bs
object, the command lines executed are as follows:I cannot find the reason behind the error message. Could you please help find the reason for such an error message or an alternative that would allow the use of
blockSize
in my case ?