[joaquinirazabal]

Extends the Dam Transfer results interface with the final-state/initial-state workflow:

• Export final state.
• Import initial state.

Both sections contain directly editable repeatable part entries. Each part can use its own file and field selection. Export and Import can both be enabled in the same calculation.

[rubenzorrilla]

I'm not sure about the final purpose of the refactoring you're doing. However, from the context, I note that you might be interested in the multi-stage capabilities already provided by the KratosCore orchestrators.

I just wanted to let you know about this just in case you were not aware.

[joaquinirazabal]

I'm not sure about the final purpose of the refactoring you're doing. However, from the context, I note that you might be interested in the multi-stage capabilities already provided by the KratosCore orchestrators.

I just wanted to let you know about this just in case you were not aware.

Thank you for the advice, @rubenzorrilla. What we need is a capability that allows us to transfer stresses from one simulation to another. Until now, our approach has been to run an initial simulation applying only certain loads, mainly the self-weight of the dam, and then transfer the resulting stresses (but not the displacements) to a new simulation where hydrostatic and thermal loads are applied.

Regarding the thermal state, another possibility is to save both the reference temperature of the concrete dam (for example, at the end of construction) and the actual temperature, and use them as the initial state in a new simulation.

Do you think the multi-stage capabilities provided by the KratosCore orchestrators could help us with this workflow?

[rubenzorrilla]

I'm not sure about the final purpose of the refactoring you're doing. However, from the context, I note that you might be interested in the multi-stage capabilities already provided by the KratosCore orchestrators.
I just wanted to let you know about this just in case you were not aware.

Thank you for the advice, @rubenzorrilla. What we need is a capability that allows us to transfer stresses from one simulation to another. Until now, our approach has been to run an initial simulation applying only certain loads, mainly the self-weight of the dam, and then transfer the resulting stresses (but not the displacements) to a new simulation where hydrostatic and thermal loads are applied.

Regarding the thermal state, another possibility is to save both the reference temperature of the concrete dam (for example, at the end of construction) and the actual temperature, and use them as the initial state in a new simulation.

Do you think the multi-stage capabilities provided by the KratosCore orchestrators could help us with this workflow?

I think they can help a lot. They provide a native mechanism to do exactly this sort of things. Per regards the temperature, and assuming that the model part is the same, I'm sure it is straightforward (I've already done it indeed). For the internal variables, it is a bit more delicate, but I'm sure it can be handled with an auxiliary process, in the line of the implementations you've pushed recently.
The nice thing of the orchestrator mechanism is that you'll be able to avoid your main script concatenating the simulations, as the native implementation will do it for you.

You can see a fluid dynamics application similar to yours here.

[joaquinirazabal]

I'm not sure about the final purpose of the refactoring you're doing. However, from the context, I note that you might be interested in the multi-stage capabilities already provided by the KratosCore orchestrators.
I just wanted to let you know about this just in case you were not aware.

Thank you for the advice, @rubenzorrilla. What we need is a capability that allows us to transfer stresses from one simulation to another. Until now, our approach has been to run an initial simulation applying only certain loads, mainly the self-weight of the dam, and then transfer the resulting stresses (but not the displacements) to a new simulation where hydrostatic and thermal loads are applied.
Regarding the thermal state, another possibility is to save both the reference temperature of the concrete dam (for example, at the end of construction) and the actual temperature, and use them as the initial state in a new simulation.
Do you think the multi-stage capabilities provided by the KratosCore orchestrators could help us with this workflow?

I think they can help a lot. They provide a native mechanism to do exactly this sort of things. Per regards the temperature, and assuming that the model part is the same, I'm sure it is straightforward (I've already done it indeed). For the internal variables, it is a bit more delicate, but I'm sure it can be handled with an auxiliary process, in the line of the implementations you've pushed recently. The nice thing of the orchestrator mechanism is that you'll be able to avoid your main script concatenating the simulations, as the native implementation will do it for you.

You can see a fluid dynamics application similar to yours here.

That's great, I wil take a look. Thanks again!