David's Astronomy Pages Notes - Session 796 (2020-07-26)

Notes (S795)

Notes Main

Home Page

Notes (S797)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (4),  Continuous Improvement (4)
	SharpCap Update to v3.2.6383.0
	Images from 2020-07-26 >>
	2020-08-03
	PHD2 Update to v2.6.9
	AllSky Computer Outage due to A/C Adapter Failure
	Investigation - Potential Observing Sessions not utilised (2020-07-29 & 2020-08-03)
	2020-08-05
	Pegasus UPB - ASCOM Driver Updates, Jun/20
	AutoStart - New Observatory Mode

Session Aims & Highlights (2020-07-26)

Main aims

1. Comet NEOWISE. Take images of comet C/2020 F3 (NEOWISE)
2. Targets. Take images of a range of targets, taking advantage of the increase in nighttime darkness (one month on from mid-summer, 2.5 hours > 12 deg solar depression)
3. Dome Driver & AstroMain. Test out dome driver under Device Hub control. Look for any glitches which had hampered the previous two sessions (S792 & S793) that were under DeviceHub control and the issue that saw the session freeze upon entering  'Closing' state in last session (S795). Test AstroMain 3.26.

Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, PHD2,  DeviceHub 4.6.1.10, UPB 1.5 
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.8
   
• AstroMain 3.26,  AstroGuard 1.4.2,   AstroPlan 1.15.3,  AstroShCap 1.2.22, AstroVOE 1.3.6
  (AstroWeather 1.10.8, AstroAllSky 3.6)
  

Highlights

• Comet NEOWISE. Images of comet C/2020 F3 (NEOWISE) coma were acquired
•  Dome Driver / AstroMain.   No repeat of the dome driver issue or AstroMain freeze issue that had hampered the recent sessions.

Lowlights

• None

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Pre-Session Weather Forecast (API data from darksky.net) Pre-Session Weather forecast showed good condition (8-14% cloud cover) with light wind (9 mph) , no rain and a minimum temperature of 11°C. In the event conditions were clear the whole night (except for some light cloud around 00:50 - 01:30) with light wind and a minimum temperature of 8°C .

Session Event Log

