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
Physical variables stored in "topo_vector" returned by calling dynamic topography postprocessor in geoid code #1758
Comments
The dynamic topography is stored in the temperature component. The suface
stress vector is stored in the vector component. Both are in the units that
the rest of the model uses. Most of the time that will mean that dynamic
topography is in meters.
…On Fri, May 19, 2017 at 6:29 PM Shangxin Liu ***@***.***> wrote:
Hi Ian, @ian-r-rose <https://github.com/ian-r-rose>
I noticed that in the new geoid code's dynamic topography function that
directly calls dynamic topography postprocessor, "topo_vector" is the
vector returned by dynamic topography postprocessor, and then "topo_values"
is evaluated at each quadrature points at the cell's boundary face from
that. The "topo_values" is further stored into the surface and CMB dynamic
topography data.
My concern is that what physical variable that "topo_vector" stores? Is it
normal deviatoric shear stress (i.e., (2*viscosity*strain_rate - P*I) *
normal_direction) or the dynamic topography in meter? It seems that it's
actually normal deviatoric shear stress from your new dynamic topography
postprocessor, yes? Because my geoid code requires that
"surface_stored_values" and "CMB_stored_values" stores the dynamic
topography values in meter unit (later in the execute template the scale of
dynamic topography contribution is further calculated), it seems that I
need further change my code a little bit if "topo_vector" is actually the
normal deviatoric shear stress instead of dynamic topography in meter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1758>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFdoN_W_L62wRPzE7ovGHNeFJxIKp0Deks5r7kIMgaJpZM4NhJzV>
.
|
In the dynamic topography part of geoid code, I see that you evaluate the "topo_values" from "topo_vector" by the line 239: and the "topo_vector" is obtained by calling dynamic topography postprocessor in the line 170: and back to your CBF dynamic topography postprocessor: the "topo_vector" is assigned in the line 218: But I didn't see the place where the stress is divided by (density_contrast * gravity) before that. Can you explain this? It seems that I misunderstand or miss something. @ian-r-rose |
Ok. Maybe I got this. I'd like to confirm with you. In your CBF dynamic topography code, At the line 328, "distributed_topo_vector" is reassigned by true dynamic topography in meter of each face_dof_indices: And later in line 380 and 381, "topo_vector" is further reassigned by the true dynamic topography in meter stored in "distributed_topo_vector": Is this the way you assign the final true dynamic topography in meter to "topo_vector"? @ian-r-rose |
Yes, that is right. The |
And what does the line 380 mean? In the dynamic topography part in geoid code, does the line 239 |
Hi Shangxin, line 380 makes sure that all entries for values in ghost cells are communicated correctly between processor boundaries (also see http://dealii.org/developer/doxygen/deal.II/classLinearAlgebra_1_1distributed_1_1Vector.html#a80ce97e2d5d009dd79b2366f8d93ba28).
That is correct, this function evaluates the solution stored in topo_vector at the quadrature points, and stores the result in topo_values. If this answers your question please close the issue. |
Thanks, Rene! I think you already told me this during GRC:) @gassmoeller |
Hi Ian, @ian-r-rose
I noticed that in the new geoid code's dynamic topography function that directly calls dynamic topography postprocessor, "topo_vector" is the vector returned by dynamic topography postprocessor, and then "topo_values" is evaluated at each quadrature points at the cell's boundary face from that. The "topo_values" is further stored into the surface and CMB dynamic topography data.
My concern is that what physical variable that "topo_vector" stores? Is it normal deviatoric shear stress (i.e., (2 * viscosity * strain_rate - P*I) * normal_direction) or the dynamic topography in meter? It seems that it's actually normal deviatoric shear stress from your new dynamic topography postprocessor, yes? Because my geoid code requires that "surface_stored_values" and "CMB_stored_values" stores the dynamic topography values in meter unit (later in the execute template the scale of dynamic topography contribution is further calculated), it seems that I need further change my code a little bit if "topo_vector" is actually the normal deviatoric shear stress instead of dynamic topography in meter.
The text was updated successfully, but these errors were encountered: