Planck Likelihoods on cluster

Use of Cobaya. camb, CLASS, cosmomc, compilers, etc.
Post Reply
Pablo Lemos
Posts: 11
Joined: December 07 2015
Affiliation: University of Sussex
Contact:

Planck Likelihoods on cluster

Post by Pablo Lemos » December 15 2015

Hello,

I am trying to run cosmomc using the public Planck likelihood. When I run it on my desktop, it works perfectly fine. However, when I try to run it on a cluster, I get an error. I have loaded the modules intel/fce/14.0.3.174 , openmpi/intel/1.8.8 , cfitsio/intel/3.300 and python/2.7.10 . Here is the error message I get:

Clik will run with the following nuisance parameters:
A_cib_217
cib_index
xi_sz_cib
A_sz
ps_A_100_100
ps_A_143_143
ps_A_143_217
ps_A_217_217
ksz_norm
gal545_A_100
gal545_A_143
gal545_A_143_217
gal545_A_217
calib_100T
calib_217T
A_planck
Using clik with likelihood file
./data/clik/low_l/bflike/lowl_SMW_70_dx11d_2014_10_03_v5c_Ap.clik
forrtl: severe (257): formatted I/O to unit open for unformatted transfers, unit 42, file /scratch/pl411/plc_2.0/low_l/bflike/lowl_SMW_70_dx11d_2014_10_03_v5c_Ap.clik/clik/lkl_0/_external/.//params_bflike.ini
Image PC Routine Line Source
libifcoremt.so.5 00007F4667D94B99 Unknown Unknown Unknown
libclik.so 00007F4668E069AD Unknown Unknown Unknown
libclik.so 00007F4668DC3CE0 Unknown Unknown Unknown
libclik.so 00007F4668DA2B0A Unknown Unknown Unknown
libclik.so 00007F4668D6F11B Unknown Unknown Unknown
libclik.so 00007F4668D6654E Unknown Unknown Unknown
libclik_f90.so 00007F466D299367 Unknown Unknown Unknown
libclik_f90.so 00007F466D29D262 Unknown Unknown Unknown
cosmomc 00000000005086E7 Unknown Unknown Unknown
cosmomc 0000000000505C78 Unknown Unknown Unknown
cosmomc 000000000055D132 Unknown Unknown Unknown
cosmomc 000000000059529B Unknown Unknown Unknown
cosmomc 000000000059F8FB Unknown Unknown Unknown
cosmomc 000000000040F896 Unknown Unknown Unknown
libc.so.6 00007F46694E4D5D Unknown Unknown Unknown
cosmomc 000000000040F789 Unknown Unknown Unknown
-------------------------------------------------------
Primary job terminated normally, but 1 process returned
a non-zero exit code.. Per user-direction, the job has been aborted.
-------------------------------------------------------
--------------------------------------------------------------------------
mpirun detected that one or more processes exited with non-zero status, thus causing
the job to be terminated. The first process to do so was:

Process name: [[2320,1],0]
Exit code: 1
--------------------------------------------------------------------------

Any ideas about what could be happening? Thank you in advance.

Antony Lewis
Posts: 1941
Joined: September 23 2004
Affiliation: University of Sussex
Contact:

Re: Planck Likelihoods on cluster

Post by Antony Lewis » December 21 2015

Please update with the solution, thanks.

Pablo Lemos
Posts: 11
Joined: December 07 2015
Affiliation: University of Sussex
Contact:

Re: Planck Likelihoods on cluster

Post by Pablo Lemos » December 22 2015

Antony Lewis wrote:Please update with the solution, thanks.
Yes, sorry. My problem was that the cluster was trying compiling and running with gfortran. It was solved when I added export F90=mpif90 to my .bashrc file.

Post Reply