Time     Event Detail 22:44:22 Session Created Live Session Created (2020-07-26 S00796, ImageSaveNum: 796001) 22:44:44   Obs.Manager Started Obs.Manager started 22:44:46   Obs.Overseer Started Obs.Overseer started 22:44:50   Services Started Observatory Services started 22:45:06   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 22:47:01   Services Started Observatory Services started 22:47:38   Camera1 Connected SBIG Camera Connected (set point -10°C) 22:48:06   Telescope Connected Telescope Connected (TheSky6) 22:49:01   Dome Opened Dome opened (opening time 43s) 22:50:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:53:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 22:53:51       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 22:56:05       Focusing Failed Foc2 Focusing Failed - failed QC check (Range) 22:56:45   UPB.Switch Restart UPB.Switch has been restarted. 22:57:09       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 22:59:34       Focusing Failed Foc2 Focusing Failed - failed QC check (Range) 22:59:56       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 23:02:21       Focusing Failed Foc2 Focusing Failed - failed QC check (Range) 23:02:57       Focusing Started Foc2 Focusing Started (Secondary Scope, using ShCap) 23:05:20       Focusing Failed Foc2 Focusing Failed - failed QC check (Quadratic) 23:06:02 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:06:07 Session Pending Session pending (2020-07-26) 23:06:09 Session Initiating Session initiating (2020-07-26) 23:06:11   Plan Requested Observing Plan requested from AstroPlan (1.15.3) 23:10:07   Plan Loaded Observing Plan loaded to queue (2020-07-26 V1 BEST PLAN, Plan ID: 526) 23:10:10   Camera1 Connected SBIG Camera Connected (set point -15°C) 23:10:15   Telescope Connected Telescope Connected (TheSky6) 23:10:27 Session Equilibration Session ready for dome & camera equilibration 23:10:31   Equilibration Started Dome Equilibration started 23:20:35   Equilibration Ended Dome Equilibration ended (10.1 mins total) 23:20:37 Session Running Session running 23:20:39   Queue Started Observing Queue started (17 targets selected) 23:20:41     Target Started (1/17) Target started (1/17, HIP 87937) 23:23:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:26:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 23:29:50     Target Completed Target completed (1/17, HIP 87937) 23:29:52     Target Started (2/17) Target started (2/17, Berkeley 45) 23:32:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:35:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 23:41:47     Target Completed Target completed (2/17, Berkeley 45) 23:41:50     Target Started (3/17) Target started (3/17, Berkeley 47) 23:43:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:46:46       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 23:52:09     Target Completed Target completed (3/17, Berkeley 47) 23:52:11     Target Started (4/17) Target started (4/17, GCVS CI Cyg) 23:54:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:56:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 00:00:27     Target Completed Target completed (4/17, GCVS CI Cyg) 00:00:29     Target Started (5/17) Target started (5/17, GCVS V Sge) 00:02:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:05:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:14:12     Target Completed Target completed (5/17, GCVS V Sge) 00:14:14     Target Started (6/17) Target started (6/17, GCVS CY Lyr) 00:15:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:18:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 00:21:57     Target Completed Target completed (6/17, GCVS CY Lyr) 00:21:59     Target Started (7/17) Target started (7/17, UGC 11435) 00:25:36       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:28:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 00:43:55     Target Completed Target completed (7/17, UGC 11435) 00:43:57     Target Started (8/17) Target started (8/17, C/2020 F3 (NEOWISE)) 00:46:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:49:50       Focusing Failed Foc1 Focusing Failed - failed QC check (Quadratic) 01:11:12     Target Completed Target completed (8/17, C/2020 F3 (NEOWISE)) 01:11:14     Target Started (9/17) Target started (9/17, GCVS S Cyg) 01:14:28       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:17:27       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 01:27:08     Target Completed Target completed (9/17, GCVS S Cyg) 01:27:10     Target Started (10/17) Target started (10/17, GCVS FG Sge) 01:29:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:32:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 01:34:31     Target Completed Target completed (10/17, GCVS FG Sge) 01:34:33     Target Started (11/17) Target started (11/17, SHK 361) 01:37:32       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:40:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 01:56:31     Target Completed Target completed (11/17, SHK 361) 01:56:33     Target Started (12/17) Target started (12/17, NGC 7625) 01:58:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:01:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 02:17:27     Target Completed Target completed (12/17, NGC 7625) 02:17:29     Target Started (13/17) Target started (13/17, Basel 12) 02:20:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:23:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 18) 02:29:59     Target Completed Target completed (13/17, Basel 12) 02:30:01     Target Started (14/17) Target started (14/17, GCVS SS Cyg) 02:31:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:34:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 19) 02:38:19     Target Completed Target completed (14/17, GCVS SS Cyg) 02:42:55     Target Started (15/17) Target started (15/17, WDS GRB 34) 02:45:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:48:01       Focusing Completed Foc1 AutoFocus Completed (Profile No 20) 02:49:50     Target Completed Target completed (15/17, WDS GRB 34) 02:51:11     Target Started (16/17) Target started (16/17, 61 Cyg) 02:54:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:56:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 21) 02:58:11     Target Completed Target completed (16/17, 61 Cyg) 02:58:13     Target Started (17/17) Target started (17/17, GCVS HH And) 03:00:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:03:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 22) 03:04:49     Target Completed Target completed (17/17, GCVS HH And) 03:04:50   Queue Completed Job Queue completed 03:04:55 Session Closing Session closing 03:05:50   Dome Closed Dome closed (closing time 50s) 03:06:10   Dome Parked Dome parked (parking time 20s) 03:07:00   Telescope Parked Telescope parked (parking time 45s) 03:07:30   Telescope Switched Off Telescope Power has been switched off via UPB Powerbox. 03:08:17   Services Stopped Night Services stopped 03:08:19 Session Housekeeping Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files) 03:08:34 Session Finished Session Finished

Session Alerts

Time     Alert Detail 22:56:44 UPB.Switch disconnected UPB.Switch has unexpectedly disconnected. Restart will be attempted

Back to Top

Operational Issues (2020-07-26, S796)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (4)
• Continuous Improvement (4)

[ Prev | Next ]

Critical Issues

• None

Major Issues

No major issues during session itself, but one issue cropped up during subsequent nights that is ranked as major due to its impact on Potential Observing and is captured below: 

