You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In both Python2 and Python3 versions of X-PSI, there seems to be a dependence of the exact MultiNest output on the order of pymultinest and numpy imports, if using a certain conda environment, even if fixing both MultiNest and NumPy seeds. Attached are the python2 conda environments, where the effect is seen and where it is not (at least during a short test run with an example script similar to that in examples/examples_fast/Modules/main.py): py2_environment_yes_effect.txt py2_environment_no_effect.txt
Pymultinest version is 2.11 in both (from commit 60c3490c7aefe126d8506e2dc025a0cc7f193512), and MultiNest version 3.12. Also tested that forcing the GCC compiler version (for X-PSI) to be the same for both does not change the results.
When the import order matters, it seems that all samples and their likelihoods are identical between the 2 cases, until a completely different parameter vector is given by MultiNest after hundreds of samples have been sampled.
The text was updated successfully, but these errors were encountered:
In both Python2 and Python3 versions of X-PSI, there seems to be a dependence of the exact MultiNest output on the order of
pymultinest
andnumpy
imports, if using a certain conda environment, even if fixing both MultiNest and NumPy seeds. Attached are the python2 conda environments, where the effect is seen and where it is not (at least during a short test run with an example script similar to that inexamples/examples_fast/Modules/main.py
):py2_environment_yes_effect.txt
py2_environment_no_effect.txt
Pymultinest version is 2.11 in both (from commit 60c3490c7aefe126d8506e2dc025a0cc7f193512), and MultiNest version 3.12. Also tested that forcing the GCC compiler version (for X-PSI) to be the same for both does not change the results.
When the import order matters, it seems that all samples and their likelihoods are identical between the 2 cases, until a completely different parameter vector is given by MultiNest after hundreds of samples have been sampled.
The text was updated successfully, but these errors were encountered: