[IGSTK-Developers] follow up from IGSTK advisory board meeting and schedule for the next two weeks

[Kevin Cleary]

Hi everyone:

 

Greetings from Barcelona! I am here for the IEEE Robotics Conference and to
co-host a workshop on Medical Robotics.

 

First, thank you all very much for attending the developer's and advisory
board meeting last week. I am a little biased, but I thought it was a great
meeting and as far as I can tell 

 

Below my signature is my start at some notes from the meeting - I will try
to work on a more formal summary later and would be glad to get any feedback
from you

 

Please note that we need to change the schedule slightly for the next two
weeks for the teleconference:

1)       The teleconference for this week will be at 2 pm on Thursday
instead of the usual time of 1 pm - I will try to find a way to call in from
Barcelona - unfortunately my hotel has the old analog phone system so I am
not sure yet

2)       The teleconference for next week will be Wednesday April 27 at 1 pm
instead of on Thursday - we have our group retreat on Thursday that week

 

Thanks very much - please let me know if you cannot make the teleconference
this week (Thursday at 2 pm)

 

Regards

 

Kevin Cleary

 

             

P.S. to David Gobbi: are you on the developer's list? IF that is the case I
will not cc you on these things.

 

------------------------------------------------------------------
Kevin Cleary, Ph.D.                        Work phone: 202-687-8253
Associate Professor                        Work fax: 202-784-3479
Deputy Director  
                            
Imaging Science and Information Systems (ISIS) Center
Department of Radiology                    Pager: 202-901-2033
Georgetown University Medical Center       Cell phone: 202-294-3409
2115 Wisconsin Avenue, Suite 603           Home phone: 301-299-0788
Washington, DC, 20007                      Home fax: 301-299-0789

 

ISIS center:  <http://www.isis.georgetown.edu/> www.isis.georgetown.edu
Research group:  <http://www.caimr.georgetown.edu/> www.caimr.georgetown.edu
WashCAS:  <http://www.washcas.org/> www.washcas.org
Email:  <mailto:cleary at georgetown.edu> cleary at georgetown.edu
-------------------------------------------------------------------

 

> 1)      We decided to have one iteration per month. This could give us 6 

> iterations before the one year review meeting. At least the first 

> three of these iterations should focus on continuing to develop the 

> base classes. There are two issues: 1) how we manage the hierarchy of 

> classes when the base class has a state machine and 2) how this one 

> integrates with the base machine of the derived classes. Later 

> iterations may move more toward including functionality needed for the
applications.

> 

>  

> 

> 2)      We developed a plan to move forward with tracking. We currently 

> have a wrapping of David Gobbi's code that can be used a baseline for 

> comparison. Sohan will have primary responsibility for continuing to 

> develop the IGSTK tracker class and should keep Hee-su inform so 

> Hee-su can take this over. Sohan will also do a survey of trackers and 

> the characteristics and will present next Thursday. It would also be 

> interesting to get a Logitech 3D mouse (check with David Gobbi as to 

> what he has) for testing.

> 

>  

> 

> 3)      For next Thursday's tcon, let us make it at 2 pm if possible. We 

> need to discuss the integration / hierachy between state machine, 

> tracker, and communication classes so Sohan can move forward. For the 

> week after, we need to move the tcon to Wednesday if people are 

> available as Sohan and I are away at our retreat.

> 

>  

> 

> 4)      Logging will be the responsibility of Hee-su. We need to put him 

> in touch with Dan Blezek and Jim Miller at GE to help since they may 

> want to put it in ITK. For logging, we discussed three possibilities 

> of logger classes: one that is very fast for critical errors (high 

> priority log), one that is very safe (separate thread), and the normal 

> one. We need a separate thread so that no matter what happens to the 

> application the critical data is saved.

> 

>  

> 

> 5)      There was some discussion on threading. We would like to support 

> multithreading but in a control and limited way. We drew an 

> architecture that included threads for tracking and logging.

> 

>  

> 

> 6)      For tracking, at the tracker class level we will continuously 

> poll the tracker and keep this data in a circular buffer. The size of 

> the buffer can be changed. The scene will have a pulse generator and 

> will prorogate the calls through the object representation classes, to 

> the spatial objects, to the tracker tools. The data will be "pulled" 

> up to the tracker tools.

> 

>  

> 

> 7)      Error handling was discussed. The idea was to propagate up event 

> levels and let the appropriate level handle it. State machine will 

> not have failure states, but if it receives an invalid, it will go to 

> a valid state (could be the same) and it will report an error event as 

> well as log the error (details TBD). There could be priorities of 

> errors. There was some discussion and some seemed skeptical (K2) 

> so the concept has yet to be proven.

> 

>  

> 

> 8)      The book will be written using Latex. We will try to use the 

> infrastructure you built for the software guide. Figures are in EPS. 

> Visio can be used. The great advantage is that everything can be in CVS.

> 

>  

> 

> 9)      Licensing objects with spatial objects viewer. If we cannot use 

> Julien's library directly, we need to write the ones that we need. The 

> guiding principle is that the entire toolkit should have a single 

> license and must be available for commercial applications (remember 

> this a small business grant intended to develop a commercial market).

> 

>  

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/igstk-developers/attachments/20050418/a849cee4/attachment.html>