dolfin team mailing list archive

[Angelo Simone <a.simone@xxxxxxxxxx>]

Anders Logg wrote:
> On Thu, Dec 07, 2006 at 01:18:49AM +0100, angelo simone wrote:
>   
> > Here's the bundle. dolfin-convert is now in pure python (i.e. there are 
> > no calls to grep) and there are no temporary files. Is it ok now?
> > The script has been tested with the attached mesh files:
> > gmsh.msh (2d)
> > old-xml.xml.gz (2d)
> > tetgen.mesh.gz (3d)
> >     
>
> Thanks, but I don't really like the write_output stuff. I have added
> your changes and modified mesh2xml so it first scans the file for the
> cell type and then does the conversion. Could you supply a patch that
> does the same thing for gmsh2xml and xml_old2xml?
>
>   

of course, I'll do that and I understand why it is necessary (from your 
latest email only the gmsh2xml is left to be fixed, thanks)


> > I have tried the output of the first two conversions with a Dolfin 
> > example and they worked out fine. The tetgen mesh, which comes from the 
> > example.poly file distributed with tetgen 1.4.1, has not been tested 
> > against Dolfin. The output does look ok though.
> >     
>
> Thanks. I have added the test meshes and your updated conversion
> script, but I don't like the write_output stuff
>
>   
> > As far as I can see from the tetgen web page 
> > (http://tetgen.berlios.de/), tetgen cannot generate 2d meshes. Is there 
> > a reason why in the script there is a check on num_dims == 2?
> >     
>
> I haven't tested, but presumably the conversion works for meshes
> generated by Triangle. I think Triangle and TetGen share the same format.
>
>   

I'll see if it works and I'll add it to the bundle




> > I will soon send a bundle to update section 8.3 of the 
> > dolfin-user-manual. A bundle on the procedure to create a bundle will be 
> > ready soon as well.
> >     
>
> Very nice.
>
> /Anders
>
>