Mesh quality variables and multiple meshes #20544
-
|
Hi everyone, I have run into an issue where the mesh quality variables don't behave nicely when there is one mesh at the first timestep, and two or more meshes at the second timestep. When there is one mesh at the first timestep, VisIt creates mesh quality variables like this: The only workaround I have found so far is to manually create my own mesh quality expressions in the expression editor. Is there a VisIt option/setting to fix or workaround this behavior? Is this an issue caused by metadata that is being reported by my custom plugin? If so, how can I fix it? Many thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
VisIt isn't built to handle this case well. I don't know of an option or setting to fix or workaround this behavior. Perhaps another @visit-dav/visit-developers could chime in. But I think the key is to have the metadata provide information for all meshes at all timesteps. You could have an empty mesh at time 0. You'll have trouble if you try to render it at time 0, but that doesn't matter. Your issue with the mesh quality variable names should disappear. Alternatively you could script things to create your own mesh quality variables automatically following a mesh naming scheme of your choosing. |
Beta Was this translation helpful? Give feedback.
VisIt isn't built to handle this case well. I don't know of an option or setting to fix or workaround this behavior. Perhaps another @visit-dav/visit-developers could chime in. But I think the key is to have the metadata provide information for all meshes at all timesteps. You could have an empty mesh at time 0. You'll have trouble if you try to render it at time 0, but that doesn't matter. Your issue with the mesh quality variable names should disappear.
Alternatively you could script things to create your own mesh quality variables automatically following a mesh naming scheme of your choosing.