I only noted a couple of things from yesterday's Visit Planner
   review. Let me know if you picked up on anything else.

      * It would be nice to give an indication on each visit if the
        schedulability is good or marginal.  It's not clear how to do that.
        A crude way would be to use the percentage of days in the year which
        are schedulable and use that to indicate how good is the chance that
        the visit will schedule.

     * It would be nice to indicate to users which orbits in the observing
       cycle are SAA hiders.  Maybe display an auxilary calender that shows
       this.  (Rob thought that if this information is already readily
       available in Spike, then maybe it would even be worth doing in
       the DG since the DG work would be very minor.)

   Unless the VP requirements group thinks otherwise, I don't think we
   need to meet again until we start thinking seriously about the
   January 2003 release.  I'll start thinking about them next Spring
   and decide how much ahead we should start working them.

   Thanks to everyone to who helped out to get the requirements
   drafted and to Chris for presenting them at the review.