CosmoMC: Planck 2018/2015 Likelihoods
-
Thomas Clarke
- Posts: 5
- Joined: November 04 2016
- Affiliation: University of Nottingham
Post
by Thomas Clarke » December 02 2019
I've installed the July 2019 version of CosmoMC to use the Planck 2018 likelihoods. I followed the instructions given on the CosmoMC pages and it seems to be running the test files correctly. However when I run 'make' I get the following warnings;
Code: Select all
ipo: warning #11021: unresolved clik_lensing_get_extra_parameter_names
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_get_lmaxs
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_data_
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_version
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_cleanup
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_extra_parameter_names
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_compute
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_try_lensing
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_has_cl
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_cleanup
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_get_lmax
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_init
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved purgeError
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_cltt_fid
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved _isError
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_clcmb_fid
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_init
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_clpp_fid
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_cal_beam_
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_fg_
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_compute
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_vecsize_
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_lmax
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved printError
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/plc-2.0/lib/libclik_f90.so
ipo: warning #11021: unresolved __xmlGenericError
Referenced in /home/ppxtjc/Documents/cosmomc/CosmoMC_2019/mpi-install/lib/libmpi.so
make[1]: Leaving directory `/home/ppxtjc/Documents/cosmomc/CosmoMC_2019/Planck_2019/CosmoMC/source'
The fact that this is referring to plc-2.0 suggests that Planck 2015 is the problem but I think I linked to that as I did previously. Any ideas what is causing this?
-
Antony Lewis
- Posts: 1943
- Joined: September 23 2004
- Affiliation: University of Sussex
-
Contact:
Post
by Antony Lewis » December 02 2019
I would use the latest version of the clik likelihood code (which can still load old 2015 data files).
-
akhil antony
- Posts: 1
- Joined: March 29 2020
- Affiliation: The Institute of Mathematical Sciences
Post
by akhil antony » January 23 2021
I got the same set of errors while compiling cosmomc with plc 3.0 also.
ipo: warning #11021: unresolved clik_lensing_get_extra_parameter_names
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_get_lmaxs
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_data_
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_version
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_cleanup
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_extra_parameter_names
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_compute
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_try_lensing
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_has_cl
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_cleanup
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_get_lmax
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_init
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved purgeError
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_cltt_fid
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved _isError
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_clcmb_fid
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_init
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_clpp_fid
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_cal_beam_
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_fg_
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_lensing_compute
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved fortran_plik_get_vecsize_
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved clik_get_lmax
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
ipo: warning #11021: unresolved printError
Referenced in /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/lib/libclik_f90.so
make[1]: Leaving directory `/storage/gpfs_maestro_home/hpc/akhil/epsilon/source
===================================
Also I was getting some warning while installing plc.
warning: /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/src/python/clik/lkl_lensing.pyx:51:13: Non-trivial type declarators in shared declaration (e.g. mix of pointers and values). Each pointer declaration should be on its own line.
/home/HPC/akhil/.local/lib/python3.6/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /storage/gpfs_maestro_home/hpc/akhil/plc_3.0/plc-3.01/src/python/clik/clik.parametric.pxd
tree = Parsing.p_module(s, pxd, full_module_name)
/home/HPC/akhil/.local/lib/python3.6/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h(17): warning #1224: #warning directive: "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION"
#warning "Using deprecated NumPy API, disable it with “ \
Will this affect the cosmomc runs? Is there any way to fix this?
-
Antony Lewis
- Posts: 1943
- Joined: September 23 2004
- Affiliation: University of Sussex
-
Contact:
Post
by Antony Lewis » January 23 2021
Warnings are usually harmless