David's Astronomy Pages Notes - Session 1283 (2024-12-13)

Notes (S1282)

Notes Main

Home Page

Notes (S1284)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (5),  Continuous Improvement (3)
	Images from 2024-12-13 >>

Session Aims & Highlights (2024-12-13)

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 RC2.4692, MeadeGeneric 1.3.11.512 , UPB 1.5, ASCOM 7.0.3 RC2,  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 RC2
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.73.8,  AstroPlan 1.42.5  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.14   
  AstroWeather 1.27.1, AstroAllSky 3.21.10 / 3.21.11,  AstroObsCam 1.11.4 (not 1.11.5), AstroColorCam 1.1.5, AstroLaunch 1.11.12

Highlights

• Targets. 25/26 planned targets observations were completed with remaining 1 target partially completed. 
•   Dome. There was no issues opening/closing the shutter during 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 22:53:16 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:53 & 06:20 22:53:19 Session AutoStarting Session autostarting (22:53) 22:53:40   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 22:54:07   Camera1 Connected SBIG Camera connected (Set point -25°C) 22:54:09 Session Created Session Created (Live, 2024-12-13 S01283, ImageSaveNum: 1283001) 22:54:14   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 22:56:12   Services Started Observatory Services started 22:56:20 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:56:24 Session Pending Session pending (2024-12-13) 22:56:26 Session Initiating Session initiating (2024-12-13) 22:56:35   Camera1 Connected SBIG Camera connected (Set point -20°C) 22:56:37   Plan Requested Observing Plan requested from AstroPlan (1.42.5) 22:57:09   Plan Loaded Observing Plan loaded to queue (Plan ID: 1066) 22:57:49   Telescope Connected Telescope connected (TheSky6) 22:58:14 Session Equilibration Session ready to Open Dome 22:58:59   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 22:59:39 Session Running Session running 22:59:42   Queue Started Observing Queue started (26 targets selected) 22:59:46     Target Started (NrZen) Target started (Focus Field 4, HIP 18637) 23:00:00       Dome Unparked Dome unparked 23:02:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:05:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:08:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:08:15       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:10:29       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:12:21       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:12:39     Target Completed (NrZen) Target completed (Focus Field 4, HIP 18637) 23:13:06     Target Started (1/26) Target started (1/26, NGC 681 w/SN2024abup) 23:17:19       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 23:34:35     Target Completed Target completed (1/26, NGC 681 w/SN2024abup) 23:35:26     Target Started (2/26) Target started (2/26, GCVS FO Ori) 23:38:55       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:41:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:46:07     Target Completed Target completed (2/26, GCVS FO Ori) 23:46:11     Target Started (3/26) Target started (3/26, GCVS CN Ori) 23:49:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:52:10       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 23:59:50     Target Completed Target completed (3/26, GCVS CN Ori) 23:59:54     Target Started (4/26) Target started (4/26, Scholz's Star) 00:04:12       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:20:09     Target Completed Target completed (4/26, Scholz's Star) 00:21:17     Target Started (5/26) Target started (5/26, AT2023clj (CV)) 00:25:17       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:42:12     Target Completed Target completed (5/26, AT2023clj (CV)) 00:43:17     Target Started (6/26) Target started (6/26, UGC 8139 w/SN2024ifu) 00:48:26       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 01:04:47     Target Completed Target completed (6/26, UGC 8139 w/SN2024ifu) 01:05:37     Target Started (7/26) Target started (7/26, UGC 8630 w/SN2024drv) 01:10:10       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 01:26:26     Target Completed Target completed (7/26, UGC 8630 w/SN2024drv) 01:27:57     Target Started (8/26) Target started (8/26, 29P/Schwassmann-Wachmann) 01:31:37       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 01:46:37     Target Completed Target completed (8/26, 29P/Schwassmann-Wachmann) 01:49:11     Target Started (9/26) Target started (9/26, UGC 5426 w/SN2024aanq) 01:53:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:56:36       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 02:13:07     Target Completed Target completed (9/26, UGC 5426 w/SN2024aanq) 02:13:11     Target Started (10/26) Target started (10/26, SN 2023ufx) 02:16:24       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:19:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 02:35:12     Target Completed Target completed (10/26, SN 2023ufx) 02:35:16     Target Started (11/26) Target started (11/26, GCVS HH And) 02:40:23       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 02:42:22     Target Completed Target completed (11/26, GCVS HH And) 02:42:26     Target Started (12/26) Target started (12/26, UGC 604 w/SN2024advj) 02:46:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:49:10       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 03:05:24     Target Completed Target completed (12/26, UGC 604 w/SN2024advj) 03:05:28     Target Started (13/26) Target started (13/26, AT2024zys (CV)) 03:08:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:12:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 03:15:50     Target Completed Target completed (13/26, AT2024zys (CV)) 03:15:54     Target Started (14/26) Target started (14/26, MRK 0628 w/SN2024aakr) 03:20:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:23:05       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 03:39:04     Target Completed Target completed (14/26, MRK 0628 w/SN2024aakr) 03:39:09     Target Started (15/26) Target started (15/26, AT2023ae (CV)) 03:42:52       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:49:04     Target Completed Target completed (15/26, AT2023ae (CV)) 03:49:08     Target Started (16/26) Target started (16/26, IC 3084 w/AT2022aaai) 03:53:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:55:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 03:59:00       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 04:00:05       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 04:10:56       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 04:12:46     Target Completed Target completed (16/26, IC 3084 w/AT2022aaai) 04:12:48   Queue Paused Queue paused for Session Suspension 04:12:51 Session Suspending Session suspending 04:13:41   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 04:13:44 Session Suspended Session suspended 04:19:57 Session Resuming Session resuming 04:20:42   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 04:20:44 Session Running Session running 04:20:46   Queue Resumed Observing Queue resumed 04:20:49     Target Started (17/26) Target started (17/26, SN 2022mox) 04:36:03     Target Completed Target partially completed (17/26, SN 2022mox) 04:36:07     Target Started (18/26) Target started (18/26, GCVS U Gem) 04:40:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:42:32       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 04:45:42     Target Completed Target completed (18/26, GCVS U Gem) 04:45:47     Target Started (19/26) Target started (19/26, NGC 4722 w/SN2024ablh) 05:07:26     Target Completed Target completed (19/26, NGC 4722 w/SN2024ablh) 05:07:30     Target Started (20/26) Target started (20/26, NGC 5235 w/SN2024grb) 05:11:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:13:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 05:23:39     Target Completed Target completed (20/26, NGC 5235 w/SN2024grb) 05:23:43     Target Started (21/26) Target started (21/26, T CrB) 05:26:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:29:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 05:34:59     Target Completed Target completed (21/26, T CrB) 05:35:03     Target Started (22/26) Target started (22/26, UGC 11087 w/SN2024ixb) 05:39:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 05:41:35       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 05:58:33     Target Completed Target completed (22/26, UGC 11087 w/SN2024ixb) 05:58:37     Target Started (23/26) Target started (23/26, AT2024adwa) 06:18:44     Target Completed Target completed (23/26, AT2024adwa) 06:18:49     Target Started (24/26) Target started (24/26, AT2022qyh (CV)) 06:22:22       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 06:28:48     Target Completed Target completed (24/26, AT2022qyh (CV)) 06:28:53     Target Started (25/26) Target started (25/26, IC 1125 w/SN2024jz) 06:33:05       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 06:49:24     Target Completed Target completed (25/26, IC 1125 w/SN2024jz) 06:50:53     Target Started (26/26) Target started (26/26, GCVS R CrB) 06:54:18       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 06:56:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 06:59:55     Target Completed Target completed (26/26, GCVS R CrB) 06:59:57   Queue Completed Job Queue completed 07:00:00 Session Closing Session closing 07:00:53   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 07:01:13   Dome Parked Dome parked (parking time 12s), Az: 90.0 deg 07:01:52   Telescope Parked Telescope parked (parking time 38s total) 07:02:17   Telescope State Handbox reads 'Scope parked Turn scope off.' 07:02:39   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 07:04:05   Services Stopped Night Services stopped 07:04:08 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 07:04:35     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 07:05:21     Dome Find Park found (Best Park Az 90.6°) 07:05:26     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.6°) 07:05:28   Dome Parked Dome parked 07:07:58   Dome Charging Dome is parked and re-charging Ok (21mA) 07:08:00 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 05:35:45 Yellow Alert Dome Discrepency Difference between Dome Az and Telescope Az is > 8 deg (UGC 11087) 05:35:47 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (UGC 11087) 07:07:58 Green Clear Dome Charging Dome is parked and re-charging Ok (21mA)

