[IGSTK-Developers] Position the CylinerSpatialObject

[Patrick Cheng]

Hi Luis,

Actually, for all the TrackerToolSpatialObject(specifically 
NeedleSpatialObject), If we know the geometry of this tool, we can take 
the Transform (rotation and translation) from the tracker and calculate 
some anchor points internally, and then place the 
TrackerToolSpatialObject in the right position in 3D. This might be a 
solution to the very confusing orientation calibration.

I agree with your point for not having it in the CylinderSpatialObject,
but I think the notation of "EntryPoint" and "TargetPoint" should go 
with the PathSpatialObject. The NeedleSpatialObject should only carry 
the information the shape of the tracker tool and it's location.

Patrick


Luis Ibanez wrote:
> 
> Hi Patrick,
> 
> This sounds like a good idea,
> 
>  but...
> 
> Shouldn't this be a method specific for the "NeedleSpatialObject" ?
> 
> 
> after all,
> the NeedleSpatialObject is the class that will
> have a notion of "EntryPoint" and "TargetPoint".
> 
> 
> Adding such methods to the Cylinder will be confusing,
> because a cylinder is a generic geometrical shape,
> and it is not designed to be inserted into a patient,
> as needles are.
> 
> 
> 
>   Luis
> 
> 
> 
> 
> -------------------
> Patrick Cheng wrote:
>> Hi all,
>>
>> I am proposing adding a RequestSetTipPoints( PointType &pts ) to the 
>> CylinderSpatialObject. The parameters passed by are two points 
>> indicates the two ends of the CylinderSpatialObject.
>>
>> Reason:
>>
>> 1. In path planing, we need to place the CylinderSpatialObject by 
>> setting entry point and target point. We don't have the Transform 
>> here. Actually place the CylinderSpatialObject by fixing it's two ends 
>> is more straight forward.
>>
>> 2. When the CylinderSpatialObject is attached to the tracker tool, 
>> even if we get the transform and orientation right (We haven't got to 
>> that point yet), Then there should be another shift applied to the 
>> CylinderSpatialObject to move it's tip to the probe tip. This is very 
>> cumbersome, confusing, and erroneous. Why don't we take the transform 
>> and the size of CylinderSpatialObject, and internally calculate the 
>> points for the two ends (Which is easy to do), and place the 
>> CylinderSpatialObject in the right position by pinpointing the two ends?
>>
>> Thank you,
>>
>> Patrick
>>
>> _______________________________________________
>> IGSTK-Developers mailing list
>> IGSTK-Developers at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>>
>>
> 
> 
>