Page 1 of 1

use_CMB now set internally from likelihoods

Posted: June 23 2017
by Rahulkumar Solanki
Hi,
I am following this post to run SNe data alone.
http://cosmocoffee.info/viewtopic.php?t ... 6560aae0c8
And I receive following errors.

Number of MPI processes: 1
file_root:test_background
NOTE: use_CMB now set internally from likelihoods
Random seeds: 24273, 409 rand_inst: 1
read jla dataset ./data/jla.dataset
Doing non-linear Pk: F
Doing CMB lensing: T
Doing non-linear lensing: T
TT lmax = 2500
EE lmax = 2500
ET lmax = 2500
BB lmax = 2500
PP lmax = 2500
lmax_computed_cl = 2500
Computing tensors: F
max_eta_k = 14000.00
transfer kmax = 5.000000
adding parameters for: JLA
Fast divided into 1 blocks
5 parameters
starting Monte-Carlo
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
Error in halofit
CAMB error
MpiStop: 0
application called MPI_Abort(MPI_COMM_WORLD, 60380640) - process 0

How can I set use_CMB=F inside the likelihood?
Thanks a lot.

Re: use_CMB now set internally from likelihoods

Posted: June 23 2017
by Antony Lewis
Try deleting use_CMB line and add

Code: Select all

use_nonlinear_lensing=F

use_CMB now set internally from likelihoods

Posted: June 23 2017
by Rahulkumar Solanki
After adding that line, I get following error.
Thanks.

Number of MPI processes: 1
file_root:test_background
Random seeds: 27667, 10429 rand_inst: 1
read jla dataset ./data/jla.dataset
Doing non-linear Pk: F
Doing CMB lensing: T
Doing non-linear lensing: F
TT lmax = 2500
EE lmax = 2500
ET lmax = 2500
lmax_computed_cl = 2500
Computing tensors: F
max_eta_k = 6625.000
transfer kmax = 0.8000000
adding parameters for: JLA
Fast divided into 1 blocks
5 parameters
starting Monte-Carlo
Calculator_CAMB: negative C_l (could edit to silent error here)
MpiStop: 0
application called MPI_Abort(MPI_COMM_WORLD, 40452000) - process 0

Re: use_CMB now set internally from likelihoods

Posted: June 23 2017
by Antony Lewis
Not sure, you'll need to figure out why use_CMB is being set to true in Initialize_CMBSettings even though no CMB likelihoods being used.