Skip to content
AMReX: Software Framework for Block Structured AMR
C++ Fortran C Roff Python Mathematica Other
Branch: master
Clone or download
Latest commit 93fb085 Nov 1, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Docs Add documentation about: Oct 26, 2019
OldTutorials Move DataServicesTest0 from OldTutorials into Tests Aug 14, 2019
Src AmrCore::regrid: return if the base level is already the max level. Nov 1, 2019
Tests remove FabView from BaseFab Oct 23, 2019
Tools For OpenACC where CCOMP is not pgc++, still include openacc.h Oct 30, 2019
Tutorials Add MultiFab parallel prefix sum tutorial example. Oct 25, 2019
paper fix IAMR DOI May 12, 2019
.gitignore update gitignore Dec 20, 2018
.travis.yml (travis) remove this package Sep 4, 2019
CHANGES update CHANGES Nov 1, 2019
CMakeLists.txt CMake: turn off tutorials by default Jun 18, 2019 fix some makefiles for the MacProjector change Oct 17, 2019
INSTALL minor update May 1, 2018
LICENSE trigger travis Jul 24, 2019 add citation to May 12, 2019 id_rsa_travis -> deploy_key Jul 30, 2019
configure fix shebang Apr 26, 2017
deploy_key.enc update deploy key used by Travis CI Jul 30, 2019

Citing DOI


AMReX Copyright (c) 2017, The Regents of the University of California, through Lawrence Berkeley National Laboratory and the Alliance for Sustainable Energy, LLC., through National Renewable Energy Laboratory (subject to receipt of any required approvals from the U.S. Dept. of Energy). All rights reserved.

If you have questions about your rights to use or distribute this software, please contact Berkeley Lab's Innovation & Partnerships Office at

NOTICE. This Software was developed under funding from the U.S. Department of Energy and the U.S. Government consequently retains certain rights. As such, the U.S. Government has been granted for itself and others acting on its behalf a paid-up, nonexclusive, irrevocable, worldwide license in the Software to reproduce, distribute copies to the public, prepare derivative works, and perform publicly and display publicly, and to permit other to do so.

License for AMReX can be found at LICENSE.

Development Model

Development generally follows the following ideas:

  • New features are committed to the development branch.

    Nightly regression testing is used to ensure that no answers change (or if they do, that the changes were expected).

    If a change is critical, we can cherry-pick the commit from development to master.

  • Bug fixes, questions and contributions of new features are welcome!

    • Bugs should be reported through GitHub issues

    • We suggest asking questions through GitHub issues as well

    • Any contributions of new features that have the potential to change answers should be done via pull requests. A pull request should be generated from your fork of amrex and target the development branch.

      If there are a number of small commits making up the PR, we may wish to squash commits upon merge to have a clean history. Please ensure that your PR title and first post are descriptive, since these will be used for a squashed commit message.

      Please note the following: If you choose to make contributions to the code then you hereby grant a non-exclusive, royalty-free perpetual license to install, use, modify, prepare derivative works, incorporate into other computer software, distribute, and sublicense such enhancements or derivative works thereof, in binary and source code form.

  • On the first workday of each month, we perform a merge of development into master. For this merge to take place, we need to be passing the regression tests.

    To accommodate this need, we close the merge window into development a few days before the merge day. While the merge window is closed, only bug fixes should be pushed into development. Once the merge from development -> master is done, the merge window reopens.

Core Developers

People who make a number of substantive contributions will be named "core developers" of AMReX. The criteria for becoming a core developer are flexible, but generally involve one of the following:

  • 100 non-trivial commits to amrex/Src/ and/or

  • addition of a new algorithm / module and/or

  • substantial input into the code design process or testing

If a core developer is inactive for multiple years, we may reassess their status as a core developer.

The current list of core developers is: Ann Almgren (LBNL), Vince Beckner, John Bell (LBNL), Johannes Blaschke (LBNL), Cy Chan (LBNL), Marcus Day (LBNL), Brian Friesen (NERSC), Kevin Gott (NERSC), Daniel Graves (LBNL), Max Katz (NVIDIA), Andrew Myers (LBNL), Tan Nguyen (LBNL), Andrew Nonaka (LBNL), Michele Rosso (LBNL), Sam Williams (LBNL), Weiqun Zhang (LBNL), Michael Zingale (Stonybrook University).


To cite AMReX, please use Citing

  doi = {10.21105/joss.01370},
  url = {},
  year = {2019},
  month = may,
  publisher = {The Open Journal},
  volume = {4},
  number = {37},
  pages = {1370},
  author = {Weiqun Zhang and Ann Almgren and Vince Beckner and John Bell and Johannes Blaschke and Cy Chan and Marcus Day and Brian Friesen and Kevin Gott and Daniel Graves and Max Katz and Andrew Myers and Tan Nguyen and Andrew Nonaka and Michele Rosso and Samuel Williams and Michael Zingale},
  title = {{AMReX}: a framework for block-structured adaptive mesh refinement},
  journal = {Journal of Open Source Software}
You can’t perform that action at this time.