[Gmsh] Help with rewrite of mesh I/O layer

[Andy and Dawn Carl]

I would also suggest that NASTRAN BDF would be a good choice.


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

Message: 2
Date: Wed, 30 Aug 2006 19:44:08 -0400
From: Christophe Geuzaine <cag32 at case.edu>
Subject: [Gmsh] Help with rewrite of mesh I/O layer
To: gmsh mailing list <gmsh at geuz.org>
Message-ID: <44F622C8.6060502 at case.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


Hi all - We are currently rewriting Gmsh's mesh module, including the
input/output layer, and I have a few questions for all of you who
use the UNV ("IDEAS Universal Mesh") mesh file format:

* What should we put in the "physical property", "material" and "color"
fields? Right now we just put the "elementary" region everywhere, and 7
(!) in the color field.

* Should we treat the physical groups like in the native MSH file
format, i.e., if physical groups are defined, only save the elements
that belong to a physical group? Right now we always save all the elements.

* I don't have access to any program that can read UNV files. Does
anyone on this list with access to such a program want to volunteer to
test a alpha-quality version of the new import/export code?

Thanks,

Christophe

PS: While we're at it, are there any mesh file formats that we should
implement besides MSH, UNV, MESH (INRIA) and STL? Due to changes in the
database, we've had to remove the P3D and the GREF formats.

-- 
Christophe Geuzaine
Assistant Professor, Case Western Reserve University, Mathematics
http://www.case.edu/artsci/math/geuzaine


------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20060831/7ae666bd/attachment.html>