Dear All,
This email is an echo of a previous one where I noticed that for XDMF
format, Node Id and Element one are not explicitely provided (for
performance issue I guess); writing an interface for renumbering
topology (connectivity), datasets and so on is not a problem by itself
(jus more work), but rather the fact that information's are lost
(information's from the solver based on the original mesh for example).
Thus I'm having a look to Exodus ii format and how I can use y h5 file
(through netCDF I guess and not directly) ... if I'm right it allows
nodes/elements Id's.
Compared to Xdmf, does somebody want to share his feedback?
(limitations, implementation, performance, parallelisation, and so on)
Thanks for any help
Regards
Paul
_______________________________________________
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:
https://public.kitware.com/mailman/listinfo/paraview
