[SCHEDULER-804]  Enhancement to Rising Plan Delay?
Type Enhancement
Priority Low
Severity Trivial
Component Dispatch Scheduler Engine
Fixed In Version [8.28.2
Versions Affected [3.43.4
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 8/9/2014

Description
See this Comm Center thread.

Comments
9/11/2018 8:07:42 PM   Bob Denny
SVN Comment
Author rbdenny
Repository svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
SVN Revision 712
Affected files /trunk/Help/Advanced.htm (Modified)
/trunk/Help/Concepts.htm (Modified)
/trunk/Help/Home.htm (Modified)
/trunk/Help/Scheduler 2018.pdf (Added)
/trunk/Scheduler/Engine.cs (Modified)
/trunk/White Papers/ACP Scheduler/Scheduler 2014.pdf (Added)
/trunk/White Papers/ACP Scheduler/Scheduler 2018.docx (Added)
/trunk/White Papers/ACP Scheduler/Scheduler 2018.pdf (Added)
Check-in comment Clean up of Rising Plan Delay to give more reasonable lead time before the meridian. Including an old white paper PDF too. GEM:804
9/11/2018 7:03:45 PM   Bob Denny
I was close. This is doing just what its supposed to do per the white paper except for the one hour buffer. Now the lead is 10% of the time span of the Plan. Tested rather thoroughly.
9/11/2018 1:49:16 PM   Bob Denny
REOPENED

Looking at this with a fresh start due to the above and some unusual behavior I have noticed. 
8/9/2014 2:03:54 PM   Bob Denny
It bridges the meridian, so this is not a problem.
4/6/2012 5:33:58 AM   Bob Denny
At present the rising plan delay will delay the plans as much as it can provided it does not breach the three limits. In practice, most of the rising plans will be delayed till it reaches transit. In effect, we'll be imaging mostly on the west side of the sky instead of on both sides of the meridian. Will this effectively limit our imaging time window? Furthermore, if we have already completed imaging all targets on the west side, Scheduler still waits until the rising plans reach transit. Which was what I observed the other day and perhaps not an optimal use of available imaging time.

Does it make sense to have a user configurable "No Delay Zone" which defines the maximum rising limit scheduler will allow? This is specified as hours before transit. For example, if "No Delay Zone" is set as 1.5 hours, then scheduler will only delay rising plans up to 1.5 hours before transit. Which means imaging for the target can start 1.5 hours before reaching the meridian.