Different brms behaviors between a Docker image and the same image imported in singularity

[mrkm-a]

@maedoc

You may also consider building your software as a Singularity container directly, since it has it’s own format.

That is one option I’m thinking about as well, although no singularity image of R appears to be as well developed as rocker, and I perhaps need a fair amount of work to build up the singularity image that is comparable to my current Docker image.

@maedoc

But you should consider

@martinmodrak

“good enough” reproducibility, which is IMHO much easier

where you might also do a series of runs with increasing iterations and see convergence of the results across platforms (local Docker vs remote HPC), i.e. the 95% CI overlap should asymptotically approach 100%. (Containerizing can still help manage software versions with this.)

Thank you for this suggestion. I agree that these are the things I should think about once I give up exact reproducibility.

@maedoc

What version of singularity are you using?

The version of singularity appears to be

• 3.6.1 on HPC,
• 3.3.0 for the desktop version, and
• 2.4 for the Vagrant version.

This might explain why I could at least run my converted Docker image on HPC but not locally.