moose icon indicating copy to clipboard operation
moose copied to clipboard

Allow higher-order variables to be read in from previous solution

Open jessecarterMOOSE opened this issue 8 months ago • 2 comments

Motivation

Using SolutionUserObject to read in previous solution data (from Exodus for example) is only correct for first-order variables. A first order variable is used to store the data from the mesh, so higher-order variable data can be incorrectly interpolated.

Design

Either have the intermediate variable order be chosen automatically based on the mesh, or allow user to specify variable order. I'm leaning towards the latter so as to not make any incorrect assumptions about what the user wants to do.

Impact

More accurate restarts

jessecarterMOOSE avatar Jun 12 '25 13:06 jessecarterMOOSE

I suppose this is addressed up to second order for nodal variables. That is sufficient for my current needs, but others may have use for more cases.

jessecarterMOOSE avatar Jun 13 '25 01:06 jessecarterMOOSE

There is only so much we are going to be able to do here without reworking the output as well. Let's leave it open

GiudGiud avatar Jun 13 '25 01:06 GiudGiud