-
Notifications
You must be signed in to change notification settings - Fork 25
refactor: separate analysis #446
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
base: main
Are you sure you want to change the base?
Conversation
Documentation build overview
Show files changed (6 files in total): 📝 6 modified | ➕ 0 added | ➖ 0 deleted
|
| ensemble: | ||
| include: true | ||
| aggregate_per_algorithm: true | ||
| evaluation: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want the ML code and evaluation to be separate analysis options in the config even though they are internally coupled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, it should be analysis.evaluation and not analysis.ensemble.evaluation?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at comments for config/config.yaml about how to separate evaluation and ML.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at comments for config/config.yaml about how to separate evaluation and ML.
Splits analysis into a more detailed configuration, allowing parts of the Snakemake workflow to depend only on parts of the config. This has the con of making it more annoying to blanket-enable all analysis. Closes #331.