Discussion:
[Gmsh] Problem with importing a mesh in Abaqus
Pierre-Frederic Villard
2013-03-18 17:03:06 UTC
Permalink
Hi,

I have issues with importing gmsh-created meshes in Abaqus 6.12. I tried
two methods, which equally failed:
1 - I tried to save the mesh as OpenCASCADE step format but I have an
error: "Error : No OpenCASCADE model found"
2 - I tried to save the model as an Abaqus INP file but I have a problem
importing it in Abaqus : "Element type "C2D3" is not supported." with
triangles and "Element type "C1D2" is not supported" with segments.

Does anyone have any idea how to solve this problem?

Cheers,

Pierre
Christophe Geuzaine
2013-04-05 10:07:55 UTC
Permalink
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.

What should we use when we export "generic" elements (i.e., not linked to any physics)?

@Omid - any ideas?
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
Christophe Geuzaine
2013-04-05 10:35:23 UTC
Permalink
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from

https://geuz.org/trac/gmsh/ticket/129

@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine
Omid Mahabadi
2013-04-05 14:13:30 UTC
Permalink
Hi,
I thought quite a bit about element types in Abaqus. The reality is that
there are so many different element types in Abaqus that makes defining
a "generic" type rather impossible. I would suggest to keep the default
Abaqus export as currently is, but give the user the option to define
custom types in the gmsh geometry file. For instance, in the case of a
2D mesh, the user may define a maximum of two strings for the 1D and 2D
element types, which can look like:
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)

I discussed the above suggestion with another colleague of mine who has
used Abaqus in the past and it made sense to them. What are your thoughts?

Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Christophe Geuzaine
2013-04-05 14:25:40 UTC
Permalink
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine
Christophe Geuzaine
2013-04-05 16:02:36 UTC
Permalink
Post by Christophe Geuzaine
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
I totally agree as user-defined types can get complicated.
On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine
Omid Mahabadi
2013-04-10 23:21:50 UTC
Permalink
Dear Christophe,
I have been using the updated Gmsh with the Abaqus NSET export and it
has been working very well so far. I've only come across a tiny issue,
that is, the names of Physical Entities are not used from the geometry
file. Instead, they are numbered automatically in the exported inp file
(e.g., PhysicalLine2,..., PhysicalSurface1,...). Is there a way to
preserve the names specified in the geo file?

Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
I totally agree as user-defined types can get complicated.
On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Christophe Geuzaine
2013-04-11 10:25:32 UTC
Permalink
Post by Omid Mahabadi
Dear Christophe,
I have been using the updated Gmsh with the Abaqus NSET export and it has been working very well so far. I've only come across a tiny issue, that is, the names of Physical Entities are not used from the geometry file. Instead, they are numbered automatically in the exported inp file (e.g., PhysicalLine2,..., PhysicalSurface1,...). Is there a way to preserve the names specified in the geo file?
This should be fixed in the latest svn.

Thanks for the feedback,

Christophe
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
I totally agree as user-defined types can get complicated.
On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
_______________________________________________
gmsh mailing list
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
Omid Mahabadi
2013-04-11 12:35:22 UTC
Permalink
Thank you very much, Christophe.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Dear Christophe,
I have been using the updated Gmsh with the Abaqus NSET export and it has been working very well so far. I've only come across a tiny issue, that is, the names of Physical Entities are not used from the geometry file. Instead, they are numbered automatically in the exported inp file (e.g., PhysicalLine2,..., PhysicalSurface1,...). Is there a way to preserve the names specified in the geo file?
This should be fixed in the latest svn.
Thanks for the feedback,
Christophe
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
I totally agree as user-defined types can get complicated.
On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
_______________________________________________
gmsh mailing list
http://www.geuz.org/mailman/listinfo/gmsh
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Omid Mahabadi
2013-05-06 14:47:20 UTC
Permalink
Hi Martin,
Yes, you would need to get one of the later versions of Gmsh from their
svn repository. I'm not aware if their new binaries include the new
feature. However, building Gmsh is fairly straightforward and is well
explained in the README.txt file that comes with the source code.

The attached geometry file should work fine with the Abaqus export.
Notice "Mesh.SaveGroupsOfNodes = 1;" at the end of the file, which will
export the abaqus Node Sets (NSETs).

