David's Astronomy Pages Notes - Session 1133 (2023-08-21)

Notes (S1132)

Notes Main

Home Page

Notes (S1134)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (0),  Small Defects (2),  Continuous Improvement (2)
	Images from 2023-08-21 >>

Session Aims & Highlights (2023-08-21)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions
2. AstroMain.  Continue to check new AstroMain version (3.62.8) for recent fixes & improvements

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.11dev4, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
   
• AstroMain 3.62.8, AstroPlan 1.38.2,   AstroShCap 1.3.15, AstroGuard 1.10.2
  AstroVOE 1.13  AstroSN 1.10,  AstroProtect 1.7,  AstroMove 1.12.4
  (AstroWeather 1.21.2, AstroAllSky 3.19.1,  AstroObsCam 1.11.4, AstroLaunch 1.10.9 (1.11.1 on Dev Computer)

Highlights

• Targets. 4/18 planned target were completed, with 2 other targets partially completed.
• AstroMain. New AstroMain version (3.62.8) operated ok but fails to fully fix the issue whereby Start Observatory Services can stall whilst starting SharpCap service.
• Dome Slews. No dome slews were affected by any significant hold-up (Hold Up Stats: 0/9 slews affected, 0%, 0.0 minutes total hold-up time). 

Notes:

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)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 22:30:21 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:30 & 03:26 22:30:26 Session AutoStarting Session autostarting (22:30) 22:30:55   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 22:31:08 Session Created Session Created (Live, 2023-08-21 S01133, ImageSaveNum: 1133001) 22:31:35   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 22:38:36   Services Started Observatory Services started 22:38:43 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:38:47 Session Pending Session pending (2023-08-21) 22:38:49 Session Initiating Session initiating (2023-08-21) 22:38:51   Plan Requested Observing Plan requested from AstroPlan (1.38.2) 22:39:50   Plan Loaded Observing Plan loaded to queue (Plan ID: 907) 22:40:12   Camera1 Connected SBIG Camera connected (set point -10°C) 22:40:48   Telescope Connected Telescope connected (TheSky6) 22:41:12 Session Equilibration Session ready to Open Dome 22:41:58   Dome Opened Dome opened (opening time 45s) 22:42:00 Session Running Session running 22:42:02   Queue Started Observing Queue started (18 targets selected) 22:42:05     Target Started (NrZen) Target started (Focus Field 21, HIP 103850) 22:42:17       Dome Unparked Dome unparked 22:47:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:49:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 22:51:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 22:52:13       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 22:54:06       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 22:55:48       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 22:56:06     Target Completed (NrZen) Target completed (Focus Field 21, HIP 103850) 22:56:10     Target Started (1/18) Target started (1/18, C/2023 E1 (ATLAS)) 22:58:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:01:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:14:29     Target Completed Target completed (1/18, C/2023 E1 (ATLAS)) 23:14:54     Target Started (2/18) Target started (2/18, GCVS BL Lac) 23:17:21       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:19:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:23:23     Target Completed Target completed (2/18, GCVS BL Lac) 23:25:12     Target Started (3/18) Target started (3/18, C/2019 T4 (ATLAS)) 23:28:24       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 23:37:22     Target Completed Target completed (3/18, C/2019 T4 (ATLAS)) 23:39:44     Target Started (4/18) Target started (4/18, M101 w/SN2023ixf) 23:43:19       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 23:59:34     Target Completed Target completed (4/18, M101 w/SN2023ixf) 00:01:45     Target Started (5/18) Target started (5/18, NGC 2326 w/AT2023pgb) 00:07:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:10:07       Focusing Failed Foc1 focusing check failed 00:10:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 00:18:42   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:18:44   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 00:18:47     Target Aborted (5/18) Target aborted (5/18, NGC 2326 w/AT2023pgb) due to cloud 00:18:49   Queue Paused Queue paused for Session Suspension 00:18:51 Session Suspending Session suspending 00:19:32   Dome Closed Dome closed (closing time 45s) 00:19:35 Session Suspended Session suspended 00:20:40     Target Cancelled Target cancelled (5/18, NGC 2326 w/AT2023pgb) due to cloud 00:42:40     Target Cancelled Target cancelled (6/18, UGC 9350 w/SN2023nny) due to cloud 00:59:12     Target Cancelled Target cancelled (7/18, C/2020 R7 (ATLAS)) due to cloud 01:19:32     Target Cancelled Target cancelled (8/18, CGCG 276-043 w/SN2022xvg) due to cloud 01:36:04     Target Cancelled Target cancelled (9/18, 12P/Pons-Brooks) due to cloud 01:47:46 Session Resuming Session resuming 01:48:31   Dome Opened Dome opened (opening time 45s) 01:48:34 Session Running Session running 01:48:36   Queue Resumed Observing Queue resumed 01:48:38     Target Started (10/18) Target started (10/18, M33 w/AT2023nou) 01:54:02       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 01:56:37       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 02:01:03     Target Completed Target partially completed (10/18, M33 w/AT2023nou) 02:01:08     Target Started (11/18) Target started (11/18, AT2022obq (CV)) 02:02:13   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:02:15   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 02:02:16     Target Aborted (11/18) Target aborted (11/18, AT2022obq (CV)) due to cloud 02:02:18   Queue Paused Queue paused for Session Suspension 02:02:20 Session Suspending Session suspending 02:03:03   Dome Closed Dome closed (closing time 45s) 02:03:05 Session Suspended Session suspended 02:10:24     Target Cancelled Target cancelled (11/18, AT2022obq (CV)) due to cloud 02:30:44     Target Cancelled Target cancelled (12/18, LEDA 1488100 w/SN2023olz) due to cloud 02:45:04     Target Cancelled Target cancelled (13/18, AT2022weo) due to cloud 03:05:04     Target Cancelled Target cancelled (14/18, UGC 2690 w/AT2023nfg) due to cloud 03:27:04     Target Cancelled Target cancelled (15/18, IC 1797 w/SN2023nnz) due to cloud 03:41:06     Target Cancelled Target cancelled (16/18, GSC 1224:29) due to cloud 03:54:36     Target Cancelled Target cancelled (17/18, Nova Per 2020) due to cloud 04:19:38     Target Cancelled Target cancelled (18/18, 2P/Encke) due to cloud 04:19:43   Queue Completed Job Queue completed 04:19:46 Session Closing Session closing 04:19:51   Dome Closed Dome already closed (closed at 02:03, closing time 45s) 04:20:09   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 04:21:29   Telescope Parked Telescope parked (parking time 76s) 04:21:44   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:22:06   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:23:29   Services Stopped Night Services stopped 04:23:32 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files) 04:23:37 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail --             No Alerts                --

