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
Maybe I should just use something like snakemake rather than reinventing the wheel, but to avoid unnecessary dependencies and keep things simpler, i think it should be possible to make my own templating system for reproducibility.
create global templates for the header of generated scripts. these would then be easy to change out if we want to run the script on a different system with a different scheduler. eg have a separate template for sge vs slurm. example for slurm would be something like:
maybe set defaults for variables, and then if a variable is required but unspecified, the default is kept, but if it's not required, the whole line is removed.
every one of my example workflows can then be rewritten as a template rather than the current cat <<EOF setup, and i can run a script that pieces the templates together based on command line options, and produces reproducible other scripts that are submitted. these scripts might always include a 'raw' shell script with all substituted variables that is easy for someone to follow, in addition to the actual sbatch script that was run on your specific system.
another template can be used for general 'path preparation' - whether that means loading modules, directly modifying the path, or something else. this template could be called multiple times within the main script template if the path needs to be different at different points.
The text was updated successfully, but these errors were encountered:
Maybe I should just use something like snakemake rather than reinventing the wheel, but to avoid unnecessary dependencies and keep things simpler, i think it should be possible to make my own templating system for reproducibility.
create global templates for the header of generated scripts. these would then be easy to change out if we want to run the script on a different system with a different scheduler. eg have a separate template for sge vs slurm. example for slurm would be something like:
maybe set defaults for variables, and then if a variable is required but unspecified, the default is kept, but if it's not required, the whole line is removed.
every one of my example workflows can then be rewritten as a template rather than the current cat <<EOF setup, and i can run a script that pieces the templates together based on command line options, and produces reproducible other scripts that are submitted. these scripts might always include a 'raw' shell script with all substituted variables that is easy for someone to follow, in addition to the actual sbatch script that was run on your specific system.
another template can be used for general 'path preparation' - whether that means loading modules, directly modifying the path, or something else. this template could be called multiple times within the main script template if the path needs to be different at different points.
The text was updated successfully, but these errors were encountered: