Steven Rieder
Steven Rieder
Yes you're right. Phantom (for now) uses fixed units and should not be called with a converter. This is a bug - it either should accept and use a converter...
Before this bug is resolved, at least the following needs to happen: - [ ] Write a test that runs Phantom without and with (h2) cooling - [ ] Test...
It seems to use `gfortran`, I would expect `mpifortran` needs to be used here instead. The argument `MPIFC="/usr/bin/gfortran -fallow-argument-mismatch"` is probably causing this.
`MPIFC` should not be set to `gfortran`, keep it at `mpifortran` or undefined. You can set `FC` to `gfortran -fallow-argument-mismatch` if this is important, but redefining an MPI compiler to...
... thinking about it further, I guess this may follow from AMUSE being configured without MPI in the first place. So a first step would be to re-run configure in...
I'd like to see the `config.mk` file (in the AMUSE root dir) of the sterrewacht installation of AMUSE, can you find this @Spijkerberg?
Thanks. This shows AMUSE was configured without MPI support, so no wonder stuff that requires MPI breaks... This will require fixing on the module level.
You will also need to install mpi4py (`pip install mpi4py`). If this is not detected, configure will set MPI_ENABLED to no.
If you re-run configure, does that change the config.mk file?
If you do `module load AMUSE` you should now get the correct prerequisites, there was an issue with mpi4py installing the wrong mpi...