Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

conctact cylinder error: There is no sub model part with name "ComputingContact" in model part "Structure" #12813

Open
luchete80 opened this issue Oct 31, 2024 · 8 comments

Comments

@luchete80
Copy link

luchete80 commented Oct 31, 2024

Description
After some corrections to ContactStructuralMechanics app, I've managed to run an old example: contactcylinders with remeshing.
This is documented in repo https://github.com/luchete80/Kratos_tutorials/
I get:

RuntimeError: Error: There is no sub model part with name "ComputingContact" in model part "Structure"
The following sub model parts are available:
"Contact"
"GENERIC_FixedBase"
"GENERIC_Displacement_Auto1"
"SkinModelPart"
"CONTACT_Contact_master_Auto1"
"CONTACT_Contact_slave_Auto1"
"Parts_Solid_Auto1"
"Parts_Solid_Auto2"

This is happening on search_base_process.py, line 223 which clear and regenerate the subModelPart "Contact".

If I replace subpart "Contact" by "ComputingContact" i get:

self.search_utility_list[key] = CSMA.ContactSearchProcess(self.main_model_part, search_parameters, properties_pair)

RuntimeError: Error: AdvancedContactSearch:: Please add the Contact submodelpart to your modelpart list

On the other hand, I see that test_dynamic_search.py

Scope
Where in Kratos is this bug happening.
E.g.

  • ContactStructuralMechanicsApplication

To Reproduce
Run the (added here) files:
https://github.com/luchete80/Kratos_tutorials/tree/master/contacting_cylinders_fixin
I've replaced the following fropm branch 9.5:
https://github.com/luchete80/Kratos_tutorials/blob/master/Fixings_Remeshing

Expected behavior
Remesh and continue

Environment

  • OS: Ubuntu 22.04
  • Branch: Kratos-9.5 release
  • Python 3.11
@loumalouomega
Copy link
Member

Sorry contact with remeshing is currentñy broken and we could not agree in an interface. This was done in a branch that does not compile anymore (2019 branch)

@luchete80
Copy link
Author

Uhm ok, I will try to run it on that one.
Thank you very much!!!

@loumalouomega
Copy link
Member

Uhm ok, I will try to run it on that one. Thank you very much!!!

The branch was private and lost

@luchete80
Copy link
Author

luchete80 commented Oct 31, 2024

Oh, what a pity. Is a chance to access to a branch/tag from this current repo with similar characteristics? Like version 6.0 or 7.0? Thanks

@loumalouomega
Copy link
Member

Unfortunately not, I uploaded an intermediate branch but it is broken, and the one actually working was in a private computer that I not longer have with me (it was 5 years+ ago)

@loumalouomega
Copy link
Member

I could try to revive the thng, but I would like to agree an interface before any job @rubenzorrilla FYI

@rubenzorrilla
Copy link
Member

Agree. We can discuss and agree about an upgraded interface and implementation. However, unfortunately at the moment we have no resources to allocate here.

@loumalouomega
Copy link
Member

Agree. We can discuss and agree about an upgraded interface and implementation. However, unfortunately at the moment we have no resources to allocate here.

I will think a new design and propose it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants