Support mesh metadata on restart/recover/checkpoint

loganharbour commented 1 year ago

Reason

Currently, if you query for mesh metadata outside of restart/recover/checkpoint, you have all of the data available. This is because it is declared by the mesh generators that generate it in the same run. When you go to get this data later on, of course it exists.

However... when you run from restart/recover/.cpr mesh file... nothing has requested or declared any of the data. First problem here is that we do not know the type of the data to load into (which is required by the restartable system). Secondly, we don't know what mesh generators existed in the previous run.

Design

Store data on the mesh generator tree and names so that it can be traversed on a second run. Use this storage the primary data structure by which we get meta data during restart recover and also not during it (for consistency).
Enable the late load of individual pieces meta data so that we can pull in this data later

Impact

Extends mesh meta data capability to restart/recover; new feature.

loganharbour commented 1 year ago

Refs https://github.inl.gov/ncrc/griffin/issues/1438

NamjaeChoi commented 1 year ago

I guess what you mean by "late load" is to load all the data into a simple char buffer first and convert it later on request?

NamjaeChoi commented 1 year ago

And how close is this to completion?

YaqiWang commented 1 year ago

If the declared meta data depend on the input parameters, I guess we will need to store the input parameters?

NamjaeChoi commented 1 year ago

One more question, will this fix the inability to omit the second argument (prefix) in getMeshProperty when it is called in places other than the mesh generators? How will you resolve duplicate metadata names with different prefix?

idaholab / moose