Reference terrain robust-threshold

[James Hollingsworth]

Hi Oleg,

Did you ever think about adding an option for a different robust-threshold for reference terrain (a bit like you do for --heights-from-dem-robust-threshold)? Otherwise, will this option use the same rt as for the match point intersections?

Cheers, J

[Oleg Alexandrov]

James,

For the ---reference-terrain option, indeed the same robust threshold is used as for interest point matching. And in fact, that may be sufficient, as both of these are in units of pixels, and there is also --reference-terrain-weight to give these more weight. For --heights-from-dem, there is a separate  --heights-from-dem-robust-threshold, because that one is not measured in pixels, but in meters. So it is trickier to tune with the same robust threshold, I think. 

BTW, as you know, both of these are rather clunky, though can make a difference if used carefully. With --heights-from-dem, there's a chance a first invocation of it would nudge things in the right direction, but if things were quite off, originally, this may not fully make things converge, as this ground constraint does not adaptively move the closest point on the DEM to follow where your current triangulated point moved. So it may help sometimes, maybe, if things did not fully converge to reinvoke this with the latest adjustments as initial guess, then retriangulation will take place and new closest point on the DEM will be assigned.

Oleg

--
You received this message because you are subscribed to the Google Groups "Ames Stereo Pipeline Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ames-stereo-pipeline...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ames-stereo-pipeline-support/f52daff8-8043-4bfb-b056-dedccf6070f6n%40googlegroups.com.

[James Hollingsworth]

Thanks for he explanation... it definitely makes more sense now. :)