[IGSTK-Users] spatial object after expired data validity AND tracker updating signal instead of position

[Aswin Mathews]

Hi Andinet,

Thanks for the answers. I will do that. I have two other questions though.

What happens if I attach a view to a tracking tool and the communication
gets cut off in between? Does the entire view window go blank?

Now I am attaching my spatial object to a tracker tool and tracker tool to a
tracker. The tracker's parent is a world reference. So, a position of
(0,0,0) on the tracker implies the world_reference. Is that correct?

Thanks,

Aswin.


On Wed, Jul 16, 2008 at 9:29 AM, Andinet Enquobahrie <
andinet.enqu at kitware.com> wrote:

> Hi Aswin,
>
>> Hi everyone,
>>
>> I have noticed that in case I lose connection to my tracker, the spatial
>> object connected to it disappears after the data validity time has expired.
>> Would it be possible to change the color of the spatial object, say from
>> green to red, rather than letting it disappear altogether?
>>
>>  You are correct. The current behavior is that the object will disappear
> if the transform
> time expires. We would like to keep it as it is in cvs ( main distribution
> )
> However, for your own use, you can locally modify the state machine
> configuration in
> ObjectRepresentation class to be able to change the actor color when the
> transform
> time expires.  It is straight forward to do that.
>
> In the ObjectRepresentation::RequestVerifyTimeStampAndUpdateVisibility()
> method,
>
> 1) InvalidTimeStamp input gets invoked if the time expires, otherwise the
> ValidTimeStamp input
> will be invoked.
>
> 2) These state input will initiate a transition to methods that will turn
> on/off the actor
> visibility. All you need to do is modify these methods and change the actor
> colors instead of
> turning on/off the visibility.
>
>  Also, I need to write a tracker for spirometer input through NiDAQ. Now,
>> by default, a tracker updates a transform. But mine's more of a signal
>> (breathing) than position. Should I just write it that the signal is one
>> axis of the transform with the other two set to zero? Is there a better way?
>>
> Yes, for minimal change, you can store the signal value as one of the
> components
> of the translation vector of the tool transform and keep the others to
> zero.  You will need
> to write NiDAQ specific tracker and trackerTool classes. You might want to
> start
> with the current tracker classes.
>
> Let us know if you more questions..
>
> -Andinet
>
>
>
>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> IGSTK-Users mailing list
>> IGSTK-Users at public.kitware.com
>> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users
>>
>
>
> --
> ==========================================================
> Andinet A. Enquobahrie, PhD
> R&D Engineer
> Kitware Inc.
>
> 28 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-371-3971 x124
> www.kitware.com
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20080716/ce7a205f/attachment.html>