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.

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

Add single-app only inputs for testing purposes #489

Open
GiudGiud opened this issue Dec 11, 2024 · 0 comments
Open

Add single-app only inputs for testing purposes #489

GiudGiud opened this issue Dec 11, 2024 · 0 comments
Assignees
Labels
model_maintenance Removing deprecation, adapting to new techniques for performance or usability

Comments

@GiudGiud
Copy link
Collaborator

Reason

It is often the case that the main input (for example neutronics) uses syntax from another app (combined like bluecrab or another single app like pgh).
This prevents using the regular main app for testing that input and requires us to use BlueCrab. This lags finding defects with models, and lets the app teams break our models in a very delayed manner
We have to stop this because it's a huge time sink to fix things in a delayed manner

Design

Create a _base.i to stash most of the syntax of the multiphysics case and share it with the single-physics case
Create "neutronics_only" inputs that shed any unsupported syntax from the neutronics inputs
Similar for other codes

Impact

Reduce maintenance time

@GiudGiud GiudGiud added the model_maintenance Removing deprecation, adapting to new techniques for performance or usability label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model_maintenance Removing deprecation, adapting to new techniques for performance or usability
Projects
None yet
Development

No branches or pull requests

2 participants