My colleague has been trying to deploy GOMAP using the Singularity container and has run into a host of issues. His comments are below:

"I've made progress but I'm constantly stymied by the confounded documentation. They seem to have forked the containers and scripts they ask you to use to run the container into multiple versions. But none of that is documented. At this point I'm getting an error from the container trying to run its own Rscript. I think they are doing a lot of work on this with special implementation for individual HPC centers (the tags are condor, bridges which are clusters). However, this and much of the approach breaks the masks the beauty of containers. 1) They did not create a fully containerized repeatable scientific workflow. THey expect you to pull down extra code from git to actually run the workflow. THen they will push part of the workflow out to an external service that is called argus. 2) The forking into different (and more sloppily undocumented) versions breaks with that portability too."

We really want to try to use GOMAP, but are really limited by the documentation. Do you plan to improve your documentation? Also, I'd really hoped this would be deployed as a fully self-contained Singularity container. Do you have plans to improve the container so everything can be run locally instead of pushing code out to an external service?