Back to Top

Operational Issues (2024-12-13 S1283)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to make remote VNC Connection to AllSky/Weather Computer (2024-12-15).  A VNC connection to the AllSky/Weather Computer couldn't be made from the Development/Analysis Computer at 2024-12-15 16:00, even the remote computer could be pinged ok and a networked folder could be opened via Windows Explorer. UltraVNC Viewer gives the error message "Failed to Connect to Server".    Trying to get a remote connection from the Observatory Computer also generates the same error message. It would seem that there is an issue with the UltraVNC server on the AllSky/Computer.   Issue resolved by visiting the Observatory.  The computer screen was blank and it wasn't responsive to moving and pressing on its touchpad.  Eventually rebooted and after configuring Windows updates Windows was successfully started. Looking back at logs indicated that AstroWeather, AstroAllSky, AstroColorCam, AstroObsCam all stopped working at about the same time 02:19:58.  Although it is likely that it wouldn't have resolved things on this occasion a separate Continuous Improvement ticket has been raised to allow a computer on the local network (Development Computer or Observatory Computer to activate a process running on the AllSky Computer (prehaps AstroLaunch program) to restart the UtlraVNC Server in case this might be helpful at some point.. 
  Resolved (AllSky/Weather Computer, UltraVNC) 
   
• After Dome slewed to UGC 11087, the Dome slewed back to the previous target, before slewing again to UGC 11087 (05:35).  Associated with telescope slew to Target 22/26 (UGC 11087) a yellow  Dome Discrepency' alert was raised at 05:35:47 with the message "Difference between Dome Az and Slave Az is > 1 (UGC 11087)". This was proceeded by a yellow Dome Discrepency alert at 05:35:45 with the message "Difference between Dome Az and Telescope Az is > 8 deg (UGC 11087)". The timeline showed that MeadeGeneric still has a residual bug when it can momentarily return Slewing=False near the start of the telescope slew.   On this occasion DeviceHub PollScopeTask saw Slewing=False at 05:35:11.811 and cancels the telescope's 'Slew in progress' state, leading to anomalous Slave Dome Behaviour.  The case also shows an issue with DeviceHub's 'Follow the Scope' mode whereby after initially slewing the dome to UGC 11087 at Az 59.4° the Dome was then commanded to go to Az 75.7° and then back to Az 59.5° wasting 18s. The latter issue has been sent to the ASCOM Team via ASCOM Talk forum (https://ascomtalk.groups.io/g/Help/message/47784).   A new 7.0.3-RC3.4694 version of DeviceHub have been provided by Peter Simpson which fixes a bug in DeviceHub slaving logic. This was tested during daytime tests on 2024-12-17 along with MeadeGeneric 1.3.11-514.  Around 10 slews were made in total, most of these were with the dome slaved to the scope, with the telescope sometimes arriving at the target first in and with the dome arriving first in other cases.  Some tests were also made with the dome initially not slaved & then either turning slaving on during the telescope slew,  or after the telescope slew.   Nothing bad happened, and there were no anomalous slaved dome behaviour.  Since issues can sometimes only present with certain timing interactions (dependant on the precise timing of polling, tasks and arrival of data from a real driver etc, it is too soon to say that the issue is resolved.  The new DH version was used in the next two live sessions (S1284-S1285) and results, reviewed on 2024-12-20,  demonstrated that the issue has been successfully fixed (https://ascomtalk.groups.io/g/Help/message/47806)
  Fixed 2024-12-20 (DeviceHub 7.0.3-RC3.4694) 
   
