You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was working in implementation of multi-domain (and later multi-material) capability and have noticed that two arrays; u_tau and tau_wall don't have to be arrays at all. They are used in four functions (Src_Kin_K_Eps, Src_Eps_K_Eps, Src_Kin_K_Eps_Zeta_F and Src_Eps_K_Eps_Zeta_F) but are always re-computed, never passed from one to another.
I suggest we turn them into normal variables defined locally in each of these functions. Is this OK for everyone?
The text was updated successfully, but these errors were encountered:
I agree with that it shouldn’t be a “global” array but still be a local one browsing through the boundary cells (since tau_wall can differ from one boundary cell to another in irregular geometries). What do you all think ?
Dear guys,
I was working in implementation of multi-domain (and later multi-material) capability and have noticed that two arrays;
u_tau
andtau_wall
don't have to be arrays at all. They are used in four functions (Src_Kin_K_Eps
,Src_Eps_K_Eps
,Src_Kin_K_Eps_Zeta_F
andSrc_Eps_K_Eps_Zeta_F
) but are always re-computed, never passed from one to another.I suggest we turn them into normal variables defined locally in each of these functions. Is this OK for everyone?
The text was updated successfully, but these errors were encountered: