David's Astronomy Pages Notes - Session 1446 (2026-09-01)

Notes (S1445)

Notes Main

Home Page

Notes (S1447)

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

Session Aims & Highlights (2026-09-01)

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.83.9, AstroPlan 1.47.1, AstroShCap 1.3.23, AstroGuard 1.13.2
  AstroMag 1.5.12, AstroVOE 2.0.1, AstroSN 1.16.1, AstroProtect 1.7, AstroMove 1.8.3
  AstroAllSky 3.28.1, AstroWeather 1.30.4, AstroObsCam 1.14, AstroNorthCam 1.12.2, AstroLaunch 1.14.9

Highlights

• Targets. 19/25 planned targets were completed with 4 targets partially completely. Other targets failed due to cloud or exceeded time slot
•  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 20:27:32 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:00 & 04:36 20:27:36   AutoStart Waiting AutoStart waiting till earliest start time at 21:00 21:00:14 Session AutoStarting Session autostarting (21:00) 21:00:21 Session Created Session Created (Live, 2026-09-01 S01446) 21:00:23   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 21:00:45   Scope Switched On Telescope Power has been switched on via UPB Switch 21:02:33   Services Started Observatory Services started 21:02:44 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:02:45 Session Pending Session pending (2026-09-01) 21:02:47 Session Initiating Session initiating (2026-09-01) 21:03:09   Camera1 Connected SBIG Camera connected (Set point -10°C) 21:03:12   Plan Requested Observing Plan requested from AstroPlan (1.47.1) 21:03:58   Plan Loaded Observing Plan loaded to queue (PlanID: 1247) 21:04:39   Telescope Connected Telescope connected (TheSky6) 21:05:03 Session Equilibration Session ready to Open Dome 21:05:49   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:05:54   Equilibration Started Dome Equilibration started 21:05:56   Equilibration Ended Dome Equilibration ended (0.0 mins total) 21:05:58 Session Running Session running 21:06:00   Queue Started Observing Queue started (25 targets selected) 21:06:03     Target Started (NrZen) Target started (Focus Field 19, HIP 93376) 21:06:18       Dome Unparked Dome unparked 21:10:22       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:12:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 21:14:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 21:14:49       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:16:36       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 21:18:20       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 21:18:41     Target Completed (NrZen) Target completed (Focus Field 19, HIP 93376) 21:33:15     Target Started (1/25) Target started (1/25, GCVS AM Her) 21:37:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:39:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 21:44:52     Target Completed Target completed (1/25, GCVS AM Her) 21:44:56     Target Started (2/25) Target started (2/25, AT 2026stb (Nova)) 21:49:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:52:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 22:03:41     Target Completed Target completed (2/25, AT 2026stb (Nova)) 22:03:45     Target Started (3/25) Target started (3/25, GCVS CI Cyg) 22:08:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:10:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 22:13:27     Target Completed Target completed (3/25, GCVS CI Cyg) 22:13:31     Target Started (4/25) Target started (4/25, AT2026lck) 22:17:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:19:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:36:09     Target Completed Target completed (4/25, AT2026lck) 22:36:13     Target Started (5/25) Target started (5/25, NGC 3310 w/AT2026uxt) 22:59:05     Target Completed Target completed (5/25, NGC 3310 w/AT2026uxt) 22:59:09     Target Started (6/25) Target started (6/25, NGC 5907 w/SN2026kid) 23:04:28       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 23:20:48     Target Completed Target completed (6/25, NGC 5907 w/SN2026kid) 23:20:52     Target Started (7/25) Target started (7/25, T CrB) 23:28:39   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:28:41   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 23:28:46     Target Aborted (7/25) Target aborted (7/25, T CrB) due to cloud 23:28:49   Queue Paused Queue paused for Session Suspension 23:28:50 Session Suspending Session suspending 23:29:40   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 23:29:44 Session Suspended Session suspended 00:26:00 Session Resuming Session resuming 00:26:45   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 00:26:50 Session Running Session running 00:26:52   Queue Resumed Observing Queue resumed 00:26:54     Target Started (8/25) Target started (8/25, NGC 7293). Using SharpCap 00:32:03       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 00:33:36     Target Failed (8/25) Target failed due to exceeded time slot (8/25, NGC 7293) 00:33:41     Target Started (9/25) Target started (9/25, M31 w/M31N 2026-04b?) 00:35:12       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:36:51       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:38:29       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:40:07       CCDSoft Issue CCDSoft has encountered an image save issue [0000] 00:41:12       Camera1 Connected SBIG Camera connected (Set point -15°C) 00:56:20     Target Completed Target partially completed (9/25, M31 w/M31N 2026-04b?) 00:56:24     Target Started (10/25) Target started (10/25, GCVS CY Lyr) 01:04:46     Target Completed Target completed (10/25, GCVS CY Lyr) 01:04:51     Target Started (11/25) Target started (11/25, Nova Aql 2026 (Nova)) 01:08:44       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 01:23:22     Target Completed Target completed (11/25, Nova Aql 2026 (Nova)) 01:23:26     Target Started (12/25) Target started (12/25, 61 Cyg) 01:25:33       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:27:16       Focusing Failed Foc1 focusing failed (failed QC check - RmsE) 01:29:03     Target Completed Target completed (12/25, 61 Cyg) 01:29:47     Target Started (13/25) Target started (13/25, NGC 7292 w/SN2026fov) 01:33:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:35:19       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 01:51:22     Target Completed Target completed (13/25, NGC 7292 w/SN2026fov) 01:51:47     Target Started (14/25) Target started (14/25, GCVS EV Lac) 01:54:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:57:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 01:59:59     Target Completed Target completed (14/25, GCVS EV Lac) 02:00:49     Target Started (15/25) Target started (15/25, GCVS HH And) 02:04:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:06:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:08:12     Target Completed Target completed (15/25, GCVS HH And) 02:09:06     Target Started (16/25) Target started (16/25, UGC 12040 w/SN2026kux) 02:12:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:14:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 02:30:27     Target Completed Target completed (16/25, UGC 12040 w/SN2026kux) 02:31:06     Target Started (17/25) Target started (17/25, WDS GRB 34) 02:34:27       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:36:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 02:38:40     Target Completed Target completed (17/25, WDS GRB 34) 02:39:34     Target Started (18/25) Target started (18/25, GCVS BL Lac) 02:42:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:44:58       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 02:48:45     Target Completed Target completed (18/25, GCVS BL Lac) 02:49:52     Target Started (19/25) Target started (19/25, GCVS DY Per) 02:53:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:55:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 03:01:19     Target Completed Target completed (19/25, GCVS DY Per) 03:01:24     Target Started (20/25) Target started (20/25, AT2022vdr (CV)) 03:06:23       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:13:17     Target Completed Target completed (20/25, AT2022vdr (CV)) 03:13:22     Target Started (21/25) Target started (21/25, AT2026eva) 03:16:49       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:19:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 03:35:33     Target Completed Target completed (21/25, AT2026eva) 03:35:37     Target Started (22/25) Target started (22/25, GCVS RX And) 03:38:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:41:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 03:43:56     Target Completed Target completed (22/25, GCVS RX And) 03:44:57     Target Started (23/25) Target started (23/25, Gliese 65) 03:49:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:51:40       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 03:57:40   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:57:42   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 03:57:45     Target Aborted (23/25) Target aborted (23/25, Gliese 65) due to cloud 03:57:47   Queue Paused Queue paused for Session Suspension 03:57:49 Session Suspending Session suspending 03:58:36   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 03:58:41 Session Suspended Session suspended 04:17:10     Target Cancelled Target cancelled (24/25, NGC 3310 w/SN2026sqf) due to cloud 04:39:28     Target Cancelled Target cancelled (25/25, GCVS ER UMa) due to cloud 04:39:32   Queue Completed Job Queue completed 04:39:35 Session Closing Session closing 04:39:37   Dome Closed Dome already closed (closed at 03:58, closing time 50s, zigbee 43s) 04:40:32   Dome Parked Dome parked (parking time 45s), Az: 90.0 deg 04:41:11   Telescope Parked Telescope parked (parking time 30s total) 04:41:35   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:42:31   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:43:57   Services Stopped Night Services stopped 04:44:00 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:44:52     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:45:37     Dome Find Park found (Best Park Az 90.5°) 04:45:43     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.5°) 04:45:45   Dome Parked Dome parked 04:48:45   Dome Charging Dome is parked and well charged (96%, 15.0v) 04:48:47 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:35:12 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:36:51 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:38:29 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 00:40:07 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 04:48:45 Yellow Alert Dome Charging Dome is parked and well charged (96%, 15.0v)

Back to Top

Operational Issues (2026-09-01 S1446)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• A series of four CCDSoft Red Alerts occurred that seem to relate to a failure to release the SBIG Camera from PHD2 (00:33 to 00:40). During Locate Frame acquisition on Target 9/25 (M31 w Nova 2026-4b?) there were four CCDSoft Red Alertsraised between 00:35:12 and 00:40:07 with messages "Image file [0000] hasn't been saved to disk, possible CCDSoft issue".  During this time eight attempts were made to Restart CCDSoft  & SBIG Camera. The last attempt finally succeeded in reconnecting the SBIG Camera in CCDSoft,  but only after PHD2 seeimingly released the SBIG camera ahead of Guiding with TS80 & 178MC camera.  The target '2026-4b?' was preceeded by Target 8/25 (NGC 7293) which was a ShCap target in whilst planned main images were to be taken through TS80 / 178MC. After performing locate frames the SBIG camera was correctly disconnected from CCDSoft and then connected to PHD2 ready for for guiding. A Guide Reference frame was taken at 00:33 which demonstrated that the SBIG camera was operating ok at that time under the direction of PHD2, though it seemed there was a suitable star for guiding on . In the event prior weather delays saw the target being then aborted due to its timeslot being exceeded. A call was made to ReconnectCCDSoftCamera() routine but the CCDCamera.Connect()  at 00:33:36 failed with an exception with the message "SBIG driver: Camera not found. Error code = 1001". The CCDSoft issues / red alerts appear to be directly related to PHD2's continued connection to the SBIG Camera.  It would seem that there is a design flaw in the JOb Executor which doesn't disconnect the SBIG camera from PHD2 when ending a target. Unless PHD2 performs an equipment disconnection the attempt to Restart CCDSoft/SBIG camera will likely always be in vain. Fixed in AstroMain 3.83.10 - the place in ExecuteQueue() routine where the call to ReconnectCCDSoftCamera()  is known precisely and a preceding new section has been added to check and release SBIG camera (Cam1) from PHD2.
    Fixed   2026-09-04 (AstroMain 3.83.10) 

Small Defects

• AstroNorthCam's new unified Object Detection routines have a number of teething issues (2026-09-02). AstroNorthCam 1.12.3 has been upgraded with newly refactored and unified Object Detection.  There are a number of small teething issues with it. These have been fixed in AstroNorthCam 1.12.4.
    Fixed  2026-09-02 (AstroNorthCam 1.12.4) 
   
• AstroNorthCam's new unified Object Detection routines is no longer copying significant ObjectPic images to the Server folder (2026-09-02). In AstroNorthCam 1.12.2 and earlier versions significant ObjectPic images were copied to the Server Folder by SaveObjectPicture() routine from where they were uploaded to the Observatory Website. The files are named NorthCam.LatestObject01.jpg to NorthCam.LatestObject12.jpg. In AstroNorthCam 1.12.3 / 1.12.4. the new equivalent routine NewSaveObjectPicture() is no longer refreshing these files with new version.   Fixed in AstroNorthCam 1.12.5 but re-including the necessary code block for copying significant ObjectPics to use these files in Server folder.
    Fixed  2026-09-02 (AstroNorthCam 1.12.5) 
   
• Keogram Cursor behaviour isn't working correctly in AstroNorthCam's Multi-Channel Frame Viewer when used on an active / unfinished Session.  AstroNorthCam'sMulti-Channel Frame Viewer displays a Day or Night Keogram for the currently selected Session, and a vertical cursor line can be used to move the current FrameTime to a specified time on the Keogram.  The behaviour breaks down when used with the currently active / non-finished session as the Day or  Nght Keogram is incomplete. The cursor operation assumes that the keogram covers a full day or full night and when it doesn't the cursor doesn't move the FrameTime to the correct time point.  Fixed in AstroNorthCam 1.12.5 by clamping Keogram.EndTime to minimum of Current Time and either Sunset (Day Keogram) or Sunrise the following morning.
    Fixed  2026-09-02 (AstroNorthCam 1.12.5) 
   
• AstroNorthCam is drawing mutiple Multiple Night-Mode Object Boxes in close proximity. AstroNorthCam 1.12.3 - 1.12.5 is using new Unified Object Detection.  In Night Mode 'False Objects' are frequent detected when there are fast moving cloud edges.  Sometime there can be 22-29 objects boxes drawn in close proximity.  It is proposed to group such boxes when they are in certain distance from one another, grouping should use the new PaddedBoxesOverlap method which is successfully used for day-mode object grouping.  Fixed in AstroNorthCam 1.12.6.
    Fixed  2026-09-03 (AstroNorthCam 1.12.6) 
   
• AstroNorthCam is still saving Star Images as NorthCam.LatestDayObject.jpg. Historically the latest version of NorthCam Object Frames and Star Frames were saved to the '/Server' Folder as "NorthCam.LatestDayObject.jpg" where it was then uploaded to the Observatory Website. Whilst the latest Star Frame is now saved to the '/Server' Folder as "NorthStars.LatestStars.jpg", AstroNorthCam 1.12.6 is still save frame as "NorthCam.LatestDayObject.jpg" , which lead to the final DayObject frame of the day being overwritten. Fixed in AstroNorthCam 1.12.7 by removing the legacy save command from the SaveStarsImage() routine
    Fixed  2026-09-03 (AstroNorthCam 1.12.6) 
   
• The Object01 image (NorthCam.LatestObject01.jpg) is not being refreshed on 'NorthCam' web page (2026-09-03 / 2026-09-04).  AstroAllSky logs don't show the NorthCam.LatestObject01.jpg file being queued for upload even though it seems to be written to the server folder by AstroNorthCam  Investigating showed a bug has been introduced into NorthCamListener when a new item was recently included in AstroAllSky's NorthCamListener() routine in program version 3.28.2 . Fixed in AstroAllSky 3.28.3 : Attention must be given to the code line "ObjNumber = i - 12" in case "Case 13 To 25", The correct equation needs to be used in order to produced ObjNumbers in range 1 to 12.(The bug "i - 11" was causing ObjNumbers in range 2 to 13)
    Fixed    2026-09-04 (AstroAllSky 3.28.3 ) 
   
• Associated with TakeImageAsync/ Camera Connection failures the log file incorrectly reports that SetSbigUsbOff commands were made by the user when they were not (00:35- 00:40) . Between 00:35 and 00:37 there were some issues with connection with SBIG Camera.  There were 4 red CCDSoft alerts raised with the message "Image file [0000] hasn't been saved to disk, possible CCDSoft issue"  The logfile shows 8 events  where "SBIG USB Camera not listed in DeviceManager"  records were written with each one being following by multiple Get/Set Camera property failures.   Finally for each event there is a "SetSbigUsbOff " action with the message "User request to turn-off USB Port to SBIG Camera". The assertion that this was a user request is incorrect - these were programmed requests from the ObsManager or Job Executor. The log messaging should be corrected.
  The action to turn the SBIG Usb Off is performed by SetSbigUsbOff(Mode As Integer) routine. The log message regarding 'User request is due to the routine being called with Mode =  CallMode.Manual . Fix attempted in AstroMain 3.83.10. by called whether RestartModeStr contains "user" an if so use CallMode.Manual, otherwise use CallMode.Auto.
    Fixed  2026-09-04 (AstroMain 3.83.10)
   
• AstroNorthCam is making too many false objection details in Night Detection Mode when sky is cloudy.  A new Unified Object detection routine was recently introduced with operation in Day Detection Mode or Night Detection Mode. The Day mode is working well, but the night mode is producing too many false detections related to moving cloud / moving cloud edges.  Long term fix is likely some form of dynamic threshold adjustment based on SunAlt, Clarity and Star Count. In the meantime Object Diff and Brightness threshold has been tightened from 20/130 to 40/150.   To monitor and review after getting more experience across a range of sky conditions. Issue apppears to have been resolved using new routine. xxxx which checks that the StdDev of brightness in a rectangular 'ring' around the object is below StvDevThreshold  (10) and that the Contrast of object (AvBrightness of object - AvBrightness of rectangular 'ring') is above ObjectContrastThreshold (30).
    Fixed  2026-09-05 (AstroNorthCam) 

Continuous Improvement

• Refactor AstroNorthCam's Find Objects routines into a single unified routine operating on each raw frame. AstroNorthCam's existing FindDayObjectsInImage() compares the last Main frame (representing the first raw frame in a 15s window) with the last Main frame. This works for detecting birds etc, but can produce false positive from cloud edges near sun set. Also any objects appearing on raw frames other than the first one are  not captured.  FindNightObjectsInImage() is somewhat similar excepting that it compares frames that are the average of raw frames over each 15s interval, and is likewise prone to false detections during twilight from cloud layers close to horizon. It is proposed to change the philosphy to search for objects in every raw frame.. This will allow the capturing of more objects and reduce the number of false detections since clouds change little over short (1.2 - 1.5s) periods of time compared to the current 15s of time. As part of this it is planned to unify the two current routines into a Single Routine 'FindObjectsInImage.  It is planned to introduce the new factored Find Object process without significant affecting the recently added Multi-Channel Frame Viewer tool.  Implemented initially in AstroNorthCam 1.12.3, but required several fixes to work correctly which were released as AstroNorthCam 1.12.4. Code still needs testing in DetectionMode.Night mode.
    Done 2026-09-02 (AstroNorthCam 1.12.3 / 1.12.4) 
   
• Modify AstroNorthCam to be able to save a "NorthCam.LatestNightObject.jpg" to Server folder for upload to Observatory Website. In AstroNorthCam 1.12.4 and earlier versions all Latest Object frames were copied to the Server folder as "NorthCam.LatestDayObject.jpg" regardless of whether it had being generated from Find Day Objects (dark objects) or Find Night Objects (bright objects) methods. It is proposed to modify the new FindObjectsInImage() folder to pass DetectMode (DetectionMode.Day or DetectionMode.Night) to SaveObjectsImage() routine and use it to separately save a "NorthCam.LatestNightObject.jpg" files when DetectMode is DetectionMode.Night. Implemented in AstroNorthCam 1.12.5. AstroAllSky 3.28.2 modified to upload the new "NorthCam.LatestNightObject.jpg" to Observatory website, and the 'northcam.htm'  page modified to display the new image file. AstroAllSky also modified to upload the 'NorthCam.LatestStars.jpg' file which is created by AstroNorthCam but not previously uploaded to website.
    Done 2026-09-02 (AstroNorthCam 1.12.5 AstroAllSky 3.28.2, Website)
   
• Enhance AstroNorthCam's Mutli-Channel Frame Viewer with a number of improvements. It is proposed to make the following improvements:
  - Extend SetComboSessions() routine to include a 'Next Day' Session  if its Day Keogram has already been started.
  ( this is to allow early morning Frames to be viewed before new session folder is created with switch in Night Date at 09:00 )
- Enable existing 'Refresh' button to actually refresh the Session List.
- Set CurrentFrameIdx to that of previous frame, when a frame is not available for current FrameTime
  (this is to allow FrameStepping to immediately commence from the current FrameTime, with a channel going to its first frame)
  Implemented in AstroNorthCam 1.12.6., with modifications to SetComboSessions(), btnRefresh_OnClick(), UpdateFrames() / GetPrevFrameIdx()
    Done 2026-09-02 (AstroNorthCam 1.12.6,  AstroAllSky 3.28.2, Website)
   