• Yellow Dome Discrepency alerts was raised for the slew to UGC 11087 (05:35).  Associated with telescope slew to Target 22/26 (UGC 11087) a yellow  Dome Discrepency' alert was raised at 05:35:47 with the message "Difference between Dome Az and Slave Az is > 1 (UGC 11087)". This was proceeded by a yellow Dome Discrepency alert at 05:35:45 with the message "Difference between Dome Az and Telescope Az is > 8 deg (UGC 11087)". The report File showed the following message for the post-slew dome position check.
    Dome Position Check
  Dome Position      Info     Dome Az. 75.7° (vs. Scope Az. 58.7°, Delta Az. 17.0°)
  Dome Discrepency   Warning  Difference between Dome Az and Telescope Az is > 8 deg
  Dome Position      Info     Dome Az. 75.7° (vs. Slave Az. 59.5°, Delta Az. 16.2°)
  Dome Discrepency   Warning  Difference between Dome Az and Slave Az is > 1 deg
  A timeline had been determined based on AstroMain, DeviceHub and MeadeGeneric logs.   These show that MeadeGeneric, after initially returning Slewing=True (at 05:35:11.711) it then momentarily returns Slewing=False (at 05:35:11.810), before continuing to again return Slewing=True (at 05:35:11.820) and for the remainder of slew.  Problem is that DeviceHub PollScopeTask sees Slewing=False at 05:35:11.811 and cancels the telescope's 'Slew in progress' state, leading to anomalous Slave Dome Behaviour.  Issue had been sent to Colin Dawson via Discord.  The case also exposed an issue with DeviceHub's 'Follow the Scope' mode. This is documented in a separate ticket below. It isn't immediately clear why the MeadeGeneric driver was momentarily returning Slewing=False.  A new version of the driver has been provided (1.3.11-514) on 2024-12-16 which contains extra logging to try to better understand and identify the bug.   This new version was used during daytime testing on 2024-12-17 along with a new version of DeviceHub (7.0.3-RC3.4694).  Around 10 slews were made in total.  Nothing bad happened, and there were no anomalous slaved dome behaviour.  Since issues can sometimes only present with certain timing interactions (dependant on the precise timing of polling, tasks and  arrival of data from a real driver etc, it is too soon to say that the issue is resolved.  The new version of the driver was used in the next two live sessions (S1284-S1285) and results reviewed on 2024-12-20.  This show that in 1 out 54 slews made MeadeGeneric Driver unexpectedly returned Slewing=False in response's to DeviceHub Initial PollScopeTask causing DH to quickly cancel its 'Slewing In Progress' state session. Details have been posted on Discord.
  Waiting on support / new driver (MeadeGeneric 1.3.11-515+) 

