A lot more modularization might be desirable of course.
Since Snakemake_model_eval cannot expect to run without the (current) main workflow, it should be the main workflow (i.e. called Snakefile), and include the (now) Snakefile_data at the appropriate place (after the first rule that it wants executed for itself by default).
Rule names can't overlap, so I'm using plots and data respectively (the first rule found is still the default though).
This should help us simplify invocation from the command line (Snakefile_data can still be run independently if needed, of course), as well as our test case which needs to run both, as demonstrated in tests/test_snakemake.py.
Restructured folders/files based on recommendations at https://snakemake.readthedocs.io/en/stable/snakefiles/deployment.html
A lot more modularization might be desirable of course.
Since
Snakemake_model_evalcannot expect to run without the (current) main workflow, it should be the main workflow (i.e. calledSnakefile), andincludethe (now)Snakefile_dataat the appropriate place (after the first rule that it wants executed for itself by default).Rule names can't overlap, so I'm using
plotsanddatarespectively (the first rule found is still the default though).This should help us simplify invocation from the command line (
Snakefile_datacan still be run independently if needed, of course), as well as our test case which needs to run both, as demonstrated intests/test_snakemake.py.