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

Incorrect nodal stress/strain in partitioned coupling with flow #73

Open
norihiro-w opened this issue Aug 29, 2016 · 3 comments
Open

Incorrect nodal stress/strain in partitioned coupling with flow #73

norihiro-w opened this issue Aug 29, 2016 · 3 comments
Labels

Comments

@norihiro-w
Copy link
Contributor

norihiro-w commented Aug 29, 2016

Nodal stress and strain values (usually used only for output) can be wrong if mechanics and flow are coupled in a partitioned way. This is because nodal strain values are always summed up for each solving DEFORMATION process. However, in each coupling iteration, the values should be reset to previous time step values. Nodal displacement and gauss point stress/strain values are still correct.

UPDATE: it seems nodal stresses are correct.

@norihiro-w norihiro-w added the bug label Aug 29, 2016
@ddettrick
Copy link

Hi Norihiro,

What is an example of mechanics and flow being coupled in a partitioned way?

Thanks for your help,

Cheers David

Please visit our new AMD website: www.acidmetalliferousdrainage.com

David Dettrick
Earth Systems | Principal Environmental Engineer/Surface and Groundwater
Hydrologist

14 Church Street, Hawthorn, Victoria, 3122, Australia

T +61 (0)3 9810 7500 | T +61 (0)3 9810 7505 (Direct) | M +61 (0)4
1756 1074

E david.dettrick@earthsystems.com.au | F +61 (0)3 9853 5030 |
www.earthsystems.com.au
http://www.earthsystems.com.au/

This email and its attachments are confidential. If you received this email
in error, please notify the sender and delete.

P Please consider the environment before printing this e-mail

On 30 August 2016 at 00:43, Norihiro Watanabe notifications@github.com
wrote:

Nodal stress and strain values (usually used only for output) can be wrong
if mechanics and flow are coupled in a partitioned way. This is because
nodal strain values are always summed up for each solving DEFORMATION
process. However, in each coupling iteration, the values should be reset to
previous time step values. Nodal displacement and gauss point stress/strain
values are still correct.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#73, or mute the thread
https://github.com/notifications/unsubscribe-auth/ANdsqLkWoNMVC3QUn4kAwQzgSmRyyH3Pks5qkvAcgaJpZM4Jvi-S
.

@norihiro-w
Copy link
Contributor Author

@ddettrick you can get an example from rect.zip. Change $OVERALL_COUPLING from 1 1 to 2 2 and you will see a difference in nodal strain.

I've just noticed that nodal stress is still correct. The description has been updated.

@ddettrick
Copy link

Thanks very much Norihiro.

Cheers David

Please visit our new AMD website: www.acidmetalliferousdrainage.com

David Dettrick
Earth Systems | Principal Environmental Engineer/Surface and Groundwater
Hydrologist

14 Church Street, Hawthorn, Victoria, 3122, Australia

T +61 (0)3 9810 7500 | T +61 (0)3 9810 7505 (Direct) | M +61 (0)4
1756 1074

E david.dettrick@earthsystems.com.au | F +61 (0)3 9853 5030 |
www.earthsystems.com.au
http://www.earthsystems.com.au/

This email and its attachments are confidential. If you received this email
in error, please notify the sender and delete.

P Please consider the environment before printing this e-mail

On 30 August 2016 at 14:29, Norihiro Watanabe notifications@github.com
wrote:

@ddettrick https://github.com/ddettrick you can get an example from
rect.zip https://github.com/ufz/ogs5/files/444008/rect.zip. Change
$OVERALL_COUPLING from 1 1 to 2 2 and you will see a difference in nodal
strain.

I've just noticed that nodal stress is still correct. The description has
been updated.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#73 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANdsqPeSywaKEa4bWRnM96wK7Zo34W5aks5qk7GagaJpZM4Jvi-S
.

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

No branches or pull requests

2 participants