Rubén Zorrilla

@RiccardoRossi @loumalouomega which is the status of this?

> In this regard, I'd ask to enforce the 3.8 version of python once we kind of solve this... Otherwise a lot of people will be affected See #10428.

Again, why the rigid body solver capability is not being added to the Core? Is there any technical limitation?

> > We define `start_time`, `end_time` in the `problem_data` section, and time step somewhere in the `solver_settings` (not in a consistent manner also). Which kind of feels like time marching...

Agree. This cannot be used in current state so an eventual user of it (which in my opinion is nonexistent) must had edited it in a custom repo.

For me it makes sense. Maybe what we could do is to take the chance to make the current `GlobalCoordinates` to call this one with the default integration method. Something...

> > For me it makes sense. Maybe what we could do is to take the chance to make the current `GlobalCoordinates` to call this one with the default integration...

> > If I'm not wrong, the same can be achieved with the `CopyModelPartNodalVar`. Besides this synchronization is missing. > > hmm checking this method, I think that the previous...

Fine for me. Thanks for the fix.

> Maybe to avoid all this hassle, @rubenzorrilla cannot you use the BaseClass as the dummy? mmm... depends on how we do the writing in the GUI. But you raised...