ContactStructuralMechanicsApplication - Python coupling #11774
Unanswered
sunethwarna
asked this question in
Q&A
Replies: 4 comments 4 replies
-
I don't remember why I did that, but could be... |
Beta Was this translation helpful? Give feedback.
1 reply
-
I can remove it if it is not killing anyone's use cases. :D |
Beta Was this translation helpful? Give feedback.
2 replies
-
We got a request that, they would like to use |
Beta Was this translation helpful? Give feedback.
1 reply
-
Is this sitll an issue? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all,
We have out that, one of the strategies in
ContactStructuralMechanicsApplication
includespybind
headers to getpython::Process
type as shown below:Kratos/applications/ContactStructuralMechanicsApplication/custom_strategies/custom_strategies/residualbased_newton_raphson_contact_strategy.h
Lines 33 to 34 in 794c315
Followings are some use cases of the
pybind
includes in the same file:Kratos/applications/ContactStructuralMechanicsApplication/custom_strategies/custom_strategies/residualbased_newton_raphson_contact_strategy.h
Line 136 in 794c315
Kratos/applications/ContactStructuralMechanicsApplication/custom_strategies/custom_strategies/residualbased_newton_raphson_contact_strategy.h
Lines 855 to 859 in 794c315
Would it be possible to change these from
python::Process
toKratos::Process
and decoupleContactStructuralMechanicsApplication
toContactStructuralMechanicsCore
andContactStructuralMechanicsApplication
as in other applications?@loumalouomega ?
Beta Was this translation helpful? Give feedback.
All reactions