-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #528 from idaholab/mat_deprecate
Marked material_components for deprecation.
- Loading branch information
Showing
7 changed files
with
163 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
.. _migrate 0 1: | ||
|
||
Migration plan for MontePy 1.0.0 | ||
================================ | ||
|
||
.. meta:: | ||
:description: Migration plan for moving from MontePy 0.x to MontePy 1.0.0 | ||
|
||
Necessity | ||
--------- | ||
|
||
The MCNP 6.2 and 6.3 manuals are ambiguously worded around whether nuclides can be repeated in a material definition. | ||
Due to this the authors of MontePy in MontePy 0.x.x assumed that repeated nuclides were not allowed. | ||
Due to this assumption material composition data were stored in python dictionary, | ||
where the keys were the nuclide and their library. | ||
Due to this if duplicate nuclides are present only the last instance of that nuclide will have its information preserved in the model. | ||
This is clearly not a desired outcome. | ||
|
||
However, it has been confirmed that duplicate nuclides are allowed in MCNP, | ||
and can be advantageous. | ||
See :issue:`504` for more details. | ||
Due to this it was decided that the best way forward was to abandon the old design, | ||
and to create a brand new data structure. | ||
This means that backwards compatibility *will* be broken, | ||
and so this fix is leading to a major version release. | ||
|
||
|
||
Deprecations | ||
------------ | ||
The following properties and objects are currently deprecated, | ||
and will be removed in MontePy 1.0.0. | ||
|
||
* :func:`montepy.data_inputs.material.Material.material_components`. | ||
This is the dictionary that caused this design problem. | ||
|
||
* :class:`montepy.data_inputs.material_components.MaterialComponents` | ||
This is the class that stores information in the above dictionary. | ||
It is largely excess object wrapping, that makes the material interface | ||
overly complex. | ||
|
||
* :class:`montepy.data_inputs.Isotope` will be renamed to ``Nuclide``. | ||
This is to better align with MCNP documentation, | ||
and better reflect that the nuclear data for a nuclide can represent | ||
isotopic, isomeric, or atomic data. | ||
|
||
|
||
New Interface | ||
------------- | ||
Currently the replacement interface has not been fully designed yet. | ||
If you have input you can `join the discussion <https://github.com/idaholab/MontePy/discussions/475>`_. | ||
There will also be some alpha-testing announced in that discussion. | ||
|
||
Once MontePy 1.0.0 is released this will be updated with information about the new interface, | ||
and how to migrate to it. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,5 +9,6 @@ User Guide | |
utilities | ||
tricks | ||
faq | ||
migrations/migrate0_1 | ||
changelog | ||
publications |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.