David's Astronomy Pages Notes - Session 1221 (2024-05-29)

Notes (S1220)

Notes Main

Home Page

Notes (S1222)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (7),  Small Defects (15),  Continuous Improvement (9)
	Images from 2024-05-29 >>

Session Aims & Highlights (2024-05-29)

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 6.6.1.1,  MeadeGeneric 1.3.9, UPB 1.5, ASCOM 6.6,   Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.68.10,  AstroPlan 1.40.1,  AstroShCap 1.3.15, AstroGuard 1.10.5   (any new items or versions in bold)
  AstroVOE 1.13.2,  AstroSN 1.10.4,  AstroProtect 1.7,  AstroMove 1.12.12
  AstroWeather 1.24.2, AstroAllSky 3.20.4,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.3

Highlights

• Targets. 6/8 planned targets observations were completed, with 1 other target partially completed and 1 target replaced during the session by C/2021 S3 (PANSTARRS), which was submitted as a ToO target.
• Dome. No issues opening/closing shutter during session. Dome closed and parked ok at end of session.

Notes:

Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance

Sky Conditions (Locate Frames)

Night Sky Summary Plot Top axis: Sky Brightness at Zenith (in ADU/s) Lefthand axis: Local Time (hh LT). Righthand axis: Sun Altitude (degs)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 23:09:56 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:49 & 01:10 23:09:59   AutoStart Waiting AutoStart waiting till earliest start time at 23:49 23:49:34 Session AutoStarting Session autostarting (23:49) 23:49:55   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 23:50:22   Camera1 Connected SBIG Camera connected (Set point -10°C) 23:50:25 Session Created Session Created (Live, 2024-05-29 S01221, ImageSaveNum: 1221001) 23:50:30   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 23:52:16   Services Started Observatory Services started 23:52:22 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:52:24 Session Pending Session pending (2024-05-29) 23:52:27 Session Initiating Session initiating (2024-05-29) 23:52:36   Camera1 Connected SBIG Camera connected (Set point -10°C) 23:52:43   Plan Requested Observing Plan requested from AstroPlan (1.40.3) 23:53:52   Plan Loaded Observing Plan loaded to queue (Plan ID: 996) 23:54:34   Telescope Connected Telescope connected (TheSky6) 23:54:58 Session Equilibration Session ready to Open Dome 23:55:44   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 23:55:45   Equilibration Started Dome Equilibration started 00:00:44   Equilibration Ended Dome Equilibration ended (5.0 mins total) 00:00:46 Session Running Session running 00:00:49   Queue Started Observing Queue started (8 targets selected) 00:00:50     Target Started (NrZen) Target started (Focus Field 15, HIP 73454) 00:01:03       Dome Unparked Dome unparked 00:03:58       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:06:41       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 00:08:54       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 00:08:56       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 00:10:44       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 00:12:27       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 00:12:45     Target Completed (NrZen) Target completed (Focus Field 15, HIP 73454) 00:14:11     Target Started (1/8) Target started (1/8, IC 3091 w/SN2024jdi) 00:20:40       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:37:52     Target Completed Target completed (1/8, IC 3091 w/SN2024jdi) 00:37:57     Target Started (2/8) Target started (2/8, AT2024ivo (CV)) 00:40:59     Target Aborted (2/8) Target aborted (2/8, AT2024ivo (CV)) due to Priority 1 ToO Target 00:41:03     Target Started (3/9) Target started (3/9, C/2021 S3 (PANSTARRS), ToO) 00:44:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:47:13       Focusing Failed Foc1 focusing failed (failed QC check - RmsE) 00:55:24     Target Completed Target completed (3/9, C/2021 S3 (PANSTARRS), ToO) 00:58:51     Target Started (4/9) Target started (4/9, GCVS BL Lac) 01:01:37       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:04:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:08:09     Target Completed Target completed (4/9, GCVS BL Lac) 01:09:09     Target Started (5/9) Target started (5/9, GCVS HH And) 01:12:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:14:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:16:47     Target Completed Target completed (5/9, GCVS HH And) 01:17:36     Target Started (6/9) Target started (6/9, AT2024dsj (CV)) 01:20:48       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:23:02       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:29:21     Target Completed Target completed (6/9, AT2024dsj (CV)) 01:29:56     Target Started (7/9) Target started (7/9, LEDA 2222714 w/SN2024iey) 01:33:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:36:14       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 01:52:39     Target Completed Target completed (7/9, LEDA 2222714 w/SN2024iey) 01:52:43     Target Started (8/9) Target started (8/9, UGC 11087 w/SN2024ixb) 01:56:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:58:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 02:05:32       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (reducing clarity) 02:06:12   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:06:14   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:06:17     Target Aborted (8/9) Target aborted (8/9, UGC 11087 w/SN2024ixb) due to cloud 02:06:19   Queue Paused Queue paused for Session Suspension 02:06:21 Session Suspending Session suspending 02:07:17   Dome Closed Dome closed (Closing time 60s, Zigbee 43s) 02:07:20 Session Suspended Session suspended 02:11:32     Target Cancelled Target cancelled (8/9, UGC 11087 w/SN2024ixb) due to cloud 02:16:43 Session Resuming Session resuming 02:17:08   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 02:17:10   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 02:17:12   Queue Paused Observing Queue pausing for Session Suspension 02:17:28   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 02:17:31 Session Running Session running 02:17:33   Queue Resumed Observing Queue resumed 02:17:34     Target Started (9/9) Target started (9/9, GCVS AM Her) 02:21:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:24:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 02:29:31     Target Completed Target completed (9/9, GCVS AM Her) 02:29:33   Queue Completed Job Queue completed 02:29:35 Session Closing Session closing 02:30:30   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 02:31:11   Dome Parked Dome parked (parking time 34s), Az: 90.0 deg 02:32:29   Telescope Parked Telescope parked (parking time 72s total) 02:32:39   Telescope State Handbox reads 'Scope parked Turn scope off.' 02:33:01   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 02:34:27   Services Stopped Night Services stopped 02:34:30 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 02:34:42     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 02:35:43     Dome Find Park found (Best Park Az 90.2°) 02:35:49     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.2°) 02:35:51   Dome Parked Dome parked 02:37:15   Dome Charging Dome is parked and re-charging Ok (55mA) 02:37:17 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 02:37:15 Green Clear Dome Charging Dome is parked and re-charging Ok (55mA)

