-
Notifications
You must be signed in to change notification settings - Fork 71
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
Stochastic behaviour of GRIDSS #687
Comments
Even running gridss with |
Do *_metrics differ? -> input files are different between runs? |
May need to run with |
Do *_metrics differ? -> No So it looks like everything starts to diverge right after the GRIDSS assembler step |
@d-cameron Hi! |
Hi!
GRIDSS clearly has non-deterministic behaviour:
Here is my example: I ran 6 times completely the same job (8cpu and 32gb) with gridss for the same set of bam files (1 normal samples + 2 tumor samples) and each time got different results for the event of interest:
What is more concserning, is that on the 7th time this paired breakpoint converted to sigle breakend:
I presume, that is a side effect of parallelism on assembly step (since all these variants has different asm ids). Is there any way to fix it, providing any parameter like seed or anything similar?
The text was updated successfully, but these errors were encountered: