[SCHEDULER-1583]  Operator Intervention on "too many" ACP Observation Errors
Type New Feature
Priority High
Severity Minor
Component Dispatch Scheduler Engine
Fixed In Version [9.09.0
Versions Affected [8.38.3
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 7/12/2021

Description
See this Comm Center thread by Steve Reilly. Sometimes his rotator just disconnects, and the effect is that ACP fails every Observation thereafter. The effect is to fail possibly every Observation that might otherwise run in a night!

Add a new setting "max consecutive failures" and put the scheduler into Operator Intervention state if that number of consecutive failures is exceeded.

Comments
10/28/2021 11:23:46 AM   Bob Denny
SVN Comment
Author rbdenny
Repository svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
SVN Revision 898
Affected files /trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/ConfigForm.cs (Modified)
/trunk/Scheduler/Engine.cs (Modified)
Check-in comment Consecurive failure limit - Add 0 to disable, allow 100 max. GEM:1583
9/3/2021 4:20:25 PM   Bob Denny
REOPENED

See this Comm Center thread by Peter Prendergast. Must allow 0 to disable this.
7/12/2021 8:40:01 AM   Bob Denny
SVN Comment
Author rbdenny
Repository svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
SVN Revision 879
Affected files /trunk/Help/RelNotes.htm (Modified)
/trunk/Scheduler/ConfigForm.cs (Modified)
/trunk/Scheduler/Engine.cs (Modified)
Check-in comment Add "consecutive ACP failure detection and transition to operator intervention. GEM:1583
4/19/2021 6:45:27 AM   Bob Denny
Another request from Steve... This needs to be done. Maybe tie into GNS. Also note Peter Hanna's request in SCHEDULER-1772.
6/8/2020 10:29:03 AM   Bob Denny
Note my message in reply to Peter Prendergast
6/5/2020 4:23:16 PM   Bob Denny
Do this for the next release. It is a great idea. It was asked for again in this post by Peter Hannah (never mind the title, it ends up being the same thing)