Rubén Zorrilla

> I tend to agree @pooyan-dadvand about this. Also note that this is the general rule of the project (we use header-only solution when there is no technical alternative). Admittedly,...

> > > > I tend to agree @pooyan-dadvand about this. Also note that this is the general rule of the project (we use header-only solution when there is no...

> > > > > > > > > > > > > I tend to agree @pooyan-dadvand about this. Also note that this is the general rule of the...

> I would go for the unique one until we find a use case for the list. @KratosMultiphysics/technical-committee and @KratosMultiphysics/implementation-committee what you think? Agree. Besides, taking into account how we...

I wonder if we shouldn't implement the rigid body solver in the KratosCore. IMO this is a key capability that can be used not only in the context of co-simulation....

> > > I wonder if we shouldn't implement the rigid body solver in the KratosCore. IMO this is a key capability that can be used not only in the...

I've not much to add in here. But in any case, this is only adding new features that do not interfere with the existent ones (we checked that the `virtual`...

Considering that we're adding a new geometry, which might be of interest to any other Kratos application, I'd add this to the Kratos core. Having said this, I'd create an...

Note that you're adding all the GiD files in the tests. Only the ones strictly necessary to run the test (i.e. the script running the test, material and settings json(s)...

> hm this will probably also change many other test results for sure the ones in CoSim and MeshMoving (=> ale-fluid solver) Potentially yes.