Máté Péntek

Do I understand correctly, that we prefer an incorrect implementation because of performance for explicit simulation in the expense of a correct implementation?

I would be in favour of having various ideas from @miguelmaso extending the StatisticsApplication.

Start with having a look at the restart requirements and capabilities of FluidDynamicsApp and StructuralMechanicsApp. Here we use it extensively separately. Once we go to Fluid-Structure-Interaction (FSI), which uses these...

Definitely go for a combination of bash script with the MainKratos. We do it on Linux clusters for large jobs without an issue. And we do have jobs that fail....

@roigcarlo it is pretty concerning it these were turned off @philbucher I will try to take a look asap @mtnzguillermo this might effect you as well

Hopefully fixed with #10108.

Oh, it turns out we actually need this as well :-)

Thanks for the draft. Will be working here. ping @RiedlAndreas

@loumalouomega I can see of 2 reasons. 1 - temporary - for now the testing and development is simpler, as one only need the CoSim to test and use. It...

Adding to the list of ToDo-s: - [x] Output time is not rounded (essential for restart), [see here](https://github.com/KratosMultiphysics/Kratos/blob/c55c4743923c2e9a432c6bef094307f76232e3ab/applications/CoSimulationApplication/python_scripts/solver_wrappers/rigid_body/rigid_body_solver.py#L246) - [ ] Takes the restarting capabilities [from here](https://github.com/KratosMultiphysics/Kratos/blob/894f3263ad66d6705c5e4fca2f7a070d9fff89be/applications/CoSimulationApplication/python_scripts/solver_wrappers/rigid_body/rigid_body_solver.py#L536), makes it aligned...