David's Astronomy Pages Notes - Session 1316 (2025-04-22)

Notes (S1315)

Notes Main

Home Page

Notes (S1317)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (6),  Continuous Improvement (18)
	Images from 2025-04-22 >>
	Current/Latest Session >>

Session Aims & Highlights (2025-04-22)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. Scope Path. Test new Scope Path plotting routine and check that it is producing smoother/less angular path
3. SN 2025fvw . Acquire a fresh set of images of NGC 5957 w/SN 2025fvw following enforced break due to run of cloudy nights
4. C/2025 F2 (SWAN). Acquire further images of new comet C/2025 F2 (SWAN) if possible

 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.7,  AstroPlan 1.43.1,  AstroShCap 1.3.15, AstroGuard 1.10.6   (any new items or versions in bold)
  AstroMag 1.2.10, AstroVOE 1.15.1,  AstroSN 1.14,  AstroProtect 1.10.6,  AstroMove 1.15.10
  AstroWeather 1.27.8, AstroAllSky 3.23.5,  AstroObsCam 1.11.4 (not 1.11.5), AstroColorCam 1.2.10, AstroLaunch 1.12.3

Highlights

• Targets. 11/14 planned target observations were completed,2 futher targets were completed.   Two ToO targets (NGC 5957 w/SN 2025fvw & C/2025 F2 (SWAN) were also acquired.
• C/2025 F2 (SWAN). Best attempt to acquire Images of C/2025 F2 (SWAN) waking up tosubmit Target as a ToO at 03:50 but it was low in sky in NW and morning haar was developing.
• SN 2025fvw. Images of SN 2025fvw  were collected at two different times during the night.
•   Dome. There was no issues opening/closing the shutter during the session. Dome closed and parked at end of session ok.

Notes

• Good Seeing
  
  

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 23:19:02 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:18 & 03:14 23:19:04 Session AutoStarting Session autostarting (23:19) 23:19:25   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:19:52   Camera1 Connected SBIG Camera connected (Set point -10°C) 23:19:55 Session Created Session Created (Live, 2025-04-22 S01316, ImageSaveNum: 1316001) 23:20:00   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 23:21:47   Services Started Observatory Services started 23:21:56 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:21:59 Session Pending Session pending (2025-04-22) 23:22:01 Session Initiating Session initiating (2025-04-22) 23:22:11   Camera1 Connected SBIG Camera connected (Set point -15°C) 23:22:18   Plan Requested Observing Plan requested from AstroPlan (1.43.1) 23:23:58   Plan Loaded Observing Plan loaded to queue (Plan ID: 1100) 23:24:40   Telescope Connected Telescope connected (TheSky6) 23:25:04 Session Equilibration Session ready to Open Dome 23:25:49   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 23:25:51 Session Running Session running 23:25:54   Queue Started Observing Queue started (13 targets selected) 23:25:57     Target Started (NrZen) Target started (Focus Field 12, HIP 58514) 23:26:12       Dome Unparked Dome unparked 23:30:04   CCDSoft Restarting CCDSoft being restarted (user action) 23:30:11   SBIG Camera Reset SBIG Camera being power-cycled 23:31:05   Camera1 Connected SBIG Camera connected (Set point -15°C) 23:34:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:37:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:40:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:40:36       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:42:51       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:44:46       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:45:07     Target Completed (NrZen) Target completed (Focus Field 12, HIP 58514) 23:45:11     Target Started (1/13) Target started (1/13, 29P/Schwassmann-Wachmann) 23:49:54       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:52:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:04:26     Target Completed Target partially completed (1/13, 29P/Schwassmann-Wachmann) 00:04:30     Target Started (2/14) Target started (2/14, NGC 5957 w/SN2025fvw, ToO) 00:09:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:11:57       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 00:28:03     Target Completed Target completed (2/14, NGC 5957 w/SN2025fvw, ToO) 00:28:05     Target Missed (3/14) Target's time slot was missed (3/14, LEDA 2155454 w/SN2025erh) 00:28:08     Target Started (4/14) Target started (4/14, NGC 2744 w/SN2025oq) 00:48:37     Target Completed Target completed (4/14, NGC 2744 w/SN2025oq) 00:48:42     Target Started (5/14) Target started (5/14, NGC 4639) 01:08:00     Target Completed Target completed (5/14, NGC 4639) 01:08:04     Target Started (6/14) Target started (6/14, NGC 4654) 01:12:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:14:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:30:40     Target Completed Target completed (6/14, NGC 4654) 01:30:44     Target Started (7/14) Target started (7/14, NGC 3277 w/SN2025coe) 01:34:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:37:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:53:53     Target Completed Target completed (7/14, NGC 3277 w/SN2025coe) 01:53:57     Target Started (8/14) Target started (8/14, NGC 3521 w/SN2024aecx) 01:59:17       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:16:22     Target Completed Target completed (8/14, NGC 3521 w/SN2024aecx) 02:16:27     Target Started (9/14) Target started (9/14, UGC 10058 w/SN2025gvs) 02:20:15       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:23:03       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 02:39:06     Target Completed Target completed (9/14, UGC 10058 w/SN2025gvs) 02:39:11     Target Started (10/14) Target started (10/14, AT2024aeey) 03:01:57     Target Completed Target completed (10/14, AT2024aeey) 03:02:01     Target Started (11/14) Target started (11/14, T CrB) 03:05:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:08:02       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 03:12:57     Target Completed Target completed (11/14, T CrB) 03:13:01     Target Started (12/14) Target started (12/14, 2MFGC 13744 w/SN2024afyu) 03:16:44       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:19:22       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 03:36:25     Target Completed Target completed (12/14, 2MFGC 13744 w/SN2024afyu) 03:36:29     Target Started (13/14) Target started (13/14, NGC 5957 w/SN2025fvw) 03:50:51     Target Aborted (13/14) Target aborted (13/14, NGC 5957 w/SN2025fvw) due to Priority 1 ToO Target 03:50:55     Target Started (14/15) Target started (14/15, C/2025 F2 (SWAN), ToO) 04:03:50     Target Aborted (14/15) Target aborted (14/15, C/2025 F2 (SWAN), ToO) due to User Intervention 04:03:55     Target Started (15/15) Target started (15/15, HIP 87937) 04:05:29   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:05:31   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 04:05:33     Target Aborted (15/15) Target aborted (15/15, HIP 87937) due to cloud 04:05:35   Queue Paused Queue paused for Session Suspension 04:05:37 Session Suspending Session suspending 04:06:23   Dome Closed Dome closed (Closing time 50s, Zigbee 44s) 04:06:26 Session Suspended Session suspended 04:12:32     Target Cancelled Target cancelled (15/15, HIP 87937) due to cloud 04:12:36   Queue Completed Job Queue completed 04:12:39 Session Closing Session closing 04:12:44   Dome Closed Dome already closed (closed at 04:06, closing time 50s, zigbee 44s) 04:13:30   Dome Parked Dome parked (parking time 36s), Az: 90.0 deg 04:14:11   Telescope Parked Telescope parked (parking time 35s total) 04:14:35   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:14:57   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:16:21   Services Stopped Night Services stopped 04:16:24 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:16:46     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:17:29     Dome Find Park found (Best Park Az 90.2°) 04:17:34     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 04:17:37   Dome Parked Dome parked 04:20:15   Dome Charging Dome is parked and re-charging Ok (18mA) 04:20:17 Session Finished Session Finished

Session Alerts & Alarms

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

Back to Top

Operational Issues (2025-04-22, S1316)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• SBIG Camera became unresponsive near start of session (xx:xx). After AutoStart connected to the CCDSoftSBIG Camera and turned on temperature regulation (-15°C) the Camera Temperature in CCDSoft was noted to be stuck on "7.5° (100%)" and evidentally stuck waiting for camera to stabilise at -15°C. Resolved by user intervening to Restart CCDSoft (including SBIG Camera).  This resolved the issue and the session continued. It is possible that AstroMain would have intervened itself at some point to Restart CCDSoft (inc SBIG Camera).  Monitor File records that clearly stuck on 7.5° (100%) from 23:23:44 to 23:29:44. After the Restart CCDSoft operation the monitor records show -12.7 (100%) at 23:31:44 and -16.1 (65%) at 23:33:44.  Logfile shows CCDCamera GetProperty timeouts at 23:20:27 to 23:20:29  but then a normal camera connection at 23:22:01 to 23:22:11, but a series of CCD Camera Property timeouts from 23:30:15 to 23:30:49, but these were whist SBIG camera was being restarted. It would appear that CCD Camera was getting data from CCDSoft ok, but the data coming from the SBIG Camera wasn't being updated.  A separate Continuous Improvement ticket is raised to monitor CCD and if cooling is on 100% and CCD Temperature doesn't change for 3 minutes, and is above  -5 degC the SBIG Camera can be deemed to be frozen and a restart CCDSoft operation should be run.
  Closed after review 2025-04-24 (Session, CCDSoft/SBIG Camera,  AstroMain, User Awarness)
   
• In-line CoPilot code suggestions have disappeared from Visual Studio (2025-04-23).  Copilot was recently enabled in Visual Studio on or around 2025-04-11 and it has proven itself to be a very useful assistent when writing and developing code.  It generally has a good sense of what I'm looking to do next.  However the facility has disappeared.  Investigating showed that Copilot it is still installed but I've run out of free code completions on the Copilot Free plan (see Fig 1). It will apparently reset on 2025-05-11 or if I upgrade to Copilot Pro (which cost $10 per month or $100 per year).  Reason for issue is understood.  A Continuous Improvement ticket is open to consider upgrading to Copilot Pro.  
  Issue understood 2025-04-18 (Visual Studio, CoPilot Plan, User Awareness)
   
• Unable to play a .mp4 file on AllSky/Weather Computer by clicking on file in Windows Explorer.  Whilst trying to diagnose an issue with DayVideos & First Frames, a video .mp4 file was clicked on and after a short delay an error dialog was produced with the message shown in Fig 2.  Computer may be near its processing limit. Problem repeated with several other .mp4 files.  Computer slow , but using 'Send To'   a media player worked ok.  Monitor situation, repeat test after computer is restarted to allow Windows Update to proceed.   Problem have resolved , as the problem didn't present itself after the computer was restarted later in the day.
  Resolved 2025-04-24 (AllSky/Weather Computer, Windows Explorer, Windows Media Player, MP4 files)

Small Defects

• The initial images from Near Focus Field were noticeably out of focus.   Foc1 focusing selected an initial Focus Position that was quite a bit smaller than the Foc1 position that we eventually determined.  Why was such a low focus position selected ?.  FOc1 Wide Focusing was able to establish rough focus position which was refined using standard Foc1 focusing. To review.  Foc1 focusing position during course of last session (S1315, 2025-04-11) was consistently around 2600-2800. The final focus profile (C/2025 F2 (SWAN) ) of the S1315 session indicated a best focus at 2614 steps (at 2.2°C).  The Locate frames for Near Zenith Focus focusing were acquired at a focus position of around 2276.  The Foc1 Wide Focusing run  (using C Filter) was centered on a forecast Focus Position centred on 1950 based on previous session focus offset and the ambient / tube temperature of 8.8°C. Whilst Focus was forecast to be at 1950, the Focus Run found the best focus at 3570 in wide profile focusing which was then refined to a best focus at 3536 in the standard profile focusing.  Focus star at 1950 had a FWHM of 16.0, which explains the doughnut shaped stars seen in the initial Locate Frames. Fits Header indicates that the Locate 1, Locate 2 and Locate 3 frames were taken with Focuser Position at 2031, 1950 & 1950 respectively. It would seem that Primary Mirror shifted position in-between sessions. Rather than the usuallly seen reduction in TCF-S focus position,  on this occasion the TCF-S focus position has increased. This might have directly or indirectly corresponded to the insertion a a few days ago of inserting two soft but firm wedges around the telescope's focus knob, which is aim to make the primary mirror less prone to shifting,  Prehaps the initial shift reflects the new firmer position but may prevent or reduce future shifts in focus,  (The focus knob was held at a position with number 50 on the low side). Ticket closed as the focusing was resolved, but situation should continue to be monitored,
  Closed 2025-04-23 (Session, LX200, Foc1 Focusing) , but continue to monitor.
   
• Incorrect First Frame poster pictures for NorthCam Day Video are being generated/uploaded to website. Reviewing the Latest NorthCam Day Videos on Website in morning of 2025-04-24, shows that the correct DayVideo (from 2025-04-23) and correct Prior Day video (from 2025-04-22) are played, but the Day Video player shows a FirstFrame poster picture from 2025-04-23 08:59:46 instead of expected First Frame containing the 2025-04-23 05:24:14 picture.  After several days of investigation and added tracing, it was eventually determined that the problem was due to a DayVideo being unnecessarily created at 05:24 which leads to StartDayVideoTime being reset, which causes it to be set again at 08:59/09:00.  Fix implemented by also resetting EndDayVideoTime when DayVideo is built at the end of daytime period, which stop DayVideo being built again at start of day period in the morning, and therefore stopping the issue with the First Frame Poster Picture being shown on the website.
  Fixed 2025-04-24 (AstroColorCam 1.2.13)
   
• AstroMag's SAM Monitor exited due to a badly formatted record in sam_dat.txt file (2025-05-25 01:00).  Directly after starting a new UT day, AstroMag's SAM Monitor exited via a loosely handled exception with the message "Index and length must refer to a location within the string. Parameter name: length".  Running 'Translate Sam File' utility later on the 'sam_data.txt revealed that the exception was occuring when parsing the record date/time from the first record in the file "25.04.25: X,21647,Y,,Z,44847".  Fixed in AstroMag 1.3.3 by using an inner Try.Catch.EndTry block so that the exception can be caught without needing to exit the read & process sam record loop.
  Fixed 2025-04-23 (AstroMag 1.3.3)
   
• AstroMag's Logfile is reporting that the LastRecord before Shuffling has a null record time ?  (2025-04-23).  Log file is consistently showing a null date/time for last record ahead of each hourly reshuffle operation as shown below
    2025-04-25 23:00:00.16 | nRecords before shuffling MagRecord() by 1 hour : 1416
  2025-04-25 23:00:00.16 | First Record :2025-04-24 22:00:55
  2025-04-25 23:00:00.16 | Last Record :0001-01-01 00:00:00
  2025-04-25 23:00:00.16 | nRecords after shuffling MagRecord() by 1 hour : 1359
  2025-04-25 23:00:00.16 | First Record :2025-04-24 23:00:52
  2025-04-25 23:00:00.16 | Last Record :2025-04-25 21:59:23
  Bug found and fixed in AstroMag 1.3.6.
    Fixed 2025-04-26 (AstroMag 1.3.6)
   
• AstroMag's Date Age field doesn't show correct age since Most-RecentSam Record if SAM View stops running. AstroMag 1.3.5 currently shows the Age since Last SamData Record when a new Sam record becomes available, but in between times and if SAM_View stops totally stops working or stops running the Age field isn't updated. This is fixed in AstroMag 1.3.6.
    Fixed 2025-04-26 (AstroMag 1.3.6)
   
• AstroMag was unintentionally closed (2025-05-25 pm).  AstroMag was unintentionally and unknowingly closed.  Checking remote VNC connection to Observatory Computer showed that AstroMag wasn't running as expected.  The program shouldn't be allowed to close when SAM Monitor & Temperature Monitor's are running. There should be a warning/request for confirmation to prevent an unintentional closure of the program. In addition a "Closing AstroMag" message should be recorded in logfile when program is closed. Fixed in AstroMag 1.3.6
  Fixed 2025-04-26 (AstroMag 1.3.6)

Continuous Improvement

• Extend AstroPlan to upload latest magnetometer charts produced by AstroMag.  AstroMag has been recently extended to produce 3 magenetometer charts and copy them to the Live Folder every 10 minutes. AstroPlan's WebUpload routines should be modified to upload the 3 files (Latest.MagnetogramChart.png, Latest.MagnetometerActivityChart.png  & Latest.MagnetometerStackChart.png) to the Observatory Website.   Website has been modified to display the charts on the Aurora Watch page (see  Aurora Watch Page (Magnetometer Station section) )
  Done 2025-04-23 (AstroPlan 1.43.2, Website)
   
• Extend AstroMag to draw produce DHZ and DIF Magnetometer Charts. AstroMag 1.3 currently produces  XYZ Magnetometer Chart (through Y axis Magnetometer remains offline). To utilise the 3-axis fully a new routine has to be implemented to calculate other vector field strengths (H and F) and angles (D & I), and the Magnetogram Chart needs extending to allow the creation of DHZ and DIF magnetogram charts. Implemented in AstroMag 1.3.1.  Without Y reading the routines need to be able to simply use X for generating the H field, and just use X and Z for generating the F f(total) field. Assumptions also have to be made for generating the D and I angles.  AstroPlan 1.43.3 updated to upload the new charts to the Observatory website.
    Done 2025-04-23 (AstroMag 1.3.1, AstroPlan 1.43.3)
   
• Extend AstroMag to draw a Downhole Temperature Graph. AstroMag reads and records downhole temperature from a sensor located with the buried Magnetometer Sensor Assembly  to upload latest magnetometer charts produced by AstroMag.  Up to now the only way to visualise any  temperature trends is to import mag_data.dat file into Excel and to plot temperature.  This was useful during indoor testing to understand the strong negative relationship between magnetometer reading and temperature.  Down that the magnetometer are buried they are less suspectable to temperature fluctuation due to the greater thermal stability below 0.8m of soil.  However it is useful to confirm minimal daily temperature variations and to measure and understand seasonal differences in temperature. In this regard it would be useful if AstroMag could automatically and manual create g a temperature chart automatically produced by AstroMag would be useful. Basic implemention made in AstroMag 1.3.2. This produces a graph covering a 24 hour period - either the last 24 hours when the SAM Monitor is running, or for any user specified date/time.  AstroPlan 1.43.3 updated to upload the new chart to the Observatory website.
    Done 2025-04-23 (AstroMag 1.3.2, AstroPlan 1.43.3)
   
• Extend AstroMag to calculate and display noise level in X over the past 30 mins / 10 mins.  To assist investigations into the level of noise in magnetometer reads, modify AstroMag to calculate and display the noise in X readings over the past 30 min period. Implemented in AstroMag 1.3.5 using two new functions : Get30minNoiseLevel(cutoffdate as date) & CalculateNoiseLevel(data() as integer).  The later function came from a Copilot Chat request.  30s noise calc/display implemented in AstroMag 1.3.5 on 2025-04-23.   This was changed to implement a 10 min noise level (based on raw 10s readings) in AstroMag 1.3.6 on 2025-04-26
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Create a setting in AstroLaunch that can detail the folder name of the current CumulusMX program.  The AllSky/Weather computer has an ongoing issue whereby after a computer restart or issue, the CumulusMX.exe program no longer works correctly (and either can't see the Ecowitt GW2000 or can't serve weather data to local host or write to data files).  In this case the workaround is to copy the entire program folder to a new folder (e.g. CumulusMX3 to CumulusMX4) and restart CumulusMX from the new created program folder. This leaves an issue that the process to Launch CumulusMX program is hard-coded to the former program location, and AstroLaunch program has to be modified to replace the old program path with the new one.  This is arkward task.  It is proposed to have the CumulusMX program folder name to become a user changeable setting in AstroLaunch (and the Setting is then saved to a disk ini file).  It is also proposed to have a backdoor facility that can copy the past program folder to the new one. Implemented in AstroLaunch 1.13
  Done 2025-04-24 (AstroLaunch 1.13)
   
• Add a 'Plot Charts Now' button to AstroMag.  AstroMag 1.3.5 currently plots Charts every 10 mins when the SamMonitor is running.  Sometimes there is a need to immediately see the effect from making a change or whatever.   Adding a button to set a 'bPlotCharts' flag that is usedby the monitor in deciding whether to plot charts would allow this added functionality.  The monitor could also set the flag itself whenever a new hour is begun to allow the stackplot chart and activity chart to be as closely aligned in Scandinavian and SAMNet charts online. Implemented in AstroMag 1.3.6.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Add a check in AstroMag to ensure that there isn't already a version of the program running.   Implemented in AstroMag 1.3.6.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Add a button to AstroMag to allow SAM View to be launched.  Implemented in AstroMag 1.3.6 , based on the code/routines used in AstroLaunch 1.13.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Modify AstroMag to load/save a settings file upon opening/closing.  Implemented in AstroMag 1.3.6. Settings like Offsets, Magnetogram Interval and 200nT Bar Height are saved to the file "AstroMag_settings.dat" in program folder.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Make AstroMag automatically change the y scale on activity chart, according the highest acivity seen during 24 hour period.  The scale range of the recently added Activity chart is currently hard coded (~ 0-220 nT).  In the event of higher activity levels the ActivityChart class object needs to be able to automatically adjust the y scale to c. 0-400 nT. Implemented in AstroMag 1.3.6.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Add a utility facility in AstroMag to allow current day's Sam Files to be purged. In the event of a particular badly formatted SAM record, the SAM View application will crash and can not be successfully restarted, under a workaround is used involving either deleting or moving SAM View's current day files to a side folder.  This is tedious to do manually especially if using a VNC Connection from IPad. It would be helpful if AstroMag had a 'Purge Sam Files' facilty that allowed the set of 6 current day files (.txt, .log, .sam) to be moved to a a timestamped purge folder. The facility should only proceed if SAM View isn't running.  Implemented in AstroMag 1.3.6, using btnPurgeTodaysSamFiles_Click() and PurgeSamFiles() routines.
    Done 2025-04-26 (AstroMag 1.3.6)
   
• Modify AstroMag's Temperature and Magnetogram Graphs (2025-04-27). Slightly modify Temperature Chart width (to be consistent with Magnetogram Charts) and annotate with the most recent temperature value.  Reduce Magnetogram Heights from 650 to 450 (to reduced the white space occupied on total of 3 graphs (XYZ, DHZ & DIF). Slight modification to Date labelling. Implemented in AstroMag 1.3.7
    Done 2025-04-27 (AstroMag 1.3.7)
   
• Extend AstroMag to produce a moving window based activity chart.  AstroMag 1.3.7 currently produces an activity chart based an layout used by SamNet which plots maximum activity see within 1 hour bins as a histogram plot.  This new ticket item proposes adding a second activity chart with same width as the Magnetogram charts, that plots maximum activity based on a 30 min moving average. This plot with be better at showing activity in near real time (the existing chart has to wait for an hour interval to finish before it can draw a new bar) and will show activity with greater resolution.  Implemented in AstroMag 1.3.8 using new ActivityCharts2 object.   AstroPlan 1.43.4 updated to upload 'Latest.MagnetometerActivityChart2.png' to the Observatory website.
  Done 2025-04-28 (AstroMag 1.3.8, AstroPlan 1.43.4)
   
• Add a facility to calculate and record the average outdoor temperature. To understand changes in the Downhole Temperature, associated with the buried magnetometer sensors, calculate and record/display the average 24 hr outdoor temperature. This could be daily number or a rolling 24 hour measurement.  It is unclear where this 24h average outdoor temperature is best calculated / accessed (AstroWeather ?, AstroMain ?, AstroMag ?).
  To consider 2025-04-24+ (AstroWeather, AstroMain, AstroMag)
   
• Extend AstroMag to produce a Downhole Temperature Graph over a selected time window. AstroMag 1.3.2 has been recently updated to produce a Downhole Temperature Chart covering the last 24 hours (SAM Monitor) or a selected 24 hour period (Utitlites) .It would be useful to be able to generate a graph from a special button utility on Utilities/Charts tabs that can produce a Temperature Chart over a longer period chosen by the user. (e.g Last 12 months, Last Month, Last Week).
    To do 2025-04-23 (AstroMag 1.3.2, AstroPlan 1.43.3)
   
• Modify AstroMain's TempMonitor/Overseer routines to recognise when CCD Temperature data has stalled and to restart CCDSoft.
  SBIG Camera became unresponsive near the start of the S1316 session and the Camera Temperature became 'stuck'  on "7.5° (100%)" whilst trying to stabilise at -15°C Camera.  The user intervened to Restart CCDSoft (incl SBIG Camera restart) and this was successful. AstroMain's TempMonitor routines should be able to recognise when the Temperature & Cooling seem to have stalled, and to intervene to restart CCDSoft.
  To do 2025-04-18 (AstroMain)
   
• Consider purchase of CoPilot Pro subscription. Copilot was recently enabled in Visual Studio on around 2025-04-11 and it has proven itself a very useful assistent when writing and developing code.  It generally has a good sense of what I'm looking to do next.  However the facility has disappeared.  Investigating showed that Copilot it is still installed but I've run out of free code completions on the Copilot Free plan. It will reset on 2025-05-11 or if I upgrade to Copilot Pro (which cost $10 per month or $100 per year).   Need to consider cost/benefit and make a decision.
  To consider 2025-04-24+ (Visual Studio, CoPilot Pro)
   
• Rebuild Geomagnetic Station using Shielded Cables.  The magnetometers in the buried magnetometer assembly (whose signal run in parallel for 10-12m through unshielded cAT6 cables) are giving readings with a much higher noise level than seen during indoor tests where cables were formed into loose bundles that were in general proximity but not in any parallel arrangement .   Testing on 2025-04-25 / 2025-04-26 (see noise test details) concluded that the noise issue is very probably due to cross-talk / interference between the 3 unshielded CAT cables connecting to the magnetometers, which run parallel. The diagnotic test that strongly supports this conclusion was a 3 hour run during which only one axis magnetometer (the X Axis magnetometer) was been operated. The issue is understood, but is not readily resolvable as it it requires digging up the whole subsurface magnetometer assembly & cabes and rebuilding from scratch using shielded CAT6 cables.  This ticket is set up to record this potential remedial task.
  On hold 2025-04-27 (Geomagnetor Station / Cables)

[ Prev | Next ]

[ Prev | Next ]

Back to Top