Skip to content

Latest commit

 

History

History
64 lines (49 loc) · 2.48 KB

README.md

File metadata and controls

64 lines (49 loc) · 2.48 KB

Meraxes

pre-commit

The Meraxes semi-analytic galaxy formation model.

Tip

See BUILD.md for detailed build instructions.

Attribution

If you use this code or its results in any publications, please cite Mutch et al. 2016b (MNRAS, 462, 250):

@ARTICLE{2016MNRAS.462..250M,
   author = {{Mutch}, S.~J. and {Geil}, P.~M. and {Poole}, G.~B. and {Angel}, P.~W. and 
	{Duffy}, A.~R. and {Mesinger}, A. and {Wyithe}, J.~S.~B.},
    title = "{Dark-ages reionization and galaxy formation simulation - III. Modelling galaxy formation and the epoch of reionization}",
  journal = {\mnras},
archivePrefix = "arXiv",
   eprint = {1512.00562},
 keywords = {galaxies: formation, galaxies: high redshift, dark ages, reionization, first stars},
     year = 2016,
    month = oct,
   volume = 462,
    pages = {250-276},
      doi = {10.1093/mnras/stw1506},
   adsurl = {http://adsabs.harvard.edu/abs/2016MNRAS.462..250M},
  adsnote = {Provided by the SAO/NASA Astrophysics Data System}
}

If you use any of the following features, please also cite the relevant papers:

AGN model : Qin et al. 2017 (arXiv:1703.04895)

Minihalo model : Ventura et al. 2024 (arXiv:2401.07396)

Contributors

  • Simon Mutch (Lead author; The University of Melbourne)
  • Paul Geil (The University of Melbourne)
  • Yuxiang Qin (The University of Melbourne)
  • Hansik Kim (The University of Melbourne)
  • Greg Poole (Astronomy Data and Compute Services)
  • Yisheng Qiu (The University of Melbourne)
  • Brad Greig (The University of Melbourne)
  • Emanuele Maria Ventura (The University of Melbourne)

How to contribute

  1. Fork the official repository.
  2. Make your changes in a new, appropriately named branch (e.g. mutch_starformation or fix_progenitor_order).
    • All git commit messages should loosely follow the standard format outlined here.
    • Ensure your new code is commented enough so that others can understand what it's doing.
  3. Issue a pull request to the official repository.