Welcome on the forums. Please post in English or French.
You are not logged in. You won't be able to post until you register and log in using the top-right bar.
Hi,
I would like to know if there is a reference to post-process results at Gauss points in ParaVis?
Also, I would like to know how ParaVis is "aware" of Gauss point location in each elements:
- does Code_Aster write in the MED file their location?
- or does ParaVis evaluate this location using some "assumptions" about the integration used in each element?
I thank you in advance for your help.
Have a good day.
Bests,
Pierre
Last edited by pierre_j (2012-07-27 08:46:20)
Offline
Hi,
PARAVIS works the same as POSTPRO regarding this matter.
The Gauss Points location is in the MED file, there's no assumption whatsoever. What the post-processing software does is to go from the reference element to the deformed one.
You need to use the special filter located in the submenu "Integration points" in order to make a Gauss visualization.
TdS
Offline
Dear Thomas,
Thank you for your help.
I simply forgot to print in MED file fields at gauss points...
(visualizing results at Gauss points is quite new to me...)
However, I would like to report a weird thing.
Enclosed, you will see what I could see, and integration point position is to me quite striking...
I believe this to be a bug either in the printing of the integration point location during their writing in MED file, either a bug in ParaVis.
Indeed, with MACR_ECLA_PG, integration point location is correct.
Do you observe the same thing?
I thank you in advance for your feedback.
Bests,
Pierre
PS:
use of Aster 11.1,
Salome 6.5.0 on windows
Last edited by pierre_j (2012-07-26 18:59:29)
Offline
Here is the med result file.
Bests,
Pierre
Offline
Hi,
I was able to reproduce the bug on PARAVIS 6.5.0. I'll file a bug.
Thanks for the feedback.
Note that it works in POSTPRO as well as Gmsh.
TdS
Offline
Thomas, thank you!
Do you know if there is a "Code_Aster/Salome bug discovery" tournament organized somewhere?
I am sure I would be able to reach good scores!
![]()
More seriously, to make maximum benefit of the open source community, competition is a good way.
It might be interesting to open for a month, each quarter of year, a topic on which orienting bug identification / code optimization, for instance:
- linear elastic material behavior
- non-linear material behavior
- shell elements
- ...
Those would be identified by whatever means chosen by the participants:
- automatic code analyzer,
- source code direct reading (my favorite!
)
- running personal test cases
Might be worth giving it a try.![]()
Thanks again.
Bests,
Pierre
Last edited by pierre_j (2012-07-27 08:44:16)
Offline
Thomas DE SOZA wrote:
Note that it works in POSTPRO as well as Gmsh.
Thomas, it also works in Salome 6.5.0 if we use MACR_ECLA_PG and directly visualize the Gauss points as elements on the resulting mesh.
Bests,
Pierre
Last edited by pierre_j (2012-07-27 08:46:09)
Offline