Back to Top

Operational Issues (2023-08-21, S1133)

• Critical Issues (0)
• Major Issues (1)
• Minor Issues (0)
• Small Defects (2)
• Continuous Improvement (2)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• Autostart held-up whilst starting ShCap service (22:33). Autostart operations became stalled whilst starting observatory services due to a stall in start ShCap/SharpCap services.    Issue is classified as 'Major' as it prevents the automated session from preceeding.  This is a known occasional issue (see S1130) and was again resolved by making a user intervention to use the backdoor facility to 'Restart ShCap Service' . This had the reliable effect of releasing the stalled start observatory services routine, and allowed the session to proceed. An attempted continuous improvement (S1130) added to AstroMain 3.62.8 that was meant to allow ObsOverseer to automatically Restart ShCap Services in the event that the Start ShCap Services task stalls didn't succesfully operate.  However one improvement added to AstroMain 3.62.8 which is to block the Start Observatory Services routine until the Restart ShCap Service (whether initiated by the user or automatically) has completed. The new code in AstroMain 3.62.8 to be reviewed to understand why ObsOverseer failed to automatically resolve the issue with Start ShCap Service holding-up.  The normal sequence of log message from ShCapService are
    Connect ShCap.Server    | ShCap Server is connected on Port: 4002
  (trace) Get DataStream  | ShCap.DataStream = Client.GetStream
  (trace) Get DataStream  | ShCap.DataStream = Client.GetStream
  Start ShCap Listener    | Starting ShCap Listening Loop
  (trace) Get Message     | ShCap.GetMessage = None
  Check ShCapConnection   | Ready
  but when problem occurs the Get Message message is missing no exceptions are recorded.   Examinig the ShCap.StartClient()  routine, it is noted that after calling ShCap.StartListening()  routine (which begins a thread to that runs ShCap.ListeningLoop routine),  there is a 200 ms delay before call to ShCap.GetMessage. It is conjectured that in some cases 200ms delay may be too short for the ListeningLoop to start/get going and the GetMessage() is somehow held-up which locks the ShCap.StartClient & StartObservatoryServices processes .  Delay time is increased from 200ms to 2s (2000ms) as this might resolve the underlying issue.  That the processes locks up at this point is supported by the occurancy of otherwise unexplainable occurance of "Get (ShCap) Message" and "Check ShCap Connection" log message when Restarting ShCap service which releases the locked ShCap.StartClient process. Tracing has been added in 3.62.9 to record holds ups associated with Get (ShCap) Message  As part of the code section to start ShCap Service within StartObservatoryServices() routine TimeStartShCapServiceStarted,  bStartShCapServiceIsRunning = True and  bShCapServiceFailed = False are set ahead of calling ShCap.StartService().   Code reviewed to see why 3.62.8's  automated resolution of frozen ShCap.StartService() process might have failed to kick in but couldn't identify an obvious cause. Extra tracing added to AstroMain 3.62.9 to understand why automated resolution of problem might have failed. Closed after review 2023-11-19 as issue hasn't been seen during the last 35 sessions (S1134-S1168).
  Closed after review 2023-11-19 (AstroMainn 3.64.7)

