Edgar J. Kaiser
Certified Consultant
Please login with a confirmed email address before reporting spam
Posted:
7 months ago
2024/11/28 18:13 JST
Hi Finn,
yes, post processing with nonlocal couplings can be pretty time consuming. The ordinary variables are not part of the solution and thus need to be calculated again and again whenever they are called.
A method that worked for me in the past is to write the result from the nonlocal coupling into a global state variable. State variables ARE part of the solution and no recalculation is needed when they get called in the post processing. The state variables do not carry a unit, so you must take care of correct units by yourself.
Cheers
Edgar
-------------------
Edgar J. Kaiser
emPhys Physical Technology
www.emphys.com
Hi Finn,
yes, post processing with nonlocal couplings can be pretty time consuming. The ordinary variables are not part of the solution and thus need to be calculated again and again whenever they are called.
A method that worked for me in the past is to write the result from the nonlocal coupling into a global state variable. State variables ARE part of the solution and no recalculation is needed when they get called in the post processing. The state variables do not carry a unit, so you must take care of correct units by yourself.
Cheers
Edgar
Please login with a confirmed email address before reporting spam
Posted:
7 months ago
2024/11/29 6:54 JST
Thank you I will try to do that!
Thank you I will try to do that!
Please login with a confirmed email address before reporting spam
Posted:
6 months ago
2024/12/10 21:12 JST
Hi Finn,
yes, post processing with nonlocal couplings can be pretty time consuming. The ordinary variables are not part of the solution and thus need to be calculated again and again whenever they are called.
A method that worked for me in the past is to write the result from the nonlocal coupling into a global state variable. State variables ARE part of the solution and no recalculation is needed when they get called in the post processing. The state variables do not carry a unit, so you must take care of correct units by yourself.
Cheers
Edgar
I tried to implement it. but it increased the solution time quiet a lot unless I select one point as geometric entity. Unfortunately I can not evaluate the state variables. When i try to evaluate a variable under derived variables, I says the variable is undefined.
>Hi Finn,
>
>yes, post processing with nonlocal couplings can be pretty time consuming. The ordinary variables are not part of the solution and thus need to be calculated again and again whenever they are called.
>A method that worked for me in the past is to write the result from the nonlocal coupling into a global state variable. State variables ARE part of the solution and no recalculation is needed when they get called in the post processing. The state variables do not carry a unit, so you must take care of correct units by yourself.
>
>Cheers
>Edgar
I tried to implement it. but it increased the solution time quiet a lot unless I select one point as geometric entity. Unfortunately I can not evaluate the state variables. When i try to evaluate a variable under derived variables, I says the variable is undefined.
Edgar J. Kaiser
Certified Consultant
Please login with a confirmed email address before reporting spam
Posted:
6 months ago
2024/12/10 21:54 JST
Hi Finn,
I only used global state variables and didn't find a significant increase in computation time even in large models and extensive integrations or averages.
If you need to tie the state to a geometrical entity (e.g. a point) you will need to do a respective evaluation e.g. a point evaluation.
A global state will be available in a global evaluation.
Cheers
Edgar
-------------------
Edgar J. Kaiser
emPhys Physical Technology
www.emphys.com
Hi Finn,
I only used global state variables and didn't find a significant increase in computation time even in large models and extensive integrations or averages.
If you need to tie the state to a geometrical entity (e.g. a point) you will need to do a respective evaluation e.g. a point evaluation.
A global state will be available in a global evaluation.
Cheers
Edgar
Please login with a confirmed email address before reporting spam
Posted:
6 months ago
2024/12/11 3:02 JST
Hello Edgar,
thanks for answering. I was a bit confused. If using state variables on component level they are bound to a geometric entity like point, boundary, domain. If instead defined globally that is not necessary and the impact on computation time is little.
I was a bit confused how to set up state variables correctly now I use:
variable_name for State
0 for initial value
if(1>0, expression, variable_name) for update expression
I have them updated at end of step.
Now the variable access is lightning fast!
Thank you!
Hello Edgar,
thanks for answering. I was a bit confused. If using state variables on component level they are bound to a geometric entity like point, boundary, domain. If instead defined globally that is not necessary and the impact on computation time is little.
I was a bit confused how to set up state variables correctly now I use:
variable_name for State
0 for initial value
if(1>0, expression, variable_name) for update expression
I have them updated at end of step.
Now the variable access is lightning fast!
Thank you!