• Nights with potential observing sessions are being missed due to marginal/poor weather forecasts (2020-08-01 & 2020-08-03).  Sessions were not initiated 2020-08-01 & 2020-08-03 as the evening weather conditions were cloudy and the weather forecast did show up obvious clear conditions for the coming night, yet the Night Summary plots show that clear intervals did develop during both night that could have (and should have) been used for observing/imaging. An investigation and review has been completed (see Investigation - Potential Observing Sessions not utilised (2020-07-29 & 2020-08-03) ) and a Continuous Improvement ticket created for introducing a new Observatory Mode called AutoStart  (see AutoStart Description & Design)
  Closed 2020-08-05, pending a Continuous Improvement Implementation (AstroMain 3.27+)

Minor Issues

• AstroPlan crashed whilst attempt to build observing plan.  AstroPlan crashed (reason unknown) leaving AstroMain waiting for plan. Program restarted and autobuild ran to generate plan. AstroMain automatically picked up the new observing plan and continued.  Issue not seen before.
  Resolved 2020-07-26 (Session,  Monitor for future occurance)
   
• Problem producing valid Focus Profile for Guidescope. Attempts to produce Focus Profile on a couple of different star fields failed during pre-session operations. After checking that the focus was more or less ok, the session was continued.    Examining the Profile it seems that the best focus position lay outside the range used for the profile and this is why a valid profile couldn't be achieved.   The issue highlights the previously recognised requirement for a precursive routine that examines focus quality over a wider range before selecting the approximate optimal range to autofocus upon.
  Issue understood and awaits new functionality (AstroMain)
   
• Session Web Page still showing Target Info 13/13 from last session.  TargetInfo Charts should be automatically set to a small null image at start of session and uploaded before Target 1 and Target 2 Info have finished uploading such that TargetInfo chart from last session should never be showing.   NightSummary6 plot also not being updated.  Issues were due to AstroPlan crashing before it had finished uploading initial session charts to WebSite.  TargetInfo chart issue resolved itself after Target 3 started. NightSummary6 plot issue was manually resolved by uploading null NightSummary6 plot that resets the correct loading of NightSummary plot
  Closed 2020-07-26 (Session)
   
• Focus Profile FWHM results don't seem to correspond with data plotted on Focus Profile charts.  For example for Target HH And (profile 22) the peak FWHM is given as 2.63"  (zen FWHM 2.59") whilst focus profile chart appears to show FWHM peaking at around 1.5".   The FWHM results are consistent with the table of individual FWHM measurements in report file.  Graphs were plotted againist a Y Axis labelled 0- 15 arc sec and it would seem that either the data is plotted in wrong position and/or the axis labeling/grid are wrong.  Examining the chart in more detail indicates whilst Y axis is labelled 0 - 15, the data plotting is consistent with a 0 - 30 axis range.  Manual changes to the Y axis range were made during manual mode focusing at the start of the session.     Manual toggling of Y Axis scale successively changes Y max from 12, through 15, 20, 30, 8 and back to 12.  It seems that grFocusProfileYMax was left at 30 following manual mode focusing.  Focus Profile graph is drawn by the routine DrawGraphFocusProfile().  Exmaining the behaviour of the routine indicates that when  grFocusProfileYMax > 20 (specifically when grFocusProfileYMax = 30 & yStep = 2) a bug causes incorrect Y Axis labels to be drawn. Bug was fixed by changing the statement 'LabelValue = LabelValue + LabelInc' where LabelInc = 1 (in all cases), to 'LabelValue = LabelValue + yStep'  
  Fixed 2020-07-29 (AstroMain 3.26.1)

Continuous Improvement

• Automated Focus Profile Graphs to be initiated with 0 to 12 arc sec range for Y Axis.  Automated Foc1 focus profile charts for session S796 where drawn based on a 0 - 30 arc sec Y Axis range (labelled as 0 - 15 due to a bug), as grFocusProfileYMax was left at 30 following Manual Mode focusing of Foc2 focuser.  When starting automated focus profiles grFocusProfileYMax should be reset to 12.
  Done 2020-07-29 (AstroMain 3.26.1)
   
• Add a precursive focusing routine  to roughly identify approximate best focus over a wider range than can be achieved using existing automated curve fitting. When focus position has changed significantly between sessions, normal automated quadratic curve fitting focusing fails to find a bets focus position as best focus position lies outside the chosen focus positon range. A new percursive routine is required that operates over a wider focus range, and identifies approximate best focus from lowest FWHM values which is then used as the basis for choosing the focus range to be used for the standard automated focusing.
  Done 2020-07-29 (AstroMain 3.26.1 / AstroShCap 1.2.23 )
   
