[vtkusers] effect of StopWhenEndReached in vtkDijkstraGraphGeodesicPath and edge-weights

[Grothausmann, Roman Dr.]

Dear mailing list members,


I'm wondering about the StopWhenEndReached switch of 
vtkDijkstraGraphGeodesicPath. As much as I understand from looking at its code 
it seems to me that with StopWhenEndReachedOff() the shortest paths to all 
vertices are computed but TraceShortestPath only outputs the one from startv to 
endv and disregards all other computed paths no matter what StopWhenEndReached 
is set to.
Is that correct/intended?
Is the filter using the previously calculated heap (with 
StopWhenEndReachedOff()) if startv stays the same but endv is changed to get 
another shortest path?

Is my understanding correct that the filter by default uses the Euclidean 
distance between points as weights (Distance2BetweenPoints in 
CalculateStaticEdgeCost) and not the number of nodes?
Would I need to modify vtkDijkstraGraphGeodesicPath itself to use other 
edge/line weights, i.e. all constant?

Any help or hints are very much appreciated
Roman

-- 
Dr. Roman Grothausmann

Tomographie und Digitale Bildverarbeitung
Tomography and Digital Image Analysis

Institut für Funktionelle und Angewandte Anatomie, OE 4120
Medizinische Hochschule Hannover
Carl-Neuberg-Str. 1
D-30625 Hannover

Tel. +49 511 532-2900