[Insight-developers] FW: Insight-developers digest, Vol 1 #851 - 6 msgs: additional agenda item
Kevin Cleary
cleary at georgetown . edu
Thu, 22 May 2003 09:45:08 -0400
Bill:
We probably need just a few minutes (maybe 10 minutes between Stephen =
and
myself) to give an update on the two MICCAI tutorials:
1) ITK course
2) open source workshop
The web site for the tutorials is=20
http://www . miccai2003 . org/content/tutorials . htm
Thanks
Kevin Cleary
Georgetown University
cleary at georgetown . edu
-----Original Message-----
From: insight-developers-admin at public . kitware . com
[mailto:insight-developers-admin at public . kitware . com] On Behalf Of
insight-developers-request at public . kitware . com
Sent: Thursday, May 22, 2003 6:41 AM
To: insight-developers at public . kitware . com
Subject: Insight-developers digest, Vol 1 #851 - 6 msgs
Send Insight-developers mailing list submissions to
insight-developers at public . kitware . com
To subscribe or unsubscribe via the World Wide Web, visit
http://public . kitware . com/mailman/listinfo/insight-developers
or, via email, send a message with subject or body 'help' to
insight-developers-request at public . kitware . com
You can reach the person managing the list at
insight-developers-admin at public . kitware . com
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Insight-developers digest..."
Today's Topics:
1. CMake version 1.6.7 Released (Ken Martin)
2. Coverage of itk files (Lorensen, William E (Research))
3. coverage (Damion Shelton)
4. RE: coverage (Lorensen, William E (Research))
5. Draft Agenda for Pittsburgh meeting (Lorensen, William E =
(Research))
6. Pittsburgh Agenda (Rev 1) (Lorensen, William E (Research))
--__--__--
Message: 1
From: "Ken Martin" <ken . martin at kitware . com>
To: <cmake at public . kitware . com>
Cc: <vtk-developers at public . kitware . com>,
<insight-developers at public . kitware . com>
Date: Wed, 21 May 2003 09:53:27 -0400
Subject: [Insight-developers] CMake version 1.6.7 Released
We are pleased to announce the release of CMake version 1.6.7. This =
patch
includes a number of bug fixes and support for Visual Studio 2003. It =
can be
downloaded from www.cmake.org A synopsis of the changes
follows:
Added support for Visual Studio 2003. Fixed a bug where LINK_FLAGS were =
not
getting passed to Visual Studio generators. Added a fix for MipsPro =
7.3.
Fix for C++ object file rule for nmake. A fix for search paths in the
FindCable and FindFLTK modules. A fix for the TRY_COMPILE command when =
make
-I is used. A fix to support very long lines in CmakeList files. =
Improved
the MACRO command to provide warnings whan a MACRO is not properly =
closed
with a matching END_MACRO. Fixed the REMOVE command to not ignore the =
first
argument. Fixed the STRING command to be inherited. Fixed some keyboard
issues with ccmake on the SGI. Fix to ccmake to not report and error if =
non
error message occur. Fixed some flags for C++ shared libs on SunOS and =
win32
executables on Borland. A fix in the implementation of the
CheckIncludeFiles.cmake module. Improved error messages when a bad =
generator
was selected. More robust CheckSymbolExists.cmake module.
Thanks
Ken
Ken Martin, PhD
Kitware Inc.
518 371 3971 x101
469 Clifton Corporate Pkwy
Clifton Park NY 12065
--__--__--
Message: 2
From: "Lorensen, William E (Research)" <lorensen at crd . ge . com>
To: insight-developers at public . kitware . com
Date: Wed, 21 May 2003 10:46:31 -0400
Subject: [Insight-developers] Coverage of itk files
Folks,
We have created a list for each developer that shows the current state =
of
code coverage for files that they checked in. We assumed that if you =
checked
in cvs revision 1.1 of a file that you were the original developer. I am
emailing the list to each developer. Each line in the file shows the =
source
file followed by the line coverage in %.
Here's a plan of attack:
1) Let me know if there is a file assigned to you that you do not think =
is
yours.
2) Let me know if there are files that should be removed.
3) Start with the lowest coverage. For each file that has 0.0% write a =
test.
4) Files below 70% should have better coverage. If possible, augment the
current test to improve the coverage. We don't want to add unnecessary
tests.
At a minimum we must generate tests for the 0.0% files.
Some developers may have disappeared. I'll forward their files to the =
PI's
when the mail bounces. Also, if you receive this e-mail and no longer =
work
on the project, please forward the email to your PI and
cc: lorensen at crd . ge . com .
Coverage is reported daily on the dashboard.=20
http://public . kitware . com/Insight/Testing/HTML/TestingResults/Dashboard/M=
ost
RecentResults-Nightly/Dashboard.html
New results rollup around 11:00am EDT. Before that time you can always =
look
at the previous day's coverage data. Files that are red have virtually =
no
coverage. Yellow files need additional testing.
Bill
--__--__--
Message: 3
Date: Wed, 21 May 2003 11:03:29 -0400
Cc: Insight-developers at public . kitware . com
To: William E Lorensen <lorensen at observ . crd . ge . COM>
From: Damion Shelton <beowulf at cs . cmu . edu>
Subject: [Insight-developers] coverage
A few questions...
There are lots of cases with my files where the coverage reports are:
BasicFilters/itkGaussianImageSource.h 46.15
BasicFilters/itkGaussianImageSource.txx 90.16
It's not clear to me why the coverage amounts differ for a given class.=20
It looks like the coverage is good for the .txx but not the .h, despite=20
being the same class. In other cases it's even more extreme:
Common/itkBloxBoundaryPointPixel.h 0.00
Common/itkBloxBoundaryPointPixel.txx 100.00
How is coverage "improved"? If there is "not enough", what is "more"?=20
Do the tests need to do more, or does the object need to be created in=20
a greater number of tests?
What about completely virtual base classes? e.g.
Common/itkBloxCoreAtomItem.h 0.00
Common/itkBloxCoreAtomItem.txx 0.00
Thanks,
-Damion-
---------
Damion Shelton
Carnegie Mellon University, Robotics Institute
A408-o Newell Simon Hall
412.268.3866 (office)
412.818.8829 (cell)
http://www . cs . cmu . edu/~beowulf
---------
During the Middle Ages, probably one of the biggest mistakes was not=20
putting on your armor because you were "just going down to the corner."
--__--__--
Message: 4
From: "Lorensen, William E (Research)" <lorensen at crd . ge . com>
To: "'Damion Shelton'" <beowulf at cs . cmu . edu>,
William E Lorensen <lorensen at observ . crd . ge . COM>
Cc: Insight-developers at public . kitware . com
Subject: RE: [Insight-developers] coverage
Date: Wed, 21 May 2003 11:31:22 -0400
Did you look at the coverage report for those files on the dashboard? =
For
example:
http://public . kitware . com/Insight/Testing/HTML/TestingResults/Sites/esopu=
s.c
rd/SunOS-5.7-c++/Coverage/__Code_BasicFilters_itkGaussianImageSource_h.ht=
ml
shows that many of the Get macros are not exercised.
The number at the left is the number of times a statement was executed. =
The
##### indicate code that is not covered. A blank means the code was =
never
compiled or is not an executable statement.
To improve, if there is already a test, you can add code to test those =
lines
that are not covered. Often error conditions are not tested and it may =
be
hard to do so.
Our goal is at least 70% coverage. The example above can easily reach =
that
adding Get's to the test.
Also, the corresponding .txx is very well covered.=20
Your second example shows that the BloxCoreAtomItem is never used. At =
least
the constrcutor/destrcutor is never executed. And the method
CalcCenterAndDiameter is not even compiled.
In summary, the coverage is per file, not per object.
-----Original Message-----
From: Damion Shelton [mailto:beowulf at cs . cmu . edu]
Sent: Wednesday, May 21, 2003 11:03 AM
To: William E Lorensen
Cc: Insight-developers at public . kitware . com
Subject: [Insight-developers] coverage
A few questions...
There are lots of cases with my files where the coverage reports are:
BasicFilters/itkGaussianImageSource.h 46.15
BasicFilters/itkGaussianImageSource.txx 90.16
It's not clear to me why the coverage amounts differ for a given class.=20
It looks like the coverage is good for the .txx but not the .h, despite=20
being the same class. In other cases it's even more extreme:
Common/itkBloxBoundaryPointPixel.h 0.00
Common/itkBloxBoundaryPointPixel.txx 100.00
How is coverage "improved"? If there is "not enough", what is "more"?=20
Do the tests need to do more, or does the object need to be created in=20
a greater number of tests?
What about completely virtual base classes? e.g.
Common/itkBloxCoreAtomItem.h 0.00
Common/itkBloxCoreAtomItem.txx 0.00
Thanks,
-Damion-
---------
Damion Shelton
Carnegie Mellon University, Robotics Institute
A408-o Newell Simon Hall
412.268.3866 (office)
412.818.8829 (cell)
http://www . cs . cmu . edu/~beowulf
---------
During the Middle Ages, probably one of the biggest mistakes was not=20
putting on your armor because you were "just going down to the corner."
_______________________________________________
Insight-developers mailing list Insight-developers at public . kitware . com
http://public . kitware . com/mailman/listinfo/insight-developers
--__--__--
Message: 5
From: "Lorensen, William E (Research)" <lorensen at crd . ge . com>
To: "'insight-developers at public . kitware . com'"
<insight-developers at public . kitware . com>
Date: Wed, 21 May 2003 17:17:04 -0400
Subject: [Insight-developers] Draft Agenda for Pittsburgh meeting
Folks,
Here's a draft agenda. Please post comments. We can discuss on the =
t-con.
Bill
Thursday---------------------------------------------------------
9:00 - Introduction / Status (Terry)
+ Introductions all around
+ Status / organizational issues
9:45 - State of the system (GE)
10:00 - Recent Developments
+ ITK Software Guide (Kitware)
+ CMake (Kitware)
+ Wrapping (Kitware)
+ Statistics (UNC)
+ Quality/Regression Testing (GE)
12:00 - Lunch
1:00 - Potential New Features
+ Pervasive pipelining
+ Other?
2:00 - New Contractor Update 1
+ Dictionary (Iowa)
+ Analyze Plugins (Mayo)
+ SNAP Plugins (Cognitica)
+ Courseware Update (Stetton/Metaxas)
4:00 - New Contractor Update 2
+ SciRun Plugins (Utah)
+ VolView Plugin (Kitware)
+ RF Ablation (Georgetown)
+ FYI - Image-guided surgery toolkit (Georgetown/Kitware)
5:00 - Adjourn
6:30 - Dinner
Friday------------------------------------------------------------------
9:00 - Release Schedules (GE / All)
+ Dates / timeline
+ Transition plan (funding/ Insight Consortium, etc.)
10:00 - ITK Theory Book (Terry/All)
11:00 - Issues
+ Open discusssion
+ ITK community access to repository / developer mailing list
+ Policy on code contribution
+ Marketing efforts
12:00 - Lunch
1:00 - Planning, Conclusions and Action Items (Terry / All)
+ Review bug list / open issues
+ What needs to be done by September
3:00 - Adjourn
--__--__--
Message: 6
From: "Lorensen, William E (Research)" <lorensen at crd . ge . com>
To: "'insight-developers at public . kitware . com'"
<insight-developers at public . kitware . com>
Date: Wed, 21 May 2003 18:19:42 -0400
Subject: [Insight-developers] Pittsburgh Agenda (Rev 1)
Added breaks and adjusted afternoon schedule to 20 min sessions.
Thursday---------------------------------------------------------
9:00 - Introduction / Status (Terry)
+ Introductions all around
+ Status / organizational issues
9:45 - State of the system (GE)
10:00 - Break
10:20 - Recent Developments
+ ITK Software Guide (Kitware)
+ CMake (Kitware)
+ Wrapping (Kitware)
+ Statistics (UNC)
+ Quality/Regression Testing (GE)
12:00 - Lunch
1:00 - Potential New Features
+ Pervasive pipelining
+ Other?
2:00 - New Contractor Update 1
+ Dictionary (Iowa)
+ Analyze Plugins (Mayo)
+ SNAP Plugins (Cognitica)
+ Courseware Update (Stetton/Metaxas)
3:20 Break
3:40 - New Contractor Update 2
+ SCIRun Plugins (Utah)
+ VolView Plugins (Kitware)
+ RF Ablation (Georgetown)
+ FYI - Image-guided surgery toolkit (Georgetown/Kitware)
5:00 - Adjourn
6:30 - Dinner
Friday------------------------------------------------------------
9:00 - Release Schedules (GE / All)
+ Dates / timeline
+ Transition plan (funding/ Insight Consortium, etc.)
10:00 - ITK Theory Book (Terry/All)
11:00 - Issues
+ Open discusssion
+ ITK community access to repository / developer mailing list
+ Policy on code contribution
+ Marketing efforts
12:00 - Lunch
1:00 - Planning, Conclusions and Action Items (Terry / All)
+ Review bug list / open issues
+ What needs to be done by September
3:00 - Adjourn
--__--__--
_______________________________________________
Insight-developers mailing list Insight-developers at public . kitware . com
http://public . kitware . com/mailman/listinfo/insight-developers
End of Insight-developers Digest