wildmeshing / triwild Goto Github PK

Hello every1.

I was wondering if there were any reason to not exporting the input features in the mesh file.

Ideally, those features should be meshed as curved edge elements, and tagged using gmsh physical groups.
Doing so, the numerical practitioner could easily enforce some special boundary conditions on those tagged feature elements.

There seems to be a threshold over which the mesh is simply returned without any refinement, ignoring target_edge_len. This seems to be the case if the edge length is even 0.01 the bounding box size.

Any one kind to share? Thanks.

Under Windows 10 with gnu gcc.

Hello,

I have compiled the project with visual 2017 and when i run in debug with figure 1 from pregenerated data I get an error.
it looks:
in function void triwild::feature::remove_high_curvature
in the loop for (int j = 0; j < ranges.size(); j += 2)
in condition if (j == ranges.size() - 2) {
in loop for (double infl: old_inflection) {
in condition if (infl > ts[i][ranges[j]] && infl < ts[i][ranges[j + 1]])
the program crash because ts[i][ranges[j + 1]] generates Assertion failed: vector subscript out of range

Did you get this error?

Hello,

I'm a new user and I'm a little confused on how to generate obj files to input. Also I was wondering if you had any examples of simpler shapes.

Thank You!

I am experiencing issues with a large targeted edge length. Triwild crashes when reproducing the coarsest part of Figure 7. The attached includes the errors. With the smaller values of targeted edge length reported in the paper there is no failure.

triwild-crash.txt

I was wondering if TriWild could be extended for manifolds (2D surface meshes embedded in a 3D space).
From the descriptions in the TriWild paper, it seems to assume that the inputs are 2D. However, .obj files can take in 3D coordinates (and as seen in https://github.com/wildmeshing/TriWild/blob/master/src/triwild/triangulation.cpp#L34, it is only using the two first coordinates)

I am interested in trying out TriWild as a replacement for Triangle in my program.

Is there a mailing list or forum or other place to ask questions? I always hate posting questions to an Issue list. Sorry if this is the wrong place, but I couldn't find any other place for questions.

I use Triangle for both simple 2D CDT and also mesh generation -- where the boundary is fully specified, but Triangle inserts interior points to reach mesh size and quality goals.

The Triangle license is problematic. It also crashes far more often than I can deal with anymore. I have tried various 'improved' wrappers that attempt to catch various failure cases more elegantly, but none of them are satisfactory.

Shewchuk is unresponsive to questions about the license and development of the library appears to be dead. This would be fine if was problem-free, but that is certainly not the case in my experience.

Hopefully TriWild improves in a number of these areas.

I need to build TriWild as a library and call that from my program -- I currently use CMake. Specifically, I use the SuperBuild approach to have a Library and Main project and then I bundle my various libraries with ExternalProject_add. I am sensitive to the dependencies I add to my program -- I much prefer libraries with few or no dependencies.

From what I can tell, TriWild requires LIBIGL and GMP. It may also require NLOPT and geogram. Digging into some of the CMake, it also appears to download aabbcc, and json. LibIGL itself requires Eigen. I couldn't really tell how deep the dependency rabbit hole goes.

Some of my users need to build my program (and any dependencies) on a computer that does not have access to the internet. Because of this (and also for testing and repeatability sake), I always embed *.zip files of dependencies in my program instead of downloading the latest version from the upstream project (as a compromise, it is better to point at a specific upstream version).

From what I can tell, TriWild's build requires an internet connection to download at least a half dozen libraries -- some of which have their own dependency chain.

That doesn't even get into the mess that is the melange of software licenses that all these libraries introduce.

Is there any place where the use of these dependencies by TriWild is clearly documented? Optional libraries are clearly identified and instructions given for leaving them out.

Is there any plan going forward to reduce the number of dependencies? A number of them appear to be relatively simple convince libraries implementing commodity data structures. In my experience, it is generally better to re-implement what is needed from these cases and drop the dependency.