Closed FriederikeHanssen closed 1 year ago
Hi @FriederikeHanssen,
Apologies for the delay getting back to you, I was off for two weeks.
There are two places where a seed can be set:
ascat.getBAFsAndLogRs
but users should only be running ascat.prepareHTS
, where the seed cannot be set so it cannot be propagated to ascat.getBAFsAndLogRs
. I will add a fix in the next commit (a few days/weeks) and will let you know so you'll have full control of the seed there. This explains why, in your example, 1_801943 has a BAF of 1 in a given run and a BAF of 0 in another run.Now, to answer your question: there should not be any adverse effect if you were to fix the seed.
Cheers,
Tom.
Hi @FriederikeHanssen,
Should be fixed now (as part of this commit) so a seed can be given to ascat.prepareHTS
and it will be propagated to ascat.getBAFsAndLogRs
.
You can give it a try by re-installing ASCAT (devtools::install_github('VanLoo-lab/ascat/ASCAT')
) and running your test again with a fixed seed for both ascat.prepareHTS
and ascat.aspcf
.
Cheers,
Tom.
Closing the issue, feel free to share additional comments if needed.
Cheers,
Tom.
Hi @tlesluyes ! Apologies for not getting back to you. It has been busy. We will test this :) Thank you for adding this functionality
Hi!
We have added ASCAT to one of our pipelines and recently experienced that the output is not reproducible (on tiny test data that is) even when run in a container: https://github.com/nf-core/sarek/issues/702 We are suspecting that since the
seed
foraspcf
is the the system time, that this is possibly the culprit.Would there be any adverse effects, if we fixed the seed?
Cheers :)