[Gmsh] FW: abaqus .inp format

[Smith, Mark]

resent due to .msh file removed by our firewall, brick.txt needs to be
renamed .msh

Hi Christophe
Last night's nightly build  23 June 2011 now doesn't show bad shaped
elements but the original gmsh mesh is second order 20 node hexahedrals
whereas the inp file is specifying C3D8 first order 8 node hex elements
& then lists 27 nodes & for the C2D4 elements it lists 9 nodes. the C3D8
should be C3D20 & I don't think there are C2D4 elements, not in Calculix
anyway?
See the attached files, brick.msh a cube meshed into 8 hex elements &
the abaqus conversion from GMSH  brick_from_GMSH.inp file to see what I
mean, brick_required.inp is the sort of output I'm after, the set names
are arbitrary.
Rather than outputting surface element sets like *Element, type=C2D4,
ELSET=SURFACE4     I would sooner have node sets for the surfaces if
this could be accommodated?

Thanks in advance

-----Original Message-----
From: Christophe Geuzaine [mailto:cgeuzaine at ulg.ac.be]
Sent: 22 June 2011 19:10
To: Smith, Mark
Cc: gmsh at geuz.org
Subject: Re: [Gmsh] abaqus .inp format

On 22/06/11 18:49, Smith, Mark wrote:
> Hi GMSH team
> I have a gmsh mesh file that I wish to convert to Abaqus format for 
> Calculix an open source FEA program, but the resulting file that GMSH 
> produces cannot be read by cgx (Calculix's pre&  post processor) I am 
> using gmsh 2.5.0 svn I don't know if this
> http://www.geuz.org/pipermail/gmsh/2010/006021.html           is the
> same problem?
>

Hi Mark - This should be fixed in recent nightly snapshots

> Thanks in advance, regards
> mark
>
> Please be advised that this email may contain confidential 
> information.  If you are not the intended recipient, please notify us 
> by email by replying to the sender and delete this message.  The 
> sender disclaims that the content of this email constitutes an offer 
> to enter into, or the acceptance of, any agreement; provided that the 
> foregoing does not invalidate the binding effect of any digital or 
> other electronic reproduction of a manual signature that is included 
> in any attachment.
>
>
>
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh
>


--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine



Please be advised that this email may contain confidential 
information.  If you are not the intended recipient, please notify us 
by email by replying to the sender and delete this message.  The 
sender disclaims that the content of this email constitutes an offer 
to enter into, or the acceptance of, any agreement; provided that the 
foregoing does not invalidate the binding effect of any digital or 
other electronic reproduction of a manual signature that is included 
in any attachment.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: brick_from_GMSH.inp
Type: application/octet-stream
Size: 4221 bytes
Desc: brick_from_GMSH.inp
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20110623/0b85e4a2/attachment.inp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: brick_required.inp
Type: application/octet-stream
Size: 7182 bytes
Desc: brick_required.inp
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20110623/0b85e4a2/attachment-0001.inp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: brick.msh
Type: application/octet-stream
Size: 6203 bytes
Desc: brick.msh
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20110623/0b85e4a2/attachment.msh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: brick.txt
URL: <http://www.geuz.org/pipermail/gmsh/attachments/20110623/0b85e4a2/attachment.txt>