Back to Top

Operational Issues (2024-05-29 S1221)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Remote Access to Observatory & AllSky/Weather Computers & fresh of live file to Observatory Website went down (2024-05-29 21:50).  Visit to Observatory confirmed than connection to router & internet was down, but the two computers were still talking to each other via the observatory's Ethernet Switch.  Resetting Ethernet Over Powerline adapter didn't resolve problem, nor did a reset of the Ethernet Switch, or resetting the LAN cable connection into the Observatory Computer, though it did have the determinental effect that Zigbee devices could not longer be operated using deConz (as this requires IP address which presumab;y was lost).  Observatory Computer restarted,  but stil didn't connect to LAN/ Internet.  Seemingly resolved in this case by resetting the Ethernet OverPowerline adapter that the Router LAN cable connects (indoors). Internet connection came back for Observatory Computer (but initially very slow, before speeding up after one minute) and again began TCP/IP and general window connections with the AllSky/Weather computer. Check from indoors showed communication with the two computers in the observatory, but LAN speeds were recorded to be slow (Average : 4.1 Mbps, 0.51 MB/s for Laptop9,  3.9 Mbps, 0.49 MB/s for Laptop7) at 22:41, but improving later (Average : 12.5 Mbps, 1.56 MB/s for Laptop9,  13.1 Mbps, 1.64 MB/s for Laptop7) at 23:01. The next morning LAN connection was running more normally (Average : 13.8 Mbps, 1.73 MB/s for Laptop9,  15.5 Mbps, 1.93 MB/s for Laptop7) at 2024-05-30 09:26  (See Fig 1). Unclear why the issue took so long too resolve. Restarting the Observatory Computer wasn't necessary and led to lose of connection to Zigbee devices upon restart
Done 2024-05-27 (Observatory / LAN, Ethernet Over Powerline)
   
• Weather Station not recieving readings from Outside Temperature/Humidity Sensor.  Fresh? batteries  were added and sensor was moved closer to the base station a week ago after a few days of prior problems and this improved the communications from the sensor for a while, but the sensor is again 'offline'.  To be investigated, prehaps a reset of base station is needed ?  Investigation showed that LCD screen on sensor was blank. Batteries replaced with definitively new ones.  Initially LCD screen blank again, but manipulating batteries triggered the sensor into life (terminal corrosion issue ?).   Reset Weather Station and reset the Oregon USB Hub, and checked that fresh data was coming through to AstroWeather.
  Resolved 2024-05-30 (Weather Station)
   
• Condensation in the AllSky Camera has again appeared and has fully cleared.  During session the condensation was effecting views to ESE to N, and reduced star count by 20%.  AllSky Camera checked following day and due to stronger wind/low humidity the condensation had cleared.
  Resolved 2024-05-30 (AllSky Camera / Dew)
   
• Session attempt was unable to AutoStart due to CCDSoft/Camera failure (2024-06-05). An attempt to autostart a live session on the night 2024-06-05 was auomatically aborted upon encountering a failure during an initial CCDSoft.Camera check at 00:13, and AstroMain was placed back into General Session mode. This prevented the acquistion of any images from the hour or so of semi-darkness (see Fig 2).  Current AutoStart procedure used in AstroMain 3.68.11 intentionally makes an initial check of the CCDSoft.Camera in order to pre-empt a critical showstopper that would cause an unsuccessful live session before the live session s created and before the LX200 Telescope is connected.  This design feature was written before a robust means of automatically fix a problem connecting to the SBIG Camera.  Issue is closed as the software operated as per design.  A separate Continuous Improvement ticket is raised to modify the AutoStart procedure so that in the event that the SBIG Camera Connection Check failing the routine to automatically fix the connection is executed to try to allow the live session to proceed (implemented in AstroMain 3.69, 2024-06-06).
  Closed 2024-06-06 (AstroMain)
   
• AstroPlan stopped uploading files to website (2024-06-18 & 2024-06-23).  AstroPlan stopped uploading fresh copies of the ObservatoryStatus and GreenhouseState virtual pictures.  Investigating problem at around 2024-06-23 18:32 shows error "FTP Queue Loop stalled at 2024-06-23 18:32:42" followed by initial exception "Timeout waiting for WinSCP to respond" at 18:40:22, followed by exception "Session is not opened" for each subsequent upload attempt. .Fixed in AstroPlan 1.40.5,  added extra condition (  InStr(ex.Message, "Session is not opened") > 0 )  in the exception catch in the UploadFileUsingSecureTransfer() routine that raises the bRestartLoader flag.
    Closed 2024-06-23(AstroPlan 1.40.5)
   
• AstroMain Obs.Manager & Obs.Monitor freezing for periods up to 7 minutes (2024-07-02 & 2024-07-03). Only 5 or 6 occasions on 2024-07-02 - 2024-07-03 the Obs.Manager & Obs.Monitor threads reported as being frozen for 6-7 minutes at a time (e.g .at 2024-07-03 01:06,  05:07 & 07:07).  ScopeMonitor, CloudSensor & LAN variously reported as also being frozen at these times.  It is notable that on each occasion that the frozen threads were reported the threads were almost immediately (within 5-9s) reported to have resumed again. Was the issue due to Obs.Overseer becoming frozen ?.  The problem seemed to resolve itself.  Examining logs suggests that the issue was possibly being triggerred by or was causing Dome errors (e.g  Exception ("Object synchronization method was called from an unsynchronized block of code") whilst getting Dome.Connected & Dome.Slaved properties at 11:03:51, 13:00:05, 15:01:23, 17:01:52, 21:04:15, 01:06:29,  05:08:03 & 07:07:06.
  Closed after review 2024-07-09 (Session, Dome, AstroMain)
   
• Observatory & Weather Charts on Observatory Website stopped refreshing (2024-07-10).  During the evening 2024-07-12 it was noticed that none of the Observatory, Weather & Greenhouse Charts on Observatory Website hadn't been refreshed since 2024-07-10 19:20.  A visit to observatory 2024-07-12 22:55 showed that both computers were running ok and communicating with each other, but didn't have any Internet Connection. Problem eventually resolved but its required both computers to be restarted (a restart of AllSky/Weather Computer was in any case required by Window Auto Update), afteriInitial attempts to fix Lan/Internet connection by resetting Ethernet Switch and resetting Ethernet Over PowerLine adapters (both ends) didn't fix the issue. (It was probably a mistake to begin by resetting the Ethernet Switch).  Records show that there were no interruptions to Power Supply on 2024-07-10, but the LAN did drop out at 19:25 and didn't return until manual intervention at 2024-07-12 23:17.
  Resolved 2024-07-12 (Observatory, Ethernet/LAN)

Small Defects

• After resolving LAN connection issue, Forecast Wind Speed & Direction wasn't being displayed on Wind Charts generated by AstroWeather. It seems that the lost in Lan/Internet connection (renewed IP connection) stopped AstroWeather from being able to automatically load fresh Weather Forecast data.   Resolved by user in this instance by restarting AstroWeather.  Is there something that AstroWeather should do to automatically monitor and restart fresh Weather forcast AP connection.  A separate continuous improvement ticket is raised to look into this.
  Resolved 2024-05-30 (LAN, Weather Forecast)
   
• Reporting of Near Zenith Focusing indicated it was taking 0s Focus Boxes.  Although focus boxes were taken (at seemingly 0.000s exposure as indicted by CCDSoft File Information / FITS Header the images nevertheless did their job in capturing the focus star and allow FWHM measurement of that star to be taken, and the telescope re-focused correctly.  Investigating shows normal preparation after taking a 3s Focus Star Image (max pixel 58698), the focus star was identified and focus exposure reported to have changed to 0.3s.  Same thing in S1220-S1217 & S1215 sessions (0.3s / 0s box), but not in S1198 (0.7s box), S1116 & S1114 (1s box). Could it be a Integer/Double conversion issue or issue with Set ExposureTime in AstroMain's new Camera object ?.  Trace message in Log file  shows   'Set ExposureTime(1) ', but then Set ExposureTime(0) and Set ExposureTime(0.3) alternating.  A similar problem affected autofocusing for certain starfields (eg BL Lac) where the focus frame which was due to have exposure times of 1.5s were captured with exposure time of 2s (2.0).  Investigating code revealed the bug (CCDCamera.FocusExposureTime was declared as integer instead of double). Bug fixed in AstroMain 3.68.11.
  Fixed 2024-05-30 (AstroMain 3.68.11)
   
• Whilst analysing S912, Du-1 (pl.neb) was noted to be incorrectly sorted.  Whilst analysing backlog of sessions from 2021, Du-1 was noted to be sorted with Stars rather than being sorted with deep sky objects. Similarly Kn 61 (Pl.Neb) and VV 37 (Faint Galaxies) was also noted to be sorted with stars rather than with deep sky objects. Fixed in AstroMain 3.68.11.
  Fixed 2024-06-02 (AstroMain 3.68.11)
   
• Field 13 in ObsEnv is unexpectedly wide (2024-06-02 12:54). During a 17 min power outage (associated with indoor electrical work,  12:54:37 to 13:11:48), Field 13 in ObsEnv data file is shown as -99000.0 instead of normal values like -2.0, -3.0, 47 etc, and causes the field to be two characters wider than normal.  This field is probably shutter battery amperage, and is caused by vcNull * 1000 (ie -99 * 1000).  Fixed implemented in AstroMain 3.68.11 & data file corrected to show -99.0.
  Fixed 2024-06-03 (AstroMain 3.68.11)
   
• Greenhouse Temperature Graphs not showing Door Open flag. AstroMain & AstroWeather were updated recently to capture Greenhouse Door State in ObsEnv file (from 2024-05-26) and display the flag on GraphID=14 and 59.  However the flag isn't getting drawn when the Greenhouse Door is open.  Zigbee is recording the change in greenhouse door state, as evidenced by AstroMain Observatory reporting for 2024-06-02 and AstroMain is sending/saving the ObsEnv records ok .
  > Greenhouse Door Info Greenhouse Door has opened (14:14:03, close time 1.9 min)
> Greenhouse Door Info Greenhouse Door has closed (14:14:07, open time 4s)
> Greenhouse Door Info Greenhouse Door has opened (14:14:58, close time 51s)
> Greenhouse Door Info Greenhouse Door has closed (14:21:23, open time 6.4 min)
> Greenhouse Door Info Greenhouse Door has opened (14:27:15, close time 5.9 min)
  Issue identified to be due to AstroMain not including GreenhouseDoorState in the ObsEnv record sent to ALlSKy/Weather Computer and due to AstroWeather not parsing the GreenhouseDoorState field, leading to ObsEnv records being appended to AllSky/Weather Computer's ObsEnv file with Door State 0.  Fixed in AstroWeather 1.24.3.
  Fixed 2024-06-03 (AstroMain 3.68.11, AstroWeather 1.24.3)
   
• 'TNS ID' field on AstroPlan's Targets List is to narrow for longer TNS Ids.  Whilst the field width is ok for tns ids like '2021axb' it is too narrow for tns ids like '2021aaxp'.  Field widened in AstroMain 1.10.4.
  Fixed 2024-06-08 (AstroPlan 1.10.4)
   
• 'Align Frames' and 'Combine' operations not working (2024-06-10).  During Analysis work on S886, 'Align Frames' (and 'Combine') operations stopped working.  SendKeys from AstroMain's analysis routines not accessing CCDSoft's 'Align Folder of Images' and 'Combine Folder of Images' operations.   Investigating showed that there was a rogue CCDSoft process that couldn't be killed (Manually trying to kill the CCDSoft Process produced error 'Access Denied' . Issue resolved by restarting the computer.
  Fixed 2024-06-10 (CCDSoft, Development Computer, User Awareness)
   
• 'Build Annotated Image for 38P/Stephan-Oterma not showing object cross-hairs (S741 Analysis).  During Analysis work on 'Comet_38P_Stephan-Oterma 3x3 30s C' image set from S741, the cross-hairs for '38P/Stephan-Oterma' couldn't be seen on the stacked & plate-solved image. It was noticed that Crosshairs X/ Y  had the anomalous value -49306.8 / 39505.3. Crop Centre X/Y had the same anomalous values.  The '<Mid' button didn't put the centre coordinates as expected (values were left unchanged).  Fits Image is an older one and doesn't contain TAG-RA, TAG-DEC keywords, which are possibly necessary for calculating Cross-Hairs coords. TAG-RA/TAG-DEC manually entered but after relinkin Crosshairs X/Y took the values -137670.7 / 80372.3 which is different but still anomalous. It was necessary to add TAG-RA/TAG-DEC keywords to at least the first Reduced Image and re-create the Stacked Image from scatch.  Issue resolved. Issue is caused by missing TAG-RA / TAG-DEC keywords in older images.
  Resolved 2024-06-10 (AstroMain, TAG-RA / TAG-DEC, User Awareness)
   
• 'Copy Coords' button routine on AstroMain's Analysis ImageSets/Target tab isn't producing correct coordinates for "38P/Stephan-Oterma" (S741 Analysis).  Instead of coordinates of  around RA: 14 05 38.783, Dec: +05 13 14.21,  which is the calculated coords for 38P/Stephan-Oterma at the time of observation (2020-01-18)  the Copy Coords button produced the value RA: 15 23 41.483, Dec -09 51 31.72, which is present day coords for 38P/Stephan-Oterma  (2024-06-10).  This seems to occur because the FIT files are old ones which don't contain TAG-RA & TAG-DEC keywords, which are now added to new FIT files to show the target coordinates at time of image acquistion. Manually entering TAG-RA/TAG-DEC with the coordinates of 38P/Stephan-Oterma at the time of observation, and using Copy Coords button again now produces the expected correct coordinates
  Closed 2024-06-10 (AstroMain, TAG-RA / TAG-DEC, User Awareness)
   
• 'Shift-Home' & 'Shift-End' keypad operations are not selecting text as expected.  'Shift-Home' and 'Shift-End' keypad operations are used whilst editing text (for example in Web Expression) in order to select text to end of line,  or text to the beginning of the current line respectively. Whilst editing web pages the operation wasn't working correctly, the cursor would moved to end or start of line as expected, but the text wouldn't be selected.   Issue couldn't be fixed by restarting Web Expression or by restarting the computer.   Issue was fixed by pressing the NumLk to toggle between to numerical entry and then back to cursor entry. .
  Fixed 2024-06-14 (Development Computer, User Awareness)
   
• Web pages for 'Session Images'  (S1090 to S1114) use an incorrect (broken) url to session's Local Files page.  'Local File'  links incorrectly use 'CCD Imaging/Analysis/...'   (which was a path used in the past ) but sessions have been relocated in 2022 or so. Links should use  'CCD Imaging/Sessions/...'   instead. Pages since S1115 don't employ a local files link on session images as more detailed links are placed on trhe session's Session Notes page. Fixed 2024-06-17.
  Fixed 2024-06-17 (Website)
   
• Web pages for 'Session Images'  (S1088 to S1000-) show a Local Files link when page is viewed on internet, when it  should only be shown when page is viewed locally.  Fixed 2024-06-17 down to S1000. Links also updated to use 'CCD Imaging/Sessions/...'  path.
  Fixed 2024-06-17 (Website)
   
• Unable to correctly send FIT file path to Nebulosity for KUG 1206+328.  Whilst performing backlog analysis of session S889 clicking 'Nebulosity' button for target should have sent file path 'KUG_1206+328 3x3 120s C\KUG_1206+328.20210424.im890036-40.av5x120s.C.FIT'  to Nebulosity using SendKeys, but instead 'KUG_1206£28 3x3 120s C\KUG_1206?28.20210424.im890036-40.av5x120s.C.FIT' was sent instead, meaning that  "?" was received by Nebulosity instead of "+3".  A similar issue occurred for  MCG +6-30-84 where "^-" was recieved by Nebulosity instead of "+6-" .  The plus sign (+) has a special meaning to SendKeys, and to specify "+" it needs to be enclosed within braces, ie "{+}".  Fixed in AstroMain 3.69.1.
  Fixed 2024-07-09 (AstroMain 3.69.1)
   
• Clicking 'Open in AstroPlan' from AstroMain opened empty Target Form with Target Name of "Not Set". Whilst performing backlog analysis of S886 (2021-04-15), it was found that clicking 'Open in AstroPlan from AstroMain's ImageSets / Target tab for Target 'NGC 4866' opened an empty Target Form. Investigating showed that 'NGC_4866 3x3 180s C' Image Set had a Target ID of '0', and that are no target entries exist in the Targets Database for 'NGC 4866'.  When Target ID = 0 AstroMain should put up a dialog explaining issue instead of opening a blank/not set Target Form. Fixed in AstroMain 3.69.1.
  Fixed 2024-07-09 (AstroMain 3.69.1)
   
• Format of columns on AstroPlan's Target List is compromised by long Target Names. Long target names such as 'C/2023 V4 (Camarasa-Duszanowicz)' cause information in Con, Program, Object Type columns to be shifted to the right compromising the layout of data on the form.  Fixed in AstroPlan 1.40.6 by trimming the Target Name where it is created than 28 characters long.
  Fixed 2024-07-28 (AstroPLan 1.40.6)

Continuous Improvement

• Convert Analysis stages, 'Align' and 'Save Combined' to use new QueryDialog process.  Also extend 'Link' dialog to also include a 5th option "Link (Other)". SaveDialog extended to include a 5th button option.
  Done 2024-06-04 (AstroMain 3.68.11)
   
• Combine various 'Repair' Buttons into Single 'Repair Frame' button and use new QueryDialog process to select required 'repair strength' . 
  Done 2024-06-04 (AstroMain 3.68.11)
   
• Change widths of different button options on QueryDialog to be the width of the widest button. The width's of different buttons on the QueryDialog currently vary depending on width of the button text, resulting in buttons on the form have a rather staggered appearance.  Modification made to ShowDialog routines so that all buttons use a common width based on width of the widest button text and to employ a minimum width of 140 px.  Implemented in AstroMain 3.68.11.
  Done 2024-06-05 (AstroMain 3.68.11)
   
• Modify AstroMain's AutoStart procedure to include an attempt to fix a CCDSoft/Camera issue that would otherwise cause the AutoStart to be aborted. . An attempt to autostart a live session on the night 2024-06-05 was auomatically aborted upon encountering a failure during an initial CCDSoft.Camera check at 00:13, and AstroMain was placed back into General Session mode.  This prevented the acquistion of any images from the hour or so of semi-darkness (see Fig 2).  The current AutoStart procedure used in AstroMain 3.68.11 intentionally makes an initial check of the CCDSoft.Camera in order to preempt what would be a critical showstopper for a live session before the session is created and before the LX200 Telescope is connected.  This design feature was written before a robust means of automatically fixing a problem connecting to the SBIG Camera, but now that one exists the AutoStart procedure would be modified to include an attempt to automatically fix the connection so that a live session can successfully proceed.
  Done 2024-06-06 (AstroMain 3.69)
   
• Review AstroWeather/ Weather Forecast download procedures. Following a  LAN connection issue with lost of internet connection, Forecast Wind Speed & Direction wasn't being displayed on Wind Charts generated by AstroWeather. It seems that the lost in Lan/Internet connection (renewed IP connection) stopped AstroWeather from being able to automatically load fresh Weather Forecast data.   Whilst resolved by user in this instance by restarting AstroWeather.  Is there something that AstroWeather program should do to automatically monitor and automatically restart fresh Weather forcast API connection..
  To review 2024-05-30 (AstroWeather, LAN, Weather Forecast)
   
• Add 'transients_2019'.htm page to website for collating images of 2019 transients. Transient pages currently exist for years 2020-2024.
  To do 2024-06-06+ (Website)
   
• Make fresh attempt to image 'Hanny's Voorwerp' near IC 2497. Hanny's Voorwerp is a mag +18 patch of emission just south of IC 2497, discovered in 2007 by Dutch Schoolteacher Hanny van Arkel as part of the Galaxy Zoo project4. Several unsuccessful attempts to image Hanny's Voorwerp were made in 2012. Make fresh attempt with longer exposure in winter 2024.
  To do 2024-06-06+ (Website)
   
• Add 'sn_2011' & 'sn_2012' pages & collate images of several SN imaged in those two year. Create Website page for collating images including SN 2011fe in M101 and 10 other supernovae.  Also query need for sn_2013 to sn_2017 ?
  In Progress 2024-06-17 (Website)
  
  Query what happened to UGC 2614 w/AT2019pxo images from S708 & S709 ?
  Query what happened to C/2017 T2 (PanStarrs) images from S793 & S794 ?
  Query : S499 & S498 contains sections for UGC 4985 & UGC 6132  but no images, were page(s) not completed or these an erronous sections that should be removed ?.  Sections for these objects including images are present in S497 session.
   
• Show flag on Observatory Website to show when Windows Auto Update requires a computer restart.  Add code to AstroMain and AstroWeather to show a flag on Observatory Status & Greenhouse Status charts to indicate that Auto Update is requiring Observatory Computer and AllSky/Weather Computers to be restarted.
  To do 2024-07-14+ (AstroMain 3.69.2, AstroWeather 1.24.4, Website)
   
• Note:   A short Observatory Power Outage (6s) occurred 2024-07-28 13:57:49 during which UPS system ran on Battery backup. 

[ Prev | Next ]

[ Prev | Next ]

Back to Top