Thomas Schöps

> That is a pitty, because we were trying to solve a problem here and even gave relatively clear recommendations that come from somewhat knowledgable people in this regards. Well,...

> I also don't understand how you can equate FreeAge and openage like this [...] I did not mean to equate the two projects, I just wanted to say that...

> Nah, it's fine. You will not have any problems with your repository if someone implements workarounds. We are misunderstanding ourselves. I was not talking about the repository getting taken...

I might look into this issue today.

I don't remember why I commented out `install_signal_handlers();`. If there's no problem with re-enabling it, I am fine with it. I remember getting some weird signals while debugging other projects...

The full-map-screenshot function itself should be quite easy to implement, I think. However, for the suggested use-case, there are at least two other things missing which may take much more...

Hi, The non-manifoldness and self-intersections you are observing are somewhat inherent to the algorithm, and also stated in our paper (see e.g. Tab. 1 or Fig. 18). Notice that the...

I would start with those parameters: * Increase `--sensor_noise_factor` to make sure that the overlapped regions are treated as the same surface instead of two different surfaces. Perhaps also increase...

It is hard for me to recognize anything in the mesh output. It even looks a bit like what I would expect when using low-frequency input with wrong camera poses...

I don't have much experience with offline algorithms for surface reconstruction. However, I think that the well-known [Poisson Surface Reconstruction](http://www.cs.jhu.edu/~misha/Code/PoissonRecon/) works very well in case the input data is good....