[SCHEDULER-326]  Observations with repeat count terminate early
Type Bug
Priority Medium
Severity Major
Component Dispatch Scheduler Engine
Fixed In Version [3.2] 3.2
Versions Affected [3.2.1] 3.2 dev
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 11/20/2009

Description 
Without explanation, a non-best efforts plan with an Observation having "lots" of repeats quits early with a message ***Running Plan xxx (best efforts) completed early: Obs yyy would not meet constraints. This is bogus.

Comments
11/21/2009 12:06:38 AM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  78
 

 

  Affected files
  /trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/Engine.cs (Modified)

 

 

  Check-in comment
  More 3.2 - Skip last minute constraint checks for non-best-efforts. All constraint checks now account for completed repeats of Observation.
GEM:326
11/20/2009 11:38:11 PM   Bob Denny 
Step 9 needs better error messages in case it is tripped as an assert instead of working for Best Efforts.
11/20/2009 11:36:53 PM   Bob Denny 
Caused by the "Step 9" check in the observation set count loop. The call to TestConstraints() does not take into account the number of repeat sets that have been completed!! It is available in the Observation's SetsCompleted property.