• Performance of Foc2 Focus Profile to be speeded up when using Sim Image. When using a Sim Camera/Sim Image a full frame image is loaded to CCDSoft and the process of analysing stars, finding Max Pixel is particularly slow. Testing of Foc2 imaging can be speeded up if a smaller focus frame box image could be used.  Normal focus Image is replaced by a small image : "C:\Data\ZWO Imaging\SharpCap\Foc2 Tests\Focus_02_8871.fits"
  Done 2020-07-29 (AstroMain 3.26.1)
   
• Introduce a new 'AutoStart' observatory mode which the user can activate anyyime during day or evening if the night conditions are judged to be safe (with no storms/heavy rain etc)  , but the chances of clear intervals are too uncertain to warrent creating a session or staying up late to create session should conditions clear.   Once activated the Obs.Manager enters a new Waiting (Auto) state in which conditions and sun alt / time are monitored through the evning/night and if acceptable criteria are met a New Live Session is created, Night Services are begun (including powering up the Telescope) and the Observatory placed into normal Automated mode to conduct the live session. See description of new AutoStart Observatory Mode
  Done 2020-08-06  (AstroMain 3.27)

[ Prev | Next ]

Back to Top

SharpCap Update to v3.2.6383.0

New Development Version of SharpCap (v3.2.6383.0, dated 2020-07-04) installed onto Observatory and Office Computers today 2020-07-26

https://www.sharpcap.co.uk/sharpcap/downloads

Back to Top

2020-08-03

PHD2 Update to v2.6.9

New Version of PHD2 (v2.6.9, dated 2020-07-04) installed onto Office Computers today 2020-08-03.   Observatory Computer was already at v2.6.9.

https://openphdguiding.org/downloads/

Back to Top

AllSky Computer Outage due to A/C Adapter Failure (2020-08-03)

Data from AllSky Computer was noticed (at 09:00) to have gone offline at c. 05:00 this morning (2020-08-03). Investigating eventually established that there was a problem with the Laptop's ASUS A/C Adapter and the laptop's battery had become heavily depleted.  An equivalent laptop A/C Adapter (19v) was employed as a workaround to provide a charging source, and the weather data monitoring reenabled at 01:00 (giving a Weather Data Outage of 8 hours).

There had been thunderstorms in the previous 12 hours and it is possible that a lighning induced power surge had possibly been involved in the failure of the A/C adapter or it could have been pure coincidence that the A/C adapter had failed at this time.   Any surge should have been surpressed by Surge Protector built into the Power Strip.

Back to Top

Investigation - Potential Observing Sessions not utilised (2020-07-29 & 2020-08-03)

Issue:  Sessions were not initiated on 2020-07-29 & 2020-08-03 as the evening weather conditions were cloudy and the weather forecast did show up any potential clear conditions, yet the Night Summary plots for both nights showed sufficiently clear intervals that could have (and ideally should have) been used for observing/imaging.

2020-07-29

Weather Forecast for 2020-07-29 Weather forecast for the night (generated at 21:00) shows dry & relatively calm conditions (4-9 mph wind) but with fairly significant cloud cover (starting at 76% at dusk and rising to 92%  in middle of night, and then increasing to 98% by dawn , av. for night : 93%). Temperature 13 degC falling to 10 degC by dawn.  No rain in forecast until 10:00 the following day. (API data from darksky.net)

Actual Weather for 2020-07-29 In the event conditions were dry and fairly calm throught the night. After 100% cloud at dusk , the sky gradually cleared between 23:30 and 00:45 becoming clear with 30+ AllSky Stars from 00:45 until dawn

Cloud Sensor & Stars Plot - 2020-07-29

Night Sky Summary Plot - 2020-07-29

Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

2020-08-03

Weather Forecast for 2020-08-03 Weather forecast for the night (generated at 21:00) shows dry & relatively calm conditions (3-6 mph wind) but with fairly significant cloud cover (73% falling to 58-59% in middle of night, and then increasing to 88-100% by dawn , av. for night : 68%). Temperature 14 degC falling to 11 degC by dawn.  No rain in forecast until 09:00 the following day. (API data from darksky.net)

