Dear Konstantinos, dear Andriy,

First, thanks for your detailled replies. It does really help!

To give some context, i am trying to implement something akin to non
intrusive domain decomposition coupling between, let's say, the part of the
domain involving local nonlinearities, handled by Getfem, and the whole
global domain, not "directly" handled by Getfem.

I thought it might have been necessary to obtain the "internal forces" at
the interface to assess the equilibrium between the domains but, now, i am
not sure it is actually required.

I will give it some thoughts.
Thanks again,
Best regards,

David.

Le ven. 24 sept. 2021 à 11:51, Konstantinos Poulios <logar...@googlemail.com>
a écrit :

> Dear David,
>
> There are different ways of calculating the "nodal forces". Probably the
> easiest one is to remove or disable the boundary condition terms and
> re-calculate the model residual with the solution that you had obtained
> with BCs enabled. After disabling BC's the model residual will not be zero
> any more but it will have the forces you are looking for in the entries
> that correspond to displacement dofs.
>
> However, nodal forces have absolutely no relevance for the problem you are
> solving. You should instead be interested in reaction tractions in stress
> units or some other meaningful physical quantity. Reaction tractions are
> e.g. a result with physical meaning which is not mesh dependent. So please
> reformulate your question describing what kind of result you are actually
> interested in. What kind of structural analysis do you want to perform? One
> thing is certain, you are not really interested in nodal forces.
>
> Best regards
> Kostas
>
>
>
>
>
>
> On Fri, Sep 24, 2021 at 11:21 AM Andriy Andreykiv <
> andriy.andrey...@gmail.com> wrote:
>
>> Dear David,
>>
>> There can be several ways to get the reaction forces. If you've applied
>> your Dirichlet boundary conditions with Lagrange multipliers, then your
>> reaction tractions (so, not forces) are the Lagrange multipliers.
>> If you want to obtain the nodal forces, you would need to integrate the
>> Lagrange multipliers alone the Dirichlet boundary, by assembling something
>> like:
>>
>> Test_u . Lagrange_multiplier
>>
>> In case you applied the Dirichlet condition somehow else and you have the
>> stress field, you can indeed apply the method you've mentioned. However,
>> what you call the nodal forces on the whole domain will be mostly zero (as
>> they balance each other in case of pure static solution), except the
>> boundary where you've applied the Dirichlet condition. But still, assuming
>> that you have Sigma tensor field in the Gauss points as im_data, you can do
>> the assembly over the whole domain as in the formula you've mentioned:
>>
>> "Sym(Grad_Test_u) : Sigma"
>>
>> I don't really remember this well, but I believe this can be simplified
>> to Grad_Test_u : Sigma when we know that Sigma is a symmetric tensor. What
>> is probably different in Getfem from most of the Finite Element text-books
>> is that Getfem always uses true tensors, as opposed to the Voight notation
>> in your example. For instance, that *B* - matrix in your text is a
>> Voight representation of a symmetric operator on the gradient of the shape
>> functions. While *B* is 6x3 in 3D, Grad_Test_u should be seen as 3x3,
>> but Sigma is 3x3, unlike stress vector in Voight notation which is 6x1.
>> This probably has some performance overhead as true tensors are not as
>> compact as the matrices in the Voight notation, but it preserves all the
>> good properties of the tensors and makes the derivations cleaner.
>>
>> Let me know if you have any other questions,
>>
>>   Andriy
>>
>>
>>
>>
>> On Fri, 24 Sept 2021 at 10:05, David Danan <daviddanan9...@gmail.com>
>> wrote:
>>
>>> Dear GetFem community,
>>>
>>> after the computation of reaction forces associated to a dirichlet
>>> condition, which gave acceptable results, i am trying now to compute the
>>> nodal forces on the whole domain, here is the expression for each element
>>>
>>> [image: image.png]
>>> By using the GWFL, is it possible to compute such quantity as a
>>> post-processing?
>>> My best guess is that i have to use the local projection method but i am
>>> stucked regarding the rest. Any idea? Is there another way to do that?
>>>
>>> Thanks in advance,
>>> David.
>>>
>>

Reply via email to