Skip to content
This repository has been archived by the owner on Nov 9, 2019. It is now read-only.

ClusteringGenomicHMMSegmenter can fail if random memory length exceeds maximum allowed. #640

Closed
samuelklee opened this issue Aug 9, 2016 · 3 comments
Closed

ClusteringGenomicHMMSegmenter can fail if random memory length exceeds maximum allowed. #640

samuelklee opened this issue Aug 9, 2016 · 3 comments
Labels
bug Copy Number tools Segmentation

Comments

@samuelklee
Copy link
Contributor

This combined with an unset random seed was causing AlleleFractionSegmenter.testChromosomesOnDifferentSegments to fail intermittently in #633. @davidbenjamin could you take a look when you get back? This could be fixed easily by a Math.min in the right place, but I don't know if the fact that the memory length seems to blow up is something generic that happens when we collapse to a single state that needs to be addressed more carefully.
@samuelklee samuelklee added this to the CNV Tools alpha-3 release milestone Aug 17, 2016
@samuelklee
Copy link
Contributor Author

@davidbenjamin can you take a quick look? I think it's probably a quick fix.

@davidbenjamin
Copy link
Contributor

Sure.

@droazen
Copy link
Contributor

droazen commented Jun 5, 2017

Issue moved to broadinstitute/gatk #2877 via ZenHub

@droazen droazen closed this as completed Jun 5, 2017
@droazen droazen mentioned this issue Jun 5, 2017
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Copy Number tools Segmentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@droazen @davidbenjamin @samuelklee