David's Astronomy Pages Notes - Session 1315 (2025-04-11)

Notes (S1314)

Notes Main

Home Page

Notes (S1315)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (1),  Minor Issues (2),  Small Defects (9),  Continuous Improvement (7)
	Images from 2025-04-11 >>
	Daytime Geomagnetic Storm (2025-04-16)
	Current/Latest Session >>

Session Aims & Highlights (2025-04-11)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. C/2025 F2 (SWAN). Acquire further images of new comet C/2025 F2 (SWAN)

 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.74.5,  AstroPlan 1.43,  AstroShCap 1.3.15, AstroGuard 1.10.6   (any new items or versions in bold)
  AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.15.6
  AstroWeather 1.27.7, AstroAllSky 3.23.2,  AstroObsCam 1.11.4 (not 1.11.5), AstroColorCam 1.2.2, AstroLaunch 1.12.2

Highlights

• Targets. 20/23 planned target observations were completed, 2 futher targets were completed.  2 ToO Targets (NGC 5957 w/SN 2025fvw & C/2025 F2 (SWAN) were also completed. 1 planned target was missed due to timeslot being replaced by a ToO.
  C/2025 F2 (SWAN). Images of C/2025 F2 (SWAN) were acquired in morning (4:25)
•   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

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 21:21:19 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:21 & 03:52 21:21:22   AutoStart Delayed Session delayed due to too few stars 21:28:37 Session AutoStarting Session autostarting (21:28) 21:29:00   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 21:29:28   Camera1 Connected SBIG Camera connected (Set point -20°C) 21:29:30 Session Created Session Created (Live, 2025-04-11 S01315, ImageSaveNum: 1315001) 21:29:35   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 21:31:18   Services Started Observatory Services started 21:31:26 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:31:28   AutoStart Delayed Session delayed due to too few stars 21:31:30 Session Pending Session pending (2025-04-11) 21:31:32 Session Initiating Session initiating (2025-04-11) 21:31:39   Camera1 Connected SBIG Camera connected (Set point -15°C) 21:31:41   Plan Requested Observing Plan requested from AstroPlan (1.43) 21:32:07   Plan Loaded Observing Plan loaded to queue (Plan ID: 1099) 21:32:48   Telescope Connected Telescope connected (TheSky6) 21:33:12 Session Equilibration Session ready to Open Dome 21:33:57   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:34:43 Session Running Session running 21:34:45   Queue Started Observing Queue started (23 targets selected) 21:34:48     Target Started (NrZen) Target started (Focus Field 10, HIP 49253) 21:35:02       Dome Unparked Dome unparked 21:39:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:42:23       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 21:44:45       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 21:44:47       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:47:00       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 21:48:49       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 21:49:08     Target Completed (NrZen) Target completed (Focus Field 10, HIP 49253) 21:49:13     Target Started (1/23) Target started (1/23, NGC 2890 w/SN2023xnl) 21:56:14       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:58:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:12:06     Target Completed Target partially completed (1/23, NGC 2890 w/SN2023xnl) 22:12:10     Target Started (2/23) Target started (2/23, AT2024aasb) 22:16:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:19:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 22:35:46     Target Completed Target completed (2/23, AT2024aasb) 22:35:50     Target Started (3/23) Target started (3/23, Vega) 22:42:07     Target Completed Target completed (3/23, Vega) 22:42:11     Target Started (4/23) Target started (4/23, SN 2023nlk) 22:46:07       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 23:02:31     Target Completed Target completed (4/23, SN 2023nlk) 23:02:35     Target Started (5/23) Target started (5/23, 29P/Schwassmann-Wachmann) 23:07:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:09:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 23:25:31     Target Completed Target completed (5/23, 29P/Schwassmann-Wachmann) 23:25:35     Target Started (6/23) Target started (6/23, T CrB) 23:30:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:32:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 23:37:21     Target Completed Target completed (6/23, T CrB) 23:37:25     Target Started (7/23) Target started (7/23, UGC 10058 w/SN2025gvs) 23:40:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:43:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:00:00     Target Completed Target completed (7/23, UGC 10058 w/SN2025gvs) 00:00:04     Target Started (8/23) Target started (8/23, NGC 3277 w/SN2025coe) 00:20:05     Target Completed Target completed (8/23, NGC 3277 w/SN2025coe) 00:20:10     Target Started (9/23) Target started (9/23, AT2025gcz) 00:25:56       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 00:43:05     Target Completed Target completed (9/23, AT2025gcz) 00:43:09     Target Started (10/24) Target started (10/24, NGC 5957 w/SN2025fvw, ToO) 00:47:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:50:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 01:06:58     Target Completed Target completed (10/24, NGC 5957 w/SN2025fvw, ToO) 01:07:00     Target Missed (11/24) Target's time slot was missed (11/24, NGC 2407 w/SN2025gmc) 01:07:02     Target Started (12/24) Target started (12/24, KIC 8462852) 01:14:14     Target Completed Target completed (12/24, KIC 8462852) 01:14:18     Target Started (13/24) Target started (13/24, AT2022abs (CV)) 01:17:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:20:23       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 01:26:53     Target Completed Target completed (13/24, AT2022abs (CV)) 01:26:57     Target Started (14/24) Target started (14/24, LEDA 1776479 w/SN2025gcv) 01:30:45       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 01:46:52     Target Completed Target completed (14/24, LEDA 1776479 w/SN2025gcv) 01:47:24     Target Started (15/24) Target started (15/24, AT2024xpy) 01:51:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:54:25       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 02:10:55     Target Completed Target completed (15/24, AT2024xpy) 02:10:59     Target Started (16/24) Target started (16/24, AT2022cya (CV)) 02:15:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:18:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 02:24:16     Target Completed Target completed (16/24, AT2022cya (CV)) 02:24:20     Target Started (17/24) Target started (17/24, AT2025fwb) 02:27:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:30:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 02:46:46     Target Completed Target completed (17/24, AT2025fwb) 02:46:51     Target Started (18/24) Target started (18/24, AT2023hru (CV)) 02:49:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:52:16       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 03:08:33     Target Completed Target completed (18/24, AT2023hru (CV)) 03:08:37     Target Started (19/24) Target started (19/24, AT2023ij (CV)) 03:12:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:15:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 03:21:25     Target Completed Target completed (19/24, AT2023ij (CV)) 03:21:29     Target Started (20/24) Target started (20/24, AT2024slv (CV)) 03:24:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:27:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 03:33:35     Target Completed Target completed (20/24, AT2024slv (CV)) 03:33:39     Target Started (21/24) Target started (21/24, GCVS BL Lac) 03:36:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:39:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 03:43:47     Target Completed Target completed (21/24, GCVS BL Lac) 03:43:51     Target Started (22/24) Target started (22/24, AT2023ygv) 03:47:40       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:50:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 04:06:52     Target Completed Target completed (22/24, AT2023ygv) 04:06:56     Target Started (23/24) Target started (23/24, AT2022pxo (CV)) 04:15:51     Target Completed Target completed (23/24, AT2022pxo (CV)) 04:15:55     Target Started (24/25) Target started (24/25, C/2025 F2 (SWAN), ToO) 04:20:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:22:33       Focusing Completed Foc1 AutoFocus Completed (Profile No 18) 04:33:14     Target Completed Target completed (24/25, C/2025 F2 (SWAN), ToO) 04:33:18     Target Started (25/25) Target started (25/25, UGC 12293 w/AT2025gyi) 04:49:20     Target Completed Target partially completed (25/25, UGC 12293 w/AT2025gyi) 04:49:22   Queue Completed Job Queue completed 04:49:25 Session Closing Session closing 04:50:20   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 04:50:38   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 04:51:27   Telescope Parked Telescope parked (parking time 45s total) 04:51:51   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:52:47   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:54:12   Services Stopped Night Services stopped 04:54:15 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:54:42     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:55:27     Dome Find Park found (Best Park Az 90.4°) 04:55:34     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.4°) 04:55:36   Dome Parked Dome parked 04:57:21   Dome Charging Dome is parked and re-charging Ok (18mA) 04:57:23 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 04:57:21 Green Clear Dome Charging Dome is parked and re-charging Ok (18mA)

Back to Top

Operational Issues (2025-04-11, S1315)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• 'Y' magnetometer readings show unexplained jumps of 100-1000 nT. The SAM III magnetometers are now buried in a 1.2m deep hole and feeding readings back to SAM III unit which are displayed in SAM_VIEW and can also be displayed in an Excel Graph (using data collated by  AstroMag). Y values show anomalous shifts/jump of 100-200 nT (see Fig 1). Situation was monitored and there were a further jumps of up to 1200nT
  A test was perform in which USB Power to the Ardunio Project Box and (thus power to the Temperature Sensor) was turned-off  which caused significant and immediate shifts in the X, Y and Z readings by -716nT,  -548nT & -454 nT respectively.  It was a surprise that the X and Z sensor readings were affected and by so much. This suggested that having the Temperature Sensor on was involved in someway with the anomalous shifts in magnetometer readings (in particular the Y Axis readings), and the Temperature Probe was left- unpowered. Whilst it appeared to have resolved the issue (with no problems for 5 hours) there was yet a further large upward shift of +1090 nT in Y readings and associated smaller shift of +120 nT in Z reading at 19:36 UT.  A further test will be performed in which the Y Axis Magnetometer is turned off (by disconnecting its wires from the SAM III unit. and monitor for any shift in Z readings. These will likely be subtle, but the aim is to establish the value of building a dedicated new Y Axis Magnetometer unit (decommisioning the existing Y Axis sensor in the process).
  To monitor 2025-04-14 (SAM III / Y Axis Sensor)

Minor Issues

• 'AstroMag's SamMonitor is encountering occasional exceptions, which lead to outages in data recording (2025-04-15). AstroMag encountered exception at around 23:59 - 00:00 UT and caused the loss of around 7 hours worth of magnetometer/temperature data recording until the issue was noticed in the morning.  This incident is easily hypothesised due to issue reading the SAM_View's sam_data.txt file as it rolls forward to a new empty file.  It is less easy to understand other exceptions and outages,  for example one at around 16:34 on 2025-04-15, and one at around around 07:06-07:07 UT on 2025-04-16 (which was just 24 mins after restarting AstroMag, due to early exception. It would be handy if AstroMag was able to log/report the message associated with exception and when exactly it occured. Fixed in AstroMag 1.24.4.
  Fixed 2025-04-16 (AstroMag 1.24.4)
   
• 'X', 'Y' and 'Z' magnetometer readings are anomously noisy. The SAM III magnetometers are now buried in a 1.2m deep hole and feeding readings back to SAM III unit which are displayed in SAM_VIEW and can also be displayed in an Excel Graph (using data collated by  AstroMag). Fig 2 compares the noise levels during indoor testing on 2025-04-08 with those during outdoor observations on 2025-04-14.  The graph from 2025-04-08 (Fig 2a) shows significantly lower noise levels (especially when the equipment was left totally undisturbed), the run was conducted on a workbench, with cables & self-build circuits made up, but not yet assembled.  The graph from 2025-04-14 (Fig 2b) shows significantly higher noise levels. The run was conducted with magnetometers and temperature sensor made up into an assembled fixture and placed downhole in its approximate final position, but not yet buried with cables run back to the SAM III Unit sitting in the Observatory.   Possibilities are
  1) the Temperature Sensor probe is somehow creating the noise (Temperature sensor is placed in same fixture as the magnetometers, though not particularly closer to X & Z sensor than during indoor testing, due to uncertainty / difficult assembly it is conceivable that the tip of the temperature probe is touching solder, wire or compenents on the self-built circuit associated with the Y Axis Magnetometer)
2) there is cross-talk between the cables wires associated with the 3 magnetometers and temperature sensor
(the cables (CAT6) are bundled using tape at 10cm intervals and run parallel for some 12-15m., whilst during the indoor tests the cables were loosely placed in a pile and didn't run parallel)
3) the sensors in the garden subsurface are affected by ground currents / noise that didn't effect the sensor when running indoors (the sensor hole would have been thought to be more isolated from external magnetic/electrical that the house interior).
4) the cable/wires or the SAM III unit are affected by hypothesied noise within the Observatory.
Propose to make some diagnostic tests that might provide a indication though :
  1) turn off the temperature sensor probe and run for 1+ hour (14:23 to 15:40+)
  2) turn off Y sensor and run for 1 hour
  3) Power the SAM III Unit from a A/C Socket on the Observatory's Power Panel, rather than a socket attached to UPS system in the Observatory Computing Bay
  4) connect the SAM III unit directly to the Observatory Computer, bypassing the Lindy USB Hub
   (whilst there are not indications that records coming from the SAM III are being corrupted, does USB cable transmit noise to the SAM III unit in someway)
  5) connect the SAM III unit directly the Development Computer (taken out to Observatory)
  6) turn-off the house's Internet-Over-Powerline (although no longer used in the Observatory, the signal could still be going over the power line to the Observatory).
  
  Turning off USB power to temperature sensor didn't noticeably decrease noise, but did cause and immediate shift in X, Y Z readings (X shift -716nT,  Y-548nT,  Z shift -454 nT)
  
  To monitor 2025-04-14 (SAM III / Y Axis Sensor)