Actual Weather for 2020-08-03 In the event conditions were dry and fairly calm, but with cloud clearing at 23:00, then moderately clear / patchy cloud between 23:00 and 01:20, and then clear to fairly clear between 01:20 and 03:30.

Cloud Sensor & Stars Plot - 2020-08-03

Night Sky Summary Plot - 2020-08-03

Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Proposed Solution

Proposed solution to the issue is to introduce a new 'AutoStart' observatory mode which the user can activate anytime during the day or evening if the night conditions are judged to be safe (i.e no storms/heavy rain etc), but the chances of clear intervals are too uncertain to warrent going to the effort of creating a session on the off-chance or staying up late to create session should conditions clear.   Once activated the Obs.Manager enters a new Waiting (Auto) state in which weather conditions and sun alt / time are monitored through the evening/night and if acceptable criteria are met a new Live Session is created, Night Services are begun (including powering up the Telescope) and the Observatory placed into Fully-Automated mode to conduct the live session.

This has the advantage that a new Session is only created if/when conditions are safe and suitable for observing.   This prevents Latest Session Web Page being overwritten with blank charts/data from a new session which may not execute any imaging. 

The new mode is detailed in the section 'AutoStart - New Observatory Mode'

Back to Top

2020-08-05

Pegasus UPB - ASCOM Driver Updates, Jun/20

Updated ASCOM Drivers for Pegasus Astro UPB (dated Jun 2020) were installed onto the Observatory & Office Computers today 2020-08-05:
 
- Observing Conditions Driver v1.5  (Jun/20)
- Focuser Driver v1.6 (Jun/20)
- Switch Driver v2.2 (Jun/20)

https://pegasusastro.com/support/

Back to Top

AutoStart - New Observatory Mode

Following an investigation & review after two potential observing session were not utilised (see Investigation - Potential Observing Sessions not utilised (2020-07-29 & 2020-08-03) ) it was proposed to introduction a new observatory mode called 'AutoStart'

Note:  Whilst the AutoStart is for now called a new Mode with its own Waiting State which will be actioned and behave differently from the current Fully-Automated Mode, it may eventually be relegated to being a just a new alternate start up state for the Fully-Automated Mode.

Descripton

'AutoStart' is a new observatory mode for the Observatory's AstroMain program, that will sit alongside the two existing modes 'Manual' and 'Fully-Automated'.   The user can activate the new AutoStart mode anytime during the day or evening if the coming night conditions are judged to be safe (with no storms/heavy rain etc), but the chances of clear intervals are too uncertain to warrant creating a session (with a new session number) or require staying up late to create a session should conditions clear.   Once activated the Obs.Manager enters a new Waiting (Auto) state in which conditions and sun alt / time are monitored through the evening/night and only if acceptable criteria are met a new Live Session is created, Night Services are begun (including powering up the Telescope) and the Observatory placed into Fully-Automated mode to conduct the live session.

Benefits

The principal advantage of the new AutoStart mode are :

• Observing Time. If AutoStart is used sufficiently often it should increase observing time due to decreased requirement to commit to an session creation in marginal conditions
   
• Probability of Session Revoke. A new session is only created if/when conditions are safe and suitable for observing.  
  This prevents a database session number being created which might need to be later revoked
   
• Latest Session Web Page. It helps prevent the Current/Latest Session web page being overwritten with blank charts/data from a new session which may not actually execute due to insufficiently clear skies.
   
• Session Start Time. The session is activated at a time that is potentially closer to the observing window.   This allows
   - additional time for last minute additions/modifications to the Target Database
   - allows charts,  such as the CCD Temperature and Focus Temperature charts,  to be more relevant to the actual observing period.

The User

• Judgement.  Although usual safeguards are expected to always be in place (Weather Monitoring, Dome Relay tied to Cloud/Rain Sensor), the user is still required to judge observatory safety risk for the coming or current night
   
• Action.  The user had to take the action of placing the Observatory into the AutoStart Mode.  This can only be done for the coming/current night.   If not used (i.e. a session is not executed)  AutoStart Mode is automatically cancelled at or before daybreak.
   
• Remote Monitoring.  Although a completely automated session is possible the user is still advised to check progress of AutoStart / Session from time to time using WebPage or VNC.  It is strongly advised that the user checks that the Observatory has successfully closed and shutdown at the end of the planned session or at dawn. 
  

Requirements

