-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Problems reading material property in InterfaceKernel #28908
Replies: 2 comments · 5 replies
-
Hello You should share your input and the header as well for the interface kernel. The interface kernel is set to act on an internal boundary between two subdomains right? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @GiudGiud,
And this is the header file:
In this case, the two material properties are not correct. The value is always zero. Thanks again for your help. Best, |
Beta Was this translation helpful? Give feedback.
All reactions
-
I forgot the input file:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @GiudGiud, I have been trying to find the problem with the Material Properties in the InterfaceDiffusion kernel. The values were set to zero because I used the wrong values when initializing the variables in DiscoFluxCPStressUpdate::initQpStatefulProperties().
In interfacediffusiondislocation
And in conservativeadvectiondislocation
As you can see the memory address of the variable in the crystal plasticity (DiscoFluxCPStressUpdate) and the advection kernel (ConservativeAdvection) is the same. And the address of the interface diffusion kernel is different. Does it means that in the interface kernel system we are using the element face material properties? |
Beta Was this translation helpful? Give feedback.
All reactions
-
hi sorry for the delay. I ll get to this this weekend. I tried to find a resource to help earlier but failed. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I can't run the input file, I need the I ll make a MWE to see if I can reproduce this without those |
Beta Was this translation helpful? Give feedback.
All reactions
-
ok I made do with I am not getting uniformly 0 values on my case. So it could have something to do with your mesh. Is it possible for you to share that with me?
Yes that is expected. The interface kernels request "boundary material data" from their inheritance on TwoMaterialPropertyInterface.
Which under the hood maps to boundary material data
So it's a different address than the kernels which use block material data, which is from regular materials. |
Beta Was this translation helpful? Give feedback.
-
Check these boxes if you have followed the posting rules.
Question
Hello Moose community,
I am using a crystal plasticity model where I define material properties that I need to use inside a modified version of ConservativeAdvection kernel and InterfaceDiffusion interface kernel.
When I read the property in the ConservativeAdvection kernel, the material properties are correct and have the same value computed in the crystal plasticity model.
However, when I read the material properties in the InterfaceDiffusion interface kernel the variables are set to zero. Do you know why this can happen?
This is the validParameters and constructor of the "ConservativeDiffusion" kernel:
This is the validParameters and constructor of the "InterfaceDiffusion" interface kernel:
In the interface kernel, the only variable that is correct is
_slip_resistance
. The other variables are always set to zero. Can you please help me with this.Thanks a lor for your help!
Best,
Brayan
Beta Was this translation helpful? Give feedback.
All reactions