What are thoughts on creating a check in the snakemake modules to see if crosstools is installed and if not, then to run the script, instead of manually needing to put it in after cloning and creating the envs. We could integrate a "start up" execution where it creates the environments only and finds the new generated reports environment name (creating a snakemake_env folder if they would like) activates it and then runs the install.R script. Could also add an option to automatically include the test data in the correct spots by cloning and moving instead of manually needing to. Just an idea to improve user experience in setting up.
What are thoughts on creating a check in the snakemake modules to see if crosstools is installed and if not, then to run the script, instead of manually needing to put it in after cloning and creating the envs. We could integrate a "start up" execution where it creates the environments only and finds the new generated reports environment name (creating a snakemake_env folder if they would like) activates it and then runs the install.R script. Could also add an option to automatically include the test data in the correct spots by cloning and moving instead of manually needing to. Just an idea to improve user experience in setting up.