Using the development Docker container (both in Docker and Singularity) the generated simulations are different from the ones that are generated on other machines including Juseless, Colab and Kaggle, as well as the stable release container. This is probably not because of differences in compilation, since installing the exact same wheel on e.g. Juseless vs. the Docker container creates different simulations. The most likely culprit for the difference is the difference of random number sequences caused by the different libraries in each platform. From what I've learned the standard C++ random number generators are not guaranteed to be reproducible across platforms. Instead random number generators from e.g. boost library might be [ref]. Therefore using boost's random number generator may be a solution.
Using the development Docker container (both in Docker and Singularity) the generated simulations are different from the ones that are generated on other machines including Juseless, Colab and Kaggle, as well as the stable release container. This is probably not because of differences in compilation, since installing the exact same wheel on e.g. Juseless vs. the Docker container creates different simulations. The most likely culprit for the difference is the difference of random number sequences caused by the different libraries in each platform. From what I've learned the standard C++ random number generators are not guaranteed to be reproducible across platforms. Instead random number generators from e.g.
boostlibrary might be [ref]. Therefore usingboost's random number generator may be a solution.