[Paraview] mesh file with a core dump
Dear all, 2 or 3 years ago, I coded a simple interface to the commercial finite element code ANSYS. It was working fine at that time. Mainly, it is a simple python interface which generates an ASCII *.vtk file in the legacy format, version 2.0. I tried to use the same interface tonight and with the latest version I can open the file, but if I click apply, paraview aborts with the following message. *** Error in `/home/utabak/external_programs/ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit/lib/paraview-5.2/paraview': free(): invalid next size (normal): 0x03255440 *** Aborted (core dumped) I tried on a simpler domain to debug a bit, but the input file seems fine to me. Moreover, I can open the same vtk file in another open source mesh generator, which is quite popular, namely, Gmsh without any errors. So I am wondering the reason for this problem. I also attached the input vtk file for your reference. Any help is appreciated. BR, Umut box.vtk Description: Binary data ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
Re: [Paraview] Paraview Visualization Ambiguity an a 2nd order Tetrahedra
On 10/23/2012 09:01 PM, Berk Geveci wrote: Ah, now I understand. This should be fixed. Try using a nightly binary. To download one, look at this page: http://paraview.org/Wiki/ParaView/Superbuild and look for instruction on how to download generated binaries. Berk, Thanks for this information, I would like to compile Paraview with vector graphics export facilites, especially svg if possible. Where shall I look for these instructions? Best, Umut P.S. Selamlar ;-) ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
Re: [Paraview] Paraview Visualization Ambiguity an a 2nd order Tetrahedra
On 10/22/2012 03:46 PM, Berk Geveci wrote: ParaView will tetrahedralize higher order elements for certain algorithms. For the most part, this should be hidden. What particular algorithm are you seeing this with? Hi, This is a mesh that I export from the commercial finite element code ANSYS. I am not sure how to answer this question. But I also could not understand the point of your question since the cell representation should be easy to understand by the software. It should only draw elements around the main nodes that represent the element, so for this case, the 10-nodes that belong to the element should form the element. Why do you relate this to a meshing algorithm? I am not expert on mesh generation of course ;-) There are two 10 node tetrahedral elements interfaced in my code for ANSYS elements. Namely, SOLID92 and SOLID187 which are both 2nd order 10 node tetra elements. If I follow this thread http://comments.gmane.org/gmane.comp.science.paraview.user/10670 which seems to solve the problem. And I can see the normal 2nd order elements without divided into extra cells. BR, Umut ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
[Paraview] Paraview Visualization Ambiguity an a 2nd order Tetrahedra
Dear all, I have a mesh which is composed of 2nd order tetrahedral elements, however if this mesh is visualized in paraview then see that inside one 2nd order elements other elements are created. So the displayed number of elements are not correct. I am a rather new user of Paraview. The vtk input file seems to be correct and I am comparing that to Gmsh input files and they match. However, Paraview divides the tetra elements in extra 1st order like elements. I guess I am mistaken at some point. Visualization of data is not a problem since the node data is fine and I am visualizing a vector displacement field on the mesh. The input file is also attached. Any comments are appreciated. Best regards, Umut # vtk DataFile Version 2.0 BLOCK ASCII DATASET UNSTRUCTURED_GRID POINTS 231 double -5.0001e-03 5.0001e-03 0.e+00 -5.0001e-03 -5.0001e-03 0.e+00 -5.0001e-03 2.5001e-03 0.e+00 -5.0001e-03 0.e+00 0.e+00 -5.0001e-03 -2.5001e-03 0.e+00 5.0001e-03 5.0001e-03 0.e+00 2.5001e-03 5.0001e-03 0.e+00 0.e+00 5.0001e-03 0.e+00 -2.5001e-03 5.0001e-03 0.e+00 5.0001e-03 -5.0001e-03 0.e+00 5.0001e-03 -2.5001e-03 0.e+00 5.0001e-03 0.e+00 0.e+00 5.0001e-03 2.5001e-03 0.e+00 -2.5001e-03 -5.0001e-03 0.e+00 0.e+00 -5.0001e-03 0.e+00 2.5001e-03 -5.0001e-03 0.e+00 -3.195138889001e-03 3.195138889001e-03 0.e+00 1.73361001e-03 2.66389001e-04 0.e+00 -2.66389001e-04 -1.73361001e-03 0.e+00 3.2060185185184998e-05 -3.2060185185184998e-05 0.e+00 7.2719907407407000e-04 -3.2271990740741002e-03 0.e+00 3.2271990740741002e-03 -7.2719907407407000e-04 0.e+00 3.2271990740741002e-03 -3.2271990740741002e-03 0.e+00 3.1127314814814998e-04 1.6887268518519000e-03 0.e+00 3.5064120370370002e-03 9.9358796296296001e-04 0.e+00 1.006412037036e-03 3.493587962963e-03 0.e+00 3.5064120370370002e-03 3.493587962963e-03 0.e+00 -1.6887268518519000e-03 -3.1127314814814998e-04 0.e+00 -3.493587962963e-03 -1.006412037036e-03 0.e+00 -9.9358796296296001e-04 -3.5064120370370002e-03 0.e+00 -3.493587962963e-03 -3.5064120370370002e-03 0.e+00 -6.95139000e-04 3.195138889001e-03 0.e+00 -3.195138889001e-03 6.95139000e-04 0.e+00 -1.39027999e-03 1.39027999e-03 0.e+00 -1.9871759259259001e-03 -2.0128240740741000e-03 0.e+00 2.0128240740741000e-03 1.9871759259259001e-03 0.e+00 1.4543981481481001e-03 -1.4543981481481001e-03 0.e+00 -5.0001e-03 -5.0001e-03 1.e-02 5.0001e-03 -5.0001e-03 1.e-02 -2.5001e-03 -5.0001e-03 1.e-02 0.e+00 -5.0001e-03 1.e-02 2.5001e-03 -5.0001e-03 1.e-02 5.0001e-03 5.0001e-03 1.e-02 5.0001e-03 -2.5001e-03 1.e-02 5.0001e-03 0.e+00 1.e-02 5.0001e-03 2.5001e-03 1.e-02 -5.0001e-03 5.0001e-03 1.e-02 2.5001e-03 5.0001e-03 1.e-02 0.e+00 5.0001e-03 1.e-02 -2.5001e-03 5.0001e-03 1.e-02 -5.0001e-03 2.5001e-03 1.e-02 -5.0001e-03 0.e+00 1.e-02 -5.0001e-03 -2.5001e-03 1.e-02 3.20486002e-03 3.20486002e-03 1.e-02 -1.734027778000e-03 2.65972002e-04 1.e-02 2.65972002e-04 -1.734027778000e-03 1.e-02 -2.9997e-04 1.6999e-03 1.e-02 -3.50486001e-03 9.95139002e-04 1.e-02 -1.00486000e-03 3.495138889001e-03 1.e-02
