[SCHEDULER-1712]  Scheduler fails if started in unsafe weather during night
Type Bug
Priority High
Severity Minor
Component Dispatch Scheduler Engine
Fixed In Version [8.3] 8.3
Versions Affected [8.2.2] 8.2.2
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 10/25/2019

Description 
See this Comm Center thread by Stacey Mills. If dispatcher is enabled during the night, and if Close-If-Idle is enabled (> 0) this it is possible for DoSchedulePass() to calculate BestPlan, which needs the scope current RA for meridian crossing test, before it starts the observatory. Need to start when there is at least one Plan with a ready Observation but avoiding Efficiency() function. This will require extreme care and a full regression test suite, plus field testing.

Comments
10/31/2019 10:42:18 AM   Bob Denny 
Positive reports, closing.
10/31/2019 10:40:38 AM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

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

 

  SVN Revision
  819
 

 

  Affected files
  /trunk/AcquireScheduler.vbs (Modified)
/trunk/AltAzRotationConstraint/AltAzRotationConstraint.csproj (Modified)
/trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/AssemblyInfo.cs (Modified)
/trunk/Scheduler/Engine.cs (Modified)

 

 

  Check-in comment
  GEM:1735 Combined commit for Comet element detection of interstellar I comets (e.g. 2I/Borisov) and for scheduler failing if started after dark in unsafe weather. 
GEM:1712
10/25/2019 4:35:56 PM   Bob Denny 
I took the easy way out. Simply assume no meridian crossing if the scope is not available. Took some time to look for other possible traps. None found. this should be it. Tested thoroughly with what I have here.
10/7/2019 12:51:35 PM   Bob Denny 
Another report, this time from Peter Prendergast.