[x] create manuscript branch, never pull from manuscript into master, only master to manuscript
[ ] examples of challenges, e.g existing frameworks
[ ] identify individual challenges, illustrate our solutions for each of those
[x] consistent software environment - building and exposing containers
[x] code tags and releases under standard semantic versioning e.g. v1.5 + generated DOIs
[x] capturing output with env and runtime details #17 ; how much of pipeline info/introspection, execution environment can be captured and added to release (and so also DOI)? For that, we should have "special" run-related releases e.g. v1.5_suffix where suffix needs to be unique (but that is a technical requirement anyway) and could potentially be a result of hashing of data to be uploaded to the release (results, env info, run info). A simpler version of the suffix could just capture NF exec profile plus a timestamp.
At a minimum, your code will run on a 16-core machine with 120 GB of memory
5GB of storage and 1 hour of compute time per month. Use your academic email to get 20GB of storage and 10 hours of compute time per month
If you’re working on preparing your code and need more storage or compute time, please contact us. You can also purchase extra compute time at $1 per hour and extra storage at $5/mo for every 50GB.
Main focus
Reproducibility
Re-computability
Re-use
Extensibility
[ ] report to be the main product of the pipeline
[x] create
manuscriptbranch, never pull frommanuscriptintomaster, onlymastertomanuscript[ ] examples of challenges, e.g existing frameworks
[ ] identify individual challenges, illustrate our solutions for each of those
v1.5+ generated DOIsv1.5_suffixwhere suffix needs to be unique (but that is a technical requirement anyway) and could potentially be a result of hashing of data to be uploaded to the release (results, env info, run info). A simpler version of the suffix could just capture NF exec profile plus a timestamp.[ ]
Discuss