pyne / data

Repository for the storage of all PyNE related data dependencies

PyNE: The Nuclear Engineering Toolkit

The PyNE project aims to provide a common set of tools for nuclear science and engineering needs.

If you are interested in the package itself, or would like to help and contribute, please let us know either on the mailing list (https://groups.google.com/forum/#!forum/pyne-dev, [email protected]) or github.

Examples, documentation, and more can be found at https://pyne.io, the official PyNE project site.

Installation

Dependencies

PyNE has the following dependencies:

1. Fortran compiler
2. C++ compiler
3. CMake (>= 2.8.5)
4. NumPy (>= 1.8.0)
5. SciPy
6. Cython (>= 0.29.21)
7. HDF5
8. PyTables
9. Python (>= 3.5.2)
10. LAPACK
11. BLAS
12. Jinja2

Optional Depenendencies:

1. MOAB
2. DAGMC
3. OpenMC

To run tutorial and examples:

1. jupyter

Additionally, building the documentation requires the following:

1. Sphinx
2. sphinxcontrib-bibtex
3. PrettyTable
4. numpydoc
5. jupyter

Most of the dependencies are readily available through package managers (such as MacPorts, Anaconda, etc.). Visit our installation page for instructions on getting PyNE up and running on your device.

Contributing

We highly encourage contributions to PyNE! If you would like to contribute, it is as easy as forking the repository on GitHub, making your changes, and issuing a pull request. If you have any questions or need assistance during this process, don't hesitate to reach out to the PyNE mailing list (https://groups.google.com/forum/#!forum/pyne-dev, [email protected]).

data's Issues

Add data that used to be served by data.pyne.io

The main pyne repo refers to data served by data.pyne.io in N places:

• virtual machine (that was probably out of date anyway) pyne-0.5+yt.ova
• mcnp_n_impr_fluka.h5m sample data for plotting originally provided by @pshriwise as part of examples
• fng_userbin22.h5m sample data for plotting originally provided by @pshriwise as part of examples
• teapot.h5m sample data for visualization originally provided by @elliottbiondo
• kaeri.zip tarball of data from KAERI originally compiled by @scopatz
• prebuilt_nuc_data.h5 copy of prebuilt nuclear data originally compiled by @scopatz
• origen-benchmark-hdf5-1.8.13.h5 (and ...1.8.14.h5) provided for testing of decay. 1.8.13 version probably provided by @scopatz but 1.8.14 version probably provided by @kkiesling

prebuilt_nuc_data.h5 needs an update

As suggested by @pshriwise here, the current prebuilt_nuc_data.h5 file needs updating. The update should incorporate the new atomic mass data from mass.mas16, namely adjusting the atomic_mass and material_library groups.

Perhaps some changes here should launch PyNE CI for testing

The recent change in distribution of the cram code caused PyNE CI to fail. Perhaps some version of CI could be implemented for some kind of changes to this repo. Or CI could always be invoked, but perform different tests depending on the kind of change...

No documentation on how to update `cram.tar.gz`

The README file indicates how to update decay.tar.gz but not how to update cram.tar.gz

No documentation on how to build platform-specific assembly code versions of `cram` and `decay`

This would be useful for long term maintainability. Might also lead to someone doing this for enrichment_symbolic