gmsh issueshttps://gitlab.onelab.info/gmsh/gmsh/-/issues2022-05-28T15:30:35Zhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/1Fix artefacts when moving the mouse over an animation2022-05-28T15:30:35ZChristophe GeuzaineFix artefacts when moving the mouse over an animationWhen Gmsh loops over views/steps and one moves the mouse over the graphics window the display sometimes gets scrambled for one frame.When Gmsh loops over views/steps and one moves the mouse over the graphics window the display sometimes gets scrambled for one frame.https://gitlab.onelab.info/gmsh/gmsh/-/issues/2add binary comparison operators (<, >, etc.) in mathEvaluator2022-05-28T15:30:36ZChristophe Geuzaineadd binary comparison operators (<, >, etc.) in mathEvaluatorThe summmary says it all: we should add support for <, >, <=, >= in the Numeric/mathEvaluator (via MathEx I guess).
+ having tests would be nice (e.g in the form a?b:c)The summmary says it all: we should add support for <, >, <=, >= in the Numeric/mathEvaluator (via MathEx I guess).
+ having tests would be nice (e.g in the form a?b:c)https://gitlab.onelab.info/gmsh/gmsh/-/issues/3remove shapeFunctions.h2022-04-01T07:19:55ZChristophe Geuzaineremove shapeFunctions.hWe should replace the last uses of shapeFunctions.h with MElement.h (might want to create a pool of MVertices to speed up temp element creation in plugins)We should replace the last uses of shapeFunctions.h with MElement.h (might want to create a pool of MVertices to speed up temp element creation in plugins)https://gitlab.onelab.info/gmsh/gmsh/-/issues/4scriptable multi-windows/multi-panes2022-04-01T07:19:55ZChristophe Geuzainescriptable multi-windows/multi-panesMulti-view (tiles/windows) are not scriptable. They should be.Multi-view (tiles/windows) are not scriptable. They should be.https://gitlab.onelab.info/gmsh/gmsh/-/issues/5Node renumbering2023-07-22T13:44:30ZChristophe GeuzaineNode renumberingIt could be interesting to add entity renumering capabilities to ease the job of solver developers.
We could e.g. add a Reverse Cuthill-McKee also to reorder the nodes.It could be interesting to add entity renumering capabilities to ease the job of solver developers.
We could e.g. add a Reverse Cuthill-McKee also to reorder the nodes.https://gitlab.onelab.info/gmsh/gmsh/-/issues/6INTERPOLATION_SCHEME{{0,0,0,0,0}{ok}} screws up the GUI2023-07-22T13:44:31ZChristophe GeuzaineINTERPOLATION_SCHEME{{0,0,0,0,0}{ok}} screws up the GUIA high-order .pos file with INTERPOLATION_SCHEME{{0,0,0,0,0}{ok}}
screws up the GUIA high-order .pos file with INTERPOLATION_SCHEME{{0,0,0,0,0}{ok}}
screws up the GUIhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/7Saving string options containing the " character does not work2022-04-01T07:19:55ZChristophe GeuzaineSaving string options containing the " character does not workCannot save string options containing the " character.
Keep this in mind when rewriting the option db.Cannot save string options containing the " character.
Keep this in mind when rewriting the option db.https://gitlab.onelab.info/gmsh/gmsh/-/issues/8Embedded edges with Delaunay/Frontal2022-04-01T07:19:55ZChristophe GeuzaineEmbedded edges with Delaunay/FrontalMake embedded edges work with the Delaunay/Frontal algorithmsMake embedded edges work with the Delaunay/Frontal algorithmshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/9Attractor fields on general surfaces2022-04-01T07:19:55ZChristophe GeuzaineAttractor fields on general surfacesMake Attractor fields work on general surfacesMake Attractor fields work on general surfaceshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/10Add function to merge/remove from lists in the parser2022-04-01T07:19:55ZChristophe GeuzaineAdd function to merge/remove from lists in the parserAdd function to merge/remove from lists in the parserAdd function to merge/remove from lists in the parserhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/11Dilate XYZ2022-04-01T07:19:55ZChristophe GeuzaineDilate XYZDilate should take 3 coefs to scale differently along x, y and z!Dilate should take 3 coefs to scale differently along x, y and z!Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/12Extrude along curve2022-07-15T19:53:51ZChristophe GeuzaineExtrude along curveIt would be nice to be able to extrude along a given curve.
We could use curve->closestPoint for each xyz in ExtrudeParams and extrude along the tangent, but this could lead to self-intersection if curvature >>It would be nice to be able to extrude along a given curve.
We could use curve->closestPoint for each xyz in ExtrudeParams and extrude along the tangent, but this could lead to self-intersection if curvature >>Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/13embedded vertices and extrusion2022-04-01T07:19:55ZChristophe Geuzaineembedded vertices and extrusionShould we take embedded vertices into account in extrusions?Should we take embedded vertices into account in extrusions?Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/14Store Octree in PViewDataList2022-04-01T07:19:55ZChristophe GeuzaineStore Octree in PViewDataListWe should store the Octree in PViewDataList and modify OctreePost to use it (the same way PViewDataGModel uses the Octree stored in GModel)We should store the Octree in PViewDataList and modify OctreePost to use it (the same way PViewDataGModel uses the Octree stored in GModel)https://gitlab.onelab.info/gmsh/gmsh/-/issues/15Arbitrary glyphs in post-processor2022-04-01T07:19:55ZChristophe GeuzaineArbitrary glyphs in post-processorThink about allowing arbitrary glyphs to represent data (like our 3D
arrows).
Definition: Glyph = drawable rigid object with a single associated scalar/vector or tensor value.
A glyph could be loaded as a mesh or a geometry; create ve...Think about allowing arbitrary glyphs to represent data (like our 3D
arrows).
Definition: Glyph = drawable rigid object with a single associated scalar/vector or tensor value.
A glyph could be loaded as a mesh or a geometry; create vertex
array or display list for each; select glyph in Point/Vector/Tensor
display dialog; define number of values to transform glyph (quaternion + scale{x,y,z}?).
Cf. old implementation for LMGChttps://gitlab.onelab.info/gmsh/gmsh/-/issues/16transparent meshes2022-04-01T07:19:55ZChristophe Geuzainetransparent meshesWe should add a global "transparency slider" for the mesh.
If value != 1, we should fill a global triangle vertex array in GModel instead of in each separate entity, and sort like in post-processing.We should add a global "transparency slider" for the mesh.
If value != 1, we should fill a global triangle vertex array in GModel instead of in each separate entity, and sort like in post-processing.https://gitlab.onelab.info/gmsh/gmsh/-/issues/17Fix 3D Delaunay for non-manifold geometries2022-04-01T07:19:55ZChristophe GeuzaineFix 3D Delaunay for non-manifold geometriesWith a single surface connected to a volume, if the 3D Delaunay modifies the volume boundary mesh we get hanging nodes.
We should precompute non-connected volumes and apply the algo to each non-connected aggregate separelely. This would...With a single surface connected to a volume, if the 3D Delaunay modifies the volume boundary mesh we get hanging nodes.
We should precompute non-connected volumes and apply the algo to each non-connected aggregate separelely. This would also improve the mesh quality and speed for close non-connected objects.
Also: we need to fix the 1D mesh in all cases.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/18Add list of recently loaded files in the GUI2022-04-01T07:19:55ZChristophe GeuzaineAdd list of recently loaded files in the GUISubject says it all :-)Subject says it all :-)https://gitlab.onelab.info/gmsh/gmsh/-/issues/19Remove duplicate mesh elements2022-11-03T17:07:38ZChristophe GeuzaineRemove duplicate mesh elementsWe shoudl add a cleanup function to remove duplicate elements (in the same spirit as GModel::removeDuplicateVertices)We shoudl add a cleanup function to remove duplicate elements (in the same spirit as GModel::removeDuplicateVertices)https://gitlab.onelab.info/gmsh/gmsh/-/issues/20Add support for Patran mesh files2022-04-01T07:19:55ZChristophe GeuzaineAdd support for Patran mesh filesSubject says it all...Subject says it all...https://gitlab.onelab.info/gmsh/gmsh/-/issues/21Add support for Samcef mesh files2022-04-01T07:19:55ZChristophe GeuzaineAdd support for Samcef mesh filesSubject says it all...Subject says it all...Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/22Improve 1D transfinite algorithm2022-04-01T07:19:55ZChristophe GeuzaineImprove 1D transfinite algorithm** Add linear lc progression in 1D transfinite generator
* Implement easier to understand "bump" function (double progression?)** Add linear lc progression in 1D transfinite generator
* Implement easier to understand "bump" function (double progression?)https://gitlab.onelab.info/gmsh/gmsh/-/issues/23Add facility to copy meshes between geometrical entities2022-04-01T07:19:55ZChristophe GeuzaineAdd facility to copy meshes between geometrical entitiesWe should add a parameter to geometrical transforms to copy the
meshes--this would allow us to do symmetries and periodic meshes.
Right now we can copy meshes using an extrusion hack: cf. periodic_unstructured.geoWe should add a parameter to geometrical transforms to copy the
meshes--this would allow us to do symmetries and periodic meshes.
Right now we can copy meshes using an extrusion hack: cf. periodic_unstructured.geohttps://gitlab.onelab.info/gmsh/gmsh/-/issues/24Improvements to extrusion algorithms2023-10-09T19:19:02ZChristophe GeuzaineImprovements to extrusion algorithmsThis issue tracks some ideas about generalizations of the extrusion algorithms:
* It would be nice to be able to create extruded meshes for OCC pipes
* not clear how to do this in all cases (cf. all the possible `trihedron` values: ...This issue tracks some ideas about generalizations of the extrusion algorithms:
* It would be nice to be able to create extruded meshes for OCC pipes
* not clear how to do this in all cases (cf. all the possible `trihedron` values: "DiscreteTrihedron", "CorrectedFrenet", "Fixed", ...); maybe just for the simplest case where we would evaluate the "guiding" curve?
* It would be nice to be able to provide a scaling function - see e.g. #1991
* It could be useful to introduce Right/Left/Alternate for extruded meshes, as for transfinite meshes
* We could fill transfinite_vertices in meshG{Face,Region}Extrude when it makes sense (so that we can use extruded+recombined surfaces to create Transfinite Volumes, or use the P3D or structured CGNS output format)
* It could be useful to define some templates to extrude + refine in order to generate "structured refinements"
* in 2D: from 1 curve to 3, or from 1 curve to 2 (left and right)
* in 3D: the usual patterns...https://gitlab.onelab.info/gmsh/gmsh/-/issues/25Pyramid elements to link unstructured and structured grids2017-03-23T16:20:50ZChristophe GeuzainePyramid elements to link unstructured and structured gridsCreate pyramids on quad surfaces inside unstructured volume before
tetrahedralizing (to enable hex/tet hybrid grids)Create pyramids on quad surfaces inside unstructured volume before
tetrahedralizing (to enable hex/tet hybrid grids)https://gitlab.onelab.info/gmsh/gmsh/-/issues/26CORDxx in BDF (Nastran) mesh files2020-08-17T08:07:41ZChristophe GeuzaineCORDxx in BDF (Nastran) mesh filesParse CORDxx entries in Nastran files to get coordinate system
definitions and use them when reading GRID + parse GRIDxx for axisym
pointsParse CORDxx entries in Nastran files to get coordinate system
definitions and use them when reading GRID + parse GRIDxx for axisym
pointshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/27Need better algorithm to draw axes2022-06-13T15:08:04ZChristophe GeuzaineNeed better algorithm to draw axesWe should implement a better algorithm to determine which axes to draw
(see e.g. how Mathematica does it)We should implement a better algorithm to determine which axes to draw
(see e.g. how Mathematica does it)https://gitlab.onelab.info/gmsh/gmsh/-/issues/28Better "filled iso" drawing in 3D2020-08-17T08:06:35ZChristophe GeuzaineBetter "filled iso" drawing in 3DCustom range on "filled iso" 3D views produces ugly plots, where one
sees inside the cut elements. (In the meantime, one can use
Plugin(CutMap) with "ExtractVolume" set to 1 (or -1): this will
generate a new view with an actual "cut" on ...Custom range on "filled iso" 3D views produces ugly plots, where one
sees inside the cut elements. (In the meantime, one can use
Plugin(CutMap) with "ExtractVolume" set to 1 (or -1): this will
generate a new view with an actual "cut" on the front (an
"iso-volume"). Then one could use Plugin(Skin) to extract the outer
surface.)https://gitlab.onelab.info/gmsh/gmsh/-/issues/29Mesh/view capping2023-07-27T12:31:09ZChristophe GeuzaineMesh/view cappingAdd new visu option to cap the mesh instead of displaying "whole"
elementsAdd new visu option to cap the mesh instead of displaying "whole"
elementshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/30Missing GUI for translate+rotate extrusions and for mesh extrusion2020-08-16T23:30:36ZChristophe GeuzaineMissing GUI for translate+rotate extrusions and for mesh extrusionThere is currently no GUI for translate+rotate extrusions and for mesh
extrusion (layer stuff)There is currently no GUI for translate+rotate extrusions and for mesh
extrusion (layer stuff)Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/31Improve labels in views2017-08-05T11:16:32ZChristophe GeuzaineImprove labels in views** add dynamic variables? E.g., if a string contains %string.string, replace it dynamically in Draw_Text2D/3D by calling Get_OptionsCategory/Get_OptionValue. (provide a global option to disable all replacements)
* position with the mous...** add dynamic variables? E.g., if a string contains %string.string, replace it dynamically in Draw_Text2D/3D by calling Get_OptionsCategory/Get_OptionValue. (provide a global option to disable all replacements)
* position with the mouse
* select/move once positioned?
* add ability to add arrows
* fonts are uglyChristophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/32Parametric curves2020-08-16T23:30:36ZChristophe GeuzaineParametric curvesRestore Parametric curve type using MathEvalRestore Parametric curve type using MathEvalChristophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/33Problem with datasets with bounding box < 1e-6 on Mac OS X2023-07-27T12:34:34ZChristophe GeuzaineProblem with datasets with bounding box < 1e-6 on Mac OS XOn Mac OS X, datasets with a bounding box < 1.e-06 don't display
properly (probably because all the OpenGL stuff is done internally in
single precision...). Should we rescale?On Mac OS X, datasets with a bounding box < 1.e-06 don't display
properly (probably because all the OpenGL stuff is done internally in
single precision...). Should we rescale?https://gitlab.onelab.info/gmsh/gmsh/-/issues/34Volume visualization2020-08-16T23:30:36ZChristophe GeuzaineVolume visualizationWe should create a "Volume visualization" range type (interpolate on
regular grid + create cut planes // to viewpoint with transparency;
can be done in a straightforward way or using 3D textures)We should create a "Volume visualization" range type (interpolate on
regular grid + create cut planes // to viewpoint with transparency;
can be done in a straightforward way or using 3D textures)Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/35Replace Metis and Chaco with Scotch?2018-01-11T09:59:06ZChristophe GeuzaineReplace Metis and Chaco with Scotch?We should maybe think about replacing the aging Metis and Chaco mesh partionners with a single interface to Scotch.
http://www.labri.fr/perso/pelegrin/scotch/We should maybe think about replacing the aging Metis and Chaco mesh partionners with a single interface to Scotch.
http://www.labri.fr/perso/pelegrin/scotch/Anthony RoyerAnthony Royerhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/356Parallel classification of lower order entities2018-01-11T09:59:25ZKoen HillewaertParallel classification of lower order entitiesCurrently, I think only elements of dimensions d and d-1 are classified on a parallel section, except for newly created partition boundaries. In case a single file is written containing all partitions, no filter on the partition id is us...Currently, I think only elements of dimensions d and d-1 are classified on a parallel section, except for newly created partition boundaries. In case a single file is written containing all partitions, no filter on the partition id is used, and we still have a full topology. However, in case a single file per partition is written, the lowest dimensions of the topology (d-2, d-3) disappear. There are two solutions possible:
- write lowest dimension topology completely in the files no matter what
- classify also lowest dimension topology per partition
What is the preferred action ?Anthony RoyerAnthony Royerhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/36robustify classificationEditor2020-08-16T23:30:36ZChristophe Geuzainerobustify classificationEditorclassificationEditor is tricky/too complicated to use: rework the GUI and make it more robustclassificationEditor is tricky/too complicated to use: rework the GUI and make it more robusthttps://gitlab.onelab.info/gmsh/gmsh/-/issues/37document Compounds2017-03-23T16:20:55ZChristophe Geuzainedocument CompoundsDocument Compound geometrical entitiesDocument Compound geometrical entitieshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/38snow leopard-display issue2020-08-16T23:30:36ZChristophe Geuzainesnow leopard-display issueIssue with display on Snow leopard, 64 bit.
words in screen menus up-side-down.Issue with display on Snow leopard, 64 bit.
words in screen menus up-side-down.https://gitlab.onelab.info/gmsh/gmsh/-/issues/39add small editor with reload capability directly into the FLTK GUI2017-03-23T16:20:57ZChristophe Geuzaineadd small editor with reload capability directly into the FLTK GUIadd small editor with reload capability directly into the FLTK GUIadd small editor with reload capability directly into the FLTK GUIhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/40Script Merge command2020-08-16T23:30:36ZChristophe GeuzaineScript Merge commandThe Merge command cannot be scripted from the GUI -- fix that!The Merge command cannot be scripted from the GUI -- fix that!https://gitlab.onelab.info/gmsh/gmsh/-/issues/41add support for multi-tile PDF export2017-08-05T11:15:40ZChristophe Geuzaineadd support for multi-tile PDF exportsubject says it allsubject says it allChristophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/42Débutante avec GMSH ayant besoin d'aide !!2020-08-16T23:30:36ZChristophe GeuzaineDébutante avec GMSH ayant besoin d'aide !!Bonjour à tous,
je vous envoie ce mail car je suis en école d'ingénieur et je dois réaliser un maillage avec gmsh. Le problème, c'est que je suis totalement novice en la matière !!!
Ma géométrie est la suivante :
3 cylindres mis bout...Bonjour à tous,
je vous envoie ce mail car je suis en école d'ingénieur et je dois réaliser un maillage avec gmsh. Le problème, c'est que je suis totalement novice en la matière !!!
Ma géométrie est la suivante :
3 cylindres mis bout à bout, le cylindre du milieu étant de diamètre inférieur aux cylindres extérieurs.
mon code est en pièce jointe : geomtrie_totale.geo
Ma première question est la suivante : est-ce que la manière dont j'ai procédé pour créer mon volume est correcte ? Parce que en régardant dans les archives, j'ai vu que certains utilisaient la fonction "extruder" (dans le fichier cylindre.geo par expemple), mais je ne sais pas à quoi cela correspond.
Au niveau du maillage, j'ai cliqué sur 3D.
J'aurais souhaité savoir à quoi correspondaient les fonctions :
- refine by splitting
- optimize
- optimize (Netzgen)
J'ai bien chercher dans le tutorial, mais cela ne m'a pas beaucoup plus éclairée ...
Voilà, si l'un de vous avait la gentillesse de m'aider, j'en serai ravie ^^
Gaëlle
PS : si vous connaissez un guide d'utilisation simplifier de GMSH, je suis preneuse !!!https://gitlab.onelab.info/gmsh/gmsh/-/issues/43Gmsh crashes on STEP file2017-03-23T16:20:59ZChristophe GeuzaineGmsh crashes on STEP fileHi,
I've just started working on a project in which I'm building 3D models with OpenCascade and writing STEP or BREP files for Gmsh to mesh them. Currently I'm just trying to understand what are Gmsh's limitations, so I'm using brep fil...Hi,
I've just started working on a project in which I'm building 3D models with OpenCascade and writing STEP or BREP files for Gmsh to mesh them. Currently I'm just trying to understand what are Gmsh's limitations, so I'm using brep files from the OpenCascade distribution. Gmsh is crashing on a couple of occasions while trying to mesh the files I'm attaching. Hope these help with Gmsh's stability. I'm using Gmsh 2.4.2, Build date: 20090921.https://gitlab.onelab.info/gmsh/gmsh/-/issues/44crash in a simple STEP file2020-08-16T23:30:36ZChristophe Geuzainecrash in a simple STEP fileI found another STEP file (this time generated by OpenCascade) that crashes Gmsh during 3D meshing. Gmsh crashes with an assertion failure in tetgen.cxx (Expression: matchflag == true). I'm attaching the STEP file, hope this helps improv...I found another STEP file (this time generated by OpenCascade) that crashes Gmsh during 3D meshing. Gmsh crashes with an assertion failure in tetgen.cxx (Expression: matchflag == true). I'm attaching the STEP file, hope this helps improve the stability of Gmsh.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/45I cannot change element type.2017-03-23T16:21:01ZChristophe GeuzaineI cannot change element type.Hi,
I'm trying to FEA an impeller.
But mesh generation with Gmsh wasn't working so well.
I want to calculate Centrifugal loading, but I've got only beam or shell element types.
Even though I choose Mesh.SubdivisionAlgorithm option to gen...Hi,
I'm trying to FEA an impeller.
But mesh generation with Gmsh wasn't working so well.
I want to calculate Centrifugal loading, but I've got only beam or shell element types.
Even though I choose Mesh.SubdivisionAlgorithm option to generate fully gexagedral meshes, the result was still B32R and S6 elements.
Please let me know what's wrong.
Best regards,
Peterhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/46Warnings from CMake2020-08-16T23:30:36ZChristophe GeuzaineWarnings from CMakeAs of now, CMake complains when generating the makefiles for gmsh :
WARNING: Target "lib" has EXCLUDE_FROM_ALL set and will not be built by default but an install rule has been provided for it. CMake does not define behavior for this c...As of now, CMake complains when generating the makefiles for gmsh :
WARNING: Target "lib" has EXCLUDE_FROM_ALL set and will not be built by default but an install rule has been provided for it. CMake does not define behavior for this case.
WARNING: Target "shared" has EXCLUDE_FROM_ALL set and will not be built by default but an install rule has been provided for it. CMake does not define behavior for this case.
Those warning could be supressed by using a CMake variable, as follows :
ADD_LIBRARY(foo-shared SHARED foo.cc)
IF(BUILD_STATIC)
ADD_LIBRARY(foo-static STATIC foo.cc)
ENDIF()
INSTALL(TARGETS foo-shared
ARCHIVE DESTINATION lib
LIBRARY DESTINATION lib
RUNTIME DESTINATION bin)
IF(BUILD_STATIC)
INSTALL(TARGETS foo-static
ARCHIVE DESTINATION lib
LIBRARY DESTINATION lib
RUNTIME DESTINATION bin)
ENDIF()
Is there an advantage in doing things as they are done now ?https://gitlab.onelab.info/gmsh/gmsh/-/issues/47cmake doesn't check if glu headers are present2017-03-23T16:21:02ZChristophe Geuzainecmake doesn't check if glu headers are presentThe cmake script doesn't check if opengl headers are present in the system, which ends up successfully generating the Makefile but fails to build due to not being able to find glu.h.The cmake script doesn't check if opengl headers are present in the system, which ends up successfully generating the Makefile but fails to build due to not being able to find glu.h.https://gitlab.onelab.info/gmsh/gmsh/-/issues/48Crash in multiscale partitionning code on linux-64 bits2020-08-16T23:30:36ZChristophe GeuzaineCrash in multiscale partitionning code on linux-64 bitsOn liux 64 bits, gmsh crashes when using multi-scale partitions.
I've been able to reproduce the bug on two different 64 bits machines, using the attached test case, and the following command :
./gmsh pelvis.geo -2 -saveall
gmsh crash...On liux 64 bits, gmsh crashes when using multi-scale partitions.
I've been able to reproduce the bug on two different 64 bits machines, using the attached test case, and the following command :
./gmsh pelvis.geo -2 -saveall
gmsh crashes after a few seconds, but don't crash when run through valgrind.
Here is the backtrace :
*** glibc detected *** ./gmsh: double free or corruption (out): 0x0000000004be1530 ***
======= Backtrace: =========
/lib/libc.so.6[0x7f42e65dddd6]
/lib/libc.so.6(cfree+0x6c)[0x7f42e65e270c]
./gmsh(_Z13PartitionMeshP6GModelR20meshPartitionOptions+0x1b2)[0xbaf912]
./gmsh(_Z21PartitionMeshElementsRSt6vectorIP8MElementSaIS1_EER20meshPartitionOptions+0x3c1)[0xbb0191]
./gmsh(_ZN19multiscalePartition9partitionER14partitionLevel+0x30)[0xbbc8c0]
./gmsh(_ZN19multiscalePartitionC1ERSt6vectorIP8MElementSaIS2_EER20meshPartitionOptions+0x16e)[0xbbdeee]
./gmsh(_Z18PartitionZeroGenusRSt4listIP5GFaceSaIS1_EERi+0x24b)[0xbac66b]
./gmsh(_Z18partitionAndRemeshP13GFaceCompound+0x57)[0xb4c297]
./gmsh(_Z17checkMeshCompoundP13GFaceCompoundRSt4listIP5GEdgeSaIS3_EE+0xfa)[0xb4d7da]
./gmsh[0xb4f7b5]
./gmsh(_ZN9meshGFaceclEP5GFace+0x152)[0xb4c152]
./gmsh(_Z12GenerateMeshP6GModeli+0x57c)[0xb32bcc]
./gmsh(_ZN6GModel4meshEi+0x9)[0xaaf7a9]
./gmsh(_Z9GmshBatchv+0x2a2)[0x9f5572]
./gmsh(main+0x9e)[0x9f44be]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7f42e6586abd]
./gmsh[0x9f4209]
======= Memory map: ========
00400000-02645000 r-xp 00000000 08:03 2493779 /home/grungi/src/gmsh/bin/gmsh
02845000-0284e000 r--p 02245000 08:03 2493779 /home/grungi/src/gmsh/bin/gmsh
0284e000-028cb000 rw-p 0224e000 08:03 2493779 /home/grungi/src/gmsh/bin/gmsh
028cb000-02be2000 rw-p 00000000 00:00 0
04971000-04e28000 rw-p 00000000 00:00 0 [heap]
20000000-203e8000 rw-p 00000000 00:0f 1585 /dev/zero
7f42e0000000-7f42e0021000 rw-p 00000000 00:00 0
7f42e0021000-7f42e4000000 ---p 00000000 00:00 0
7f42e41fd000-7f42e4202000 r-xp 00000000 08:01 4791 /usr/lib/libXdmcp.so.6.0.0
7f42e4202000-7f42e4401000 ---p 00005000 08:01 4791 /usr/lib/libXdmcp.so.6.0.0
7f42e4401000-7f42e4402000 rw-p 00004000 08:01 4791 /usr/lib/libXdmcp.so.6.0.0
7f42e4402000-7f42e4428000 r-xp 00000000 08:01 965 /lib/libexpat.so.1.5.2
7f42e4428000-7f42e4628000 ---p 00026000 08:01 965 /lib/libexpat.so.1.5.2
7f42e4628000-7f42e462a000 r--p 00026000 08:01 965 /lib/libexpat.so.1.5.2
7f42e462a000-7f42e462b000 rw-p 00028000 08:01 965 /lib/libexpat.so.1.5.2
7f42e462b000-7f42e4634000 r-xp 00000000 08:01 4815 /usr/lib/libXrender.so.1.3.0
7f42e4634000-7f42e4833000 ---p 00009000 08:01 4815 /usr/lib/libXrender.so.1.3.0
7f42e4833000-7f42e4834000 r--p 00008000 08:01 4815 /usr/lib/libXrender.so.1.3.0
7f42e4834000-7f42e4835000 rw-p 00009000 08:01 4815 /usr/lib/libXrender.so.1.3.0
7f42e4835000-7f42e48b4000 r-xp 00000000 08:01 5086 /usr/lib/libfreetype.so.6.3.20
7f42e48b4000-7f42e4ab4000 ---p 0007f000 08:01 5086 /usr/lib/libfreetype.so.6.3.20
7f42e4ab4000-7f42e4ab9000 r--p 0007f000 08:01 5086 /usr/lib/libfreetype.so.6.3.20
7f42e4ab9000-7f42e4aba000 rw-p 00084000 08:01 5086 /usr/lib/libfreetype.so.6.3.20
7f42e4aba000-7f42e4ac1000 r-xp 00000000 08:01 1040 /lib/librt-2.10.1.so
7f42e4ac1000-7f42e4cc0000 ---p 00007000 08:01 1040 /lib/librt-2.10.1.so
7f42e4cc0000-7f42e4cc1000 r--p 00006000 08:01 1040 /lib/librt-2.10.1.so
7f42e4cc1000-7f42e4cc2000 rw-p 00007000 08:01 1040 /lib/librt-2.10.1.so
7f42e4cc2000-7f42e4cc4000 r-xp 00000000 08:01 4780 /usr/lib/libXau.so.6.0.0
7f42e4cc4000-7f42e4ec3000 ---p 00002000 08:01 4780 /usr/lib/libXau.so.6.0.0
7f42e4ec3000-7f42e4ec4000 r--p 00001000 08:01 4780 /usr/lib/libXau.so.6.0.0
7f42e4ec4000-7f42e4ec5000 rw-p 00002000 08:01 4780 /usr/lib/libXau.so.6.0.0
7f42e4ec5000-7f42e4ee0000 r-xp 00000000 08:01 5811 /usr/lib/libxcb.so.1.1.0
7f42e4ee0000-7f42e50df000 ---p 0001b000 08:01 5811 /usr/lib/libxcb.so.1.1.0
7f42e50df000-7f42e50e0000 r--p 0001a000 08:01 5811 /usr/lib/libxcb.so.1.1.0
7f42e50e0000-7f42e50e1000 rw-p 0001b000 08:01 5811 /usr/lib/libxcb.so.1.1.0
7f42e50e1000-7f42e50e4000 r-xp 00000000 08:01 1940 /lib/libuuid.so.1.3.0
7f42e50e4000-7f42e52e4000 ---p 00003000 08:01 1940 /lib/libuuid.so.1.3.0
7f42e52e4000-7f42e52e5000 r--p 00003000 08:01 1940 /lib/libuuid.so.1.3.0
7f42e52e5000-7f42e52e6000 rw-p 00004000 08:01 1940 /lib/libuuid.so.1.3.0
7f42e52e6000-7f42e52e8000 r-xp 00000000 08:01 4803 /usr/lib/libXinerama.so.1.0.0
7f42e52e8000-7f42e54e7000 ---p 00002000 08:01 4803 /usr/lib/libXinerama.so.1.0.0
7f42e54e7000-7f42e54e8000 rw-p 00001000 08:01 4803 /usr/lib/libXinerama.so.1.0.0
7f42e54e8000-7f42e5518000 r-xp 00000000 08:01 5078 /usr/lib/libfontconfig.so.1.3.0
7f42e5518000-7f42e5718000 ---p 00030000 08:01 5078 /usr/lib/libfontconfig.so.1.3.0
7f42e5718000-7f42e5719000 r--p 00030000 08:01 5078 /usr/lib/libfontconfig.so.1.3.0
7f42e5719000-7f42e571a000 rw-p 00031000 08:01 5078 /usr/lib/libfontconfig.so.1.3.0
7f42e571a000-7f42e572e000 r-xp 00000000 08:01 4799 /usr/lib/libXft.so.2.1.13
7f42e572e000-7f42e592d000 ---p 00014000 08:01 4799 /usr/lib/libXft.so.2.1.13
7f42e592d000-7f42e592e000 r--p 00013000 08:01 4799 /usr/lib/libXft.so.2.1.13
7f42e592e000-7f42e592f000 rw-p 00014000 08:01 4799 /usr/lib/libXft.so.2.1.13
7f42e592f000-7f42e5939000 r-xp 00000000 08:01 5015 /usr/lib/libdrm.so.2.4.0
7f42e5939000-7f42e5b38000 ---p 0000a000 08:01 5015 /usr/lib/libdrm.so.2.4.0
7f42e5b38000-7f42e5b39000 r--p 00009000 08:01 5015 /usr/lib/libdrm.so.2.4.0
7f42e5b39000-7f42e5b3a000 rw-p 0000a000 08:01 5015 /usr/lib/libdrm.so.2.4.0
7f42e5b3a000-7f42e5b3f000 r-xp 00000000 08:01 4795 /usr/lib/libXfixes.so.3.1.0
7f42e5b3f000-7f42e5d3e000 ---p 00005000 08:01 4795 /usr/lib/libXfixes.so.3.1.0
7f42e5d3e000-7f42e5d3f000 r--p 00004000 08:01 4795 /usr/lib/libXfixes.so.3.1.0
7f42e5d3f000-7f42e5d40000 rw-p 00005000 08:01 4795 /usr/lib/libXfixes.so.3.1.0
7f42e5d40000-7f42e5d42000 r-xp 00000000 08:01 4789 /usr/lib/libXdamage.so.1.1.0Abortedhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/49Compound Surface meshing fails when seam edge is present2018-03-27T21:00:38ZChristophe GeuzaineCompound Surface meshing fails when seam edge is presentPresently, when compound surfaces are used, we do not project the points on the model faces : on GFaceCompound.cc, we have commented
those 4 lines
// if(lt->gf && lt->gf->geomType() != GEntity::DiscreteSurface){
// SPoint2 pv = lt->...Presently, when compound surfaces are used, we do not project the points on the model faces : on GFaceCompound.cc, we have commented
those 4 lines
// if(lt->gf && lt->gf->geomType() != GEntity::DiscreteSurface){
// SPoint2 pv = lt->gfp1*(1.-U-V) + lt->gfp2*U + lt->gfp3*V;
// return lt->gf->point(pv.x(),pv.y());
// }Gmsh 4.0PA BeaufortPA Beauforthttps://gitlab.onelab.info/gmsh/gmsh/-/issues/50Copille error2020-08-16T23:30:36ZChristophe GeuzaineCopille errorerror:
[ 0%] Building CXX object CMakeFiles/gmsh.dir/Geo/GModelIO_Mesh.cpp.o
/home/buldi/work/FEM/gmsh/Geo/GModelIO_Mesh.cpp: In static member function ‘static GModel* GModel::createGModel(std::map<int, MVertex*, std::less<int>, std::...error:
[ 0%] Building CXX object CMakeFiles/gmsh.dir/Geo/GModelIO_Mesh.cpp.o
/home/buldi/work/FEM/gmsh/Geo/GModelIO_Mesh.cpp: In static member function ‘static GModel* GModel::createGModel(std::map<int, MVertex*, std::less<int>, std::allocator<std::pair<const int, MVertex*> > >&, std::vector<int, std::allocator<int> >&, std::vector<std::vector<int, std::allocator<int> >, std::allocator<std::vector<int, std::allocator<int> > > >&, std::vector<int, std::allocator<int> >&, std::vector<int, std::allocator<int> >&, std::vector<int, std::allocator<int> >&, std::vector<int, std::allocator<int> >&)’:
/home/buldi/work/FEM/gmsh/Geo/GModelIO_Mesh.cpp:2945: error: ‘INT_MIN’ was not declared in this scope
/home/buldi/work/FEM/gmsh/Geo/GModelIO_Mesh.cpp:2946: error: ‘INT_MAX’ was not declared in this scope
make[2]: *** [CMakeFiles/gmsh.dir/Geo/GModelIO_Mesh.cpp.o] Błąd 1
make[1]: *** [CMakeFiles/gmsh.dir/all] Błąd 2
make: *** [all] Błąd 2
patch in attachhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/51compilation error2017-03-23T16:21:04ZChristophe Geuzainecompilation error[ 0%] Building CXX object CMakeFiles/gmsh.dir/Plugin/Eigenvalues.cpp.o
/opt/local/bin/g++-mp-4.3 -DFLTK1 -DNO_PARALLEL_THREADS -DTETLIBRARY -mmacosx-version-min=10.5 -O3 -ftree-vectorize -I/Users/colignon/gmsh/Common -I/Users/colignon...[ 0%] Building CXX object CMakeFiles/gmsh.dir/Plugin/Eigenvalues.cpp.o
/opt/local/bin/g++-mp-4.3 -DFLTK1 -DNO_PARALLEL_THREADS -DTETLIBRARY -mmacosx-version-min=10.5 -O3 -ftree-vectorize -I/Users/colignon/gmsh/Common -I/Users/colignon/gmsh/Fltk -I/Users/colignon/gmsh/Geo -I/Users/colignon/gmsh/Graphics -I/Users/colignon/gmsh/Mesh -I/Users/colignon/gmsh/Solver -I/Users/colignon/gmsh/Numeric -I/Users/colignon/gmsh/Parser -I/Users/colignon/gmsh/Plugin -I/Users/colignon/gmsh/Post -I/Users/colignon/gmsh/Qt -I/Users/colignon/gmsh/contrib/ANN/include -I/Users/colignon/gmsh/contrib/Chaco/main -I/Users/colignon/gmsh/contrib/DiscreteIntegration -I/Users/colignon/gmsh/contrib/MathEx -I/Users/colignon/gmsh/contrib/Metis -I/Users/colignon/gmsh/contrib/NativeFileChooser -I/Users/colignon/gmsh/contrib/Netgen -I/Users/colignon/gmsh/contrib/Netgen/libsrc/include -I/Users/colignon/gmsh/contrib/Netgen/libsrc/interface -I/Users/colignon/gmsh/contrib/Tetgen -I/Users/colignon/gmsh/contrib/Fl_Tree -I/Users/colignon/gmsh/contrib/gmm -I/Users/colignon/gmsh/contrib/kbipack -I/opt/local/include -I/opt/opencascade:/opt/local-geuz -I/opt/opencascade:/opt/local-geuz/include -o CMakeFiles/gmsh.dir/Plugin/Eigenvalues.cpp.o -c /Users/colignon/gmsh/Plugin/Eigenvalues.cpp
/Users/colignon/gmsh/Solver/multiscaleLaplace.cpp: In constructor 'multiscaleLaplace::multiscaleLaplace(std::vector<MElement*, std::allocator<MElement*> >&, std::vector<MVertex*, std::allocator<MVertex*> >&, std::vector<double, std::allocator<double> >&)':
/Users/colignon/gmsh/Solver/multiscaleLaplace.cpp:334: error: 'linearSystemGmm' was not declared in this scope
/Users/colignon/gmsh/Solver/multiscaleLaplace.cpp:334: error: expected primary-expression before 'double'
/Users/colignon/gmsh/Solver/multiscaleLaplace.cpp:334: error: expected `;' before 'double'
/Users/colignon/gmsh/Solver/multiscaleLaplace.cpp:335: error: '_lsysb' was not declared in this scope
/opt/local/bin/cmake -E cmake_progress_report /Users/colignon/gmsh/CMakeFiles 4https://gitlab.onelab.info/gmsh/gmsh/-/issues/52Copille error2017-03-23T16:21:05ZChristophe GeuzaineCopille error/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:12:29: error: linearSystemGmm.h: Nie ma takiego pliku ani katalogu
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp: In constructor ‘multiscaleLaplace::multiscaleLaplace(std::v.../home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:12:29: error: linearSystemGmm.h: Nie ma takiego pliku ani katalogu
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp: In constructor ‘multiscaleLaplace::multiscaleLaplace(std::vector<MElement*, std::allocator<MElement*> >&, std::vector<MVertex*, std::allocator<MVertex*> >&, std::vector<double, std::allocator<double> >&)’:
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:335: error: ‘linearSystemGmm’ was not declared in this scope
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:335: error: expected primary-expression before ‘double’
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:335: error: expected `;' before ‘double’
/home/buldi/work/FEM/gmsh/Solver/multiscaleLaplace.cpp:336: error: ‘_lsysb’ was not declared in this scope
make[2]: *** [CMakeFiles/gmsh.dir/Solver/multiscaleLaplace.cpp.o] Błąd 1
make[1]: *** [CMakeFiles/gmsh.dir/all] Błąd 2
make: *** [all] Błąd 2https://gitlab.onelab.info/gmsh/gmsh/-/issues/53make install "worning"2017-03-23T16:21:05ZChristophe Geuzainemake install "worning"before:
gmsh-git (master)]$ sudo make install
[100%] Built target gmsh
Install the project...
-- Install configuration: "RelWithDebInfo"
-- Installing: /usr/bin/gmsh
-- Up-to-date: /usr/include/gmsh/GmshConfig.h
-- Up-to-date: /usr/inclu...before:
gmsh-git (master)]$ sudo make install
[100%] Built target gmsh
Install the project...
-- Install configuration: "RelWithDebInfo"
-- Installing: /usr/bin/gmsh
-- Up-to-date: /usr/include/gmsh/GmshConfig.h
-- Up-to-date: /usr/include/gmsh/GmshVersion.h
-- Up-to-date: /usr/include/gmsh/Gmsh.h
....
-- Up-to-date: /usr/share/doc/gmsh/README.txt
-- Up-to-date: /usr/share/doc/gmsh/LICENSE.txt
-- Up-to-date: /usr/share/doc/gmsh/CREDITS.txt
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view4.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t6.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/bgmesh.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t10.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view3.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t9.geo
...
-- Up-to-date: /usr/share/doc/gmsh/demos/filter.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/fields.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/hex.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/sphere-surf.stl
-- Up-to-date: /usr/share/doc/gmsh/demos/multislice.script
-- Up-to-date: /usr/share/doc/gmsh/demos/machine.i1
-- Up-to-date: /usr/share/man/man1/gmsh.1
--->> patch
after:
(master)]$ sudo make install
[100%] Built target gmsh
Install the project...
-- Install configuration: "RelWithDebInfo"
-- Up-to-date: /usr/bin/gmsh
-- Up-to-date: /usr/share/doc/gmsh/README.txt
-- Up-to-date: /usr/share/doc/gmsh/LICENSE.txt
-- Up-to-date: /usr/share/doc/gmsh/CREDITS.txt
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view4.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t6.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/bgmesh.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t10.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view3.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t9.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view1.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t4.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t8.par
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t7.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t2.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view5.msh
-- Up-to-date: /usr/share/doc/gmsh/tutorial/view2.pos
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t5.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t8.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t3.geo
-- Up-to-date: /usr/share/doc/gmsh/tutorial/t1.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.i5
-- Up-to-date: /usr/share/doc/gmsh/demos/sphere.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/cube.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/lowmem-anim.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/splines.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.i3
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.i4
-- Up-to-date: /usr/share/doc/gmsh/demos/isosurf.script
-- Up-to-date: /usr/share/doc/gmsh/demos/title.script
-- Up-to-date: /usr/share/doc/gmsh/demos/antenna.i1
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.i1
-- Up-to-date: /usr/share/doc/gmsh/demos/sphere-discrete.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/component8_in_a_box.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/machine.i2
-- Up-to-date: /usr/share/doc/gmsh/demos/encode.script
-- Up-to-date: /usr/share/doc/gmsh/demos/piece-extr-rec.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/primitives.pos
-- Up-to-date: /usr/share/doc/gmsh/demos/antenna.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/piece.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/rotate.script
-- Up-to-date: /usr/share/doc/gmsh/demos/pripyrtet.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/piece-extr.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/anim.script
-- Up-to-date: /usr/share/doc/gmsh/demos/component8.step
-- Up-to-date: /usr/share/doc/gmsh/demos/transfinite.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/plot2d.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/cone.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/machine.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/tower.i2
-- Up-to-date: /usr/share/doc/gmsh/demos/filter.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/fields.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/hex.geo
-- Up-to-date: /usr/share/doc/gmsh/demos/sphere-surf.stl
-- Up-to-date: /usr/share/doc/gmsh/demos/multislice.script
-- Up-to-date: /usr/share/doc/gmsh/demos/machine.i1
-- Up-to-date: /usr/share/man/man1/gmsh.1
is'n ... include ... in installhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/54Lost all lines, surfaces, and volumes after saving MSH file.2017-03-23T16:21:06ZChristophe GeuzaineLost all lines, surfaces, and volumes after saving MSH file.I'd been trying gmsh 2.3 for a few hours, wanting to create a mesh of a 3D scene for import into Elmer.
After a lot of guess-and-check (because the Elmer documentation is uselessly cryptic) I did get Elmer to load the obstacles of the s...I'd been trying gmsh 2.3 for a few hours, wanting to create a mesh of a 3D scene for import into Elmer.
After a lot of guess-and-check (because the Elmer documentation is uselessly cryptic) I did get Elmer to load the obstacles of the scene but there were no boundaries planes and no mesh volume.
I had saved and restarted Gmsh several times during this process. Elmer seems to crash if the msh file has the "Save all entities" option ticked, so it is necessary to save all entities in one file, then save only physical groups to another file. I was also occasionally saving the geometry to a separate .geo file.
The next time I loaded my .msh file, only the Points were there and all the lines and surfacesan had disappeared.
It was lucky I had a geo file as a backup, but still this should not happen.https://gitlab.onelab.info/gmsh/gmsh/-/issues/55TODO IN DG2017-03-23T16:21:07ZChristophe GeuzaineTODO IN DGTODO list & Problèmes que l'on devrait aborder lundi prochain :
-) L'utilisation directe de PView avec des maps pour sauver les champs foire: j'ai implémenté un truc de remplacement (CG)
-) Again, pour le format de post pro, on ne peu...TODO list & Problèmes que l'on devrait aborder lundi prochain :
-) L'utilisation directe de PView avec des maps pour sauver les champs foire: j'ai implémenté un truc de remplacement (CG)
-) Again, pour le format de post pro, on ne peut sauver dans le nouveau format que les éléments isoparamétriques. (CG)
-) Implicit -- linearAlgebra -- dofManager (CG + JON + JFR)
-) faire des tests de perfs (THIS AFTERNOON + EMI + VL)
-) Maxwell (Explicit propagation & implicit highly non linear superconducting stuff) (AK)
-) 3D closures are incomplete (EM)
-) Multigrid (SAM, VL)
-) hybrid meshes -- multiple groups (JF)
-) parallel stuff (KOEN, JF, CG, JON)
-) IP Dirichlet Boundary Condition (JON & JF & SAM)
-) SIP ?? later ...
-) limiter (BS & EMI)
-) multirate RKhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/56Add command in parser to reset options to default values2017-03-23T16:21:07ZChristophe GeuzaineAdd command in parser to reset options to default valuesIt would be useful to have a command to reset options to their default valuesIt would be useful to have a command to reset options to their default valueshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/57Streamlines plugin crashes2017-03-23T16:21:07ZChristophe GeuzaineStreamlines plugin crashesI am using gmsh V2.4.1. For my lecture I want to show a very simple example: streamlines around an airfoil based on laplace equation.
I am using 2nd order tetrahedron elements (10 nodes, etype 11). I am able to visualize the flux vector ...I am using gmsh V2.4.1. For my lecture I want to show a very simple example: streamlines around an airfoil based on laplace equation.
I am using 2nd order tetrahedron elements (10 nodes, etype 11). I am able to visualize the flux vector but the streamlines plugin crashes. Is there any known problem with 2nd order tetrahedrons?https://gitlab.onelab.info/gmsh/gmsh/-/issues/58Streamlines plugin crashes with second order elements2017-03-23T16:21:08ZChristophe GeuzaineStreamlines plugin crashes with second order elementsI am using gmsh V2.4.1. For my lecture I want to show a very simple example: streamlines around an airfoil based on laplace equation.
I am using 2nd order tetrahedron elements (10 nodes, etype 11). I am able to visualize the flux vector ...I am using gmsh V2.4.1. For my lecture I want to show a very simple example: streamlines around an airfoil based on laplace equation.
I am using 2nd order tetrahedron elements (10 nodes, etype 11). I am able to visualize the flux vector but the streamlines plugin crashes. Is there any known problem with 2nd order tetrahedrons?
The file is larger than 256kb, but I can send you an email if necessary.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/59There's no Min or Max function in the parser2020-01-07T17:13:18ZChristophe GeuzaineThere's no Min or Max function in the parserWe should add Min/Max functions in the parserWe should add Min/Max functions in the parserhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/60tutorial improvements2017-03-23T16:21:09ZChristophe Geuzainetutorial improvementsfrom Takuya OSHIMA, oshima@eng.niigata-u.ac.jp, on the mailing-list:
Hi,
We are doing some detailed review of the tutorial files (t1.geo -
t9.geo that come with Gmsh 2.4.2) as a process of creating teaching
materials for our FE code th...from Takuya OSHIMA, oshima@eng.niigata-u.ac.jp, on the mailing-list:
Hi,
We are doing some detailed review of the tutorial files (t1.geo -
t9.geo that come with Gmsh 2.4.2) as a process of creating teaching
materials for our FE code that uses Gmsh as preprocessing front
end. In the process, at the stage of the review until t3.geo, we came
to have the following comments (we hope we are not nitpicking). What
do you think?
Thanks,
Takuya
[t1.geo]
Line 62 "specifying their orientation": it might be better if we have
an explanation that this applies only for lines and surfaces, and
have an example in one of the following physical entity definitions
so that one can see how to specify the orientation.
[t2.geo]
Overall, one may hardly be able to follow the tutorial since there is
little explanation about which entities Points 8, 12, 16, 7, Lines
102-105, etc. are referring to (and which exact process generated
the entities). If the entity numbers are to be obtained by saving
unrolled geometry as explained at the bottom of t2.geo, the
explanation might be better to come at the top of the file and to be
clearly stated as such.
Lines 32-33 "a list": it might be better if it is clearly stated that
the list is referring to tmp[] (obvious for programmers, but not for
non-programmers).
[t3.geo]
Line 40 "news": the special meaning of the variable may be worth
being mentioned.
Lines 76-77 "`Tools->Options->Save as defaults' button": there does
not seem to be such a button on the GUI?
Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
_______________________________________________
gmsh mailing list
gmsh@geuz.org
http://www.geuz.org/mailman/listinfo/gmshhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/61Cannot extrude rotation about 2Pi2017-03-23T16:21:10ZChristophe GeuzaineCannot extrude rotation about 2PiHello,
having definded a plain surface, I want to extrude it about 2Pi. The command doesn't force an error, so its listed in the Message Console, but the lines, surfaces and volumes that shall be created bz the extrusion are not display...Hello,
having definded a plain surface, I want to extrude it about 2Pi. The command doesn't force an error, so its listed in the Message Console, but the lines, surfaces and volumes that shall be created bz the extrusion are not display on the GUI. Extrusion rotation of the same plain surface about something tiny smaller than 2Pi works just fine, but is unfortunately not sufficient for my use.
Thanks,
Richardhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/62new file Cell.cpp refered by CMakeLists.txt is missing2017-03-23T16:21:10ZChristophe Geuzainenew file Cell.cpp refered by CMakeLists.txt is missingRun 'ccmake /Users/colignon/gmsh' to fine-tune the configuration.
-- Configuring done
CMake Error in CMakeLists.txt:
Cannot find source file "Cell.cpp". Tried extensions .c .C .c++ .cc .cpp
.cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx ...Run 'ccmake /Users/colignon/gmsh' to fine-tune the configuration.
-- Configuring done
CMake Error in CMakeLists.txt:
Cannot find source file "Cell.cpp". Tried extensions .c .C .c++ .cc .cpp
.cxx .m .M .mm .h .hh .h++ .hm .hpp .hxx .in .txxhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/63add ability to pick/select mesh vertices in GUI2023-07-27T12:34:49ZChristophe Geuzaineadd ability to pick/select mesh vertices in GUIWe should draw mesh vertices using vertex arrays and add the ability to select them.
This requires some changes
* in the VertexArray class to store vertex pointers if necessary
* in drawMesh to not use immediate drawing mode for ve...We should draw mesh vertices using vertex arrays and add the ability to select them.
This requires some changes
* in the VertexArray class to store vertex pointers if necessary
* in drawMesh to not use immediate drawing mode for verticeshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/64create MPEGS directly from within Gmsh2017-03-23T16:21:11ZChristophe Geuzainecreate MPEGS directly from within GmshIt would be nice to be able to create movies (e.g. mpeg) directly from within Gmsh, without using a script (or at least without using an external binary like mpeg_encode or mencoder): it's really a pain to create even simple movies on Wi...It would be nice to be able to create movies (e.g. mpeg) directly from within Gmsh, without using a script (or at least without using an external binary like mpeg_encode or mencoder): it's really a pain to create even simple movies on Windows.
We could e.g. just include the sources from mpeg_encode in contrib and provide a simple "Save As->MPEG" export option.https://gitlab.onelab.info/gmsh/gmsh/-/issues/65improve plugin GUI2017-03-23T16:21:11ZChristophe Geuzaineimprove plugin GUIGmsh Plugins are very powerful but the inerface is quite hard to use. Here are some suggestions to improve it:
* Several plugins have non-intuitive names (Evaluate, Extract, CutMap):
Evaluate -> Modify ou EvaluateInPlace
Extract -> Ev...Gmsh Plugins are very powerful but the inerface is quite hard to use. Here are some suggestions to improve it:
* Several plugins have non-intuitive names (Evaluate, Extract, CutMap):
Evaluate -> Modify ou EvaluateInPlace
Extract -> Evaluate
CutMap -> CutIso or CutLevelSet
CutParametric -> CutParametricCurve
* CutGrid should work for 3D grids (specify 4 points and U,V,W)
* Divergence, Gradient and Curl should be combined into a single Derivate plugin (like Integrate)
* There should be a short (one line) help in the main plugin window (so that you don't have to go into the Help tab just to understand what the plugin does)
* There could be plugin categories (at least "basic" and "advanced"?)https://gitlab.onelab.info/gmsh/gmsh/-/issues/66Visibility table lists names from wrong categories2017-03-23T16:21:12ZChristophe GeuzaineVisibility table lists names from wrong categoriesWhen all IDs for points, lines, surfaces etc. are generated using newp, newl, news etc, then Tools->Visibility may choose wrong category in its "Name" column. Attached are screenshots and geometry file creating this problem. The "OATPT_0...When all IDs for points, lines, surfaces etc. are generated using newp, newl, news etc, then Tools->Visibility may choose wrong category in its "Name" column. Attached are screenshots and geometry file creating this problem. The "OATPT_003" was assigned to a point (hence "PT" inside the label), but in table it is shown for both point #128 and surface #128.https://gitlab.onelab.info/gmsh/gmsh/-/issues/67Cannot use post-processing view in .msh format for background mesh2017-03-23T16:21:13ZChristophe GeuzaineCannot use post-processing view in .msh format for background meshWe cannot use a post-processing file based on a model/mesh as a background mesh for the same model/mesh : basically, as one remeshes, the original mesh is destroyed, which also invalidates the post-processing view...We cannot use a post-processing file based on a model/mesh as a background mesh for the same model/mesh : basically, as one remeshes, the original mesh is destroyed, which also invalidates the post-processing view...Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/68add way to load post-processing files on the fly when animating2017-03-23T16:21:14ZChristophe Geuzaineadd way to load post-processing files on the fly when animatingWhen data becomes available while we are visualizing a multistep solution, we should be able to load it automatically.
The best solution is probably to have some sort of command in a script that tells which file names should be watched.When data becomes available while we are visualizing a multistep solution, we should be able to load it automatically.
The best solution is probably to have some sort of command in a script that tells which file names should be watched.https://gitlab.onelab.info/gmsh/gmsh/-/issues/69improve GUI for mesh visibility2017-03-23T16:21:14ZChristophe Geuzaineimprove GUI for mesh visibilityWe shoudl have a big button in the main window to hide/show the mesh (without going into the option panel)We shoudl have a big button in the main window to hide/show the mesh (without going into the option panel)https://gitlab.onelab.info/gmsh/gmsh/-/issues/70improve GUI for changing mesh size2017-03-23T16:21:14ZChristophe Geuzaineimprove GUI for changing mesh sizeWe should have a big slider in the main window to quickly change the mesh element size (-clscale), without going into the option panel.We should have a big slider in the main window to quickly change the mesh element size (-clscale), without going into the option panel.https://gitlab.onelab.info/gmsh/gmsh/-/issues/71Carriage return2017-03-23T16:21:15ZChristophe GeuzaineCarriage returnAt the end of a geo file it seems to be compulsory to add a carriage return!!!
You get an error if you forget.
That should be corrected... ;-)At the end of a geo file it seems to be compulsory to add a carriage return!!!
You get an error if you forget.
That should be corrected... ;-)https://gitlab.onelab.info/gmsh/gmsh/-/issues/72bad orientation for the export STL2017-03-23T16:21:15ZChristophe Geuzainebad orientation for the export STLThe orientation of a surface mesh exported in the STL format is not correctThe orientation of a surface mesh exported in the STL format is not correcthttps://gitlab.onelab.info/gmsh/gmsh/-/issues/73Major memory leak when using extruded rotation2017-03-23T16:21:16ZChristophe GeuzaineMajor memory leak when using extruded rotationA major memory leak has been detected with valgrind when meshing an extruded rotation in a .geo file. This is very critical for us, especially on Windows platform.
Valgrind log on the attached geo file gives at the end:
==29023== 435,...A major memory leak has been detected with valgrind when meshing an extruded rotation in a .geo file. This is very critical for us, especially on Windows platform.
Valgrind log on the attached geo file gives at the end:
==29023== 435,648 bytes in 4,538 blocks are definitely lost in loss record 835 of 837
==29023== at 0x4C22515: operator new(unsigned long) (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==29023== by 0x5EE452: Create_Vertex(int, double, double, double, double, double) (Geo.cpp:113)
==29023== by 0x5EE54E: DuplicateVertex(Vertex*) (Geo.cpp:882)
==29023== by 0x5F4AD7: DuplicateCurve(Curve*, bool) (Geo.cpp:930)
==29023== by 0x5F5E08: Extrude_ProtudeCurve(int, int, double, double, double, double, double, double, double, double, double, double, Surface**, int, ExtrudeParams*) (Geo.cpp:2167)
==29023== by 0x5F7075: ExtrudeShapes(int, List_T*, double, double, double, double, double, double, double, double, double, double, ExtrudeParams*, List_T*) (Geo.cpp:2374)
==29023== by 0x74438F: gmsh_yyparse() (Gmsh.y:2567)
==29023== by 0x52E1A4: ParseFile(std::string, bool, bool) (OpenFile.cpp:175)
==29023== by 0x5B7E3E: GModel::readGEO(std::string const&) (GModelIO_Geo.cpp:40)
==29023== by 0x530250: MergeFile(std::string, bool) (OpenFile.cpp:364)
==29023== by 0x530792: OpenProject(std::string) (OpenFile.cpp:440)
==29023== by 0x4F1D0A: main (Main.cpp:76)
==29023==
==29023==
==29023== 2,080,984 (1,403,440 direct, 677,544 indirect) bytes in 3,310 blocks are definitely lost in loss record 837 of 837
==29023== at 0x4C22515: operator new(unsigned long) (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==29023== by 0x5F3AF2: Create_Curve(int, int, int, List_T*, List_T*, int, int, double, double) (Geo.cpp:480)
==29023== by 0x5F3FAD: CreateReversedCurve(Curve*) (Geo.cpp:1352)
==29023== by 0x5F4AFB: DuplicateCurve(Curve*, bool) (Geo.cpp:932)
==29023== by 0x5F5E08: Extrude_ProtudeCurve(int, int, double, double, double, double, double, double, double, double, double, double, Surface**, int, ExtrudeParams*) (Geo.cpp:2167)
==29023== by 0x5F7075: ExtrudeShapes(int, List_T*, double, double, double, double, double, double, double, double, double, double, ExtrudeParams*, List_T*) (Geo.cpp:2374)
==29023== by 0x74438F: gmsh_yyparse() (Gmsh.y:2567)
==29023== by 0x52E1A4: ParseFile(std::string, bool, bool) (OpenFile.cpp:175)
==29023== by 0x5B7E3E: GModel::readGEO(std::string const&) (GModelIO_Geo.cpp:40)
==29023== by 0x530250: MergeFile(std::string, bool) (OpenFile.cpp:364)
==29023== by 0x530792: OpenProject(std::string) (OpenFile.cpp:440)
==29023== by 0x4F1D0A: main (Main.cpp:76)
==29023==
==29023== LEAK SUMMARY:
==29023== definitely lost: 1,878,624 bytes in 8,253 blocks.
==29023== indirectly lost: 769,544 bytes in 15,105 blocks.
==29023== possibly lost: 290,257 bytes in 117 blocks.
==29023== still reachable: 3,033,839 bytes in 28,604 blocks.
==29023== suppressed: 0 bytes in 0 blocks.https://gitlab.onelab.info/gmsh/gmsh/-/issues/74Parse error for comment containing If keyword2017-03-23T16:21:17ZChristophe GeuzaineParse error for comment containing If keywordHi,
I'm using gmsh 2.4.2 mac binary. I found something strange. If you open the following simple geo file in gmsh, the Message Console reports "Error : Unexpected end of file". If you remove the comment that begins with "If" the pr...Hi,
I'm using gmsh 2.4.2 mac binary. I found something strange. If you open the following simple geo file in gmsh, the Message Console reports "Error : Unexpected end of file". If you remove the comment that begins with "If" the problem goes away.
For i In {0:9}
If ( i != 0 )
// If x
Printf("i=%g", i);
EndIf
EndForChristophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/75Tensorial fields visualization enhancements2018-08-21T10:17:59ZChristophe GeuzaineTensorial fields visualization enhancementsMay I suggest two enhancements for better tensorial fields visualization:
- In Node data or Elmt data section of .msh2 file format, the second int tag corresponds to the number of values defined by node/element. For the visualization, ...May I suggest two enhancements for better tensorial fields visualization:
- In Node data or Elmt data section of .msh2 file format, the second int tag corresponds to the number of values defined by node/element. For the visualization, it automatically recognizes the values 1 (scalar), 3 (norm of vector) and 9 (von Mises equivalent value). It would be useful to recognize 6 as well to reduce amount of data in result file (symmetric tensor as for strain/stress under SPH).
For this, a convention has to be adopted for:
- The way values are listed (v0-v4-v8-v1-v5-v2 or v0-v4-v8-v5-v2-v1 or v0-v1-v2-v4-v5-v8)
- Multiplicative factor for shear values - classically, a '2' is used for strain, and '1' for stress; other approach is to use sqrt(2) for all fields; maybe for coherence with the other fields type in gmsh, better to always keep '1'.
- In the 'Extract' plugin, if dealing with a tensorial field and von-Mises stress is illustrated, it would be logical to have the corresponding von Mises formula instead of sqrt(v0*v0 + v1*v1 + v2*v2), which is valid for vectors.https://gitlab.onelab.info/gmsh/gmsh/-/issues/76Not compiling on msvc2017-03-23T16:21:18ZChristophe GeuzaineNot compiling on msvcHello,
The following functions do not compile on msvc :
GModelFactory :
sphere(..)
inline GEntity* extrude_ (GModel *gm, GEntity* e,
inline GEntity* revolve_ (GModel *gm, GEntity* e,
They all should return a value.
extrude and revo...Hello,
The following functions do not compile on msvc :
GModelFactory :
sphere(..)
inline GEntity* extrude_ (GModel *gm, GEntity* e,
inline GEntity* revolve_ (GModel *gm, GEntity* e,
They all should return a value.
extrude and revolve should rreturn the result of extrude(..) and revolve(..) but i don't know for *OCCFactory::sphere
Laurenthttps://gitlab.onelab.info/gmsh/gmsh/-/issues/77Nastran bulk format - handle '.dat' extension2017-03-23T16:21:18ZChristophe GeuzaineNastran bulk format - handle '.dat' extensionExport in bulk format from Catia gives '.dat' files extension. Gmsh can read such format but expects '.bdf' or '.nas'. So, the solution is to rename the file...
I don't know the rule about the correct file extension for this kind of f...Export in bulk format from Catia gives '.dat' files extension. Gmsh can read such format but expects '.bdf' or '.nas'. So, the solution is to rename the file...
I don't know the rule about the correct file extension for this kind of format but I think that if Catia exports '.dat', it's a sufficiently good reason to handle such extension within Gmsh.
Thanks,
Olivier Pierard - Cenaerohttps://gitlab.onelab.info/gmsh/gmsh/-/issues/78deal with relative paths with -watch option2017-08-05T11:31:52ZChristophe Geuzainedeal with relative paths with -watch option-watch works well with absolute paths -- check what's going on with reltive paths-watch works well with absolute paths -- check what's going on with reltive pathshttps://gitlab.onelab.info/gmsh/gmsh/-/issues/79Duplicate elements when using overlapping physical group2017-03-23T16:21:19ZChristophe GeuzaineDuplicate elements when using overlapping physical groupWhen 2 physical regions overlaps the same gentity, this gentity owns a number of elements that is equal to the number of physical regions * the real number of elements (after a mesh + save mesh and read .msh).
This cause to have multiple...When 2 physical regions overlaps the same gentity, this gentity owns a number of elements that is equal to the number of physical regions * the real number of elements (after a mesh + save mesh and read .msh).
This cause to have multiple time the same elements when importing elements using this :
unsigned int nbElem=entity->getNumMeshElements();
nbElem is not correct :https://gitlab.onelab.info/gmsh/gmsh/-/issues/80DefaultOptions.h NameCommand42017-03-23T16:21:19ZChristophe GeuzaineDefaultOptions.h NameCommand4At line 363 in DefaultOptions.h
https://geuz.org/svn/gmsh/trunk/Common/DefaultOptions.h
NameCommand4 overwrites NameCommand1:
old: { F|O, "NameCommand4", opt_solver_name_command1, "%s",
fix: { F|O, "NameCommand4", opt_solver_name_command...At line 363 in DefaultOptions.h
https://geuz.org/svn/gmsh/trunk/Common/DefaultOptions.h
NameCommand4 overwrites NameCommand1:
old: { F|O, "NameCommand4", opt_solver_name_command1, "%s",
fix: { F|O, "NameCommand4", opt_solver_name_command4, "%s",
Nigel Nunn
nnnunnn@gmail.comhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/81dll symbols2017-03-23T16:21:20ZChristophe Geuzainedll symbolsWhen trying to create a gmsh.dll using shared project in Visual Studio, no library symbols are exported.
see : http://www.cmake.org/Wiki/BuildingWinDLL for details.
NicolasWhen trying to create a gmsh.dll using shared project in Visual Studio, no library symbols are exported.
see : http://www.cmake.org/Wiki/BuildingWinDLL for details.
NicolasChristophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/82comparison (==) not assignment (=); two seperate bugs2017-03-23T16:21:21ZChristophe Geuzainecomparison (==) not assignment (=); two seperate bugsMZone.cpp zoneData() Line 221:
old: eVecIt->index == cElem++;
new: eVecIt->index = cElem++;
Numeric.cpp computeDistanceRatio() Line 999:
old: a == 0.0;
new: a = 0.0;MZone.cpp zoneData() Line 221:
old: eVecIt->index == cElem++;
new: eVecIt->index = cElem++;
Numeric.cpp computeDistanceRatio() Line 999:
old: a == 0.0;
new: a = 0.0;https://gitlab.onelab.info/gmsh/gmsh/-/issues/83Face2 -> Face82017-03-23T16:21:21ZChristophe GeuzaineFace2 -> Face8Geo/CustomContainer.h (line 311)
old: Face2 f8;
new: Face8 f8;
offset8 = f8.get_offset();Geo/CustomContainer.h (line 311)
old: Face2 f8;
new: Face8 f8;
offset8 = f8.get_offset();https://gitlab.onelab.info/gmsh/gmsh/-/issues/84index out of range2017-03-23T16:21:22ZChristophe Geuzaineindex out of rangeGeo/GModelIO_CGNS.cpp (line 1071)
old: std::sort<int*, ZoneBoVecSort>(&iZBV[0], &iZBV[numBoVert],
new: std::sort<int*, ZoneBoVecSort>(&iZBV[0], &iZBV[numBoVert-1],Geo/GModelIO_CGNS.cpp (line 1071)
old: std::sort<int*, ZoneBoVecSort>(&iZBV[0], &iZBV[numBoVert],
new: std::sort<int*, ZoneBoVecSort>(&iZBV[0], &iZBV[numBoVert-1],https://gitlab.onelab.info/gmsh/gmsh/-/issues/85Add MZoneBoundary<N>::preInit(), postDestroy() ?2017-03-23T16:21:22ZChristophe GeuzaineAdd MZoneBoundary<N>::preInit(), postDestroy() ?Geo/GModelIO_CGNS.cpp (from line 415)
switch(meshDim) {
case 2:
MZone<2>::preInit();
MZoneBoundary<2>::preInit(); // Add?:
write_CGNS_zones<2>(*this, zoneDefinition, ...);
MZone<2>::postDestroy();
MZoneBo...Geo/GModelIO_CGNS.cpp (from line 415)
switch(meshDim) {
case 2:
MZone<2>::preInit();
MZoneBoundary<2>::preInit(); // Add?:
write_CGNS_zones<2>(*this, zoneDefinition, ...);
MZone<2>::postDestroy();
MZoneBoundary<2>::postDestroy(); // Add?:
break;
case 3:
MZone<3>::preInit();
MZoneBoundary<3>::preInit(); // Add?:
write_CGNS_zones<3>(*this, zoneDefinition, ...);
MZone<3>::postDestroy();
MZoneBoundary<3>::postDestroy(); // Add?:
break;
}https://gitlab.onelab.info/gmsh/gmsh/-/issues/86writeCGNS now running; need to check what it writes!2017-03-23T16:21:23ZChristophe GeuzainewriteCGNS now running; need to check what it writes!writeCGNS now runs (for a variety of output options), but still need to check what is actually being written.
With regard to the show-stopper in interiorBoundaryVertices(...) in file Geo/MZoneBoundary.cpp, in the lines (from 814) follow...writeCGNS now runs (for a variety of output options), but still need to check what is actually being written.
With regard to the show-stopper in interiorBoundaryVertices(...) in file Geo/MZoneBoundary.cpp, in the lines (from 814) following the comment
//--A new vertex was inserted
the code was attempting to push_back a CCon::FaceVector<FaceDataB> object into the member "faces",
CCon::FaceVector<FaceDataB> faces
By using FaceAllocator<T> with face2Pool, the custom memory management appears to side-step the calling of constructors.
My guess is that the std::vector members (_v, _si) in class FaceDataB::face (e.g. MFace) are "incomplete". Behind the scenes, there is the usual auto-alloc/dealloc triggered by adding into a std::map using operator[], and the problem bit when deallocating a std::vector that had not been properly "constructed".
First attempt at a simple fix:
By replacing the FaceT member with FaceT* we fix this issue of auto-deleting "un-constructed" containers. The simple data type(pointer) member is allocated in the ctor, then we create and store its FaceT object once the FaceDataB object is safely in the container. See comments in the code.
Note: we must now make sure to delete these pointers.
See adjusted version of MZoneBoundary::clear();
Three files are attached:
1. Geo/MZoneBoundary.h
2. Geo/MZoneBoundary.cpp
3. Geo/GModelIO_CGNS.cpp
Also, here is a fix for the partial update that slipped into svn yesterday: Geo/GModelIO_CGNS.cpp (from line 415)
switch(meshDim) {
case 2:
MZone<2>::preInit();
MZoneBoundary<2>::preInit();
write_CGNS_zones<2>(*this, zoneDefinition, numZone, options,
scalingFactor, vectorDim, groups[face],
cgIndexFile, cgIndexBase);
MZone<2>::postDestroy();
MZoneBoundary<2>::postDestroy();
break;
case 3:
MZone<3>::preInit();
MZoneBoundary<3>::preInit();
write_CGNS_zones<3>(*this, zoneDefinition, numZone, options,
scalingFactor, vectorDim, groups[region],
cgIndexFile, cgIndexBase);
MZone<3>::postDestroy();
MZoneBoundary<3>::postDestroy();
break;
}
Nigelhttps://gitlab.onelab.info/gmsh/gmsh/-/issues/87Invalid scripts makes Gmsh crash2017-03-23T16:21:23ZChristophe GeuzaineInvalid scripts makes Gmsh crashWhen working on a geo script, we often make bugs. Most of them are repported in the Message Console. But sometimes, the application crash without any message, wich is very frustrating. If this script is Temp/untitled.geo, Gmsh will not l...When working on a geo script, we often make bugs. Most of them are repported in the Message Console. But sometimes, the application crash without any message, wich is very frustrating. If this script is Temp/untitled.geo, Gmsh will not launch anymore.
I reproduced this behaviour in the attached script.
The bug is, I forgot a semicolon on line 5.
When loading .geo file, GModel::importGEOInternals() tries to compute Surface 6, but crash in fullMatrix<double>::svd() on line
F77NAME(dgesvd)("O", "A", &M, &N, _data, &LDA, S._data, _data, &LDA,
VT._data, &LDVT, WORK._data, &LWORK, &info);
This surface is incoherent and shouldn't be computed.https://gitlab.onelab.info/gmsh/gmsh/-/issues/88gmsh failes to construct 3D mesh from initial 2D surface mesh2017-03-23T16:21:24ZChristophe Geuzainegmsh failes to construct 3D mesh from initial 2D surface meshgmsh failes to construct 3D mesh from initial 2D surface mesh (see examples attached)
*Case 1:*
Run 'gmsh tetr-small.geo -3'
Everything works as expected - msh file is generated
*Case 2:*
Run 'gmsh tetr-medium.geo -3'
gmsh failes:
gms...gmsh failes to construct 3D mesh from initial 2D surface mesh (see examples attached)
*Case 1:*
Run 'gmsh tetr-small.geo -3'
Everything works as expected - msh file is generated
*Case 2:*
Run 'gmsh tetr-medium.geo -3'
gmsh failes:
gmsh: /home/geuzaine/src/gmsh/contrib/Tetgen/tetgen.cxx:22434: void tetgenmesh::rearrangesubfaces(tetgenmesh::list*, tetgenmesh::list*, tetgenmesh::list*, int*): Assertion `dest(starttet) == workpt' failed.
*Case 3:*
Run 'gmsh tetr-big.geo -3'
gmsh hangs after 'Delaunizing segments'
*Info:*
OS: Linux (Fedora 11)
gmsh version: 2.4.2 (binary)https://gitlab.onelab.info/gmsh/gmsh/-/issues/89nodes outside element2017-03-23T16:21:25ZChristophe Geuzainenodes outside elementHello,
I'd like to report a possible bug.
In some tetrahedral elements of fifth order (56-nodes), some of nodes (exactly number 55 -the last one) is outside the element.
Best regards,
W.A.Hello,
I'd like to report a possible bug.
In some tetrahedral elements of fifth order (56-nodes), some of nodes (exactly number 55 -the last one) is outside the element.
Best regards,
W.A.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/90point seemingly not projected on extrusion surface during edge split2017-03-23T16:21:26ZChristophe Geuzainepoint seemingly not projected on extrusion surface during edge splitThis error appeared during the 3D mesh generation on an extruded geometry (both surfaces and volume extruded). I noticed this bug on svn version 7874 (and some versions earlier); I have added the geo file and a number of visualisations. ...This error appeared during the 3D mesh generation on an extruded geometry (both surfaces and volume extruded). I noticed this bug on svn version 7874 (and some versions earlier); I have added the geo file and a number of visualisations.
The node 115 (see images) seems interpolated between nodes 45 and 55; it looks as if the node 115 was created during the split of an edge between these nodes, yet not reprojected on the curved extruded surface.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/91Post processing rotation of vector field2017-03-23T16:21:27ZChristophe GeuzainePost processing rotation of vector fieldPost processing of a result vector field (e.g. from ELMER) has following problem:
rotation of nodes works fine, but the orientation of the result vectors do not rotatePost processing of a result vector field (e.g. from ELMER) has following problem:
rotation of nodes works fine, but the orientation of the result vectors do not rotatehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/92Problem if variable definition in the first line of an option file2017-03-23T16:21:27ZChristophe GeuzaineProblem if variable definition in the first line of an option fileHello,
I use GMSH for windows version 2.4.2. I use *.opt files to open files with options. In one of my files, I used to define a variable in the first line of the file:
```
MyView = 0;
If (MyView == 0)
General.RotationX = 10.0;
EndIf...Hello,
I use GMSH for windows version 2.4.2. I use *.opt files to open files with options. In one of my files, I used to define a variable in the first line of the file:
```
MyView = 0;
If (MyView == 0)
General.RotationX = 10.0;
EndIf
```
This would produce an error: variable "MyView" undefined. If I add a comment as a first line of the file, this works perfectly.
Thanks for the great quality of your program.
Sincerely,
Christophe H.https://gitlab.onelab.info/gmsh/gmsh/-/issues/93Gmsh crashes with 2D plots for 1D data2017-03-23T16:21:28ZChristophe GeuzaineGmsh crashes with 2D plots for 1D dataGmsh crashes when changing from 3D to 2D plots for 1D data
here is the backtrace
[orphu:02901] *** Process received signal ***
[orphu:02901] Signal: Segmentation fault (11)
[orphu:02901] Signal code: Address not mapped (1)
[orphu:029...Gmsh crashes when changing from 3D to 2D plots for 1D data
here is the backtrace
[orphu:02901] *** Process received signal ***
[orphu:02901] Signal: Segmentation fault (11)
[orphu:02901] Signal code: Address not mapped (1)
[orphu:02901] Failing at address: (nil)
[orphu:02901] [ 0] /lib/libpthread.so.0(+0xef60) [0x7f2d8b7b9f60]
[orphu:02901] [ 1] gmsh(_ZN15PViewDataGModel8getValueEiiiiiRd+0x7f) [0x791bff]
[orphu:02901] [ 2] gmsh() [0x8a1ceb]
[orphu:02901] [ 3] gmsh(_ZN11drawContext11drawGraph2dEv+0x4f4) [0x8a2b64]
[orphu:02901] [ 4] gmsh(_ZN11drawContext6draw2dEv+0xcc) [0x8870ec]
[orphu:02901] [ 5] gmsh(_ZN12openglWindow4drawEv+0x2b0) [0x81f490]
[orphu:02901] [ 6] /usr/lib/libfltk_gl.so.1.1(_ZN12Fl_Gl_Window5flushEv+0x7f) [0x7f2d956f7ccf]
[orphu:02901] [ 7] /usr/lib/libfltk.so.1.1(_ZN2Fl5flushEv+0xb3) [0x7f2d9526fc33]
[orphu:02901] [ 8] /usr/lib/libfltk.so.1.1(_ZN2Fl4waitEd+0x154) [0x7f2d9526fec4]
[orphu:02901] [ 9] /usr/lib/libfltk.so.1.1(_ZN2Fl5checkEv+0xd) [0x7f2d9526ff5d]
[orphu:02901] [10] gmsh() [0x849f06]
[orphu:02901] [11] /usr/lib/libfltk.so.1.1(_ZN8Fl_Menu_6pickedEPK12Fl_Menu_Item+0x9a) [0x7f2d952951ea]
[orphu:02901] [12] /usr/lib/libfltk.so.1.1(_ZN9Fl_Choice6handleEi+0x106) [0x7f2d95277856]
[orphu:02901] [13] /usr/lib/libfltk.so.1.1(_ZN8Fl_Group6handleEi+0x12b) [0x7f2d95283cab]
[orphu:02901] *** End of error message ***https://gitlab.onelab.info/gmsh/gmsh/-/issues/94Problem with multiple physicals for one elementary region -- .msh format logic2018-07-26T10:57:23ZChristophe GeuzaineProblem with multiple physicals for one elementary region -- .msh format logicWhen several physical entities are defined on the same elementary entity, the .msh format saves several elements (with different tags)--one for each physical region.
This is not bad in itself, but when gmsh reads the .msh file again, it...When several physical entities are defined on the same elementary entity, the .msh format saves several elements (with different tags)--one for each physical region.
This is not bad in itself, but when gmsh reads the .msh file again, it stores the duplicate elements in the (single, uniaue) elementary region, and subsequent queries as to which element belongs to which physical group cannot be answered! Indeed, the physical information is stored in the elementary region (not in the element).
The cleanest solution would be to NEVER generate duplicate elements. The .msh format should si,ply have a $PhysicalGroups field that stores the Physical-to-Elemnetary/ies relationship.Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/95Copile error "GlobalBoVertexMap"2017-04-12T19:31:45ZChristophe GeuzaineCopile error "GlobalBoVertexMap"copile error:
[ 0%] Building CXX object CMakeFiles/gmsh.dir/Geo/GModelIO_CGNS.cpp.o
In file included from /home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:36:
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h: In member function ‘void MZo...copile error:
[ 0%] Building CXX object CMakeFiles/gmsh.dir/Geo/GModelIO_CGNS.cpp.o
In file included from /home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:36:
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h: In member function ‘void MZoneBoundary<DIM>::clear()’:
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:319: error: expected ‘;’ before ‘itEnd’
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:320: error: expected ‘;’ before ‘itBoV’
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:321: error: ‘itBoV’ was not declared in this scope
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:321: error: ‘itEnd’ was not declared in this scope
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:324: error: expected nested-name-specifier
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:324: error: expected ‘(’
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:324: error: expected ‘;’
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:325: error: ‘ref’ was not declared in this scope
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h: In member function ‘void MZoneBoundary<DIM>::clear() [with unsigned int DIM = 2u]’:
/home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:1159: instantiated from ‘int write_CGNS_zones(GModel&, int, int, const CGNSOptions&, double, int, const PhysGroupMap&, int, int) [with unsigned int DIM = 2u]’
/home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:421: instantiated from here
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:319: error: dependent-name ‘std::map::iterator’ is parsed as a non-type, but instantiation yields a type
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:319: note: say ‘typename std::map::iterator’ if a type is meant
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:320: error: dependent-name ‘std::map::iterator’ is parsed as a non-type, but instantiation yields a type
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:320: note: say ‘typename std::map::iterator’ if a type is meant
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h: In member function ‘void MZoneBoundary<DIM>::clear() [with unsigned int DIM = 3u]’:
/home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:1159: instantiated from ‘int write_CGNS_zones(GModel&, int, int, const CGNSOptions&, double, int, const PhysGroupMap&, int, int) [with unsigned int DIM = 3u]’
/home/buldi/praca/fem/gmsh/Geo/GModelIO_CGNS.cpp:430: instantiated from here
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:319: error: dependent-name ‘std::map::iterator’ is parsed as a non-type, but instantiation yields a type
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:319: note: say ‘typename std::map::iterator’ if a type is meant
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:320: error: dependent-name ‘std::map::iterator’ is parsed as a non-type, but instantiation yields a type
/home/buldi/praca/fem/gmsh/Geo/MZoneBoundary.h:320: note: say ‘typename std::map::iterator’ if a type is meant
make[2]: *** [CMakeFiles/gmsh.dir/Geo/GModelIO_CGNS.cpp.o] Błąd 1
make[1]: *** [CMakeFiles/gmsh.dir/all] Błąd 2
make: *** [all] Błąd 2Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/gmsh/gmsh/-/issues/96embedded line bug2017-03-23T16:21:30ZChristophe Geuzaineembedded line bugSome line segments in embedded lines can disappear during the refinement stage of the MeshAdapt algorithm.
See attached test-case.
Need to verify that line segements are correctly tagged in BDS db before edge swapping takes place.Some line segments in embedded lines can disappear during the refinement stage of the MeshAdapt algorithm.
See attached test-case.
Need to verify that line segements are correctly tagged in BDS db before edge swapping takes place.https://gitlab.onelab.info/gmsh/gmsh/-/issues/97Build fails under Mac OS X 10.62017-03-23T16:21:30ZChristophe GeuzaineBuild fails under Mac OS X 10.6I have successfully built gmsh 2.4.2 under Mac OS X 10.6 (in m32 mode since fltk doesn't support m64). However, version 2.5.0 gives me the following error during the build stage:
Scanning dependencies of target gmsh
[ 0%] Building CXX ...I have successfully built gmsh 2.4.2 under Mac OS X 10.6 (in m32 mode since fltk doesn't support m64). However, version 2.5.0 gives me the following error during the build stage:
Scanning dependencies of target gmsh
[ 0%] Building CXX object CMakeFiles/gmsh.dir/Fltk/Main.cpp.o
In file included from /tmp/gmsh-2.5.0/Geo/GEntity.h:13,
from /tmp/gmsh-2.5.0/Geo/GVertex.h:13,
from /tmp/gmsh-2.5.0/Geo/GModel.h:14,
from /tmp/gmsh-2.5.0/Fltk/Main.cpp:12:
/tmp/gmsh-2.5.0/Geo/SPoint3.h: In member function 'double SPoint3::distance(const SPoint3&) const':
/tmp/gmsh-2.5.0/Geo/SPoint3.h:100: error: 'sqrt' was not declared in this scope
In file included from /tmp/gmsh-2.5.0/Geo/SOrientedBoundingBox.h:15,
from /tmp/gmsh-2.5.0/Geo/GEntity.h:15,
from /tmp/gmsh-2.5.0/Geo/GVertex.h:13,
from /tmp/gmsh-2.5.0/Geo/GModel.h:14,
from /tmp/gmsh-2.5.0/Fltk/Main.cpp:12:
/tmp/gmsh-2.5.0/Geo/SVector3.h: In member function 'double SVector3::norm() const':
/tmp/gmsh-2.5.0/Geo/SVector3.h:30: error: 'sqrt' was not declared in this scope
/tmp/gmsh-2.5.0/Geo/SVector3.h: In function 'double norm(const SVector3&)':
/tmp/gmsh-2.5.0/Geo/SVector3.h:77: error: 'sqrt' was not declared in this scope
In file included from /tmp/gmsh-2.5.0/Geo/GVertex.h:14,
from /tmp/gmsh-2.5.0/Geo/GModel.h:14,
from /tmp/gmsh-2.5.0/Fltk/Main.cpp:12:
/tmp/gmsh-2.5.0/Geo/GPoint.h: In member function 'double GPoint::distance(GPoint&)':
/tmp/gmsh-2.5.0/Geo/GPoint.h:53: error: 'sqrt' was not declared in this scope
make[2]: *** [CMakeFiles/gmsh.dir/Fltk/Main.cpp.o] Error 1
make[1]: *** [CMakeFiles/gmsh.dir/all] Error 2
make: *** [all] Error 2https://gitlab.onelab.info/gmsh/gmsh/-/issues/98segmentation fault at refine by splitting on basic 2d mesh2020-01-21T09:40:44ZChristophe Geuzainesegmentation fault at refine by splitting on basic 2d meshRefine By Splitting on a basic 2d mesh made of 2 elements ends up with a segmentation fault, both with gmsh-2.5.0 and gmsh-2.5.1-svn-Linux. Everything works fine with gmsh-2.4.2 on the same mesh.Refine By Splitting on a basic 2d mesh made of 2 elements ends up with a segmentation fault, both with gmsh-2.5.0 and gmsh-2.5.1-svn-Linux. Everything works fine with gmsh-2.4.2 on the same mesh.https://gitlab.onelab.info/gmsh/gmsh/-/issues/99Clarify/extend/simplify File->Save As vs. View->Save As2017-03-23T16:21:31ZChristophe GeuzaineClarify/extend/simplify File->Save As vs. View->Save AsUsers seem confused by the two ways to save data: either with File->Save As or View->Save As.
The underlying idea is simple: "File" works on GModel, "View" works on PView. However, just doing "File->Save As" and entering a file that end...Users seem confused by the two ways to save data: either with File->Save As or View->Save As.
The underlying idea is simple: "File" works on GModel, "View" works on PView. However, just doing "File->Save As" and entering a file that ends with .pos will create a mesh statistics post-processing view, which is probably not what the user wanted: he/she probably just wanted to save the currently visible post-processing view to disk...
What we could do: provide File->Save As->Post-processing View + a small window with
----------------------
| o Save All Views
| o Save Visible View
|
| x Save only visible entities
|
| xxxxxxxxxx Format
----------------------
| Cancel Save
----------------------