Minor IssuesMinor Issues

• None

Small Defects

• Logfile has ShCap message that incorrectly refer to "Stopping PHD2 Listening Loop" (22:38). 'Stop ShCap Listener' log messages incorrectly refer to "Stopping PHD2 Listening Loop" when they should refer to "Stopping ShCap Listening Loop". Defect doesn't affect functionality. Fixed in AstroMain 3.62.9.  
  Done 2023-08-22 (AstroMain 3.62.9)
   
• Start Observatory Services incorrectly referred to as 'Manual (Services)' in logfile (22:31). Start Observatory Services routine was called as part of AutoStart Operations after specifying that Night Services are requied when beginning the live session. The associated log messages were referred to a "Manual (Services), but  'Manual' should only be referenced when initiating Start Observatory Services from the button facility on the Observatory tab. The logfile should instead refer to the  associated messages as "Session (Services)".  Code likely uses 'szTargetName + " (Services) and szTargetName is presumably being set to "Manual" as some point. There are two code statements that explicitly use 'szTargetName = "Manual" ' . Two in OpenSession(), one SetMode_Manual() and one in TestCaptureRefFrame().  This is still as issue as of 2024-04-13 (session S1208).  Fix attemped in AstroMain 3.68.3. (szTargetName = "Manual" is bypassed if szTargetName = "AutoStarting" in OpenSession() routine), but missed a codeline that set szTargetName = "Session" which prevent the fix from performing as intended. Fixed this in AstroMain 3.68.4.
  Fixed 2024-04-17 (AstroMain 3.68.4)

Continuous Improvement

• Add a "Start Services (continued)" Report Title if we have performed a 'Restart ShCap Service' whilst starting Observatory Services. Code was recently added to AstroMain 3.62.8 code to 'StartObservatoryServices()' routine to place a hold on Start Observatory Services if Restart ShCap Service is executed.  A new report title after completing 'Restart ShCap Service' would be helpful in clearly visual closing out the reporting of 'Restart' operations and the continuation of Start Services operations (normally these will comprise report lines from starting Observatory Manager, TCF-S Focuser and ObsEnv services.
  Done2023-08--22(AstroMainn 3.62.9)
   
• Change 'Weather Station' status flag on Observatory tab to 'Yellow' when the WeatherStation Monitor has only recently started up instead of a 'Red' Flag.  Weather Station status is usually shows as Red Flag when ObsMonitor services is first started. This can be misleading and can  because of time taken to initially fetch a Weather Station record or because Weather Station is only updated every 1 minute or so. Status should therefore be shown as a Yellow Flag (instead of a Red Flag) during first 2 minutes after starting ObsMonitor / WeatherStation Listening Loop (implemented by reference to a new WeatherStation variable : TimeListeningStated (Date)  )
  Done2023-08--22(AstroMainn 3.62.9)

[ Prev | Next ]

Back to Top