Cheers,
Omid
Dear M. Mahabadi,
Do you have a small working example of an Abaqus export from GMSH
including node sets? I can't find anything like that in the
documentation or wiki. Would be very useful.
Also, this functionality is available only with the svn version,
right? It's not gonna work with 2.7.0, right?
Thanks a lot for your help.
Kind regards,
Martin
Post by Omid Mahabadi
Dear Christophe,
I have been using the updated Gmsh with the Abaqus NSET export and it
has been working very well so far. I've only come across a tiny issue,
that is, the names of Physical Entities are not used from the geometry
file. Instead, they are numbered automatically in the exported inp file
(e.g., PhysicalLine2,..., PhysicalSurface1,...). Is there a way to
preserve the names specified in the geo file?
Thank you,
Omid
/>/
/>>>/
/>>>>/ Hi,
/>>>>/ Mesh.Abaqus.ElementType.1D = "C1D2"
/>>>>/ Mesh.Abaqus.ElementType.2D = "C2D3"
/>>>>/ (I'm just mimicking gmsh's syntax here)
/>>>>/
/>>>>/ I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
/>>>>/
/>>>/ With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
/>>/ I totally agree as user-defined types can get complicated.
/>>/ On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
/>/ Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
/>/
/>>>/
/>>>>/ Thank you,
/>>>>/ Omid
/>>>>/
/>>>>/
/>>>>>/
/>>>>>>/
/>>>>>>>/ Hi,
/>>>>>>>/
/>>>>>>>/ 1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
/>>>>>>/ Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
/>>>>>>/
/>>>>>>>/ 2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
/>>>>>>>/
/>>>>>>/ Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
/>>>>>>/
/>>>>>>/ What should we use when we export "generic" elements (i.e., not linked to any physics)?
/>>>>>>/
/>>>>>/ I've committed r15202 with the ideas from
/>>>>>/
/>>>>>/ https://geuz.org/trac/gmsh/ticket/129
/>>>>>/
/>>>>>/
/>>>>>/
/>>>>>/
/>>>>>>>/ Does anyone have any idea how to solve this problem?
/>>>>>>>/
/>>>>>>>/ Cheers,
/>>>>>>>/
/>>>>>>>/ Pierre
/>>>>>>>/
/>>>>>>>/
/>>>>>>>/ _______________________________________________
/>>>>>>>/ gmsh mailing list
/>>>>>>>/ gmsh at geuz.org <http://www.geuz.org/mailman/listinfo/gmsh>
/>>>>>>>/ 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 <http://www.montefiore.ulg.ac.be/%7Egeuzaine>
/>>>>>>/
/>>>>>>/
/>>>>>>/
/>>>>/ --
/>>>>/ Omid Mahabadi
/>>>>/ Geomechanica, Inc.
/>>>>/ Tel: (647) 478-9767 x824
/>>>>/
/>>/ --
/>>/ Omid Mahabadi
/>>/ Geomechanica, Inc.
/>>/ Tel: (647) 478-9767 x824
/>>/
/
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Martin Genet
2013-05-06 16:14:07 UTC
Permalink
Works like a charm—with both the nightly and svn versions.

One thing I noticed though, is that both the elem and node sets have
the same name, which seems to confuse Abaqus a little bit. Would that
make sense to add e.g. NODES_/ELEMS_ as a prefix for the node/elem sets?

Martin
Post by Omid Mahabadi
Hi Martin,
Yes, you would need to get one of the later versions of Gmsh from their svn repository. I'm not aware if their new binaries include the new feature. However, building Gmsh is fairly straightforward and is well explained in the README.txt file that comes with the source code.
The attached geometry file should work fine with the Abaqus export. Notice "Mesh.SaveGroupsOfNodes = 1;" at the end of the file, which will export the abaqus Node Sets (NSETs).
Cheers,
Omid
Dear M. Mahabadi,
Do you have a small working example of an Abaqus export from GMSH including node sets? I can't find anything like that in the documentation or wiki. Would be very useful.
Also, this functionality is available only with the svn version, right? It's not gonna work with 2.7.0, right?
Thanks a lot for your help.
Kind regards,
Martin
Post by Omid Mahabadi
Dear Christophe,
I have been using the updated Gmsh with the Abaqus NSET export and it
has been working very well so far. I've only come across a tiny issue,
that is, the names of Physical Entities are not used from the geometry
file. Instead, they are numbered automatically in the exported inp file
(e.g., PhysicalLine2,..., PhysicalSurface1,...). Is there a way to
preserve the names specified in the geo file?
Thank you,
Omid
/>/
/>>>/
/>>>>/ Hi,
/>>>>/ Mesh.Abaqus.ElementType.1D = "C1D2"
/>>>>/ Mesh.Abaqus.ElementType.2D = "C2D3"
/>>>>/ (I'm just mimicking gmsh's syntax here)
/>>>>/
/>>>>/ I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
/>>>>/
/>>>/ With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
/>>/ I totally agree as user-defined types can get complicated.
/>>/ On a side note, for your information I've realized that now Element numbers don't start from 1 anymore.
/>/ Indeed: that's a side-effect of the new scheme. Since we must remember the numbers in the ELSETS, we cannot just renumber on-the-fly as before.
/>/
/>>>/
/>>>>/ Thank you,
/>>>>/ Omid
/>>>>/
/>>>>/
/>>>>>/
/>>>>>>/
/>>>>>>>/ Hi,
/>>>>>>>/
/>>>>>>>/ 1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
/>>>>>>/ Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
/>>>>>>/
/>>>>>>>/ 2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
/>>>>>>>/
/>>>>>>/ Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
/>>>>>>/
/>>>>>>/ What should we use when we export "generic" elements (i.e., not linked to any physics)?
/>>>>>>/
/>>>>>/ I've committed r15202 with the ideas from
/>>>>>/
/>>>>>/ https://geuz.org/trac/gmsh/ticket/129
/>>>>>/
/>>>>>/
/>>>>>/
/>>>>>/
/>>>>>>>/ Does anyone have any idea how to solve this problem?
/>>>>>>>/
/>>>>>>>/ Cheers,
/>>>>>>>/
/>>>>>>>/ Pierre
/>>>>>>>/
/>>>>>>>/
/>>>>>>>/ _______________________________________________
/>>>>>>>/ gmsh mailing list
/>>>>>>>/ gmsh at geuz.org <http://www.geuz.org/mailman/listinfo/gmsh>
/>>>>>>>/ 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 <http://www.montefiore.ulg.ac.be/%7Egeuzaine>
/>>>>>>/
/>>>>>>/
/>>>>>>/
/>>>>/ --
/>>>>/ Omid Mahabadi
/>>>>/ Geomechanica, Inc.
/>>>>/ Tel: (647) 478-9767 x824
/>>>>/
/>>/ --
/>>/ Omid Mahabadi
/>>/ Geomechanica, Inc.
/>>/ Tel: (647) 478-9767 x824
/>>/
/
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Omid Mahabadi
2013-04-05 15:49:16 UTC
Permalink
Post by Christophe Geuzaine
Post by Omid Mahabadi
Hi,
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be understood by Abaqus/Standard (had to change lines, triangles and quads). We might want more flexibility in the future, but it might also be overkill (we need types for 1st order and 2nd order elements, etc.).
I totally agree as user-defined types can get complicated.
On a side note, for your information I've realized that now Element
numbers don't start from 1 anymore.
Post by Christophe Geuzaine
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
Post by Christophe Geuzaine
Hi,
1 - I tried to save the mesh as OpenCASCADE step format but I have an error: "Error : No OpenCASCADE model found"
Hi Pierre-Frederic - This would actually not export the mesh, but the CAD model - so it's not what you want.
2 - I tried to save the model as an Abaqus INP file but I have a problem importing it in Abaqus : "Element type "C2D3" is not supported." with triangles and "Element type "C1D2" is not supported" with segments.
Indeed. I just had a look at the Abaqus documentation, and C2D3 and C1D2 do not seem to be in the general "Element Indexes" available in Abaqus/Standard.
What should we use when we export "generic" elements (i.e., not linked to any physics)?
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Christophe Geuzaine
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Pierre-Frederic Villard
2013-05-02 14:37:04 UTC
Permalink
Dear Christophe and Omid,

The SVN r15421 did solve partially my problem. I manage to import the mesh
in Abaqus/CAE 6.12. "Physical" elements are nicely recognized as Assembly's
Sets, even with their name.

However, I cannot use them to apply boundary conditions. Do you know where
the problem comes from or should I try to directly post on Abaqus forum?

.geo and .inp files are attached.

Thank you very much for the help.

Best wishes,

Pierre
Post by Omid Mahabadi
Hi,
I thought quite a bit about element types in Abaqus. The reality is that
there are so many different element types in Abaqus that makes defining a
"generic" type rather impossible. I would suggest to keep the default
Abaqus export as currently is, but give the user the option to define
custom types in the gmsh geometry file. For instance, in the case of a 2D
mesh, the user may define a maximum of two strings for the 1D and 2D
Post by Omid Mahabadi
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine who has
used Abaqus in the past and it made sense to them. What are your thoughts?
With SVN r15202 I at least changed the default tags to tags that should be
understood by Abaqus/Standard (had to change lines, triangles and quads).
We might want more flexibility in the future, but it might also be overkill
(we need types for 1st order and 2nd order elements, etc.).
Post by Omid Mahabadi
Thank you,
Omid
Post by Christophe Geuzaine
On 18 Mar 2013, at 18:03, Pierre-Frederic Villard <
Post by Pierre-Frederic Villard
Hi,
I have issues with importing gmsh-created meshes in Abaqus 6.12. I
1 - I tried to save the mesh as OpenCASCADE step format but I have an
error: "Error : No OpenCASCADE model found"
Post by Omid Mahabadi
Post by Christophe Geuzaine
Hi Pierre-Frederic - This would actually not export the mesh, but the
CAD model - so it's not what you want.
Post by Omid Mahabadi
Post by Christophe Geuzaine
Post by Pierre-Frederic Villard
2 - I tried to save the model as an Abaqus INP file but I have a
problem importing it in Abaqus : "Element type "C2D3" is not supported."
with triangles and "Element type "C1D2" is not supported" with segments.
Post by Omid Mahabadi
Post by Christophe Geuzaine
Indeed. I just had a look at the Abaqus documentation, and C2D3 and
C1D2 do not seem to be in the general "Element Indexes" available in
Abaqus/Standard.
Post by Omid Mahabadi
Post by Christophe Geuzaine
What should we use when we export "generic" elements (i.e., not linked
to any physics)?
Post by Omid Mahabadi
Post by Christophe Geuzaine
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Pierre-Frederic Villard
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine
Omid Mahabadi
2013-05-02 16:51:42 UTC
Permalink
Dear Pierre,
Unfortunately, I do not have access to Abaqus now so I cannot really
test anything. You may want to directly post on the Abaqus forum.

