The --loopanalyze option seem to perform --loopfilter

[Bob-O-Rama]

While attempting to create an unfiltered .pto for testing, specifying the --loopanalyze option still seemed to perform filtering. For example:

./cvfind --detect orb --pattern lrtb --rowsize 20 --overlap 30 --hugin --cellsize 50 --loopanalysis -o out.pto in.pto

Resulted in may pairs being dropped, apparently because of loop homography failing to find valid loops.

[Bob-O-Rama]

loopFilter is enabled by default, but not unset when a less aggressive loop level is selected. The following implication chain for all levels is enforced:

loopRepair --> loopFilter --> loopAnalyze --> trialHomography --> doHomography

This is because each more intensive steps requires the others to be enabled to set up data structures for the next stage.

Proposed solution:

After parsing the CLI, if loop analyze or trial homography is explicitly specified, the more aggressive options are disabled, this is irrespective of the other options specified. In other words specifying loopRepair and loopAnalyze in any combination will result in loopAnalyze. Nothing specified uses the existing default.