Personal tools
You are here: Home → Project Info → LANDIS-II v6.0 → Iteration 7
Log in


Forgot your password?
New user?
 

Iteration 7

Continuing the Construction phase, the goal of this iteration is to refine succession and begin modifying the Core utility module. Work will also begin on documentation and user widgets.

  • Phase: Construction
  • Dates: July 14 - August 3rd, 2010

Tasks

  • Core Framework
    • Srinivas: Finish any remaining tasks for Main, PlugIn, Species, Ecoregions.
    • Srinivas/Rob: Refactor Succession. First, generate a document (using DOxygen?) that lists all the classes and functions in the base succession library. Next, we will review the document and decide how to refactor base succession to provide maximal flexibility to future developers. After review, modify base succession as necessary.
    • Begin work on Core utility library, replacing random number generation with the Troeschutz random number library.
    • Sridevi/Rob: Demonstrate web-based user widgets. Refine based on my feedback.
    • Sridevi: Create DOxygen files for every c# project in the core. (Highest Priority).
    • Jimm: Mull over where the new RasterIO class and the new IUserInterface belong.
    • Jimm: Write a code snippet demonstrating how new Random Generator will work within extensions.
    • Jimm: Develop a plan for linking the two LSMLs to the Core. Implementing the plan will be the focus of iteration 8.

Assessment

  • Core Framework
    • Almost all tasks completed for Main, PlugIn, Species, Ecoregions. Sri will double-check. Some low priority items may not happen.
    • Replaced random number generator with Troschuetz Random Number library.
    • Core framework redesigned into an API and an Implementation (including RasterIO).
    • A plan has been developed for including LSMLs into the Core (see iteration 8 plan).
  • Other
    • User widgets abandoned due to time/budget constraints
    • Doxygen files created.
  • Lessons Learned
    • Troschuetz random number library dll must be in the bin/ directory.
    • DOxygen documentation may not be the best option for our audience.
  • Hit and Misses
    • Hit! Nearly all tasks completed.
    • Hit: Good communication working closely together.
    • Miss! Widgets had to be abandoned; student let go.
Document Actions