Simplifying simulation cloning with Python scripting

Thanks for the insights, Gaurav!

Unfortunately, I’m a bit confused about these two lines:

Why is this being done again?

Also, as you can see, the word "type" is highlighted differently. I looked it up and found that it can be used either as a function or as a metaclass (whatever taht means).

On top of that, the get_initial_solution_choice() function returns a string — specifically, one of the following: 'Constant values', 'Turbo', 'Techno effects', or 'From solution'.  What do we need that for? "Type" and "dom_params" are not used afterwards in the code.

So I’m a bit lost here.

Hello KBB,

In this computational domain, it can be observed that the plugins for "hexpress_parameters" are required. However, the function associated with "from Solution" is not defined under the "hexpress_parameters" module. Consequently, the module "euranus_parameters" is utilized instead.

The "euranus_parameters" module is specifically designed for turbo applications. It is assumed that the development team will define the "from_solution" functionality for both modules in future versions.

This is indeed awesome. Very helpful