Javi Gárate

@maceligueta @juliobarna At this point, the problemtype generates: - mdpa with nodes, elements and submodelpart for the floor - project parameters json - materials file - laser file [melting.gid.zip](https://github.com/KratosMultiphysics/GiDInterface/files/7526910/melting.gid.zip)

Hi @AlejandroCornejo Could you attach an example of that backward normal issue? I'm checking the `rayleigh_alpha `one

Hi Dr. @AlejandroCornejo , I've tested your case (changing a bit the end_time and the pressure and I got this contact  I don't know about that normal direction issue,...

I was planning to create 2 examples (2D and 3D) for the Structural mechanics application where we can see the contact working. Maybe it's a good moment to close this...

Hi @rubenzorrilla and @adityaghantasala My proposal for the ProjectParameters > solver_settings is the following: ```json "solver_settings": { "implementation": "MPC", "model_part_name": "FluidModelPart", "domain_size": 2, "solver_type": "Monolithic", "model_import_settings": { "input_type": "mdpa", "input_filename":...

ping @KratosMultiphysics/fluid-dynamics

Thanks @rubenzorrilla Let @soudah play in this branch. I won't allow the merging until a Bio** Application (derived from fluid dynamics) is created for these changes.

In my solution, I need several servers behind an nginx The urls are: www.server.com/view/user1 www.server.com/view/user2 ... The only way to get there is by adding the path as querystring www.server.com/view/user1?path=/view/user1/websockify...

Yes we do > > only silicon, I don't have an intel machine on hand :/ > > Usually is more complex to compile in silicon, so it should work....

Hi @AFranci The first part, if you have tested it and works, it's fine. For the second query, I could not reproduce it, so send me more information if it's...