-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Improve MooseObject::mooseError()
with more context, correct file paths with many inputs
#26945
Improve MooseObject::mooseError()
with more context, correct file paths with many inputs
#26945
Conversation
Job Documentation on e662172 wanted to post the following: View the site here This comment will be updated on new commits. |
1519080
to
16b4d43
Compare
MooseObject::mooseError()
with more context
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise looks fine
Good again. Changes: resolved your request, added 5e9aad1. This lets you associate actions that you create in a meta action with a parameter. Easiest example is |
Job Test timings on e662172 wanted to post the following: View timings here This comment will be updated on new commits. |
Job Coverage on e662172 wanted to post the following: Framework coverage
Modules coverageExternal petsc solver
Optimization
Peridynamics
Solid mechanics
Stochastic tools
Thermal hydraulics
Full coverage reportsReports
Warnings
This comment will be updated on new commits. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jk, should resolve app errors
Reminder for self: Still need to resolve file name parameters |
What is the confusion? It is possible that I am the confused one. Do we expect the changes here to incur app failures, and the plan is to patch them? |
The path base where to look for |
MooseObject::mooseError()
with more contextMooseObject::mooseError()
with more context, correct file paths with many inputs
Excuse all of the spam, I didn't plan on this needing this much more... but it is actually ready for review. few app failures, working on those fixes. |
e6b2940
to
0423b82
Compare
0423b82
to
cf41d0e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see anything concerning here. The only thing I didn't understand as a whole is the "clone" versus "copyConstruct" calls I see. It appears we are using both. What's the difference?
Clone duplicates the input parameters and creates a new object from those parameters (less chance at screwing up state). Copy construct is really only used in two cases: direct copy construct for mesh and relationship managers |
Closes #26947
MooseObjectAction
, their moose errors are associated with the syntax location for the associated actionapplyParameters()
from the action's parameters,paramError()
within said objects will be linked directly to the action's parametersFactory
orActionFactory
App patches: