[Gmsh] PROBLEM READING NODEDATA

[Mandija, S.]

Hi,

I am a PhD student. I started working with this program one month ago. Initially, I was able to save post-processing data in a precise way, but after it was upgraded by my department, I started having problems. I explain a little bit more: After opening a 3D meshed cylinder with a vector field in it (“filename.msh”), I was able to calculate the curl of this vector field (thanks to the gmsh plugin Curl) and save the result obtained. In order to save this new postprocessing file, I was able to click on the arrow on the right of the “nameview_Curl” and then click on “save as” and then “Msh”. The result was a *.pos file. After importing the file in Matlab, the first section was related to the node ($Nodes), so I was able to identify for each node the number of the node and the x-y-z coordinate value in four different columns, then one section for the elements($Elements), and finally one section related to the node data($NodesData) with the same size of the node section. That means this section had the same number of rows (each one for a different node) and the same number of columns (the first one identifying the node number and then three columns related to the x-y-z value of the curl of the vector field for that precise node).

Now after upgrading the software, when I save the “nameview_Curl” and import the *.pos file in Matlab, I notice, as before, a first section related to the nodes and a section related to the elements. Now, instead of having the final section related to “$NodeData” as before, I have a new section called $ElementNodeData with the same number of rows as the $Element section, and as columns, after two starting columns identifying the element number and type, I have three columns repeated four times since the mesh is made by tetrahedron (in the online documentation is written:

“value: is a real number giving the value associated with a node or an element. For NodeData (respectively ElementData) views, there are ncomp values per node (resp. per element), where ncomp is the number of field components. For ElementNodeData views, there are ncomp times number-of-nodes-per-elements values per element.”).

Since I need the x-y-z value of the coordinate of each node and the x-y-z value of the curl of the vector field for each node, as I had before upgrading the software in the respective sections $Node and $NodeData, is there a way to obtain this information again? Is there a particular way to save the *.pos file so I can get this information again?

What I am expecting is a file with one section related to the geometry of each node that contains a number that identifies the node and the x-y-z coordinate value, and a section related to nodedata with contains the identify number of the related node, so I can relate the data to the geometrical position of one node, and the x-y-z value of the curl of the vector field as I was able to obtain with the previous version.



Hoping in a soon reply, I thank you all.

Stefano Mandija


------------------------------------------------------------------------------

De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren. Het Universitair Medisch
Centrum Utrecht is een publiekrechtelijke rechtspersoon in de zin van de W.H.W.
(Wet Hoger Onderwijs en Wetenschappelijk Onderzoek) en staat geregistreerd bij
de Kamer van Koophandel voor Midden-Nederland onder nr. 30244197.

Denk s.v.p aan het milieu voor u deze e-mail afdrukt.

------------------------------------------------------------------------------

This message may contain confidential information and is intended exclusively
for the addressee. If you receive this message unintentionally, please do not
use the contents but notify the sender immediately by return e-mail. University
Medical Center Utrecht is a legal person by public law and is registered at
the Chamber of Commerce for Midden-Nederland under no. 30244197.

Please consider the environment before printing this e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20131010/3352108e/attachment.html>