Rubén Zorrilla

> Remember to merge [KratosMultiphysics/GiDInterface#971](https://github.com/KratosMultiphysics/GiDInterface/pull/971) after Sure! Thanks for the reminder in any case.

@uxuech any advance in this regard?

> > Why it is needed to have a different analysis stage for remeshing? > > Because if you remesh you need to reinitialize everything, maybe we can integrate the...

> … I know this... What I'm asking is in which situation you might want to remesh before and after the InitializeSolutionStep()?

> > > > ContactStructuralMechanicsApplication > > > > > > > > > @KratosMultiphysics/technical-committee consider it to be in a very good state. Nevertheless, our impression is that it...

@loumalouomega, let me clarify something based on your last response. Utility applications necessarily need to not include any physics. The `ContactStructuralMechanicsApplication` does so, meaning that it cannot be a utility...

I'd follow @philbucher 's suggestion as it keeps the "automatic" handling of the flush, which I find is more convenient for the user.

Lets wait for the merge until it is also available in Kratos master.

@KratosMultiphysics/technical-committee has been discussing about this again. We are in favour of the change as current behaviour might be misleading. However, we're afraid of how this propagates through the code....

Shouldn't we add this to the base implicit strategy?