[SCHEDULER-396]  Problems with Best Efforts Plans
Type Bug
Priority Low
Severity Trivial
Component Dispatch Scheduler Engine
Fixed In Version [3.3] 3.3
Versions Affected [3.2] 3.2
Severity Closed
Resolution Cannot Reproduce
Reported By Bob Denny
Resources Bob Denny
Start Date 3/29/2010

Description 
See this Comm Center thread. It does sound like a corner-case logic bug. This turned out to uncover several problems:



    
    
  1. In his submitted database, AS_Leo was marked Pending (Obs in Best Efforts Plan would not meet constraints), yet the Observation was marked Complete (Obs would not meet constraints).
    2. 
    
  2. The ImageSets were still marked Pending.
    3. 
    
  3. The error he got indicated that the Plan was attempted but no Observations were found, which reflects the state in (1).
    4. 



Best Efforts general review resulted from this.

Comments
11/26/2010 3:24:44 PM   Bob Denny 
Cannot repro original problem. Even with the Plan pending, and the Obs Completed (initial conditions in the DB he sent), the dispatcher fixes that to Obs Pending, then acquires it.
11/26/2010 3:12:11 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

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

 

  SVN Revision
  111
 

 

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

 

 

  Check-in comment
  Improvements to Best Efforts
GEM:396
11/26/2010 1:46:14 PM   Bob Denny 
Interesting... Resubmitting the Plan in the desktop browser did not clear the Completed status for the Observation! However, if I switched from All Users to the specific user Hambsch, it shows Pending.
11/26/2010 12:08:12 PM   Bob Denny 
The problematic plan looks like this:
















Clearly a bogus state for the Observation! This is probably related to the inconsistent Observation states I have seen occasionally when resubmitting.  projects. The Plan is marked Best Efforts. And check this:

















For some reason resubmitting didn't fix this? Or was it caught by the dispatcher right after resubmitting, evaluated, found to be unable to meet constraints, then marked complete instead of failed?
5/5/2010 2:39:50 PM   Bob Denny 
Repro scenario with database is now available in this thread, in the 03-May message from Tom.
3/29/2010 12:59:13 PM   Bob Denny 
Awaiting a repro scenario from Tom. Can't reproduce it so far.