-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
identify sharable theory predictions #35
Comments
Is the full model and parameter set for MFLike written down somewhere? I could extract it from the code (and the notebook) I guess. |
Fiducial model for the V0.6 release is LCDM, with params set according to this camb inifile: https://github.com/ACTCollaboration/actsims/blob/master/data/cosmo2017_10K_acc3_params.ini Fiducial foreground model is set according to the following dict: No bandpass integration (dirac-delta bandpass), no systematics params. This amounts to setting: band_integration: "bandint_shift_93" : 0, |
The particular example of |
Sure, I mean something different, apologies for not being clear enough. SOLikeT/soliket/clusters/tinker.py Line 129 in 2874450
SOLikeT/soliket/xcorr/limber.py Line 32 in 1d0a7fc
Since in principle the Pk_interpolator is the same for all these observables, I'd like to have it inizialized once for all with the same input settings (e.g., same kmax, same transfer, same redshift range, all wide enough to encompass all the tracers etc). In other words, I don't want clusters, xcorr and other likelihoods to get different requirements from the Boltzmann code for the very same object. Does it make sense to you? |
Cobaya should already combine requirements to make required spanning k ranges range for all calculations and do one computation. The interpolator object should also be cached so each theory will receive the same interpolator object when called with the same field arguments. |
Identify theory predictions that are shared by many likelihoods (e.g., Pk interpolator needed by clusters and xcorr) and compute them once for all the likelihoods.
The text was updated successfully, but these errors were encountered: