[Gmsh] Visualising point data imported from MED files

[Christophe Geuzaine]

Your file is almost correct: you just need to fix the node indices in the point elements (you start referencing nodes at index 0, while the nodes actually start at 1).

(I have patched Gmsh to not crash anymore when the indices are incorrect.)

Cheers,

Christophe

> On 18 May 2018, at 09:20, Tomasz Koziara <t.koziara at gmail.com> wrote:
> 
> Dear Christophe,
> 
> Here is an output file with POINT1 elements exported using the previously quoted lines of code:
> 
> https://www.dropbox.com/s/izu5o15b2ow8y9u/spring_system0rb_ele.med.gz?dl=0 <https://www.dropbox.com/s/izu5o15b2ow8y9u/spring_system0rb_ele.med.gz?dl=0>
> 
> And here is a stack trace of the crush which I am getting on a OS X 10.10.5 when opening this file with Gmsh 3.0.6:
> 
> https://www.dropbox.com/s/q4fdk6thv2woy7q/spring_system0rb_bug.txt.gz?dl=0 <https://www.dropbox.com/s/q4fdk6thv2woy7q/spring_system0rb_bug.txt.gz?dl=0>
> 
> If there is a better way of annotating the MED file with elements information in this case, I would appreciate an advice:)
> 
> Best regards,
> Tomek
> 
> 
> On 17 May 2018 at 21:36, Christophe Geuzaine <geuzaine at gmail.com <mailto:geuzaine at gmail.com>> wrote:
> 
> HI Tomasz,
> 
> I'm not sure that we have actually tested it, but looking back at our MED reader we should handle the case. Don't hesitate to send your tentative MED files with point elements in them - we'll have a look.
> 
> Ch.
> 
>> On 17 May 2018, at 21:32, Tomasz Koziara <t.koziara at gmail.com <mailto:t.koziara at gmail.com>> wrote:
>> 
>> Ha, ha:) I tried that, but failed, for the time being:) I only have the examples distributed with MED library to provide inspiration; That was the code:
>> 
>> std::vector<med_int> conn;
>> for (i = 0; i < num; i ++)
>> {
>>   conn.push_back(i);
>> }
>> 
>> ASSERT (MEDmeshElementConnectivityWr(fid, meshName, MED_NO_DT, MED_NO_IT, 0., MED_CELL, MED_POINT1,
>>         MED_NODAL, MED_FULL_INTERLACE, conn.size(), &conn[0]) >= 0, "Could not write MED elements");
>> 
>> which is just a minor modification of the standard output for volumetric elements; do feel free to advice on a more suitable way of doing that:) Thank You; Tomek
>> 
>> On 17 May 2018 at 21:09, Christophe Geuzaine <geuzaine at gmail.com <mailto:geuzaine at gmail.com>> wrote:
>> 
>> Gmsh displays all meshes and post-processing data based on elements: so indeed you will need to add "point elements" (1 point for each vertex) in the med file in order to visualize it.
>> 
>> Christophe
>> 
>> 
>>> On 17 May 2018, at 14:56, Tomasz Koziara <t.koziara at gmail.com <mailto:t.koziara at gmail.com>> wrote:
>>> 
>>> Dear Christophe,
>>> 
>>> Here: https://www.dropbox.com/s/ve8rm3qjyvew1uq/spring_system0rb.med.gz?dl=0 <https://www.dropbox.com/s/ve8rm3qjyvew1uq/spring_system0rb.med.gz?dl=0>
>>> 
>>> Best regards,
>>> Tomek
>>> 
>>> 
>>> 
>>> On 17 May 2018 at 08:50, Christophe Geuzaine <geuzaine at gmail.com <mailto:geuzaine at gmail.com>> wrote:
>>> 
>>> Can you send a (small) example file?
>>> 
>>>> On 14 May 2018, at 13:08, Tomasz Koziara <t.koziara at gmail.com <mailto:t.koziara at gmail.com>> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> Continuing development of MED export in parmec <http://parmes.org/parmec/> I keep using Gmsh to test it. This time I am exporting nodes with time dependent scalar and vector fields attached to them. There are no elements or connectivity declared in the mesh. After import Gmsh shows all the views (per field) but I am not able to visualise anything. I would appreciate a helpful hint or comment:)
>>>> 
>>>> Thank you,
>>>> Tomek
>>>> _______________________________________________
>>>> gmsh mailing list
>>>> gmsh at onelab.info <mailto:gmsh at onelab.info>
>>>> http://onelab.info/mailman/listinfo/gmsh <http://onelab.info/mailman/listinfo/gmsh>
>>> 
>>> 
>>> _______________________________________________
>>> gmsh mailing list
>>> gmsh at onelab.info <mailto:gmsh at onelab.info>
>>> http://onelab.info/mailman/listinfo/gmsh <http://onelab.info/mailman/listinfo/gmsh>
>> 
>> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://onelab.info/pipermail/gmsh/attachments/20180518/b89ac472/attachment.html>