Removing support for XML Settings files #612
Merged
Conversation
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
john-science
added
architecture
|
I have tested this PR against ~30 downstream ARMI-based projects, and all of their unit tests still passed. |
|
Very happy about this. I will take a detailed look later today, hopefully. |
jakehader
approved these changes
Apr 2, 2022
keckler
reviewed
Apr 4, 2022
keckler
approved these changes
Apr 4, 2022
keckler
approved these changes
Apr 4, 2022
drewj-usnctech
added a commit
to drewj-usnctech/armi
that referenced
this pull request
Apr 20, 2022
…efine-system-builders * terrapower/master: (24 commits) Update docstring formatting in `getPotentialParentFromSettingValue` (terrapower#627) Removing inherited docstrings from Docs (terrapower#628) Removing bare "import armi" statements (terrapower#626) Fixing assembly number issue in DB Load (terrapower#615) Making the app version more available (terrapower#624) Adding MPI tests to code coverage (terrapower#625) Removing support for XML Settings files (terrapower#612) Minor language cleanup in new standards and practices. (terrapower#610) remove extraneous `mpicov` arg from tox.ini envlist (terrapower#604) Swap flux param (terrapower#605) Fixing _fluxSwapParam for NumPy arrays (terrapower#607) Unshaped component (terrapower#600) Fixing docstring (terrapower#601) Adding options to settings report (terrapower#598) Adding coding standards and practices to Docs (terrapower#597) Removing defunct code from HistoryTrackerInterface (terrapower#594) Fix to a bug where an ARMI application could not call (terrapower#593) Tracking ARMI Requirements (terrapower#590) Remove PyYaml Dependency (terrapower#586) Filling out code coverage for entry points (terrapower#587) ...
albeanth
pushed a commit
to albeanth/armi
that referenced
this pull request
Apr 21, 2022
scottyak
pushed a commit
to scottyak/armi
that referenced
this pull request
Oct 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR removes support for the XML CaseSettings files. From here on out we will only support the YAML format.
This is meant as a simplification step. You will notice that much code can be removed when dropping this support; and much of the code that is left is simpler.
As part of this "clean out the old stuff we don't use any more" I hope to soon drop support for XML blueprint files, and the old geomFiles.
I think ARMI could be simpler and easier to understand. Dropping complicated support for old, defunct features is an easy win toward this end. For instance, our support for XML input/data file is holding back a PR at this very moment:
#595 (comment)
Also, I think I have seen a lot of activity lately where XML input files and the old geomFiles have made our current work much slower than it needs to be.
Checklist
If user exposed functionality was added/changed:
setup.py.