[fuseCut] Mesher: read the neighbour-inversion iteration count as int

[dspl1236]

Fixes #2178.

Mesher::graphCutPostProcessing reads an iteration count with get<bool>:

int invertTetrahedronBasedOnNeighborsNbIterations =
  _mp.userParams.get<bool>("hallucinationsFiltering.invertTetrahedronBasedOnNeighborsNbIterations", 10);

and uses it as a loop bound at line 317. The result is 1 either way:

• with the option set, boost::property_tree's bool translator does not accept a value like "10", so the get falls back to its default;
• the default supplied here is 10, which converts to bool true, which converts back to int as 1.

So the 4-neighbour inversion pass runs once, whatever is configured — neither the configured value nor the intended default of 10 ever reaches the loop.

The second hunk changes nbSolidAngleFilteringIterations from get<double> to get<int>. That one is not a defect — the double translator parses "10" and the narrowing gives 10 — but it is the same mistake on an int count, two lines below, so it seemed worth correcting while the file is open.

Effect

The later rounds remove the isolated spikes and pits that the first round exposes. Measured with only these calls changed:

data set	faces, as shipped	faces, reading it as int
6-view monstree	500,572	500,057
107-photo engine bay	2,364,995	2,361,583

About 0.8 s more on the larger job. Small in face count, but it is the difference between the pass doing what the parameter asks and doing one round regardless.

Found while porting the meshing stage to HIP for AMD GPUs, but this is CPU code and is not platform specific; both measurements above are from CPU runs.

🤖 Generated with Claude Code