David's Astronomy Pages Notes - Session 1331 (2025-06-01)

Notes (S1330)

Notes Main

Home Page

Notes (S1332)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (6),  Small Defects (3),  Continuous Improvement (4)
	- Figures (2)
	Images from 2025-06-01  >>

Session Aims & Highlights (2025-06-01)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 7.0.3 RC3.4694, MeadeGeneric 1.3.12.522 , UPB 1.5,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S 6.0.6
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 7.0.3 RC3
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.75,  AstroPlan 1.43.10  AstroShCap 1.3.15, AstroGuard 1.11   (any new items or versions in bold)
  AstroMag 1.4.19, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.16
  AstroWeather 1.27.9, AstroAllSky 3.24.1,  AstroObsCam 1.11.4 (not 1.11.5), AstroNorthCam 1.4.5, AstroLaunch 1.13.1

Highlights

• Targets.  None of the 8 planned target observations were completed during fully automated operations, due to initial cloud and CCDSoft/Camera issues and a possible abort/telescope issue.  Imaging was then made using manual directed single-target acquisition , with 4 of the original 8 planned targets successfully acquired + one additional new target (C/2023 C2 (ATLAS)).
• CCD Camera. There were issues with the CCDSoft / CCDCamera ,at the start of the session which required a mixture of automated and manual interventions to fully resolve, after which the remainder of session was conducted without problem.
•  Dome. There was no issues opening/closing the shutter during the session. Dome closed and parked at end of session ok.

Notes

Summary Plots & Logs

Observing Plan Plan not created for this session

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 00:17:16 Session Monitoring AutoStart monitoring for Live Session opportunity between 00:17 & 01:07 00:17:18 Session AutoStarting Session autostarting (00:17) 00:17:39   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 00:18:06   Camera1 Connected SBIG Camera connected (Set point -10°C) 00:18:08 Session Created Session Created (Live, 2025-06-01 S01331, ImageSaveNum: 1331001) 00:18:14   Scope Switched On Telescope Power has been switched on via UPB Switch 00:20:04   Services Started Observatory Services started 00:20:12 Observatory (Auto) Observatory placed in Fully-Automated Mode 00:20:14 Session Pending Session pending (2025-06-01) 00:20:16 Session Initiating Session initiating (2025-06-01) 00:20:25   Camera1 Connected SBIG Camera connected (Set point -15°C) 00:20:32   Plan Requested Observing Plan requested from AstroPlan (1.43.10) 00:21:36   Plan Loaded Observing Plan loaded to queue (Plan ID: 1116) 00:22:19   Telescope Connected Telescope connected (TheSky6) 00:22:43 Session Equilibration Session ready to Open Dome 00:23:28   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 00:23:33 Session Running Session running 00:23:36   Queue Started Observing Queue started (8 targets selected) 00:23:38     Target Started (NrZen) Target started (Focus Field 16, HIP 78946) 00:23:53       Dome Unparked Dome unparked 00:27:24       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 00:27:26   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:27:28   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 00:27:30   Queue Paused Observing Queue pausing for Session Suspension 00:27:32 Session Suspending Session suspending 00:28:19   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 00:28:22 Session Suspended Session suspended 00:30:24 Session Resuming Session resuming 00:31:09   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 00:31:11     Target Started (NrZen) Target started (Focus Field 16, HIP 78946) 00:31:13 Session Running Session running 00:31:15   Queue Resumed Observing Queue resumed 00:34:18     SBIG Camera Take Image failed (Command timed-out) 00:34:22     CCDSoft Restarting CCDSoft being restarted (attempt to fix Camera Exception) 00:34:29   SBIG Camera Reset SBIG Camera being power-cycled 00:35:20     Camera1 Connected SBIG Camera connected (Set point -15°C) 00:35:39     SBIG Camera Take Image successfully completed (earlier flags are reset) 00:36:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:37:04         SBIG Camera Take Image failed (Command timed-out) 00:37:08         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:37:15   SBIG Camera Reset SBIG Camera being power-cycled 00:38:07         Camera1 Connected SBIG Camera connected (Set point -15°C) 00:38:14         SBIG Camera Take Image successfully completed (earlier flags are reset) 00:39:40         SBIG Camera Take Image failed (Command timed-out) 00:39:44         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:39:51   SBIG Camera Reset SBIG Camera being power-cycled 00:40:43         Camera1 Connected SBIG Camera connected (Set point -15°C) 00:41:10         SBIG Camera Take Image successfully completed (earlier flags are reset) 00:42:02         SBIG Camera Take Image failed (Command timed-out) 00:42:06         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:42:13   SBIG Camera Reset SBIG Camera being power-cycled 00:43:05         Camera1 Connected SBIG Camera connected (Set point -15°C) 00:43:12         SBIG Camera Take Image successfully completed (earlier flags are reset) 00:44:06   CcdCamera Frozen CcdCamera appears to be frozen at around 00:44 in section 'GetCameraProperties / Status' 00:44:37         SBIG Camera Take Image failed (Command timed-out) 00:44:41         CCDSoft Restarting CCDSoft being restarted (attempt to fix frozen CcdCamera) 00:44:48   SBIG Camera Reset SBIG Camera being power-cycled 00:51:11         CCDSoft Restarting CCDSoft being restarted (user action) 00:51:19   SBIG Camera Reset SBIG Camera being power-cycled 00:52:10         Camera1 Connected SBIG Camera connected (Set point -15°C) 00:52:16         SBIG Camera Take Image successfully completed (earlier flags are reset) 00:52:59       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 00:54:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 00:54:55       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:57:00       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 00:58:53       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 00:59:13     Target Completed (NrZen) Target completed (Focus Field 16, HIP 78946) 00:59:15     Target Missed (1/8) Target's time slot was missed (1/8, T CrB) 00:59:17     Target Missed (2/8) Target's time slot was missed (2/8, GCVS CY Lyr) 00:59:19     Target Started (3/8) Target started (3/8, 61 Cyg) 00:59:38     Target Aborted (3/8) Target aborted (3/8, 61 Cyg) due to Priority 1 ToO Target 00:59:42     Target Started (4/9) Target started (4/9, T CrB, ToO) 01:00:05     Target Failed (4/9) Target failed due to slew error (4/9, T CrB, ToO) 01:02:03 User Intervention User Intervention to abort job queue & switch back to Manual Mode 01:02:06   Queue Aborted Job Queue aborted 01:02:08 Observatory (Manual) Observatory placed in Manual Mode 01:02:51     Target Started (1/1) Target started (1/1, T CrB) 01:10:13     Target Completed Target completed (1/1, T CrB) 01:12:09     Target Started (1/1) Target started (1/1, GCVS CY Lyr) 01:16:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:18:01       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 01:22:00     Target Completed Target completed (1/1, GCVS CY Lyr) 01:22:19     Target Started (1/1) Target started (1/1, GCVS BL Lac) 01:26:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:28:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:32:31     Target Completed Target completed (1/1, GCVS BL Lac) 01:34:54     Target Started (1/1) Target started (1/1, NGC 5957 w/SN2025fvw) 01:39:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:41:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:58:26     Target Completed Target completed (1/1, NGC 5957 w/SN2025fvw) 02:02:19     Target Started (1/1) Target started (1/1, C/2023 C2 (ATLAS)) 02:07:31       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:10:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 02:22:01     Target Completed Target completed (1/1, C/2023 C2 (ATLAS)) 02:22:12 User Intervention User request to close and finish session 02:22:14 Session Closing Session closing 02:23:02   Dome Closed Dome closed (Closing time 49s, Zigbee 43s) 02:23:20   Dome Parked Dome parked (parking time 11s), Az: 90.0 deg 02:24:10   Telescope Parked Telescope parked (parking time 45s total) 02:24:33   Telescope State Handbox reads 'Scope parked Turn scope off.' 02:24:55   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 02:26:19   Services Stopped Night Services stopped 02:26:22 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 02:26:34     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 02:27:18     Dome Find Park found (Best Park Az 90.3°) 02:27:23     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.3°) 02:27:26   Dome Parked Dome parked 02:27:47   Dome Charging Dome is parked and re-charging Ok (21mA) 02:27:49 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 00:34:18 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:35:39 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 00:37:04 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:38:14 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 00:39:40 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:41:10 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 00:42:02 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:43:12 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 00:44:37 Red Alert SBIG Camera Alert Take Image failed (Command timed-out) 00:44:41 Red Alert CcdCamera CcdCamera appears to be frozen (last cycle at 00:44:06) in section 'GetCameraProperties / Status' 00:52:16 Green Clear SBIG Camera Take Image successfully completed (earlier flags are reset) 02:27:47 Green Clear Dome Charging Dome is parked and re-charging Ok (21mA)

Back to Top

Operational Issues (2025-06-01, S1331)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (6)
• Small Defects (3)
• Continuous Improvement (4)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Locate Frame 3 failed during Near Zenith Focusing due to Camera Issue (00:33).  After successfully taking the first two locate frames for Focus Field 16, the 3rd Locate Frame failed due to CCDSoft/CCDCamera freezing. Issue was resolved at the time by an automated RestartCCDSoft() operation to  TakeImageASync called the CCD.TakeImage method at 00:33:37.29  which was returned at 00:33:37.33. Camera.Status moved to 'Taking Picture' at 00:33:37.39, and to 'Exposing Light' at 00:33:39.12.   The 10s exposure should have finished at 00:33:49 (TakeImageAsync set a TimeOutPoint of 00:34:18.29).  At 00:33:54.90 the Obs.Monitor was logged as "Pending (4s) in section 'Refresh Dome Picture/Draw Camera State'  "  implying it froze at around 00:33:50 - 00:33:51 .    At the same time (00:33:54.90) a CcdCamera holdup was logged with message "CcdCamera is Pending (5s) ' in section 'GetCameraProperties / Status' ", implying it froze at around 00:33:49 - 00:33:50.  Between 00:33:51.98 and 00:33:55.99, Get CCDCamera.Status/State/IsExposureComplete' were each logged to have "timed-out after 2s", implying a freeze time at 00:33:50.   TakeImageAsync recorded that its 'Wait on Camera.TakeImage completion'  had timed out at 00:34:18, and at  00:34:22 the RestartCCDSoft() operation was called. It would seem that ObsMonitor task are commencing before the Image has finished downloading and this might have caused CCDSoft to lock up.  TakeImageAsync could probably have intervened at an early moment to call RestartCCDSoft given that ObsMonitor and CCDCamera were both showing Pending/Potential Frozen States. 
   To investigate  2025-06-02 (Session, AstroMain 3.75.1)
   
• Focus Frame 1/23 , 7/23 & 16/23 failed during Near Zenith Focusing due to Camera Issue (00:36- 00:44).  After successfully recovering after Locate3 failure, with successful acquistion of Locate Frame 4 and Focus Locate Frame, the first focus profile frame (1/23) failed.  TakeImageAsync called CCDCamera.TakeImage to take 0.3s subframe at 00:36:33.12, and set a TimeOutPoint of 00:37:04.42.  Get IsExposureComplete was reported to have timed out after 2s at 00:36:37.42 which implies a freeze time at 00:36:35.42.   Obs.Monitor was logged as " Pending (4s) in section 'Refresh Dome Picture/Draw Camera State' at 00:36:40.17.  At around the same time CcdCamera was logged  as "Pending (5s) ' in section 'GetCameraProperties / IsExposureComplete' " at 00:36:40.18 which implies a freeze time at around 00:36:35.  Issue is similar to the one that occurred at 00:33 during Locate Frame3.  The immediate automated call to RestartCCDSoft was successful and the focusing profile continued with frame 2/23 after first posting an apparent measurement result from frame 1/23.    Further frame failures/RestartCCD operations occured for focus frame 7/23 at 00:39  & frame 16/23. at 00:44.   Whilst the RestartCCDSoft() operation after frame 7/23 was successful, the RestartCCDSoft operation at 00:45 following the 16/23 failure was not with the ConnectCamera element reporting "SBIG driver: Device not found"  issue after both connection attempts.  Frames 16/23* to 20/23* failed with log file recording "TakeImageAsync  Fail | Camera is not connected "  and "Camera not restarted. Number of RestartCCDSoft calls has been exceeded".   User intervened and manually initiated a RestartCCDSoft() operation at 00:51 which successful restored Camera operability. and focus frame 21/23 & 22/23 were successfully acquired and focus profile was successful.   If the job executor had been allowed to make follow-up RestartCCDSoft attempts would it have been able to restore the Camera operability itself, or was user involvement neccessary (when the 'SBIG driver: Device not found' issue occurs does it need permissions that the automated thread doesn't have ? )  Modify RestartCCDSoft to make it be called by invoking a threaded operation start via objconsole. (early attempts to invoke RestartCCDSoft via objconsole caused the UI to lock up for the duration of the operation).  Threshold test for restarting CCDSoft using nRestartCCDSoftDuringFocusing counter is increased from 3 to 7 on AstroMain 3.75.1.   AstroMain 3.75.1 also changed to use  objConsole.Invoke(Sub()   )  to call every RestartCCDSoftByThread() except the one called via button click.
   Fix / Mitigation attempted  2025-06-02  (AstroMain 3.75.1)
   
• Slew to ToO Target 4/9, T CrB failed (00:59).  The Planned observation of  target 1/2 (T CrB) failed due to missed start. After the session resumed and CCD Camera Issues were overcome and the telescope was focussed the queue continued with Target 3/8 (61 Cyg). Whilst the 61 Cyg target was starting T CrB was submitted as a 'Take Immediately ToO Target' from AstroPlan which was imported to AstroMain's Queue at 00:59. The Slew to 61 Cyg (started at 00:59:24.73) was aborted by the Job Executor (at 00:59:31.67), after which the Post Slew Scope Checks gave the message "Scope isn't pointing to the target" & "Possible 'Timed out waiting for received data' problem". These were not unexpected given the situation. Operations then moved directly to Target 4/9 (T CrB)  ". The slew to T CrB (called at 00:59:55.35) was reported as taking 1s, and the following messages were given "Zero Dome Slew Angle   Warning - Slew Angle = 0.0" and "Scope isn't pointing to the target (Ang Sep. = 64.4 arc degs)" and the target was reported as "Target failed  (Due to slew error)".  As a consequence of this Job Queue/automated operations were aborted by the user and the session moved back to manual mode. There were no telescope slew problems during the following Single-Object (ad-hoc) imaging of T CrB was successfully achieved (telescope slew angle of 89.8° in 33.6s) and this mode of semi-manual operation was continued until the end of the night. Logfile shows that the original attempted slew to T CrB failed due to an exception with the message "Command in progress". Before that logs show Telescope.Abort being given at 00:59:31.67 which was some 6s after the telescope slew to 61 Cyg was commenced.  What do the MeadeGeneric log show and suggest ?. Examining the MeadeGeneric Ascom log from the session shows slew to 61 Cyg coords being received at 00:59:25.15, the scope starting to slew at 00:59:25.43, the Abort Slew being received at 00:59:26.54 and scope still slewing for some 32s more, with Slewing = False not showing until 00:59:58.85.   The driver doesn't record the next SlewToCoordinatesAsync until 01:02:58.60 (during the slew from the manually initiated T CrB target). There is no SlewToCoordinatesAsync log line at around 00:59:55.35.  It would seem that attempted call to slew to RaDec  should not have been made as the telescope was still slewing at this time. AstroMain's slew to target should check telescope state.  DeviceHub's ASCOM Telescope Log for the TheSky6 connection shows SlewToCoordinatesAsync: Method being entered at 00:59:25.15 with the Method being exited at 00:59:30.81.  The next SlewToCoordinatesAsync: message is at 01:02:58.60 .  The DeviceHub activity log show slews at 00:59:25.88 and 01:02:59.32, but there is no indication of any slew attempt in between.  Issue fixed in AstroMain 3.75.1, the scope is check upon entering OB.SlewToTargetRaDec and if scope is found  to be unexpectedly slewing the routine enters a wait loop which waits for current slew in progress  to end or exit upon a 3 minute timeout.
   Fixed  2025-06-02 (AstroMai 3.75.1)
   
