Asynchronous Reasoning and Learning (ARL)

Objective: Asynchronous Case-Based Reasoning and Learning for Transfer Learning in Wargus/TIELT

Project documentation

KB Articles

Project milestones

Project plan

• Infrastructure
  • Define and create directory structure (Chip)
    • project name: arltl - done
    • directories: etc (build, config/xml, images, ...), lib (external, jars, tielt, ...), src, doc (javadoc, specs/uml, ...) - done
  • Users and permissions in CVS (Chip)
  • Select and setup issue tracking system (Chip)
    • setup bugzilla via CNS - done
    • define workflow (open, solved, verified, closed)- done
  • Setup domain (Michael)
    • Determine TIELT platform (Windows?) and insulate from client platform (Windows, Mac, Unix, cross-platform) - done
    • Setup TIELT - done
    • Setup Wargus - Changed to MadRTS
    • Select and code Wargus scenario in Wargus/TIELT (Manu) - Chaged to MadRTS
• Specs and Docs
  • Sketch XML configuration schema (Juan)
    • Executive config - done - configuration.xsd in CVS/doc/specs
    • Module config - done - configuration.xsd in CVS/doc/specs
    • Command line arguments can override XML config parameters
  • Agree on and document KB articles on: (everyone, Juan to collect)
    • coding conventions - eclipse default styleguide
    • instrumentation methodology (debugging, logging, levels–critical/warning/info/performance, comments, ...)
    • build procedure (setup local area, build scripts, ...)
    • source control procedure (checkin/checkout rules, ...)
    • command line arguments (debug level, config path, ...) and defaults
  • Platform decisions
    • collaboration (swiki, email list)
    • source control (cvs)
    • testing (junit)
    • logging, debugging, levels (log4j)
    • language (JVM v5)
    • documentation (UML specs, javadoc)
    • dev environment (developer's choice: default = eclipse, emacs, ...)
    • build (ant)
    • issue tracking (bugzilla)
    • dev environment (cross-platform: Windows, Mac, Unix, ...)
  • Define package for external delivery (long-term goal)
• Development
  • Package naming scheme: edu.gatech.cc.arltl.*

1. Iteration 1
   • Implement packages (stub interfaces and factories)
     • Agent (Manu) - done
     • Planner (Chip) - done
     • Learner (Michael) - done
     • Controller (Chip) - done
     • Driver (Juan) - done
     • Model (Michael) - done
   • Implement "simple" (dummy) classes
     • Executive (Driver) (Juan) - done
     • BasicAgent (SimpleAgent) (Manu) - done
     • BasicPlanner (Chip) - done
     • BasicLearner (Michael) - done
     • BasicController (Chip) - done
   • Implement Model classes (-next time-, Juan to put thought into this)
     • Blackboard - done
     • State (base class) - done
     • Action (base class) - done
   • Implement interface to World (Michael)
     • Simple MDP (Asteroid Lite)
2. Iteration 2
   • Implement "simple" alogirhtm classes
     • Add XML node for Environment interface to XML controler node - Juan
     • Memory-based planner - Manu
     • Simple probabilistic planner - Michael
   • Implement Model classes
     • Incorporate Sensor class into Blackboard - Michael
   • Implement interface to World - Michael
     • Implement new Environment class to interface with TIELT
     • TIELT - Asteroid Lite - optional - Michael
     • TIELT - MadRTS - Michael