You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are observing non-deterministic behavior of whamg when run multiple times across cloud VMs on the same BAM file, where about 5-10% of calls are different. I see from a quick search of the code base that random sampling is used to estimate metrics (this seems to be seeded to the system clock with srand in wham and not in whamg), but from the logs it looks like these estimates converge consistently.
Can anyone reproduce this behavior?
Either way, it would also be very useful to set the random seed manually from the command line.
The text was updated successfully, but these errors were encountered:
We are observing non-deterministic behavior of
whamg
when run multiple times across cloud VMs on the same BAM file, where about 5-10% of calls are different. I see from a quick search of the code base that random sampling is used to estimate metrics (this seems to be seeded to the system clock withsrand
inwham
and not inwhamg
), but from the logs it looks like these estimates converge consistently.Can anyone reproduce this behavior?
Either way, it would also be very useful to set the random seed manually from the command line.
The text was updated successfully, but these errors were encountered: