Skip to content
common astrophysical microphysics routines with interfaces for the different AMReX codes
Fortran Jupyter Notebook Python C++ Makefile TeX Other
Branch: master
Clone or download
Latest commit 3e6ce0f Nov 1, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
EOS
conductivity fix compilation Oct 16, 2019
integration fix some sizes Oct 29, 2019
interfaces VODE90 for simplified SDC (#194) Oct 13, 2019
networks port to CUDA Oct 31, 2019
neutrinos Update dumdt in sneut5 to match Itoh paper, eq. 3.3 Mar 15, 2019
python_library actual_network.f90 -> actual_network.F90 May 28, 2019
rates ifdef CUDA -> ifdef AMREX_USE_CUDA Sep 26, 2018
screening
sphinx_docs another fix Sep 28, 2019
unit_test Initialize state separately to avoid paying UVM cost while timing Oct 28, 2019
util add note May 1, 2019
.gitignore don't store runtime_parameters.rst Sep 28, 2019
.mailmap
.travis.yml Use python 3.7 again. Fix requirements. Dec 20, 2018
.zenodo.json Merge branch 'development' of github.com:StarKiller-astro/Microphysic… Mar 31, 2019
CHANGES.md changes for 19.11 Nov 1, 2019
GMicrophysics.mak
Make.Microphysics
README.md
deploy_docs.sh Add Travis CI deployment from development branch. Dec 20, 2018
id_rsa_travis.enc
requirements.txt Add jupyter and ipywidgets to requirements. Dec 20, 2018

README.md

Build Status DOI

Microphysics

A collection of astrophysical microphysics routines for stellar explosions

There are several core types of microphysics routines hosted here:

  • EOS/: these are the equations of state. All of them use a Fortran derived type eos_t to pass the thermodynamic state information in and out.

  • integration/: this holds the various ODE integrators. Some have been marked up with OpenACC to run on GPUs

  • interfaces/: this holds the Fortran derived types used to interface with the EOS and networks. Note: copies of these are included with Maestro and Castro. They are copied here for testing and to enable other codes to use this repo.

  • networks/: these are the reaction networks. They serve both to define the composition and its properties, as well as describe the reactions and energy release when reactions occur.

  • neutrinos/: this holds the plasma neutrino cooling routines used in the reaction networks.

  • rates/: this contains some common rate routines used by the various aprox networks, and could be expanded to contain other collections of rates in the future

  • screening/: the screening routines for nuclear reactions. These are called by the various networks

  • unit_test/: code specific to unit tests within this repo. In particular,

    • test_eos will test an equation of state by first calling it will (rho, T), and then calling it with other inputs to recover rho and/or T. A cube of data, with rho, T, and X is tested.

    • test_react will call a reaction network on a cube of data (rho, T, X).

  • util: linear algebra routines for the various integrators (including BLAS and LINPACK)

AMReX-Astro Codes

At the moment, these routines are written to be compatible with the AMReX-Astro codes, Maestro and Castro.

To use this repository with AMReX codes, set MICROPHYSICS_HOME to point to the Microphysics/ directory.

There are various unit tests that work with the AMReX build system to test these routines.

Other Simulation Codes

The interfaces are fairly general, so they can be expanded to other codes. This will require adding any necessary make stubs for the code's build system as well as writing unit tests for that build system to ensure the interfaces are tested.

Documentation

A user's guide for Microphysics can be found in Docs/. Type make to build it from its LaTeX source.

A PDF of the user's guide is available here: http://bender.astro.sunysb.edu/Castro/staging/Microphysics/Docs/MicrophysicsUsersGuide.pdf

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.

  • Contributions are welcomed from anyone. Any contributions that have the potential to change answers should be done via pull requests. A pull request should be generated from your fork of Microphysics and target the development branch. (If you mistakenly target master, we can change it for you.)

    Please add a line to CHANGES summarizing your change if it is a bug fix or new feature. Reference the PR or issue as appropriate. Additionally, if your change fixes a bug (or if you find a bug but do not fix it), and there is no current issue describing the bug, please file a separate issue describing the bug, regardless of how significant the bug is. If possible, in both the CHANGES file and the issue, please cite the pull request numbers or git commit hashes where the problem was introduced and fixed, respectively.

    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.

  • On the first workday of each month, we perform a merge of development into master, in coordination with AMReX, Maestro, and Microphysics. 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 StarKiller Microphysics. The criteria for becoming a core developer are flexible, but generally involve one of the following:

  • 10 non-merge commits to Microphysics/ (including Docs/) or one of the problems that is not your own science problem or

  • addition of a new algorithm / module or

  • substantial input into the code design process or testing

Core developers will be recognized in the following ways:

  • invited to the group's slack team

  • listed in the User's Guide and website as a core developer

  • invited to co-author general code papers / proceedings describing StarKiller Microphysics, its performance, etc. (Note: science papers will always be left to the science leads to determine authorship).

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

You can’t perform that action at this time.