-
Notifications
You must be signed in to change notification settings - Fork 34
Set a fixed seed for all steps #43
Comments
I think we should do the same for SCENIC. |
Good idea. But there are some things internal to pySCENIC that would need this addition as well. One thing in particular is the AUCell step, when calculating the cell rankings, ties are broken dependent on the random seed (aertslab/pySCENIC#99). This is a fix that would need to be implemented on the pySCENIC side. I believe the same applies to the ranking in the cisTarget step as well. For GRNBoost2/Genie3, there is already an option to set the seed in the pySCENIC CLI, but this needs to be implemented in the NF process here also. |
The user should be able to use a custom seed => put the seed as a param part of the config. |
Current stochastic processes:
|
Use seed for nondeterministic processes vib-singlecell-nf/vsn-pipelines#43
Nice work on this @dweemx ! But it's not quite finished for the pySCENIC steps. Maybe it would be better if we start another issue in that repo? It would need work on the pySCENIC codebase before we're able to implement anything here. |
What did I miss ? |
No you didn't miss anything. But there some things internal to pySCENIC (ctx and aucell steps) that are still stochastic. I'll start an issue there. |
This regards the following processes:
The
|
Fully reproducible workflows from version |
Good Job |
Especially important for dimensionality reduction, clustering, etc.
The text was updated successfully, but these errors were encountered: