David's Astronomy Pages Notes - Session 1430 (2026-05-17)

Notes (S1430A)

Notes Main

Home Page

Notes (S1431)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (1),  Small Defects (2),  Continuous Improvement (4)
	- Figures (0)
	Images from 2026-05-17  >>

Session Aims & Highlights (2026-05-17)

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. Check new AstroMain xx.xx  version for any issues or problems following introduction of a number of changes.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6 6.0.0.65, CCDSoft5 5.0.201, DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3, PulsarDome 6.4.0.0
• Peg-Unity 2.12, Peg-Focuser 2.12, Peg-Switch 2.12, TCF-LSI 3.3.5
• SharpCap 3.2.6482, PHD2 2.6.14, Siril 1.4.2, deCONZ 2.18.2, ASCOM 7.1.0.4707
   
• AstroMain 3.82.1, AstroPlan 1.46.2, AstroShCap 0.0, AstroGuard 1.13.2
  AstroMag 1.5.12, AstroVOE 1.16, AstroSN 1.16, AstroProtect 1.7, AstroMove -
  AstroAllSky 3.27.10, AstroWeather 1.30.3, AstroObsCam 1.13.1, AstroNorthCam 1.8.2, AstroLaunch 1.14.9

Highlights

• Targets. 8/10 planned targets were completed with 2 targets partially completely.
•  Dome. No issues open/closing shutter. Dome was successfully parked at the end of the session.

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) Note:  The NorthCam Star Count line is unreliable and should be ignored (The AstroNorthCam 'Find' Star method is producing many false positives from clouds)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 23:34:51 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:34 & 02:20 23:34:56 Session AutoStarting Session autostarting (23:34) 23:35:02 Session Created Session Created (Live, 2026-05-17 S01430) 23:35:05   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:35:26   Scope Switched On Telescope Power has been switched on via UPB Switch 23:37:13   Services Started Observatory Services started 23:37:23 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:37:27 Session Pending Session pending (2026-05-17) 23:37:29 Session Initiating Session initiating (2026-05-17) 23:37:53   Camera1 Connected SBIG Camera connected (Set point -20°C) 23:37:59   Plan Requested Observing Plan requested from AstroPlan (1.46.2) 23:39:55   Plan Loaded Observing Plan loaded to queue (PlanID: 1231) 23:40:36   Telescope Connected Telescope connected (TheSky6) 23:41:00 Session Equilibration Session ready to Open Dome 23:41:02   Wait On Weather Waiting for acceptable conditions 23:41:04 Session Suspending Session suspending 23:41:06   Dome Closed Dome already closed 23:41:08 Session Suspended Session suspended 23:41:40   Queue Started Observing Queue started (10 targets selected) 23:47:41 Session Resuming Session resuming 23:48:26   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 23:48:29 Session Running Session running 23:48:31   Queue Resumed Observing Queue resumed 23:48:33     Target Started (1/10) Target started (1/10, GCVS RZ LMi) 23:48:46       Dome Unparked Dome unparked 23:53:50       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:55:51       Focusing Completed Foc2 AutoFocus Completed (Profile No 1, wide) 23:57:37       Focusing Completed Foc2 AutoFocus Completed (Profile No 1) 00:00:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:02:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 2, wide) 00:04:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 2) 00:09:30     Target Completed Target completed (1/10, GCVS RZ LMi) 00:09:34     Target Started (2/10) Target started (2/10, NGC 4205 w/SN2026fvx) 00:13:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:15:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:31:45     Target Completed Target completed (2/10, NGC 4205 w/SN2026fvx) 00:31:49     Target Started (3/10) Target started (3/10, NGC 4914 w/SN2026fjc) 00:51:50     Target Completed Target completed (3/10, NGC 4914 w/SN2026fjc) 00:51:54     Target Started (4/10) Target started (4/10, T CrB) 00:56:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:58:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:02:40     Target Completed Target completed (4/10, T CrB) 01:02:44     Target Started (5/10) Target started (5/10, UGC 11058 w/SN2026ewd) 01:06:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:08:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:25:17     Target Completed Target completed (5/10, UGC 11058 w/SN2026ewd) 01:25:21     Target Started (6/10) Target started (6/10, AT2026iul (CV)) 01:29:01       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:31:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:38:15     Target Completed Target completed (6/10, AT2026iul (CV)) 01:38:19     Target Started (7/10) Target started (7/10, GCVS CY Lyr) 01:42:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:44:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 01:48:08     Target Completed Target completed (7/10, GCVS CY Lyr) 01:48:12     Target Started (8/10) Target started (8/10, NGC 6070 w/SN2026ejy) 01:52:25       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 02:09:00     Target Completed Target completed (8/10, NGC 6070 w/SN2026ejy) 02:09:04     Target Started (9/10) Target started (9/10, AT2026lck) 02:13:41       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 02:22:40   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:22:42   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:22:44     Target Aborted (9/10) Target aborted (9/10, AT2026lck) due to cloud 02:22:46   Queue Paused Queue paused for Session Suspension 02:22:48 Session Suspending Session suspending 02:23:35   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 02:23:37 Session Suspended Session suspended 02:28:15     Target Cancelled Target cancelled (9/10, AT2026lck) due to too few stars 02:39:22 Session Resuming Session resuming 02:40:07   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:40:09 Session Running Session running 02:40:12   Queue Resumed Observing Queue resumed 02:40:14     Target Started (10/10) Target started (10/10, GCVS S Cyg) 02:45:42   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:45:44   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:45:47     Target Aborted (10/10) Target aborted (10/10, GCVS S Cyg) due to cloud 02:45:49   Queue Paused Queue paused for Session Suspension 02:45:53 Session Suspending Session suspending 02:46:42   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 02:46:44 Session Suspended Session suspended 02:50:33 Session Resuming Session resuming 02:51:18   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 02:51:20 Session Running Session running 02:51:23   Queue Resumed Observing Queue resumed 02:51:25     Target Started (10/10) Target started (10/10, GCVS S Cyg) 03:02:57     Target Completed Target partially completed (10/10, GCVS S Cyg) 03:02:59   Queue Completed Job Queue completed 03:03:01 Session Closing Session closing 03:03:49   Dome Closed Dome closed (Closing time 49s, Zigbee 44s) 03:04:07   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 03:05:02   Telescope Parked Telescope parked (parking time 46s total) 03:05:25   Telescope State Handbox reads 'Scope parked Turn scope off.' 03:06:22   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 03:07:46   Services Stopped Night Services stopped 03:07:49 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 03:08:16     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 03:09:00     Dome Find Park found (Best Park Az 90.4°) 03:09:06     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 03:09:08   Dome Parked Dome parked 03:12:09   Dome Charging Dome is parked and well charged (95%, 14.9v) 03:12:11 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:24:54 Yellow Alert Dome Dome has been stationary for more than 15 mins 00:28:00 Green Alarm Dome Dome Movements have begun again (outage 18.1 mins) 03:12:09 Yellow Alert Dome Charging Dome is parked and well charged (95%, 14.9v)

Back to Top

Operational Issues (2026-05-17 S1430)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Near Zenith Focusing wasn't performed at start of session and focusing relied on Foc1/Foc2 focusing on Target 1/10. Sessions are meant to always perform Foc1/Foc2 Focusing at a Near Zenith Focus field.   This is to give the best chance of achieving autofocus at the start of the session, because the Focus Field is specially chosen to include a reasonable bright focus star, and it at near zenith,  with greatest chance of avoiding cloud, that low altitude focus fields may suffer from. The ideal situation can be upset for a session suspension at the wrong moment.  Reviewing the session report file
   23:37  Observing Plan requested (with StartTime 23:59, ie 21.4 minutes starting time)
 23:40  Expected Times listed :
    - Expected Shutter Opening, 23:40
    - Expected Near Zenith Foc1, 23:44
    - Expected Near Zenith Foc2,  23:52
    - Expected Queue Start, 23:58
 23:41 Unable to proceed (due to too few stars)
 23:41 Session Suspending (shutter already closed)
 23:41 Session Suspended
 23:41 Job Queue Started
 23:41 Target 1/10 (RZ LMi) commenced
 23:41  Focus Fields loaded, FocusField 14 selected.
 23:41 Target 1/10 (RZ LMi) entered Wait On Weather loop (Earliest Start 23:54, Planned start 23:59, Planned End 00:11)
 23:47 Session Resuming / Shutter Opened
 23:48 Session Running, RZ LMi continued
 23:53 Foc2 Focusing (Wide & Normal)
 23:59 Foc1 Focusing (Wide & Normal)
 00:04 Main Imaging (3 x 90s)
 00:09 Target Completed
  Code needs to be examined to see what situations lead to Near Zenith Focusing and which don't. There were no issues with NearZenith Focusing in the following S1431 session (2026-05-20).
  To investigate 2026-05-19+ (Session, AstroMain 3.82.2+, Near Zenith Focusing)

Small Defects

• Dashed line of best fit through S Cyg CheckStar points in AstroMain's new MagnitudePlotter is anomalous (post-session). AstroMain 3.82.1 / 3.82.2 beta has been extended to produce a Magnitude Plot, including the addition of a dashed line of best fit through Check Star points. A graphs produced for S Cyg contained an anomalous line of best fit through Checkstar Points (V Filter Band). Investigating show the database records for S Cyg contained a couple point where checkstar1 magnitude value was vcNull (-99), and that these were being included in the regression line maths, and this was due to a bug in BuildCheckPoints() routine which should have excluded such points but didn't.  Bug fixed in AstroMain 3.82.2
  Fixed 2026-05-18 (AstroMain 3.82.2)
   
• During Session Suspension the log file contains too many messages and ObsWorker may be doing unneccessary work (23:41 to ).  Whilst session was suspended, the log file contains a pair of log messages every second:
  23:41:52.22 | GCVS RZ LMi Log     UpdateTpnNextTargets Info  | Updating TP.NextTargets(): 0 (GCVS RZ LMi), 1 (NGC 4205 w/SN),etc
23:41:53.23 | GCVS RZ LMi (trace) UpdateTpnNextTargets Trace | Running UpdateTpnNextTargets(), 'StartItem= 1
and is producing the following log message every 5s.
  23:41:54.83 | GCVS RZ LMi (Worker) (trace) WriteSessionLogs Info | Calling ObsManager.WriteLatestSessionLogs()
   UpdateTpnNextTargets() modified to record TP.NextTargets string and only log changes in the NextTargets string.The multiple WriteSessionLogs / mutiple trace messages are coming from handleSuspendedStage11 and due to an incorrect reference to LastWriteLogsTime (date).
  Fixed 2026-05-18 (AstroMain 3.82.2) 

Continuous Improvement

• Add Airmass and Altitude to the list of X Axis Types in AstroVma to allow cross-plotting. .
  Done 2026-05-19 (AstroMain 3.82.2, AstroVma 0.3 ) 
   
• Extend AstroPlan's schedule builder to optimise observations by airmass using smarter/directed logic. When viewing the Altitude Plan Plot for the Session's Best/Final Observing Plan it is quite often noticed that there will be a couple of observation in the plan, which if swapped, would raise the altitude (and thus reduce the airmass) of both observations.  At the same time it is noticed that the Convergence Plot showing overall PlanFitness of best plan versus Generation No, is generally flat and not improving. When generating new generation candidate plans it is proposed that a certain number of them include optimising Altitude/Airmass by swapping a couple of planned observations, not by random cross-assignment but by logical testing and cross-assignment.   Within the RunGA() routine, on each generation 40% of new population with comprises .Implemented in AstroPlan 1.46.3
  Done 2026-05-19 (AstroPlan 1.46.3)
   
• Modify AstroPlan Booked Observation specification and use to have an optional tolerance around Observation StateTime.  In AstroPlan 1.46.2 and earlier versions Booked Observations were defined by strict StartTime's (i.e. by a strict time slot).  This is still required for certain observations such as a specific transit or other time related events.  For booked observation involving multiple observations of a target through the course of the night, some level of flexibility over start time of reach observations is permissible if it can better integrate them witthin a set of GA chosen observations, minimizing the presence and length of any gaps. Column 'StartTimeTolerance' added to Booked Observation's DataGridView and database to define the Observation's +/- timeslot tolerance in minutes.  Handling to use the more flexible timeslots have been added to CreatePlan(), MutatePlan(), BreedPlan() routines. Implemented in AstroPlan 1.46.3 / 1.47
  Done 2026-05-21 (AstroPlan 1.47)
   
• Extend AstroPlan's schedule building to be able to include multiple observations for a particular target within an Observing Plan. Unless target observations are specifically booked, or a set of targets are to be cycled through repeatedly to the end of the night, AstroPlan's schedule builder is designed to include no more than a single observation of a given target.  There is a need to override this behaviour and specially include multiple observations of a certain targets.   There would probably be some constraints so that observations are separated by a certain minimum about (say 60 minutes ?).  This needs careful review as it represents a significant change from current specification & coding. An analysis has been performed and the best method to achieve the aim is to use Booked Observations and add to add new features/tool o make the booking of multiple observations easier. The introduction of a StartTimeTolerance (mins)  columns in Booking's Form's DataGridView on the database bookings table also helps. Implemented in AstroPlan 1.47
  Done 2026-05-21 (AstroPlan 1.47)

[ Prev | Next ]

Back to Top Issue,  Back to Top