Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Loading Unstable Nuclides from the RIPL-3 Database using the ARMI_RIPL_PATH Environment Variable #74

Merged
merged 2 commits into from
May 15, 2020
Merged

Loading Unstable Nuclides from the RIPL-3 Database using the ARMI_RIPL_PATH Environment Variable #74

merged 2 commits into from
May 15, 2020

Commits on May 15, 2020

  1. Adding an ARMI_RIPL_PATH environment variable to determine if 

    nuclide bases should read in unstable nuclide data from the RIPL-3
data files. These data files are not distributed with the framework,
so a user will have to download them separately.
    @jakehader
    jakehader committed May 15, 2020
    Configuration menu
    Copy the full SHA
    c8c47f9 View commit details
    Browse the repository at this point in the history

  2. Addressing review comments and adding installation documentation for the 

    RIPL-3 decay data files within the `user_install.rst` file.

After rending the HTML docs for `nuclideBases` I noticed that the nuclide
table was too large for the section, so I removed the MC2-2 and MC2-3
labels from the table. These seem to be implementation details that
aren't necessarily required at a high-level to understand the nuclide
objects.
    @jakehader
    jakehader committed May 15, 2020
    Configuration menu
    Copy the full SHA
    c338824 View commit details
    Browse the repository at this point in the history