Section 1.2.4 of the book, with title "Directory Structure", <br>has some misleading (incorrect ?) information.<br><br><br>The second paragraph says:<br><br><br>IGSTK is organized into several different modules, or CVS checkouts. If you are using an<br>
official release, you will see three important modules: the Source, Testing, and Examples<br>modules. The source code can be found in the Source module; testing code, input data, and<br>baseline images can be found in Testing; and example applications using IGSTK are available<br>
in Examples directory. There is also an Utilities directory containing some auxiliary scripts.<br>The Source directory contains all the components of IGSTK. When you are working with this<br>library, you can refer to the code in Testing and Examples to learn how the classes are being<br>
used.<br><br><br>This is confusing subdirectories with CVS modules.<br><br>The CVS modules of IGSTK are:<br><ul><li>IGSTK</li><li>IGSTKSandbox</li><li>IGSTKDocuments</li></ul><br>Referring to the subdirectories "Source", "Testing" and "Examples" as "CVS modules" <br>
is incorrect.<br><br>We probably should refer to them simply as "directories" or "subdirectories".<br><br>Something like:<br><br><br>IGSTK is organized into several different subdirectories. If you are using an<br>
official release, you will see three important subdirectories: the Source, Testing, and Examples<br>
subdirectories. The source code can be found in the Source subdirectory; testing code, input data, and<br>
baseline images can be found in Testing; and example applications using IGSTK are available<br>
in Examples directory. There is also an Utilities directory containing some auxiliary scripts.<br>
The Source directory contains all the components of IGSTK. When you are working with this<br>
library, you can refer to the code in Testing and Examples to learn how the classes are being<br>
used.<br><br><br> Luis<br><br><br>