• Make certain improvement to logging and reporting of PHD2 Equipment Connections and Disconnections.  During the S1446 session there was  series of four CCDSoft Red Alerts  that seem to relate to a failure to release the SBIG Camera from PHD2 . Whilst investigating the issue it was apparent that logging of PHD2 equipment connections and disconnections could be improved - currentlly in AstroMain 3.83.9 and earlier version equipment connections aren't logged whilst disconnection are logged but without specifying the equipment being disconnected. Equipment connections are reported well,  but there is a gap in reporting equipment disconnections. Implemented in AstroMain 3.83.10
    Done  2026-09-04 (AstroMain 3.83.10) 
   
• Add RejectBlobByContext() function to AstroNorthCam to better enable FindObjectsInImage to discriminate between real object detections and cloud edge detections. Cloud Edge 'false' objects can occur at night time when a bright (illuminated) cloud moves across dark back ground star. The cloud edge sees a significant positive difference and can is flagged up as a blob / candidate object.   Discreiminating between real night time objects and cloud edge (false) objects is proving to be probematic in the new Unified Detection routine (AstroNorthCam 1.12.2 to 1.12.7) , when running in DetectionMode.Night. Tightening Diff and Brightness Thresholds is not sufficient as it can at the same time reduce the capability of detecting real objects. It is proposed to include a new function 'RejectBlobByContext()'  function that collects brightness statistics from an area around the candidate object (blob) allow it to be rejected based on StdDev.   If the candidate object is set against background sky the background region can be expected to have a StdDev of 5-15 and can be taken as a real object, where as if the background region , comprises part cloud and part background sky it can be expected to have a higher StdDev of  25–40 and can be rejected.  Implemented in AstroNorthCam 1.12.8 using StdDevThreshold =10.0 , BlobContrastThreshold = 30
    Done  2026-11-01 (AstroNorthCam 1.12.8)
   
• Modify AstroNorthCam's BuildObjectFrame to save a clean, unannotated 15s frame for each Object Frame. AstroNorthCam has been recently modified to save an Objects Frame based on bitmap generated from either a 15s Min accumulator (Day Detection Mode) or a 15s Max accumulator (Night Detection Mode).  In some cases a line of boxes may be drawn on the image representing the position of a moving object every 1s or so.  These boxes tend to hide/cover the detected object and its track. The main frame (either the first 1s frame in 15s window in day time or an average frame in night time are not suited for this role. Instead it is proposed that a clean, unannotated image frame is created and saved for each object frame created.   The frames would be stored in a folder called ."./Objects/Clean15s". A new 'Clean15s' Image Type would be defined and used for displayed Clean15s in AstroNorthCam's Mult-Channel Frame Viewer. Implemented in AstroNorthCam 1.12.9.
    Done  2026-09-04 (AstroNorthCam 1.12.9)
   
• Create a new Objects Viewer Form to allow NorthCam images to be quickly toggled between shows annotated Objects Frames and unannotated Clean15s frames. AstroNorthCam 1.12.9 was recently modified to create and save an unannotated frame version for each annotated Objects frame that is created.  It is proposed to add an extra Viewer Form to AstroNorthCam to allow rapid toggling between annotated and unannotated frames. To be implemented in AstroNorthCam 1.12.10.
    Done  2026-09-05 (AstroNorthCam 1.12.10)
   
• Consider dynamically modifying AstroNorthCam's Night time Object Detection Thresholds based on SunAlt, Clarity and Star Count. The thresholds for night time object detection are currently defined in text boxes in AstroMain 1.12.5 earlier versions, formerally this was a ObjectDiffThreshold (~20) which has been supplemented in 1.12.5 by a ObjectBrightnessThreshold (~130). It is proposed to make the thresholds dynamic in someway;  when the sky is cloudy the thresholds need to be tightened in order to reduce the number for false detection due to cloud edges, whilst when the sky is clear the thresholds can be relaxed in order to achive greater detection sensitivity.  To implement in AstroNorthCam 1.13.
  To do 2026-11-01 (AstroNorthCam 1.13)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top