hey @amojarro ! Thanks for all of your help with the input data. if you are interested, I added an implementation (and docs for it) using Singularity images, two ways! (just like eggs). I wrote about it here:
For the PR below, there are the following additions:
a Singularity and Singularity.devel file, which show two kinds of container (with the same content) you can build (one for developer, one for intended user)
I put the docs (singularity.md) in the docs folder if you wanted to try github pages for them (they have some templates that render really nicely!)
I added an example / equivalent runscript for singularity (carrierseq_singularity.sh)
A cool idea I'm thinking about - let's say that you provide a container with some repo, and given that it's easy to use and run, wouldn't it be cool if anyone that ran one of the containers had an easy way to contribute their result (eg, replicate your experiment?) The simplest idea I can come up with is to drop some result file in a folder in the repo, and PR. Let me know your thoughts!
hey @amojarro ! Thanks for all of your help with the input data. if you are interested, I added an implementation (and docs for it) using Singularity images, two ways! (just like eggs). I wrote about it here:
http://containers-ftw.org/apps/examples/carrierseq
For the PR below, there are the following additions:
A cool idea I'm thinking about - let's say that you provide a container with some repo, and given that it's easy to use and run, wouldn't it be cool if anyone that ran one of the containers had an easy way to contribute their result (eg, replicate your experiment?) The simplest idea I can come up with is to drop some result file in a folder in the repo, and PR. Let me know your thoughts!