2019-09-04 12:29:48 +02:00
|
|
|
# monofonIC
|
2019-05-09 21:52:55 +02:00
|
|
|
|
2019-09-04 12:29:48 +02:00
|
|
|
High order LPT/QPT tool for single resolution simulations
|
|
|
|
|
|
|
|
|
|
## Build Instructions
|
|
|
|
|
Clone code including submodules (currently only CLASS is used as a submodule):
|
|
|
|
|
|
|
|
|
|
git clone --recurse-submodules https://ohahn@bitbucket.org/ohahn/monofonic.git
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Create build directory, configure, and build:
|
|
|
|
|
|
|
|
|
|
mkdir monofonic/build; cd monofonic/build
|
|
|
|
|
|
|
|
|
|
ccmake ..
|
|
|
|
|
|
|
|
|
|
make
|
|
|
|
|
|
|
|
|
|
this should create an executable in the build directory.
|
2019-12-19 12:52:08 +01:00
|
|
|
|
|
|
|
|
If you run into problems with CMake not being able to find your local FFTW3 or HDF5 installation, it is best to give the path directly as
|
|
|
|
|
|
|
|
|
|
FFTW3_ROOT=<path> HDF5_ROOT=<path> ccmake ..
|
|
|
|
|
|
2019-12-19 12:55:56 +01:00
|
|
|
make sure to delete previous files generated by CMake before reconfiguring like this.
|
|
|
|
|
|
|
|
|
|
## Running
|
|
|
|
|
|
|
|
|
|
There is an example parameter file 'example.conf' in the main directory. Possible options are explained in it, it can be run
|
|
|
|
|
as a simple argument, e.g. from within the build directory:
|
|
|
|
|
|
|
|
|
|
./monofonic ../example.conf
|
|
|
|
|
|
|
|
|
|
If you want to run with MPI, you need to enable MPI support via ccmake. Then you can launch in hybrid MPI+threads mode by
|
|
|
|
|
specifying the desired number of threads per task in the config file, and the number of tasks to be launched via
|
|
|
|
|
|
|
|
|
|
mpirun -np 16 ./monofonic <path to config file>
|
|
|
|
|
|
|
|
|
|
It will then run with 16 tasks times the number of threads per task specified in the config file.
|
