Aleksandr Petrosyan

I see. Congrats on your job and I wish you well. With that said, a disclaimer that the project is not being actively developed (at least for now) would be...

The issue here are the checks in `_pypolychord.cpp`, which are not part of the C++ api altogether. If you're using an internal function, having no error checking is the least...

> Some of it however is important for raising exceptions appropriately from the loglikelihood/prior/dumper functions. While writing the project up, I implemented a couple of sanity checks in this [file](https://github.com/appetrosyan/LCDM-NS/blob/master/framework/polychord_model.py)....

I can’t run anything PolyChord. The shortest error message I get is ``` FORTRAN RUNTIME ERRROR: array rank of PUT is not 1. ``` And that’s what I get without...

A fresh install is a clear venv, brew MPI, brew GFortran. Pip install every dependency.

Exactly the same error messages. Running with `mpirun` just wraps the segfaults into MPI warnings.

Nope. It fails with the following. ``` [app-mbp:07451] *** Process received signal *** [app-mbp:07451] Signal: Segmentation fault: 11 (11) [app-mbp:07451] Signal code: Address not mapped (1) [app-mbp:07451] Failing at address:...

1. Fortran works like a charm. 2. Nope. Same bare info: ``` [app-mbp:07995] *** Process received signal *** [app-mbp:07995] Signal: Segmentation fault: 11 (11) [app-mbp:07995] Signal code: Address not mapped...

On my system python is python2.7, so [here's](https://pastebin.com/UqfVhD2K) the output of the same with python3.

This is not too critical, as Cobaya still uses PolyChord v1.16, which runs OK on my machine.