Distance inverted returns same result as Distance

[trassshhub]

Describe the bug
distance inverted (p2-p1) returns same result as distance (p1-p2).

To Reproduce
Steps to reproduce the behavior:
Do two trackings with same targets and parameters, except one with "distance inverted" and one with "distance" as tracking metric.
Results are the same.

Expected behavior
Expecting "distance" to return result with higher values when 2 targets are further apart and smaller values when targets are closer, while "distance inverted" should return smaller values when targets are further apart and higher values targets are closer,

Runtime:

• OS: Windows 10
• Version: 0.5.0

Additional context
Can I have a further explanation on the need of selecting center line after distance-based tracking? Is it for projection? Is it possible to return the raw distance between the two points?

[michael-mueller-git]

Thanks for reporting. Bug also apply to y and x. Fixed with 6d11368. Invert functions will be functional again in the next release version.

[michael-mueller-git]

Can I have a further explanation on the need of selecting center line after distance-based tracking?

Is mainly relevant for roll prediction to determine the actual turning point. The program calculate the offset values for tracked feature and the selected start and endpoint of the center line. (We could theoretically remove this for distance prediction. But for simpler program structure i include the menu for all options).

Is it possible to return the raw distance between the two points?

Only the normalized raw distance: Enable the raw_output in the config file and select option distance (p1-p2) or the inverted equivalent.

[michael-mueller-git]

fixed in v0.5.1