mmg icon indicating copy to clipboard operation
mmg copied to clipboard

open source software for bidimensional and tridimensional remeshing

Results 41 mmg issues
Sort by recently updated
recently updated
newest added

# Environment | | | |--------| ---------------| | OS | macOS Big Sur | | Compiler | clang version 11.1.0 | | mmg | 5b7cf4e7f5b9630af199026c90159c8ee83d60fc | | Build | Debug...

kind: regression
part: ls discretization

- [x] Remove old (and useless) things: - [x] Dart related config; - [x] useless compiler flags / options; - [x] Make configuration more friendly with cmake-gui : - [x]...

kind: enhancement
part: cmake

- [ ] Call secure scanf / printf function to remove the flag `_CRT_SECURE_NO_WARNINGS` - [ ] Review warnings to see what can be cleaned to a minimal cost

kind: enhancement
platform: windows
part: compilation

I've been testing out mmgs on some triangle surfaces, and I really like what it can do! Is it possible to give mmgs feature boundaries to use instead of a...

kind: question
part: mesh adaptation
part: surface model

Hi, I'm observing a weird bulging effect with mmgs's surface remeshing. If I take a unit cube and remesh it with the default option, without angle detection (`-nr -hausd 0.01`),...

kind: enhancement
part: mesh adaptation
part: surface model

Hi there, Thanks for the great library! I am testing the possibility of using mmg2d for mesh generating that conforms to a given set of segment constraints. I noticed that...

kind: bug
part: mmg2d
part: mesh generation

I find Mmg tremendously useful, especially its 3D mesh optimization feature. Perhaps it could be made even more useful if more than Gmsh and Medit files would be accepted. Wrapping...

kind: wish
part: I/O

I am facing problems with MMG3D with preserving reference of vertices of parallelTriangles. I freeze the adaptation at these boundary triangles using MMG3D_Set_parallelTriangle. In order to match the frozen triangles...

kind: bug
part: mmg3d
part: library

The exit statuses of functions are non-consistent in the library, e.g., `MMG2D_Set_meshSize` returns `1` on success, while `MMG2D_mmg2dlib` returns `MMG5_SUCCESS` (defined to `0`) on success. Would it be possible to...

kind: enhancement
part: library

This gives a failure return value if mesh quality is null, previously if mesh quality was null a segmentation fault with no return would occur in this routine. I've added...