Iteration 4

• Phase: Elaboration
• Dates: April 22 - May 20, 2010

Tasks

Architecture

• Finish GDAL proof-of-concept
• Move relevant tasks from LANDIS-II web site to Google Code web site

Student Tasks

• Finish utility library tasks, including DOxygen
• Create project and solution files for all active extensions. For libraries, migrate and run tests.
• Commit project and solution files to repository.
• Review project/solution files with Rob and Jimm, particularly the tests.
• Remove cohorts from the Core

Assessment

Architecture

• Jimm completed the GDAL proof-of-concept. It runs on OS X, and consists of 4 projects:
  • the public API of the spatial library,
  • an implementation of the library's API using GDAL,
  • a sample extension that uses the library to write a 2-band ERDAS Imagine raster, and then to read it back in, verifying its pixel data; and
  • a sample program that runs the sample extension.
• Jimm reviewed the to-do list for the geospatial library. Each task was assessed and was deemed done or irrelevant, or was moved to the library's issue tracker at Google Code.

Student Tasks

• Sridevi made progress on two tasks for the Utility library (adding copyright notices and license information to source files).
• Srinivas added project and solution files to all the active extensions, as well as the libraries used by them. Rob reviewed these new files. The files have been committed to the repository.
• The core's to-do list has been divided among the students. Srinivas has been assigned the cohort module, and Sridevi has been assigned the remaining modules (Main, Plug-ins, Ecoregions, Species). Each student is developing a comprehensive strategy to address their assigned tasks, which they will review with Rob before proceeding.

Lessons learned

• By default, Visual C# 2010 targets NET 4.0. But extensions compiled for NET 4.0 aren't compatible with LANDIS-II 5.1, so the new project files had to be reconfigured to target NET 3.5 instead.
• Need to document how to construct project files for the extensions' and libraries' unit tests. These files have already been created for core's tests; so need to review these to identify the steps for building and running a set of tests.
• Need to more closely monitor student hours spent per task to ensure they get assistance in a timely manner when they get bogged down.