Small Defects

• AstroMain announced that AllSky Star & Synopsis data was active again with a huge outage time (2024-12-15 16:29).  After annoucing that AllSky Star & Synopsis data has been inactive for more than 5 mins at 16:03:38 when AstroMain program was restarted to pick up a new version. After resolving the data issue on the AllSky/Weather Computer, AstroMain then announced an all-clear at 16:29:46  with the message  "AllSky Star & Synopsis data is active again (outage 18,385,469.8 mins)".  The display of a huge number associated with MinutesSince a Null date is inappropriate and needs to be fixed, either time since monitoring started or with "outage time is unknown".
  Fixed 2024-12-15 (AstroMain 3.73.8)
   
• Problem with NorthCam Rolling keogram plot following a 14 hour outage of the AllSky/Weather Computer (2024-12-15).  Due to an outage of the AllSky/Weather Computer at 02:20 from to 16:30, there was no new keogram lines added to the NorthCam Rolling Keogram during this time. When the ObsColorCam program was restarted and the prior Rolling Keogram data was shifted to the left end of the keogram ok. The 'infilled' HH  annotation wasn't drawn one pixel too high. And seem to be posted over older annotation. Due to the timing of the outage tasks that run at SunAlt 0 (Sunrise) and SunAlt 0 (Sunset), such as Closeout keograms and copy Day/Night Keograms to PriorDay/PriorNightKeograms didn't occur resulting in certain keograms being temporarily not the correct one.  Fixed in AstroColorCam 1.1.6., the posting over 'older annotation' is a mystery and can only be explained by AstroColorCam program still partially running during the 02:20 - 16:30 time frame, but how this was possible is unclear. 
  Fixed 2024-12-15 (AstroColorCam 1.1.6)
   
• Cropped Image Scale showing 0 on AstroMain ImageSets/Image Tab Post-Session Analysis).  After Capturing a 'Sq. Root' image of NGC 473 (from session S1262) the scale box for the cropped picture type (382 width) showed as 0 rather than 100. On clicking the adjacent 'Build' button an exception is reported  "Create enlarged image   Fail   Exception  (Parameter is not valid). Worked around by clicking on the '100' button, which opens Image Builder, showing a 100% sized image cropped as a 382 pixel wide picture. Issue seen on some other recent cases.  Problem also occured with UGC 1596 from session S1262 and it was run through Visual Studio debugger. It was found that ImageBuilder.GetLastCropScale()  routine was trying to determine scale from "sqrootscale125pc.crop.dat" filename, but failed and instead returned 0. If the file was renamed as "sqrootscale.125pc.crop.dat" the routine would correctly return the scale value 125, suggesting that there was a defect in the original creation of the settings file.   A workaround is incorporated in AstroMain 3.73.8 to use an alternative method of determining the image scale where these incorrectly named settings files have historically been created.  The routine that that creates the Settings filename has been modified to use existing file name using legacy name like "sqrootscale125pc.crop"  where '/_Settings/sqrootscale125pc.crop.dat' exists or like "sqrootscale.125pc.crop" where a legacy file doesn't exist.
  Fixed 2024-12-16 (AstroMain 3.73.8)
   
