While successfully running cosmomc in our cluster with march 2014 version, when I go to chain directory , and open test.inputparams : I find that the the input it displays for
l min and l_max
lmax_computed_cl = 2500
lmin_computed_cl = 2000
does it mean it is only doing analysis for high ls with above range ?
I WOULD LIKE TO CHANGE l_min = to be very low value for my analysis say l=200. Can some body tell me which file I should go and change it ?
cosmomc l_min_comuted_cl
-
Antony Lewis
- Posts: 1943
- Joined: September 23 2004
- Affiliation: University of Sussex
- Contact:
Re: cosmomc l_min_comuted_cl
No, it doesn't mean that.
lmin_computed_cl = 2000 means that it will always calculate CL up to at least 2000, regardless of what the likelihood requests.
lmax_computed_cl does mean not to compute above 2500, instead filling in with a scaled template. Usually it would be higher than 2500. you don't need to manually include either settings for normal runs.
lmin_computed_cl = 2000 means that it will always calculate CL up to at least 2000, regardless of what the likelihood requests.
lmax_computed_cl does mean not to compute above 2500, instead filling in with a scaled template. Usually it would be higher than 2500. you don't need to manually include either settings for normal runs.
-
Subinoy Das
- Posts: 18
- Joined: March 20 2006
- Affiliation: NYU
cosmomc l_min_comuted_cl
Thanks a lot. I have two naive questions as running first time
I was wondering if I want to increase k slicing ( more k points ) where should I change.
Also, If I want exclude BICEP2 , just run it for planck and BAO , where I have to turn it off.
I was wondering if I want to increase k slicing ( more k points ) where should I change.
Also, If I want exclude BICEP2 , just run it for planck and BAO , where I have to turn it off.