-
Notifications
You must be signed in to change notification settings - Fork 90
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
WIP: Export of discontinuous fields to VTK #867
base: master
Are you sure you want to change the base?
Conversation
Co-authored-by: Fredrik Ekre <[email protected]>
Test caseGenerated to validate the discontinuous, tests for different reference shapes will be needed before merge... DG tutorial (dg penalization variation)The results looks quite strange, any idea if this is reasonable @AbdAlazezAhmed / @termi-official ? (I'm wondering if something is off in the export, but test case looks correct) |
Any reason not to use
Looks correct for me. The parameter which you tune is basically a penalty on the jump in the gradients between the elements. Please notice in the first figure in the section above that your gradients are essentially continuous with large jumps between elements. Just look at the formula for 1D and I think you will understand what happens. :) Also, a too small value for the penalty parameter makes the forumlation unstable, which is why you see this weird checkerboarding pattern. |
Since it uses the nodal coordinate, the result wouldn't be discontinuous. But it is a good point adding that to validate the the result is continuous when it should!
Yes, that was the idea of the test to generate such a case :) |
Until VTK supports discontinuous fields, this patch, building on top of #692 makes a vtk grid that is geometrically discontinuous as well, allowing discontinuous interpolations to be visualized.
TODO
apply_analytical!
to validate continuity when it should be