• A red UPB Powebox Alert should be raised when the Pegasus UPB Software is stopped (2024-12-15). Whilst testing code for when Dew Heater Control fails due to objPowerBox2 not being connected,  it was found that ObsManager correctly triggers a routine to restart UPB Software & Services including restart TCF-S Focuser, but no red alert is raised by ObsManager/ObsOverseer to record that an issue arose with the Powerbox.  The UPB PowerBox service is restarted by ObsManager when bRestartPowerboxConnection flag is raised. This flag is set to True when.   AstroMain 3.73.9 modified so that a red alert is raised at all points where the bRestartPowerboxConnection flag is raised.
  Fixed 2024-12-15 (AstroMain 3.73.9)
   
• A green AllSky/Synopsis' all-clear isn't reporting the outage time correctly (2024-12-18 08:39). At 08:38:56 a red 'AllSky/Synopsis' alert was raised during General Session with the message "AllSky Star & Synopsis data has been inactive for more than 5 mins". This was followed at  08:39:11 by a green 'all-clear' with the message "AllSky Star & Synopsis data is active again (outage 0.4 mins)". It would seem that the outage should have been reported as 5.3 minutes.   Its unclear why the issue exactly arises, has it happened at a change from Night to Day in AstroAllSky.    The outage is calculated from MinutesSince (LastScorecardOutageTime), where LastScorecardOutageTime is set to  Env.TimeOfLastUpdate(EProp.Scorecard) when the 'inactive for more than 5 mins' alert is raised (ie a point when Env.MinutesSinceLastUpdate(EProp.Synopsis) > 5 ) FOr consistency AstroMain/ObsManager Main Loop is changed in AstroMain 3.73.9 to set LastScorecardOutageTime to Env.TimeOfLastUpdate(EProp.Synopsis) instead of  Env.TimeOfLastUpdate(EProp.Scorecard).
  Fix attempted 2024-12-18 (AstroMain 3.73.9), but continue to monitor

Continuous Improvement

• Extend AstroMain's ImageSet Utility/Process to handle additional contents text. Extend ProcessTargetStr() routine to handle "- Dwarf Irregular Galaxy", "- Nearby Star" , "Type Ia-91bg", "Type Ic", "Local Group Galaxy", "Local Group".  Implemented in AstroMain 3.73.9.
  Done 2024-12-16 (AstroMain 3.73.9)
   
• Extend AstroAllSky's NightSummaryPlot6 to include a nighttime keogram track from the NorthCam.  AstroAllSky has recently be extended to draw the NorthCam Keogram lines from the new NorthCam Camera as a background to the DaySummaryPlot6. This new proposal is to widen the NightSummaryPlot6 chart and draw NorthCam Keogram lines in a new track on the right hand side of the chart.   AstroColorCam (1.1.7) modified to export of a keogram line every 30s instead of every 60s to support the NightSummaryPlot6 update frequency, and to export a 230px version of the keogram line 'Latest.NorthCamKeogramLine2.bmp'.
  Done 2024-12-17(AstroAllSky 3.22,  AstroColorCam 1.1.7)
   
• Extend AstroLaunch to be able to restart UltraVNC Server upon seeing presence of a Trigger File or some other Listening process.  A VNC connection to the AllSky/Weather Computer couldn't be made from the Development/Analysis Computer at 2024-12-15 16:00, even the remote computer could be pinged ok and a networked folder could be opened via Windows Explorer. UltraVNC Viewer gives the error message "Failed to Connect to Server". Trying to get a remote connection from the Observatory Computer also generates the same error message. It would seem that there is an issue with the UltraVNC server on the AllSky/Computer (it was later determined that there was a computer issue in which all programs seemed to have stopped work during the night at 02:20. Although it might not have helped in this situation but to potentially avoid making an observatory visit to resolve a problem in the future AstroLaunch program should be extended to able to restart the VNC Server upon seeing a specific trigger file placed on the computer remotely via Windows Explorer or even monitor the VNC Server process and restart it itself.
  On Hold (AstroLaunch)

[ Prev | Next ]

[ Prev | Next ]

Back to Top