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
Contact action for multiple contact pairs #18022
Comments
@jiangwen84 Feel free to add/correct to this. |
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposes.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposes.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposes.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push.
…ion. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push.
) * Add capability for defining multiple contact pairs in the contact action. Refs. #18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push. * Add missing requirement from test * Address Wen's comments on mechanical contact action * Add capability of defining multiple contact pairs in thermal action * Address Wen's comments II * Address Ben's comment on documentation
Well, unfortunately, I was excited to try the recently-merged code out on a model I'm working with, and it didn't work. I got an error like this:
I'm not sure where it's getting that side set 1002. I'm enforcing contact on sides 1 and 3 and 10 and 11. I have sidesets 1000 and 1001. I can share the model with you, @recuero |
Did not get that issue
|
Doh! I wasn't actually using a version of MOOSE that had your fix merged in. Works fine when I do that! |
…holab#18056) * Add capability for defining multiple contact pairs in the contact action. Refs. idaholab#18022 This capability should work for any node on face combination. The contact parameters for the action will the same for all the contact pairs defined by the user in the form of a vector. A simple example is added for demonstration and initial testing purposest push. * Add missing requirement from test * Address Wen's comments on mechanical contact action * Add capability of defining multiple contact pairs in thermal action * Address Wen's comments II * Address Ben's comment on documentation
Reason
Users may set up problems where multiple (maybe many) contact pairs are needed. It can be tedious to create one block for each possible contact pair.
Design
User will provide a vector of boundary pairs to define mechanical contact. In principle, the same contact-related parameters will be used for all contact pairs.
Impact
More user-friendly contact action
Tasks
The text was updated successfully, but these errors were encountered: