-
Notifications
You must be signed in to change notification settings - Fork 87
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix issues related to database and setting migration
This is a big one, sorry. - Adds an !include tag to the YAML parser, allowing blueprints to refer to external files when useful. These are resolved early on, and the fully-formed document can be re-serialized, or piped into the database for completeness. - Removes the `latticeFile` attribute from the grid blueprints. This was done because it makes the set of input files boundless, which leads to issues in non-file-based approaches to dealing with inputs (e.g., streams, database storage, test fixtures, etc.) - Re-arranges some of the migrations from the geometry.py-based methods of expressing core layout. SystemLayoutInput objects now have a method to render themselves as gridBlueprints. - In support of the above, the radial and axial sub-meshing in the geom files had to be moved to the assembly blueprint, alongside the axialMeshPoints. These should all actually be whipped up from settings, since they are ultimately physics-related (nodal neutronics), but at least for now they are in the same place. The migration capability to move these over is a bit simplistic right now, as to be able to migrate a full-complexity geom file to the blueprints with meshing parameters would require complex modifications to the assembly blueprints.
- Loading branch information
Showing
34 changed files
with
1,007 additions
and
414 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
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
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.