Agenda&Status 092205

From IGSTK

IGSTK Weekly T-con September 22, 2005 1pm EST

Agenda:

1. Review action items
2. Current activities
   1. I6 feature list and coding activities
3. Dashboard status Dashboard
4. Component status
5. Technical topics
6. Project business
7. Schedule
8. Any other business

Action Items (Age in weeks)

1. AC -> WS (7) Transfer and install the copyright fixing script(s) from ITK.
2. RA (4) Improve coverage of igstkView
3. RA (3) Put 5 CT chest dataset slices into IGSTK cvs and put the full dataset into dspace.
4. SA (3) Put 5 MR dataset slices into IGSTK cvs and put the full dataset into dspace.
5. DG (1) Increase coverage of the NDICommandInterpreter. Look into testing on Zion.
6. DG (1) Polaris tracker has UMR and UMC issues that need to be fixed.
7. RA (1) Set up a code review table for iteration 6.

Component Status

1. State Machine (LI)
2. Tracker (DG)
   1. (DG,HS) using Logger to record serial communication stream as ASCII-encoded text file. Binary stream files were converted to ASCII-encoded text files.
   2. (DG,HS) NDICommandInterpreter now handles errors from Communication::Read & Write.
   3. (HS) using Traxtal Tool SROM for PolarisTrackerTest.
   4. (DG) lots of code in NDICommandInterpreter was rearranged to improve coverage
3. SerialCommunication (DG)
   1. (DG,HS) event invocation moved from derived classes to SerialCommunication class so that events can be linked more directly to the state machine
   2. (DG,HS) adjust state machine to improve error handling capability
   3. (DG) Communication events moved to igstkEvents.h
4. Viewer (RA)
5. Spatial Objects (JJ)
6. Logger (HS)
7. Object Representation (RA)
8. Image Reader/Writer (AE)
   1. Added igstkMRImageReader class
   2. Added Get functions to access useful DICOM tags such as Modality and PatientID
   3. Added event-observer for handing errors such as invalid request and image reading failure
9. Tracker Landmark Registration (AE)
   1. Added event-observer for handling errors such as invalid request and transform computation failure
10. Application (PC)

Schedule:

• April 29 : closeout Iteration 3 reviews and tag CVS mainline
• May 2 - June 17 : Release 2, Iteration 4
• June 19 - August 17 : Iteration 5
  • Jul 28 - Aug 4 : Code Review
  • Aug 5 - Aug 9 : Move Code
  • Aug 11  : Verfiy and Apply Final Tag
  • Aug 12 - Aug 17 : Fix Wiki Documentation
• August 8 - October 25 : Iteration 6 (end R2)
  • Aug 8 - Aug 11 : Create Feature List
  • Aug 12 - Aug 18 : Write Functional Requirements
  • Aug 19 - Sep 8 : Develop Code
  • Sep 9 - Sep 19 : Add Formal Requirements to Bug Tracker
  • Sep 20  : Tag Sandbox
  • Sep 21 - Sep 28 : Code Review
  • Sep 29 - Oct 5 : Move Code
  • Oct 6  : Verify and Apply Final Tag
  • Oct 7 - Oct 10 : Fix Documentation
  • Oct 11  : Freeze Repository
  • Oct 12 - Oct 18 : Fix Remaining Bugs
  • Oct 19 - Oct 21 : Increase Code Coverage
  • Oct 24 - Oct 25 : Create and Release R2 Package
• Year 1 / Release 2 Review Meeting: November 10-11