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

More native functionality for quadrature points #185

Closed
GregVernon opened this issue Aug 12, 2020 · 3 comments
Closed

More native functionality for quadrature points #185

GregVernon opened this issue Aug 12, 2020 · 3 comments

Comments

@GregVernon
Copy link

Currently, variables associated with quadrature points are written to variables with indexed names, where the indices represent the quadrature point index -- for example stress_xx_1,  stress_xx_2, stress_xx_3,...   stress_xx_8 for a 2x2x2 quadrature scheme. This can get confusing in simulations where blocks have different quadrature schemes.

A possible extension to Exodus could be to allow for a more organized means for writing values to quadrature points.

@gsjaardema
Copy link
Member

There is an option that the application can specify the suffices to be used for multi-component fields. The IOSS call to define the field and its suffix list is create_named_suffix_field_type in Ioss_VariableType.h However, this only works for the "non-composite fields" similar to vector, tensor, ... For the "composite fields" which is what a tensor+quadrature points type field in your example is, IOSS is currently limited to using a "named field" plus a "numbered-suffix" field.

I'm not sure how much effort it would be to make composite fields work with two "named fields" which would make it possible to define a more logical mapping from suffix to quadrature point location. I will try to take a look...

@github-actions
Copy link
Contributor

github-actions bot commented Nov 6, 2020

Stale issue message

@gsjaardema
Copy link
Member

gsjaardema commented Feb 23, 2022

See Discontinuous-Galerkin for a potential solution for some of the needs raised in this issue.

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

No branches or pull requests

2 participants