• Operational Time Window. A time Window has to be set  and define the period in which AutoStart can create/commence a Live Session.
  Default times to be based on some form of SunAlt +/- x Mins  (with possible option for the user to override ?)
   
• Earliest Start Time. AutoStart won't create & commence a session before the earliest operational time.
   
• Cancellation of AutoStart.  If conditions don't allow a Session to begin before the end of the operational time window, AutoStart Mode is cancelled and the Observatory is placed back into Manual Mode.   This is to prevent a session was unexpectedly or unsafely starting the following night.  (User has to always initiate AutoStart Mode on the day/night that AutoStart will be run).   AutoStart Mode can be cancelled by the user and the Observatory returned to Manual Mode.
   
• No waiting for user input. After initial checks have been completed and the Observatory is placed into AutoStart Mode there must be no manual Dialog Boxes which user has to acknowledge for the code to proceed. Existing dialog boxes for example Confirm Ok before powering up the telescope have to be by-passed when in AutoStart Mode
   
  
• Extra Checks. Since AutoStart involves an even greater level of automation than current operations, extra checks need to be put in place to ensure all relevant hardware & software is started /communicating before proceeding with the actual Live Session

AutoRun Criteria

• Conditions.  Criteria for running AutoRun are expected to be similar to those used for judging safe & acceptable conditions for opening the Observatory that are used by existing Equilibration & Resume states. Criteria may be slightly stricter to ensure that conditions are stable and not quickly revert to cloudy or otherwise poor conditions.
   
• Time Window. Criteria will take into account the operational time window presented / modified / accepted when AutoStart Mode was initiated by the user.

AutoRun Sequence

• Check software/hardware state (Weather Data, Dome, Focuser etc)
• Create Session
• Select and start Night Services (Telescope, PHD2 Connection, SharpCap Server etc)
• Check that Services are working
• Move To Fully-Automated Mode

Risks:

• Not all supporting software starts up and is available for Session to successfully proceed
  >> Extra checks need to be put in place to ensure associated software (PHD2, SharpCap) is up and running when AutoStart Mode is initiated
   
  
• User is not aware about state of the AutoStart progress because a Session hasn't been created and Report/Log File data is not neccessary uploaded to Latest Session WebPage
  >> Extra data about state of the AutoStart progress needs to be sent to Current/Latest Session web page without unnecessarily overwriting Last Session information until the New Session is actually created.
   
  
• Not all supporting services and hardware start up and are available for the Session to successfully proceed
  >> Extra checks need to be put in place to ensure all required services are hardware (Weather Data, Telescope etc) are up and running before executing the session in a Fully-Automated mode
   
• Conditions could still deterioriate between AutoStart creating a session (when conditions were acceptable) and being ready to actually open the observatory and begin observing
  >> Accept residual risk,  it is less than risk when beginning an Automated Session early in evening and/or is less than the risk consequence of not observing when conditions turned out to be good later in night and a Session wasn't initiated.
   
• Risks to Telescope, especially if an observing session doesn't take place ?
  Does scope tracking need to be turned off after initial connection ?.  
  In the morning does scope need to be Parked and Power turned off by AutoStart if session hasn't taken place ?
  (would this need to be done manually, or need to be automated with suitable checks).
  >> In practice Scope is Only Powered Up / Connected if Session is to immediately go to Fully Automtated, which would normally SetTrackingOff due Staring process and would normally Park Telescope and Power it down during the Closing State at end of session)

Development, Testing & Deployment

• 1st Test Code : Proof of concept test version coded in AstroMain 3.27  (2020-08-05)
• 1st Test Version : Working code ready for live test, AstroMain 3.27  (2020-08-06)
• 1st Live Test : Live test, AstroMain 3.27  (2020-08-06, S797 Attempt)
   
  
• 2nd Test Version : Fixes and improvements to AutoStart routines, AstroMain 3.27.1  (2020-08-07)
• 2nd Live Test : Live test, AstroMain 3.27.1 (2020-08-08, S797)
   
• 3rd Test Version : Fixes and improvements to AutoStart routines, AstroMain 3.27.2  (2020-08-08 / 2020-08-09)
• 3rd Live Test : Live test, AstroMain 3.27.2 (2020-08-09)
  
  
• 4th Test Version : Fixes and improvements to AutoStart routines, AstroMain 3.27.3  (2020-08-10)
• 4th Live Test : Live test, AstroMain 3.27.3  (TBA)
  

Back to Top