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
Currently we have zip files for each, and so snakemake tracks the folder that contains the files. This led to some awkward workarounds (defining the atlas dir as an input, but the files themselves as parameters). Ultimately it would be better to have the individual files tracked in the workflow, both for error checking, and for future maintenance (eg adding more atlas/template files), so marking this as a nice to have feature for v2.0. Perhaps could use some automation to help grab urls, or use a s3 bucket where the file path can be part of the url..
The text was updated successfully, but these errors were encountered:
Currently we have zip files for each, and so snakemake tracks the folder that contains the files. This led to some awkward workarounds (defining the atlas dir as an input, but the files themselves as parameters). Ultimately it would be better to have the individual files tracked in the workflow, both for error checking, and for future maintenance (eg adding more atlas/template files), so marking this as a nice to have feature for v2.0. Perhaps could use some automation to help grab urls, or use a s3 bucket where the file path can be part of the url..
The text was updated successfully, but these errors were encountered: