mesh conversion gambit to Nastran
I would like to convert a mesh from gambit to Nastran. How can I do that with sfepy ? A small example would be appreciated.
Thanks in advance. Nils
On 01/09/12 16:49, nil...@googlemail.com wrote:
I would like to convert a mesh from gambit to Nastran. How can I do that with sfepy ? A small example would be appreciated.
Saving a mesh in nastran format is not yet implemented. If it was, you would use script/convert_mesh.py script.
Example use: ./script/convert_mesh.py meshes/3d/cylinder.mesh new.vtk
Currently supported formats for writing are:
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk
I cannot implement it right now, so if you feel like trying implementing it, check BDFMeshIO class in sfepy/fem/meshio.py - write(self, filename, mesh, **kwargs) method needs to be added there. Otherwise you can create a new enhancement issue, so that your request is not forgotten :)
Cheers, r.
Hi
I have no idea about the state of this code, but they seem to be active:
code.google.com/p/pynastran/
I believe you could quite easily add it to sfepy. Regarding licensing I'm not sure about GNU GPL v3 (pynastran) vs BSD (sfepy).
The feature would be nice for me as well. :-))
/PMC
2012/1/9 Robert Cimrman cimr...@ntc.zcu.cz
On 01/09/12 16:49, nil...@googlemail.com wrote:
I would like to convert a mesh from gambit to Nastran. How can I do that with sfepy ? A small example would be appreciated.
Saving a mesh in nastran format is not yet implemented. If it was, you would use script/convert_mesh.py script.
Example use: ./script/convert_mesh.py meshes/3d/cylinder.mesh new.vtk
Currently supported formats for writing are:
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk
I cannot implement it right now, so if you feel like trying implementing it, check BDFMeshIO class in sfepy/fem/meshio.py - write(self, filename, mesh, **kwargs) method needs to be added there. Otherwise you can create a new enhancement issue, so that your request is not forgotten :)
Cheers, r.
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel+unsubscribe@** googlegroups.com sfepy-devel%...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/sfepy-devel?hl=en http://groups.google.com/group/sfepy-devel?hl=en .
On 01/09/12 19:05, Peter M. Clausen wrote:
Hi
I have no idea about the state of this code, but they seem to be active:
code.google.com/p/pynastran/
I believe you could quite easily add it to sfepy. Regarding licensing I'm not sure about GNU GPL v3 (pynastran) vs BSD (sfepy).
Unfortunately we cannot include any GPL code :(, see e.g. [1].
The feature would be nice for me as well. :-))
Yes, it would be good to support most of the common formats. Maybe we could ask them to be so kind to provide a basic writing function (simple bdf text format) under BSD-compatible terms?
In general, it is good when a format reading/writing class is implemented by someone using that format (I do not have/use Nastran as you may see from its bad coverage in sfepy). So anyone, contributions are welcome! :)
IMHO writing a function like that is not difficult, especially if you have an example and the original program to test it.
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
Cheers, N.
On Jan 9, 5:02 pm, Robert Cimrman cimr...@ntc.zcu.cz wrote:
On 01/09/12 16:49, nil...@googlemail.com wrote:
I would like to convert a mesh from gambit to Nastran. How can I do that with sfepy ? A small example would be appreciated.
Saving a mesh in nastran format is not yet implemented. If it was, you would use script/convert_mesh.py script.
Example use: ./script/convert_mesh.py meshes/3d/cylinder.mesh new.vtk
Currently supported formats for writing are:
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk
I cannot implement it right now, so if you feel like trying implementing it, check BDFMeshIO class in sfepy/fem/meshio.py - write(self, filename, mesh, **kwargs) method needs to be added there. Otherwise you can create a new enhancement issue, so that your request is not forgotten :)
Cheers, r.
On 01/10/12 11:23, nil...@googlemail.com wrote:
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
*blush* Sorry, I have overlooked, that SfePy _can_ save in nastran's .bdf format! (Thanks to Vladimir Lukes).
Just use
./script/convert_mesh.py file.neu file.bdf
It was the "./script/convert_mesh.py -l" that was wrong - it's fixed now in the git repo.
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk sfepy: nastran
Close the issue, please, if it works for you. (From gambit export in the .neu format.)
r.
On 01/10/2012 11:53 AM, Robert Cimrman wrote:
On 01/10/12 11:23, nil...@googlemail.com wrote:
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
*blush* Sorry, I have overlooked, that SfePy _can_ save in nastran's .bdf format! (Thanks to Vladimir Lukes).
I tested BDF writer just for a few simple meshes. Please, let me know how it works for you.
Vladimir
Just use
./script/convert_mesh.py file.neu file.bdf
It was the "./script/convert_mesh.py -l" that was wrong - it's fixed now in the git repo.
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk sfepy: nastran
Close the issue, please, if it works for you. (From gambit export in the .neu format.)
r.
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
./convert_mesh.py ~/Downloads/plate_total.neu plate_new.bdf sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHDPM.py cannot be imported! sfepy: reason: 'module' object has no attribute 'd_hdpm_surfdvel' sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHyperElasticity.py cannot be imported! sfepy: reason: name 'Volume' is not defined sfepy: reading mesh (/home/nwagner/Downloads/plate_total.neu)... Traceback (most recent call last): File "./convert_mesh.py", line 99, in <module> main() File "./convert_mesh.py", line 68, in main mesh = Mesh.from_file(filename_in) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ mesh.py", line 435, in from_file mesh = io.read(mesh, omit_facets=omit_facets) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ meshio.py", line 2341, in read assert_(row[0] == 'ENDOFSECTION') File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/base/ base.py", line 138, in assert_ raise ValueError( 'assertion failed!' ) ValueError: assertion failed!
grep -a2 ENDOFSECTION ~/Downloads/plate_total.neu NUMNP NELEM NGRPS NBSETS NDFCD NDFVL 18132 11795 1 5 3 3 ENDOFSECTION NODAL COORDINATES 2.4.6 1 1.60000000000e-001 1.60000000000e-001 -2.00000000000e-002
18131 1.53125548753e-001 1.92495751551e-001 2.63045876856e-001
18132 1.30962487325e-001 1.81412260269e-001 2.77274676176e-001ENDOFSECTION ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812
11795 6 10 16717 18128 16720 18087 18124 16696 18094 18125 17823 16686 ENDOFSECTION ELEMENT GROUP 2.4.6 GROUP: 1 ELEMENTS: 11795 MATERIAL: 2 NFLAGS: 1
3882 3883 3884 3885 3886 3887 3888 38893890 3891 3892 3893 3894 3895 3896 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_side 0 311 0 24
5403
5404ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_top 0 1221 0 24
5310
5311ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symx_end 0 1005 0 24
1586
1587ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symy_end 0 1017 0 24
1708
1709ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
444 6 4
517 6 1ENDOFSECTION
On 10 Jan., 13:08, Vladimír Lukeš vlu...@kme.zcu.cz wrote:
On 01/10/2012 11:53 AM, Robert Cimrman wrote:
On 01/10/12 11:23, nil...@googlemail.com wrote:
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
*blush* Sorry, I have overlooked, that SfePy _can_ save in nastran's .bdf format! (Thanks to Vladimir Lukes).
I tested BDF writer just for a few simple meshes. Please, let me know how it works for you.
Vladimir
Just use
./script/convert_mesh.py file.neu file.bdf
It was the "./script/convert_mesh.py -l" that was wrong - it's fixed now in the git repo.
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk sfepy: nastran
Close the issue, please, if it works for you. (From gambit export in the .neu format.)
r.
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
./convert_mesh.py ~/Downloads/plate_total.neu plate_new.bdf sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHDPM.py cannot be imported! sfepy: reason: 'module' object has no attribute 'd_hdpm_surfdvel' sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHyperElasticity.py cannot be imported! sfepy: reason: name 'Volume' is not defined sfepy: reading mesh (/home/nwagner/Downloads/plate_total.neu)... Traceback (most recent call last): File "./convert_mesh.py", line 99, in<module> main() File "./convert_mesh.py", line 68, in main mesh = Mesh.from_file(filename_in) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ mesh.py", line 435, in from_file mesh = io.read(mesh, omit_facets=omit_facets) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ meshio.py", line 2341, in read assert_(row[0] == 'ENDOFSECTION') File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/base/ base.py", line 138, in assert_ raise ValueError( 'assertion failed!' ) ValueError: assertion failed!
grep -a2 ENDOFSECTION ~/Downloads/plate_total.neu NUMNP NELEM NGRPS NBSETS NDFCD NDFVL 18132 11795 1 5 3 3 ENDOFSECTION NODAL COORDINATES 2.4.6 1 1.60000000000e-001 1.60000000000e-001 -2.00000000000e-002
18131 1.53125548753e-001 1.92495751551e-001 2.63045876856e-001 18132 1.30962487325e-001 1.81412260269e-001 2.77274676176e-001ENDOFSECTION ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812
11795 6 10 16717 18128 16720 18087 18124 1669618094 18125 17823 16686 ENDOFSECTION ELEMENT GROUP 2.4.6 GROUP: 1 ELEMENTS: 11795 MATERIAL: 2 NFLAGS: 1
3882 3883 3884 3885 3886 3887 3888 38893890 3891 3892 3893 3894 3895 3896 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_side 0 311 0 24
5403 5404ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_top 0 1221 0 24
5310 5311ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symx_end 0 1005 0 24
1586 1587ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symy_end 0 1017 0 24
1708 1709ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
444 6 4 517 6 1ENDOFSECTION
On 10 Jan., 13:08, Vladimír Lukešvlu...@kme.zcu.cz wrote:
On 01/10/2012 11:53 AM, Robert Cimrman wrote:
On 01/10/12 11:23, nil...@googlemail.com wrote:
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
*blush* Sorry, I have overlooked, that SfePy _can_ save in nastran's .bdf format! (Thanks to Vladimir Lukes).
I tested BDF writer just for a few simple meshes. Please, let me know how it works for you.
Vladimir
Just use
./script/convert_mesh.py file.neu file.bdf
It was the "./script/convert_mesh.py -l" that was wrong - it's fixed now in the git repo.
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk sfepy: nastran
Close the issue, please, if it works for you. (From gambit export in the .neu format.)
r.
On 10 Jan., 21:21, Vladimír Lukeš vlu...@kme.zcu.cz wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
./convert_mesh.py ~/Downloads/plate_total.neu plate_new.bdf sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHDPM.py cannot be imported! sfepy: reason: 'module' object has no attribute 'd_hdpm_surfdvel' sfepy: WARNING: module /home/nwagner/local/lib64/python2.6/site- packages/sfepy/terms/termsHyperElasticity.py cannot be imported! sfepy: reason: name 'Volume' is not defined sfepy: reading mesh (/home/nwagner/Downloads/plate_total.neu)... Traceback (most recent call last): File "./convert_mesh.py", line 99, in<module> main() File "./convert_mesh.py", line 68, in main mesh = Mesh.from_file(filename_in) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ mesh.py", line 435, in from_file mesh = io.read(mesh, omit_facets=omit_facets) File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/fem/ meshio.py", line 2341, in read assert_(row[0] == 'ENDOFSECTION') File "/home/nwagner/local/lib64/python2.6/site-packages/sfepy/base/ base.py", line 138, in assert_ raise ValueError( 'assertion failed!' ) ValueError: assertion failed!
grep -a2 ENDOFSECTION ~/Downloads/plate_total.neu NUMNP NELEM NGRPS NBSETS NDFCD NDFVL 18132 11795 1 5 3 3 ENDOFSECTION NODAL COORDINATES 2.4.6 1 1.60000000000e-001 1.60000000000e-001 -2.00000000000e-002
18131 1.53125548753e-001 1.92495751551e-001 2.63045876856e-001 18132 1.30962487325e-001 1.81412260269e-001 2.77274676176e-001 ENDOFSECTION ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812
11795 6 10 16717 18128 16720 18087 18124 16696 18094 18125 17823 16686 ENDOFSECTION ELEMENT GROUP 2.4.6 GROUP: 1 ELEMENTS: 11795 MATERIAL: 2 NFLAGS: 1
3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_side 0 311 0 24
5403 5404 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 plate_top 0 1221 0 24
5310 5311 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symx_end 0 1005 0 24
1586 1587 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 symy_end 0 1017 0 24
1708 1709 ENDOFSECTION BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
444 6 4 517 6 1 ENDOFSECTION
On 10 Jan., 13:08, Vladimír Lukešvlu...@kme.zcu.cz wrote:
On 01/10/2012 11:53 AM, Robert Cimrman wrote:
On 01/10/12 11:23, nil...@googlemail.com wrote:
I have filed a ticket. See http://code.google.com/p/sfepy/issues/detail?id=166
*blush* Sorry, I have overlooked, that SfePy _can_ save in nastran's .bdf format! (Thanks to Vladimir Lukes).
I tested BDF writer just for a few simple meshes. Please, let me know how it works for you.
Vladimir
Just use
./script/convert_mesh.py file.neu file.bdf
It was the "./script/convert_mesh.py -l" that was wrong - it's fixed now in the git repo.
$ ./script/convert_mesh.py -l sfepy: Supported writable mesh formats are: sfepy: comsol sfepy: hdf5 sfepy: medit sfepy: vtk sfepy: nastran
Close the issue, please, if it works for you. (From gambit export in the .neu format.)
r.
I think it's better to send it off-list due to size. Do you agree ?
668K plate_total.neu.gz
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, Vladimír Lukešvlu...@kme.zcu.cz wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
On 1/11/12, Vladimír Lukeš vlu...@kme.zcu.cz wrote:
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, Vladimír Lukešvlu...@kme.zcu.cz wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Unfortunately, I am not familiar with the gambit format, but I have asked someone. In the meantime I have removed the boundary conditions from the file I have send to you. There seems to be another problem with the element connectivity. Only one element is converted by sfepy's convert_mesh.py. How about TET10 elements ?
ELEMENTS/CELLS 2.4.6
1 6 10 1824 2452 1865 2441 2454 1861 2812
2813 2814 285$NASTRAN Bulk Data File created by SfePy $ BEGIN BULK $ $ ELEMENT CONNECTIVITY $ CHEXA 1 1 1556 6 10 1268 1331 1236 +0000001 +00000011333 1334
On 01/11/2012 10:13 AM, Nils Wagner wrote:
On 1/11/12, Vladimír Lukešvlu...@kme.zcu.cz wrote:
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, Vladimír Lukešvlu...@kme.zcu.cz wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Unfortunately, I am not familiar with the gambit format, but I have asked someone. In the meantime I have removed the boundary conditions from the file I have send to you. There seems to be another problem with the element connectivity. Only one element is converted by sfepy's convert_mesh.py. How about TET10 elements ?
Unfortunately, only "basic" elements like quad4, hex8, tri3 and tet4 are supported by Sfepy readers. Of course, you can use the higher order elements, but the extra nodes are generated by Sfepy itself.
ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812 2813 2814 285$NASTRAN Bulk Data File created by SfePy $ BEGIN BULK $ $ ELEMENT CONNECTIVITY $ CHEXA 1 1 1556 6 10 1268 1331 1236 +0000001 +00000011333 1334
On Jan 11, 11:24 am, Vladimír Lukeš vlu...@kme.zcu.cz wrote:
On 01/11/2012 10:13 AM, Nils Wagner wrote:
On 1/11/12, Vladimír Lukešvlu...@kme.zcu.cz wrote:
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, Vladimír Lukešvlu...@kme.zcu.cz wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
It doesn't work for me. I guess that some keywords are not supported yet. Any idea ? Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Unfortunately, I am not familiar with the gambit format, but I have asked someone. In the meantime I have removed the boundary conditions from the file I have send to you. There seems to be another problem with the element connectivity. Only one element is converted by sfepy's convert_mesh.py. How about TET10 elements ?
Unfortunately, only "basic" elements like quad4, hex8, tri3 and tet4 are supported by Sfepy readers. Of course, you can use the higher order elements, but the extra nodes are generated by Sfepy itself.
ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812 2813 2814 285
$NASTRAN Bulk Data File created by SfePy $ BEGIN BULK $ $ ELEMENT CONNECTIVITY $ CHEXA 1 1 1556 6 10 1268 1331 1236 +0000001 +00000011333 1334
Is it planned to support higher order elements like tet10 elements in the near future ?
On Wed, 11 Jan 2012, nil...@googlemail.com wrote:
On Jan 11, 11:24ÄĹźËam, VladimÄĹźËr LukeÄĹźË vlu...@kme.zcu.cz wrote:
On 01/11/2012 10:13 AM, Nils Wagner wrote:
On 1/11/12, VladimÄĹźËr LukeÄĹźËvlu...@kme.zcu.cz ÄĹźËwrote:
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, VladimÄĹźËr LukeÄĹźËvlu...@kme.zcu.cz ÄĹźË wrote:
It seems to be a problem in the NEUreader. Please, can you send your mesh file?
On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
> It doesn't work for me. > I guess that some keywords are not supported yet. > Any idea ? > Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
ÄĹźË ÄĹźËBOUNDARY CONDITIONS 2.4.6 ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË wall ÄĹźË ÄĹźË ÄĹźË 1 ÄĹźË ÄĹźË1248 ÄĹźË ÄĹźË ÄĹźË 0 ÄĹźË ÄĹźË ÄĹźË 6
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Unfortunately, I am not familiar with the gambit format, but I have asked someone. In the meantime I have removed the boundary conditions from the file I have send to you. There seems to be another problem with the element connectivity. Only one element is converted by sfepy's convert_mesh.py. How about TET10 elements ?
Unfortunately, only "basic" elements like quad4, hex8, tri3 and tet4 are supported by Sfepy readers. Of course, you can use the higher order elements, but the extra nodes are generated by Sfepy itself.
ÄĹźË ÄĹźË ÄĹźË ÄĹźËELEMENTS/CELLS 2.4.6 ÄĹźË ÄĹźË ÄĹźË ÄĹźË 1 ÄĹźË6 10 ÄĹźË ÄĹźË 1824 ÄĹźË ÄĹźË2452 ÄĹźË ÄĹźË1865 ÄĹźË ÄĹźË2441 ÄĹźË ÄĹźË2454 ÄĹźË ÄĹźË1861 ÄĹźË ÄĹźË2812 ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË ÄĹźË 2813 ÄĹźË ÄĹźË2814 ÄĹźË ÄĹźË 285
$NASTRAN Bulk Data File created by SfePy $ BEGIN BULK $ $ ELEMENT CONNECTIVITY $ CHEXA ÄĹźË 1 ÄĹźË ÄĹźË ÄĹźË 1 ÄĹźË ÄĹźË ÄĹźË 1556 ÄĹźË ÄĹźË6 ÄĹźË ÄĹźË ÄĹźË 10 ÄĹźË ÄĹźË ÄĹźË1268 ÄĹźË ÄĹźË1331 ÄĹźË ÄĹźË1236 ÄĹźË ÄĹźË+0000001 +00000011333 ÄĹźË ÄĹźË1334
Is it planned to support higher order elements like tet10 elements in the near future ?
To support this in mesh readers is rather easy. To support it in computations is more complex a will not be done soon. Do you want just to conert the mesh, or ise the "quadratic" geometry while solving something with sfepy?
r.
On 1/11/12, Robert Cimrman cimr...@ntc.zcu.cz wrote:
On Wed, 11 Jan 2012, nil...@googlemail.com wrote:
On Jan 11, 11:24 am, Vladimír Lukeš vlu...@kme.zcu.cz wrote:
On 01/11/2012 10:13 AM, Nils Wagner wrote:
On 1/11/12, Vladimír Lukešvlu...@kme.zcu.cz wrote:
On 01/10/2012 08:35 PM, nil...@googlemail.com wrote:
On 10 Jan., 21:21, Vladimír Lukešvlu...@kme.zcu.cz wrote: > It seems to be a problem in the NEUreader. Please, can you send your > mesh file?
> On 01/10/2012 07:05 PM, nil...@googlemail.com wrote:
>> It doesn't work for me. >> I guess that some keywords are not supported yet. >> Any idea ? >> Here is the output ...
The problem is in reading boundary conditions from the neu file. Do you know what the numbers in the definition of boundary conditions mean? Yes, the second one is the number of BCs, but the others?
BOUNDARY CONDITIONS 2.4.6 wall 1 1248 0 6
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Unfortunately, I am not familiar with the gambit format, but I have asked someone. In the meantime I have removed the boundary conditions from the file I have send to you. There seems to be another problem with the element connectivity. Only one element is converted by sfepy's convert_mesh.py. How about TET10 elements ?
Unfortunately, only "basic" elements like quad4, hex8, tri3 and tet4 are supported by Sfepy readers. Of course, you can use the higher order elements, but the extra nodes are generated by Sfepy itself.
ELEMENTS/CELLS 2.4.6 1 6 10 1824 2452 1865 2441 2454 1861 2812 2813 2814 285$NASTRAN Bulk Data File created by SfePy $ BEGIN BULK $ $ ELEMENT CONNECTIVITY $ CHEXA 1 1 1556 6 10 1268 1331 1236 +0000001 +00000011333 1334
Is it planned to support higher order elements like tet10 elements in the near future ?
To support this in mesh readers is rather easy. To support it in computations is more complex a will not be done soon. Do you want just to conert the mesh, or ise the "quadratic" geometry while solving something with sfepy?
r.
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
At the moment, I am interested in the mesh conversion capabilities of sfepy.
On 01/11/12 13:29, Nils Wagner wrote:
On 1/11/12, Robert Cimrmancimr...@ntc.zcu.cz wrote:
On Wed, 11 Jan 2012, nil...@googlemail.com wrote:
Is it planned to support higher order elements like tet10 elements in the near future ?
To support this in mesh readers is rather easy. To support it in computations is more complex a will not be done soon. Do you want just to conert the mesh, or ise the "quadratic" geometry while solving something with sfepy?
At the moment, I am interested in the mesh conversion capabilities of sfepy.
Ok. We may add this capability (if Vladimir has time and will to do it), but in an case, I would recommend you to try looking and all gambit export formats and nastran import formats - maybe the two packages can talk together in a natural way.
r.
2012/1/11 Robert Cimrman cimr...@ntc.zcu.cz
On 01/11/12 13:29, Nils Wagner wrote:
On 1/11/12, Robert Cimrmancimr...@ntc.zcu.cz wrote:
On Wed, 11 Jan 2012, nil...@googlemail.com wrote:
Is it planned to support higher order elements like tet10 elements in the near future ?
To support this in mesh readers is rather easy. To support it in computations is more complex a will not be done soon. Do you want just to conert the mesh, or ise the "quadratic" geometry while solving something with sfepy?
At the moment, I am interested in the mesh conversion capabilities of sfepy.
Ok. We may add this capability (if Vladimir has time and will to do it), but in an case, I would recommend you to try looking and all gambit export formats and nastran import formats - maybe the two packages can talk together in a natural way.
r.
I would like to take back my former comment - allthough a Nastran input is nice in SfePy (sorry, I had not seen it) it is not the main purpose of the package to be a mesh converter! I think there quite some need for a (free/open source) file format converter, but there is very few volenteers for such a project. I could participate if someone started such a project - sfepy as base is probably not a bad place to start. I would not be maintainer, but I can test the typical commercial solver formats; Nastran, Abaqus and Ansys.
On 01/11/12 18:14, Peter M. Clausen wrote:
2012/1/11 Robert Cimrmancimr...@ntc.zcu.cz
On 01/11/12 13:29, Nils Wagner wrote:
On 1/11/12, Robert Cimrmancimr...@ntc.zcu.cz wrote:
On Wed, 11 Jan 2012, nil...@googlemail.com wrote:
Is it planned to support higher order elements like tet10 elements in the near future ?
To support this in mesh readers is rather easy. To support it in computations is more complex a will not be done soon. Do you want just to conert the mesh, or ise the "quadratic" geometry while solving something with sfepy?
At the moment, I am interested in the mesh conversion capabilities of sfepy.
Ok. We may add this capability (if Vladimir has time and will to do it), but in an case, I would recommend you to try looking and all gambit export formats and nastran import formats - maybe the two packages can talk together in a natural way.
r.
I would like to take back my former comment - allthough a Nastran input is nice in SfePy (sorry, I had not seen it) it is not the main purpose of the package to be a mesh converter! I think there quite some need for a (free/open source) file format converter, but there is very few volenteers for such a project. I could participate if someone started such a project - sfepy as base is probably not a bad place to start. I would not be maintainer, but I can test the typical commercial solver formats; Nastran, Abaqus and Ansys.
Yes, it would be nice to have a BSD-licensed mesh converter in Python that supports most of the standard formats. I will happily accommodate such code in SfePy. We support some of the formats, but so far we have implemented only what we really needed for our work, so the support is by no means complete. We need people scratching their own itches to help with that :)
BTW. are you aware of [1]?
r.
participants (5)
-
nil...＠googlemail.com -
Nils Wagner
-
Peter M. Clausen -
Robert Cimrman -
Vladimír Lukeš