Good luck,
Omid
Post by Pierre-Frederic Villard
Dear Christophe and Omid,
The SVN r15421 did solve partially my problem. I manage to import the
mesh in Abaqus/CAE 6.12. "Physical" elements are nicely recognized as
Assembly's Sets, even with their name.
However, I cannot use them to apply boundary conditions. Do you know
where the problem comes from or should I try to directly post on
Abaqus forum?
.geo and .inp files are attached.
Thank you very much for the help.
Best wishes,
Pierre
On Fri, Apr 5, 2013 at 4:25 PM, Christophe Geuzaine
On 05 Apr 2013, at 16:13, Omid Mahabadi
Post by Omid Mahabadi
Hi,
I thought quite a bit about element types in Abaqus. The reality
is that there are so many different element types in Abaqus that
makes defining a "generic" type rather impossible. I would suggest
to keep the default Abaqus export as currently is, but give the
user the option to define custom types in the gmsh geometry file.
For instance, in the case of a 2D mesh, the user may define a
maximum of two strings for the 1D and 2D element types, which can
Post by Omid Mahabadi
Mesh.Abaqus.ElementType.1D = "C1D2"
Mesh.Abaqus.ElementType.2D = "C2D3"
(I'm just mimicking gmsh's syntax here)
I discussed the above suggestion with another colleague of mine
who has used Abaqus in the past and it made sense to them. What
are your thoughts?
With SVN r15202 I at least changed the default tags to tags that
should be understood by Abaqus/Standard (had to change lines,
triangles and quads). We might want more flexibility in the
future, but it might also be overkill (we need types for 1st order
and 2nd order elements, etc.).
Post by Omid Mahabadi
Thank you,
Omid
On 05 Apr 2013, at 12:07, Christophe Geuzaine
On 18 Mar 2013, at 18:03, Pierre-Frederic Villard
Post by Pierre-Frederic Villard
Hi,
I have issues with importing gmsh-created meshes in Abaqus
1 - I tried to save the mesh as OpenCASCADE step format but I
have an error: "Error : No OpenCASCADE model found"
Post by Omid Mahabadi
Hi Pierre-Frederic - This would actually not export the mesh,
but the CAD model - so it's not what you want.
Post by Omid Mahabadi
Post by Pierre-Frederic Villard
2 - I tried to save the model as an Abaqus INP file but I
have a problem importing it in Abaqus : "Element type "C2D3" is
not supported." with triangles and "Element type "C1D2" is not
supported" with segments.
Post by Omid Mahabadi
Indeed. I just had a look at the Abaqus documentation, and
C2D3 and C1D2 do not seem to be in the general "Element Indexes"
available in Abaqus/Standard.
Post by Omid Mahabadi
What should we use when we export "generic" elements (i.e.,
not linked to any physics)?
Post by Omid Mahabadi
@Omid - any ideas?
I've committed r15202 with the ideas from
https://geuz.org/trac/gmsh/ticket/129
@Abaqus users: let me know if this is better...
Post by Pierre-Frederic Villard
Does anyone have any idea how to solve this problem?
Cheers,
Pierre
_______________________________________________
gmsh mailing list
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
<http://www.montefiore.ulg.ac.be/%7Egeuzaine>
Post by Omid Mahabadi
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824 <tel:%28647%29%20478-9767%20x824>
--
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science
http://www.montefiore.ulg.ac.be/~geuzaine
<http://www.montefiore.ulg.ac.be/%7Egeuzaine>
--
Omid Mahabadi
Geomechanica, Inc.
Tel: (647) 478-9767 x824
Loading...