MPICH 64-bit?

[kmanalo]

Any experiences with using non 32-bit MPIs?

I'm on a compute cluster that uses MVAPICH2 (MPICH ABI compatible)

https://www.mpich.org/abi/

[kmanalo]

I actually have a self-answer here, while it's viable it's likely not worth the trouble with the current architecture.

I ended up using the pre-built binaries from the multibugs-2.0 Ubuntu release and I can confirm running up to 24 processors in a container (Singularity chosen here).

I'll be happy to share or contribute the recipe if there's interest.

I could then run the seeds model afterwards.

[rjbgoudie]

Great! Please do share the recipe - we've also had success with running MultiBUGS within Singularity so glad you found the same solution worked for you. I will try to find our recipe in case comparing notes is helpful.

[kmanalo]

Sure

https://gist.github.com/kmanalo/5e98a8b2e7b88adbb892678689fa696f

[beew]

How do you get mpich:i386 on Ubuntu 20.04? It is not even in the repository any more. It is 2020 why is this software still uses 32 bit libs?

[iadenisov]

1. We are working on 64x compiler for BlackBox Component Builder http://herschel.oberon.org So soon there should be the way to use 64x mpich libs. We are searching sponsors for the Hershel project to speed up the development.
2. For new Ubuntu version, I would suggest to use precompiled mpich executables and libraries http://pub.iadenisov.ru/mpich32.tar
   For my applications I am using the script:

#!/bin/sh

PATH=./mpich32/bin:$PATH; export PATH
LD_LIBRARY_PATH=./mpich32/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH

mpiexec $@

I think, that this should work for MultiBUGS also.

[beew]

1. We are working on 64x compiler for BlackBox Component Builder http://herschel.oberon.org   So soon there should be the way to use 64x mpich libs. We are searching sponsors for the Hershel project to speed up the development.

2. For new Ubuntu version, I would suggest to use precompiled mpich executables and libraries http://pub.iadenisov.ru/mpich32.tar
   For my applications I am using the script:

#!/bin/sh

PATH=./mpich32/bin:$PATH; export PATH
LD_LIBRARY_PATH=./mpich32/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH

mpiexec $@

I think, that this should work for MultiBUGS also.

Hi, Thanks for the reply. It turns out that the Linux binary tarballs already contains mpich32, I also tried your method with the .deb by extracting the contents and ran it locally, it was all fine provided you change the path in the startup script.

However, there seems to be a problem with R2MultiBUGS, it just seqfaults and crashes. Now since this is Linux the debug mode doesn't work I have no idea what happens. But my guess is that in the R environment the environmental variables are not set so it was loading the 64 bit libraries and in this case openmpi. I don't know the internal working of MultiBUGS or R2MultiBUGS, but is my guess correct and if so is there a way to address that without having to use these environmental variables globally (i.e in R itself, and R may not even work if you try that)?

[darren-greenwood]

@kmanalo struggling to adapt your code to work on CentOS 7 distribution. Was wondering if 64-bit MPI was the way forward.