• AstroNorthCam's 'find stars' routine continues to pick up to many false positive from clouds  (2025-06-01).  AstroNorthCam 1.4.5 has been released with a new feature to detect stars in nighttime images. This was developed/tested on images from Jan 2025 and hasn't really been tested with images from late May/June.  During the first part of the night 2025-05-31 there were some cloud moving eastwards along the northern horizon and appeared to attract a lot of false - 'star' detections. During the night of 2025-06-01 there was similar isssues wuth a lot of false positives.  So many that the NorthCam StarCount line shown on the NIghtSummary plot is misleading.  Until a fix is made the feature needs to be turned off in some way. A separate Continuous Improvement ticket has been rasied to add a checkbox that can be used to suppress the transfer of StarCount number to AstroAllSky/AstroMain and instead issue a Null count (vcNull).   This was added in AstroNorthCam 1.4.6 and will be used until an improved Find Stars algorithum can be delivered.
   To resolve  2025-06-02 (AstroNorthCam 1.4.6, AstroAllSky)
   
• Subsurface Temperatures measured with the DS18B20 Temperature Sensor Probe show anomalous flat values. The surface temperatures measured by the DS18B20 Temperature Sensor Probe aided by Ardunio Circut & Script typically shows periods where the temperature is fluctuating between 2 or 3 discrete temperatures (ie expected measurement jitter / random read errors) and periods up to 10 hours long where the temperature reading appear absolutely flat (see Fig 1).  It is unclear if there is an issue that is causing the temperature sensor / ardunio project to stop reading new values and then resume again or that the reading is close enough to a read value that it is liable to jump between 2-3 values which are offset from actual temperature. A separate Continuous Improvement ticket has been rasied to log every Subsurface Temperature reading to a separate log file for analysis. This was added in AstroMag 1.4.20 and will be reviewed after a day or two to see what it indicates.
   To understand & resolve  2025-06-02 (SAM III system, AstroMag 1.4.20)
   
• X & Y Magnetometer reading are noticeably drifting upwards (2025-06-02).  Following the G3 Geomagnetic Storm on the morning of 2025-06-01 both X & Y magnetometers are both been drifting upwards relative to Comparsion Stations (whilst the Z axis has been drifting downwards slightly. The drift isn't steady. The X Axis anomaly occurred from 13:00 to 21:00 on 2025-06-01. A similar issue occurred on 2025-05 -xx.  The upwards drift would suggest that either the system was experiencing colder temperatures that assumed during the drift period, or that raw values were being overly corrected by the temperature coefficients used.  The cause and the solution may only be discovered once the planned GA tool is built.
   To understand & resolve  2025-06-02 (SAM III system, AstroMag )

Small Defects

• Resuming Queue after Session Suspension happened before Take ObsCam Image/Aux Light Switched Off (00:28).  Due to a slight timing issue the report messages 'Resuming Queue / Queue continuing after Session Suspension' were reported before the ReportComment2B message 'Aux Light  / Aux Light has switched off', which is logically part of the Session Suspended operation.  The Resume Queue code should be delayed until after the time that the 'Aux Light has switched off' would be expected. message has stroNorthCam's 'find stars' routine continues to pick up to many false positive from clouds  (2025-06-01).   Logs show command to Take ObsCam Image being made at 00:28:20 (Suspended Stage 2), with Aux Light being turned on/off at 00:28:21 and then repeated Turn on again at 00:28:27 and then turned off again at 00:28:49.55 (on time 22s)  and then unexpectedly turned on again at 00:28:49.58 (Suspended Stage 4).  The log shows ObsManager entering Suspended Stage 9 (Release JobExecutor) at 00:28:54 (5s later).   At 00:28:56.55 the log records a Zigbee Event -  Aux Light switched off (00:28:56, on time 7 sec) during Suspended Stage 11.   The behaviour of the Aux Light is odd, so the issue with the Queue Resuming before the AuxLight switches off is more of a glitch in the Zigbee/Aux Light system ? Nevertheless it is proposed to add a hold with timepoint before Releasing the JobExecutor in Suspended Stage 9.  Fixed in AstroMain 3.75.1.
   Fixed  2025-06-02 (AstroMain 3.75.1)
   
• AstroNorthCam's 'find objects/birds' routine is picking up false positive from a particular house in nearby estate (2025-06-02 / 2025-06-03).  AstroNorthCam routine to detect daytime objects, most particularly flying birds, is regularly picking up a false positive detection from the tip of the roof of the highest house in the housing estate in NNE direction (Fig 2).  The exclusion zone needs to be modified to ensure tip of house is not included in the active region.
   Fixed  2025-06-03 (AstroNorthCam 1.4.7
   
• AstroAllSky is creating NightSummaryPlot pictures with overly long TickMarks on bottom of AllSky Track (2025-06-02 / 2025-06-03).  As a side effect of recent implementation of NorthCamStarCount axis a bug has been introduced that gives rise to very long TickBars in DPD and Stars / Clarity Axes. Bug fixed in AstroAllSky 3.24.2.
   Fixed  2025-06-03 (AstroAllSky 3.24.2)

Continuous Improvement

• Add Subsurface Temperature Logging to AstroMag.  The surface temperatures measured by the DS18B20 Temperature Sensor Probe aided by Ardunio Circut & Script typically shows periods where the temperature is fluctuating between 2 or 3 discrete temperatures (ie expected measurement jitter / random read errors) and periods up to 10 hours long where the temperature reading appear absolutely flat (see Fig 1).  It is unclear if there is an issue that is causing the temperature sensor / ardunio project to stop reading new values and then resume again or that the reading is close enough to a read value that it is liable to jump between 2-3 values which are offset from actual temperature. It is proposed to write every read value out to a separate log file for analysis. 
   Done  2025-06-02 (AstroMag 1.4.20)
   
• Add a checkbox to AstroNorthCam program to suppress the output of NorthCam StarCount. AstroNorthCam 1.4.5 was been released with a new feature to detect stars in nighttime images. This was developed/tested on images from Jan 2025 and hasn't really been tested with images from late May/June.  During the first part of the night 2025-05-31 there were some cloud moving eastwards along the northern horizon and appeared to attract a lot of false - 'star' detections. During the night of 2025-06-01 there was similar isssues wuth a lot of false positives.  So many that the NorthCam StarCount line shown on the NIghtSummary plot is misleading.  Until a fix is made the feature needs to be turned off in some way.  It is proposed to to add a checkbox to Charts Tab (default value - unchecked) that can be used to suppress the transfer of StarCount number to AstroAllSky/AstroMain and instead issue a Null count (vcNull).   This was added in AstroNorthCam 1.4.6 and will be used until an improved Find Stars algorithum can be delivered.
   Done  2025-06-02 (AstroNorthCam 1.4.6, AstroAllSky)
   
• Modify AstroMag to be able to download & use Comparison Station data from a 5 day period.  AstroMag 1.4.20 download Comparison Station data from a two day period (typically yesterday and today) which provides sufficient data to create 24h stackplots.  However it is intended to be able to in future create Stackplot Charts covering a 5 day period and to use comparison data in a new GA tool to determine best settings parameters that give best temperature correction for Clair Geomagnetic Station.  AstroMag has already been modified to handle 5 days worth of Clair data.  This ticket is to update ImportStationData() routine to load up to 6 days worth of data (last 5 day files and today).  Implemented in AstroMag 1.4.21.   Implementation has been done in such a way that once past day files have been download, they are then accessed from disk instead of being repeatedly downloaded every 10mins. To ensure their presence & completeness they are re-downloaded upon the first call to ImportStation data after AstroMag is started. The files for the current day are always downloaded (as they will contain new data since the last downloaded. To handle UT / LT differences the past day file will be uploaded up to 01:00 on the current day.  a 'backdoor' checkbox 'Force Station Download' can be use to force day files to be redownloaded if there is some doubt about their presence or completness, or a different time period or set of stations are being used for making historical charts.
   Done 2025-06-02 (AstroMag 1.4.21)
   
• Modify AstroMag to be able to create 5 day Charts.  AstroMag 1.4.21 and earlier versions are designed to just make 24h charts.  However it is intended to be able to in future create Stackplot Charts covering a 5 day period and to use comparison data in a new GA tool to determine best settings parameters that give best temperature correction for Clair Geomagnetic Station.  AstroMag has already been modified to handle 5-6 days worth of Clair data and 5-6 days worth of Comparison Station data..  This ticket is to update Charts routine to lbe able to create 5d charts whilst retaining capability to make the standard 24h charts.  Implemented in AstroMag 1.4.22.  AstroPlan 1.43.11 also modified to updated the rename file Latest.MagnetogramChart_XYZ.png, and to upload the latest 5d charts.
   Done 2025-06-03 (AstroMag 1.4.22, AstroPlan 1.43.11)

[ Prev | Next ]

[ Prev | Next ]

Back to Top