This folder contains the EFTCAMB code.

Compiling EFTCAMB requires a modern fortran compiler capable of handeling F2008 features. These includes:

ifort (tested with v>15.0)
gcc/gfortran (tested with v>6.0)

To use other parts of the code, like the test or documentation parts other requirements have to be met. These include a fully fledged python installation. We warmly suggest to install a bundled package like (https://www.continuum.io/downloads).

A docker with all the required libraries is available at dockerhub.

To get started with the EFTCAMB Python wrapper, you need to first download the entire package using Git:

git clone https://github.com/LinSJ-astronomy/pyEFTCAMB.git

Next, it's recommended(really recommended) to create a new environment using Conda and install the necessary dependencies:

conda create -n EFTCAMB_env gfortran lapack numpy python sympy scipy packaging -c conda-forge

Note for Mac Users: If you're using a Mac with an Apple Silicon chip (e.g., M1, M2), ensure you install the appropriate version of gfortran for your architecture (arm64):

conda create -n myenv-arm gfortran_osx-arm64 -c conda-forge

You can verify that you're using the correct version of gfortran by executing:

which gfortran

Finally, navigate to the package directory and install the package in editable mode:

pip install -e ./pyEFTCAMB

This will allow you to import the Python package camb as usual in your projects.

The EFTCAMB distribution contains a folder called example that can be used to produce some example notebooks for brief instruction and sevral example input files of cobaya for sampling and statistical modelling.

To use cobaya, just follow the instruction at:

https://readthedocs.org/projects/cobaya/badge/?version=latest

The example folder is an example of how to select EFTCAMB flags and set parameters needed from the flags. You can copy the folder and replace the input files to produce single purpose packages to easily produce and plot results.

We provide a set of notes that contain all the details and formulas of the EFTCAMB implementation:

• EFTCAMB/EFTCosmoMC: Numerical Notes v3.0
  Bin Hu, Marco Raveri, Noemi Frusciante, Alessandra Silvestri, arXiv:1405.3590 [astro-ph.CO]

The EFTCAMB source files documentation is automatically built at any modification of the code and can be found at this link.

Besides above documentation, there are several flowchart or markdown files helping you easily find your model flags and set parameters in “find_your_model" folder.

If you use the EFTCAMB/EFTCosmoMC package, please refer the original CAMB/ CosmoMC paper and ours:

• Effective Field Theory of Cosmic Acceleration: an implementation in CAMB
  Bin Hu, Marco Raveri, Noemi Frusciante, Alessandra Silvestri,
  arXiv:1312.5742 [astro-ph.CO] Phys.Rev. D89 (2014) 103530

• Effective Field Theory of Cosmic Acceleration: constraining dark energy with CMB data
  Marco Raveri, Bin Hu, Noemi Frusciante, Alessandra Silvestri,
  arXiv:1405.1022 [astro-ph.CO] Phys.Rev. D90 (2014) 043513

This is the usual, fair way of giving credit to contributors to a scientific result. In addition, it helps us justify our effort in developing the EFTCAMB code as an academic undertaking.

EFTCAMB is a modification of the CAMB code. The code part of CAMB that is not modified is copyrighted by the CAMB authors and released under their licence.

For the part of code that constitutes EFTCAMB see the LICENSE file in eftcamb/LICENSE.

In addition to CAMB makefile targets EFTCAMB comes with the additional:

• eftcamb: to compile EFTCAMB;
• eftcamb_apps: to compile EFTCAMB applications like the EFTCAMB benchmarker;
• eftcamb_dep: to automatically sort out EFTCAMB source file dependencies;
• eftcamb_doc: to build the EFTCAMB automatic documentation;
• intel_profile: to compile EFTCAMB with the options that allow profiling with the VTUNE profiler;
• profile: to compile EFTCAMB with the options that allow general profiling;

In the folder eftcamb all the source files for EFTCAMB are stored. In an effort to have small and readable files the the naming convention allows to have an intuition of the hierarchy of the code from alphabetical order of files.

For this reason we use the following convention for the prefixes:

• 01_ compile time utilities;
• 02_ pure and general purpose algorithms;
• 03_ EFTCAMB cache containing the storage for all cosmological quantities of interest;
• 04_ general parametrizations for 1D functions;
• 05_ general parametrizations for 2D functions;
• 06_ abstract implementation of EFT models;
• 07_ implementation of pure EFT models;
• 08_ implementation of alternative EFT parametrizations;
• 09_ implementation of designer mapping EFT models;
• 10_ implementation of full mapping EFT models;
• 11_ general EFT algorithms (RGR, stability, init);

If you modify or add one or more files make sure to issue make eftcamb_dep before compiling the code to ensure that all dependencies are properly sorted out and built.