Small Defects

• A small number of CCD images weren't acquired at their designated set point temperature (23:21). Locate Frames 2 & 3 from Target 9/23 (AT2025gcx, #1315073-74 ) were acquired at CCD Temeperature -19.1 & -18.2°C.  It is hypothesized that CCD Monitor was attempting to change set point temperature from -20°C to -15°C but ultimately gave up as Locate Frame 4 was acquired at -20°C ? , however logs provide no supporting evidence for this (cooling 63% & 68% are little different from preceeding & succeeding frames (64% &  62% respectively). The figure of 68% cooling does suggest that the camera had slightly boosted its cooling to take temperature back to -20°C, but it is unclear why temperature had dropped. The 4th Main Frame from Target 7/23 (UGC 10058, 1315063) had an anomolous CCD Temperature of -18.7°C instead of expected -20°C. The 5th image from Target  17/24 (AT2025fwb, #1315128) had a slightly anomalous temperature of -20.9°C instead of expected -20°C.  Closed after review 2025-04-12.
  Closed after review 2025-04-12 (Session, AstroMain)
   
• ' None' command on AstroMove's Backup Tab isn't unchecking AstroProtect or AstroVma. Fixed in AstroMove 1.15.7.   Progress Bar and Status isn't getting reset for AstroVma in initial fix. Fixed 2025-04-15 and reissued as AstroMove 1.15.7.
  Fixed 2025-04-15 (AstroMove 1.15.7)
   
• 'AstroMag' is occasionally capturing & displaying -127.0 temperature values (2025-04-14). AstroMag is now installed on Observatory Computer and is reading temperature values from the DS18B20 Waterproof Digital Temperature Sensor Probe that is located in the downhole Geomagnetic Sensor Fixture and tied back to Observatory via a 15m cable (3 wires).  The Ardunio is noted to occasionally pass back solitary 'null' values (-127.0) instead of actual temperatures (like 7.19).   This seems to be a limit of the sensor system in its new environment (it didn't seem to do this during indoor testing).   AstroMag should be updated so that solitary null values are ignored and the last valid temperature is presented and used for data logging.  If null value persist for longer than a certain time (5s ?) then the null value should be presented/used.  Later logging (added in AstroMag 1.2.5 or so) indicated that between 2025-04-16 12:26 and 14:22 (a period of 1h 56m) there had been 335 readings with -127.0 value. At a sampling rate of approximately 1s this corresponds to 335 bad values in 6960 reads, or a rate of 1 in 20 reads.
  Fixed 2025-04-14 (AstroMag 1.2.2)
   
• There are occasions when AstroMag's Monitors are running and the Stop Monitor button does stop the monitoring thread. It is noticed that there are occasions when either the SAM III data monitor or Temperature Monitor are running (as indicated by green 'running' flag) and clicking the associated 'Stop Monitor' doesn't seem to stop the monitor (or at least doesn't reset the 'running' flag back to red). It seems to happen when the monitor isn't getting data from the relevant source. It would seem that the check on associated bStopMonitor flag is by-passed ?. Investigating suggests that in event of a higher level exception, monitoring is being exited with resetting the running flag back to Salmon color.  Fixed in AstroMag 1.2.2.
  Fixed 2025-04-14 (AstroMag 1.2.2)
   
• 'AstroMag' is occasionally capturing & displaying anomalous temperature values (2025-04-14). AstroMag is now installed on Observatory Computer and is reading temperature values from the DS18B20 Waterproof Digital Temperature Sensor Probe that is located in the downhole Geomagnetic Sensor Fixture and tied back to Observatory via a 15m cable (3 wires).  The sam_data.dat file is noted to contain occasional 'bad' values,e g. record at 2025-04-14 18:43:52 showed a temperature of 85.0 (compared to preceeding and succeeding value of 9.13 and 9.19 respectively.  AstroMag 1.2.3 / 1.2.4 modified
  Fixed 2025-04-15 (AstroMag 1.2.4)
   
• X, Y, Z Magnetometer reading captured by AstroMag every 1 minute are pretty spikey (2025-04-14).  The spikey curves generated from AstroMag data file looks like read-noise.  Whilst the SAM_VIEW (logging mode) outputs reads every 10s, they only become flushed to the sam_data.txt file every 60s (ie every minute). Better (smoother / more representative) values can be obtained by averaging 6 reading across each 1 minute window.  AstroMag's Monitor Magnetometer should therefore be modified so that instead of reading the most recent reading every 60s, it should reads the last 6 lines and calculate the average reading. Implemented in AstroMag 1.2.4
  Fixed 2025-04-15 (AstroMag 1.2.4)
   
• AstroMag stopped recording data (2024-04-17 02:12). AstroMag's data file showed that data stopped recording at 02:12 LT (01:12 UT) meaning that data between 02:11 and 0:23 LT wasn't captured in the sam_data.dat file .  The program's log file indicates that aConversion Exception had occured at 02:12:59 with the message "Conversion from string "2017.04.25 01:11:36: X" to type 'Integer' is not valid" and the SamMonitor routine exited. Examining the sam_data.txt source file show a bad record at  01:12:08 UT.
    17.04.25 01:11:48: X,20879,Y,14929,Z,44512
  17.04.25 01:12:08: X,2017.04.25 01:11:36: X,20905,Y,14909,Z,44520
  17.04.25 01:12:18: X,20894,Y,14925,Z,44520
  The file shows a similar issue with records at 03:38:08, 06:02:36 & 07:16:08 UT
    17.04.25 03:38:0817.04.25 03:37:36: X,20785,Y,12772,Z,44333
  17.04.25 06:03:08: 17.04.25 06:02:36: X,20748,Y,12646,Z,44357
  17.04.25 07:16:08: 17.04.25 07:15:36: X,20766,Y,12550,Z,44357
  Later on after restarting SAM View it output an badly formatted record at
   17.04.25 09:54:507.04.25 09:54:18: X,21229,Y,,Z,44459
 17.04.25 12:34:51: 17.04.25 12:34:19: X,21147,Y,,Z,44375
  The creation of these badly formatted records would seem to be due to a bug in SAM View (or in SAM III unit itself ?).  The badly formatted record in the specific format expressed (where there are two date values) doesn't prevent AstroMag from determinating the record date from the first 17 characters of the first field, and the issue caused by the X axis value like  "2017.04.25 01:11:36: X" will be caught by a fix just added in AstroMag 1.2.7 which uses a custom Try.Catch.EndTry blocks to deal with null (missing) X, Y & Z values. It is possible that the badly formatted records in sam_data.txt is responsible for SAM View crashing with unhandled exception when program was restarted in the morning at 10:23. It was confirmed that the '2025-04-17.txt' record showed the same badly formatted records.  Issue is deemed to be resolved for AstroMag (through the originating problem with occasional badly  formatted SAM_View records remains). 
  Resolved 2025-04-17 (AstroMag 1.2.7)
   
• SAM View crashing with unhandled exception (2024-04-17 10:23). As part of diagnostic testing to understand problems involving significant shifts in Y Axis readings along with associated smaller shifts in X and/or Z Axis readings, SAM View was closed, SAM III Unit turned-off and the Y Axis Magnetometer was disconnected from the SAM III Unit.  After restarting SAM III, SAM_View was started,  but after a short while SAM View crashed with an unhandled AccessViolation exception in msvcrt.dll with message "Access violation writing location ..." . Restarting SAM_View showed that the problem was repeatable.  Issue resolved by removing the SAM View's data files for the current day (generic) & for 2025-04-17 (specific) by moving them to a separate folder, and then restarting SAM View. It is possible that the crash is caused by badly formatted records in sam_data.txt.  Separately it has been identfied that the sam_data.txt contains some badly formatted records (see above ticket in which bad records was causing AstroMag's SamMonitor to exit).  SAM View is seemingly able to recognise when there is a format problem as log file as it identifies a line in error
    SAM_View - Convert:
   1st sensor : X-component
   2nd sensor : Y-component
   3rd sensor : Z-component
  line 1303: 17.04.25 03:38:0817.04.25 03:37:36: X,20785,Y,12772,Z,44333
  Lines : 3305
  Correct : 3304
  Errors : 1
  Despite this self-analysis it evidentally doesn't prevent the program from crashing. Removing the bad records from 'sam_data.txt' and '20250417.txt' and splicing the earlier records and the more recent records together, allows the SAM View GUI to display the magnetogram but the program puts up an error dialog in German (see Fig 5) and crashes again (all before saving the new plot to the /Charts folder).  The .sam files (sam_data.sam & 20250417.sam) were deleted (and SAM View restarted to see what would happen but again the program crashed.  Unable to determine & fix the specific issue with SAM View's current files they were deleted and SAM View restarted afresh. 
  Resolved 2025-04-17 (SAM View)
   
• AstroMag crashing with unhandled exception whilst reading sam_data.txt file (2024-04-17 10:25). As part of diagnostic testing to understand problems involving significant shifts in Y Axis readings along with associated smaller shifts in X and/or Z Axis readings, the Y Axis Magnetometer was disconnected from the SAM III Unit.  After restarting SAM_View,  AstroMag's SAM Monitor was started,  but AstroMag quickly encountered an unhandled exception with a message like "string can be converted to integer".  Issue immediately recognised to be due to a null (empty) field for Y Axis value in SAM Views sam_data.txt file, with records like  "17.04.25 09:35:38: X,21177,Y,,Z,44404" . Issue fixed in AstroMag 1.2.7 by including handling for null value entries.  Handling included for parsing sam_data.txt record, for handling the averaging of 6 x 10s records, the substitution of null values (-999999) into the sam_data.dat file and display of null/missing data "--".
  Fixed 2025-04-17 (AstroMag 1.2.7)
   
• AstroMag isn't using 'AstroMag.log' file name for logging (2024-04-17). Whilst trying to track down exception details associated with an issue at 2024-04-17 02:12  the expected log file 'AstroMag.log' couldn't be located in the '/ Logs' folder.  After a bit of hunting it was determined that AstroMag was writing to a logfile called 'AstroVma.log'.  Issue fixed in AstroMag 1.2.8.    Existing AstroVma.log renamed as AstroMag.log and AstroMag (1.2.8) was restarted.
  Fixed 2025-04-17 (AstroMag 1.2.8)

Continuous Improvement

• Add functionality to AstroMain's VMA routines to record photometry measurements in the Photometry.DB database.  A sqlite database for recording Photometry Measurements has been added called Photometry.DB, which is managed from new AstroVma program.  Functionality should be added to AstroMain's VMA routines to record photometry measurements in the new database.  This is to allow continued prototyping of the AstroVma application.  Implemented in AstroMain 3.74.6.
  Done 2025-04-13 (AstroMain 3.74.6)
   
• Add Utility buttons to AstroMag to open useful folders.  AstroMag (1.2.2) has been created with monitors for SAM II data and Downhole Temperature.  It would be useful to have buttons/routine that allow the opening of a number of specific folders connected with the Geomagnetic Station.  Folders include SAM III Installation Disk (Software Source), SAM Program Folder (More Programs), Magnetometer Data, Magnetometer Charts. Also a button to open the Data file produced by AstroMag.
  Done 2025-04-14 (AstroMag 1.2.3)
   
• Add routines in AstroMag and AstroPlan that moves the SAM Magnetogram chart to 'live' folder and uploads it to Observatory website.  SAM_VIEW continuously updates a magnetogram chart that it saves to the files "C:/Data/Magnetometer/Charts/sam_data.png" and "C:/Data/Magnetometer/Charts/yyyymmdd" . AstroMag should be modified to include a thread that copies the file to the "C:/Data/CCD Imaging/Live/LatestSamChart.png" folder and also maintains a "PriorSamChart.png" file.   AstroPlan should be updated to upload the two files to the Observatory Website, and an appropriate place on a website page found to display the charts.
  Done 2025-04-16 (AstroMag 1.2.6,  AstroPlan 1.43.1, Website)
   
• Add field width formatting to the data file produced by AstroMag.  AstroMag stores records in a comma delineated file called 'sam_data.dat' based on data from SAM View's sam_data.txt and data read from Temperature Sensor. Whilst comma delineation allows the file contents to be read by a VB.Net application or imported into Excel, for visual review it would be handy if fields had a fixed with.  The X,Y, Z, H fields need to be wider enough to display vcNullLarge values (-999999).  Implemented in AstroMag 1.Implemented 1.2.7.
  Done 2025-04-17 (AstroMag 1.2.7)
   
• Add a 'Close Calculator Windows button/routine to AstroMove's Admin Tab. .
  Done 2025-04-17 (AstroMove 1.15.8)
   
• Finalise the tie-back of sensor cables to SAM III Unit. Sensors cables from the 3 magnetometers and the downhole temperature probe have been temporarily tied back to SAM III Unit and Ardunio Project Box respectively using the cables length and exposed wires used during indoor testing.  The cables are longer than needed and awkwardly they are of different lengths. Due to the different positions of the 3 sensors the Z Axis cable is shortest cable and X Axis cable is the longest. Observatory Computing Bay needs to be tidied up by finalising the tie-back of sensor cables. This will involve  cutting cables to equal length and the re-expose of CAT6 wires used for GND, Signal(Out) & 5vDC, and then reconnecting to the Pale Green coloured 10-port Terminal Block at the back of the SAM III Unit.  The Temperature Sensor cable to be similarly finalised, connected it to the 3-port terminal block in the Ardunio Project Box and its box lid finally attached.  Shortening the cable might make a small improvement to the noise issue that is seen to effect the magnetometer readings since the installation of the Sensor Fixture & Tie-back to Observatory.
  To Do 2025-04-16 (Observatory Computing Bay, SAM III Unit) 
    
• Add a facility to AstroMag to retrospectively build a data file segment from a SAM View data file.  In the event that AstroMag is not running for some reason, but SAM View is running, there is data that isn't getting captured in AstroMag's 'sam_data.dat' file. Where data is logged by SAM View into sam_data.txt or relevant file like 20250417.txt it would be useful if AstroMag could recover it, even if its to a work file that user manually splices into the 'sam_data.dat' master file.
  To Do 2025-04-17+ (AstroMag 1.2.9)

[ Prev | Next ]

[ Prev | Next ]

Back to Top

Daytime Geomagnetic Storm (2025-04-16)

A major daytime geomagnetic storm occured today (2025-04-16) which was picked up by the Observatory's new Geomagnetic Station which is still undergoing commissioning tests & observations.

After performing a diagnostic test involving turning off power to the station's downhole temperature sensor at 13:23 UT (which produced a downward shift in readings from all 3 magnetometers (X, Y & Z) it was noticed at around 14:20 that the readings from Station's X and Z sensors had been progressively increasing and the reading from Y sensor began to fluctuate more than it had been.   

Graph of Magnetometer Observations (2025-04-16)

A check-in to the latest Scandinavian Stacked Magnetogram Charts showed that there was significant ongoing geomagnetic activity, and there was a good correspondance between deflections is Scandinavian Magnetogram lines (H Component) and those seen in the Station's X Component plot.

Plot of Scandinavian Magnetometer Readings with an overlay of the X Component from Clair Observatory's geomagnetic station

Note: The shift in X readings at 13:23 UT in original data has been corrected in order to make the Clair Observatory's magnetogram.

NASA Auroral Forecast for 18:00 UT is shown below.

Back to Top