David's Astronomy Pages Notes - Session 1035 (2022-09-01)

Notes (S1034)

Notes Main

Home Page

Notes (S1036)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (5),  Small Defects (7),  Continuous Improvement (10)
	Images from 2022-09-01 >>        [ Local Files >> ]
	2022-09-01
	AllSky Camera Recalibration

Session Aims & Highlights (2022-09-01)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by time & twilight conditions.
2. Guiding.  Check out guiding performance after rolling PHD2 version back to 2.6.10dev3 (from 2.6.11) and making some improvements to Guiding Manager in AstroMain 3.54.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.6.0.16,  MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.10dev3
   
• AstroMain 3.54,  AstroPlan 1.32,   AstroShCap 1.3.12, AstroGuard 1.8.2
  AstroVOE 1.10.1  AstroSN 1.8.3,  AstroProtect 1.7,  AstroMove 1.9.1
  (AstroWeather 1.17.6, AstroAllSky 3.16,  AstroObsCam 1.9, AstroLaunch 1.9.4)

Highlights

• Targets.  Data was acquired from 22 out of 23 planned targets, 2 of which were only partially completed (due to cloud) and 4 had compromised guiding. 1 target failed due to cloud.
• Guiding. Guiding performance for 17 out of 22 targets was good, and for other 5 targets data was still usuable (either due to manual selection of guide star, short exposures or disabled guide output). Dec Guide performance was particularly good,  RA guide performance limited by need to respond to residual Periodic Error.  Rolling back PHD2 version to 2.6.10dev3 didn't have any effect on the 'AutoFind selecting Very Low SNR Star' issue.

Notes:

• Guiding problems with
    - C/2019 U5 (PANSTARRS)  (no guide star, some data still usuable)
    - IC 1132 (bad guide star SNR 7, manually repicked guide star after the 3rd frame)
    - GCVS Z And (bad guide star SNR 9, guide output disabled, images still usuable due to short exposures)
    - NGC 5894 (no guide star, guide output disabled / not applicable, some images still usuable )
    - GCVS RX And (bad guiding SNR 18, images still usuable )
  

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 15:21:43 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:03 & 04:03 15:21:45   AutoStart Waiting AutoStart waiting till earliest start time at 21:03 21:03:47   AutoStart Delayed Session delayed due to too few stars 21:24:15 Session AutoStarting Session autostarting (21:24) 21:24:47 Session Created Session Created (Live, 2022-09-01 S01035, ImageSaveNum: 1035001) 21:24:50   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 21:26:33   Services Started Observatory Services started 21:26:40 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:26:45 Session Pending Session pending (2022-09-01) 21:26:47 Session Initiating Session initiating (2022-09-01) 21:26:49   Plan Requested Observing Plan requested from AstroPlan (1.32) 21:27:25   Plan Loaded Observing Plan loaded to queue (Plan ID: 797) 21:27:50   Camera1 Connected SBIG Camera connected (set point -10°C) 21:27:57   Telescope Connected Telescope connected (TheSky6) 21:28:21 Session Equilibration Session ready to Open Dome 21:29:06   Dome Opened Dome opened (opening time 45s) 21:29:51 Session Running Session running 21:29:53   Queue Started Observing Queue started (23 targets selected) 21:29:57     Target Started (NrZen) Target started (Focus Field 19, HIP 93376) 21:30:15   Dome Unparked Dome unparked 21:36:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:39:34       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 21:41:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 21:41:33       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:43:23       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 21:45:06       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 21:45:23     Target Completed (NrZen) Target completed (Focus Field 19, HIP 93376) 21:45:28     Target Started (1/23) Target started (1/23, C/2019 U5 (PANSTARRS)) 21:51:59       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 22:02:44     Target Completed Target completed (1/23, C/2019 U5 (PANSTARRS)) 22:02:48     Target Started (2/23) Target started (2/23, IC 1132 w/SN2022prv) 22:23:50     Target Completed Target completed (2/23, IC 1132 w/SN2022prv) 22:23:54     Target Started (3/23) Target started (3/23, C/2022 E3 (ZTF)) 22:26:34       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:28:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:39:58     Target Completed Target completed (3/23, C/2022 E3 (ZTF)) 22:40:02     Target Started (4/23) Target started (4/23, HIP 87937) 22:41:49     Dome Slew Dome slew held up at Az. 247.0, 246.9, 222.3° (Total delay 76s) 22:44:26       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:46:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 22:49:07     Target Completed Target completed (4/23, HIP 87937) 22:49:11     Target Started (5/23) Target started (5/23, SH 2-71) 22:51:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:54:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 23:16:17     Target Completed Target completed (5/23, SH 2-71) 23:16:21     Target Started (6/23) Target started (6/23, UGC 3923 w/SN2022rqc) 23:20:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:22:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 23:39:36     Target Completed Target completed (6/23, UGC 3923 w/SN2022rqc) 23:39:40     Target Started (7/23) Target started (7/23, NGC 6745 w/SN2022prr) 23:42:45       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:44:46       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 00:00:35     Target Completed Target completed (7/23, NGC 6745 w/SN2022prr) 00:00:39     Target Started (8/23) Target started (8/23, AT2022idn) 00:03:13       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:05:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 00:21:25     Target Completed Target completed (8/23, AT2022idn) 00:21:29     Target Started (9/23) Target started (9/23, GCVS CI Cyg) 00:24:09       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:26:11       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 00:30:17     Target Completed Target completed (9/23, GCVS CI Cyg) 00:30:21     Target Started (10/23) Target started (10/23, GCVS SS Cyg) 00:32:45       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:34:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:39:07     Target Completed Target completed (10/23, GCVS SS Cyg) 00:46:36     Target Started (11/23) Target started (11/23, GCVS Z And) 00:49:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:52:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 00:56:43     Target Completed Target completed (11/23, GCVS Z And) 00:56:47     Target Started (12/23) Target started (12/23, NGC 5875 w/SN2022oqm) 01:00:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:02:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 01:18:44     Target Completed Target completed (12/23, NGC 5875 w/SN2022oqm) 01:18:48     Target Started (13/23) Target started (13/23, NGC 5894 w/SN2022pgf) 01:24:53       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:27:10       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 01:43:32     Target Completed Target completed (13/23, NGC 5894 w/SN2022pgf) 01:43:36     Target Started (14/23) Target started (14/23, AT2022qus (CV)) 01:46:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:49:10       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 01:55:14     Target Completed Target completed (14/23, AT2022qus (CV)) 01:55:18     Target Started (15/23) Target started (15/23, GCVS BL Lac) 01:57:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:59:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 02:03:49     Target Completed Target completed (15/23, GCVS BL Lac) 02:03:53     Target Started (16/23) Target started (16/23, NGC 157 w/SN2022jli) 02:07:21       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 02:23:13     Target Completed Target completed (16/23, NGC 157 w/SN2022jli) 02:24:35     Target Started (17/23) Target started (17/23, Nova Per 2020) 02:27:35       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:29:39       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 02:37:57     Target Completed Target completed (17/23, Nova Per 2020) 02:39:05     Target Started (18/23) Target started (18/23, NGC 132 w/AT2022sjd) 02:42:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:45:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 03:01:41     Target Completed Target completed (18/23, NGC 132 w/AT2022sjd) 03:01:45     Target Started (19/23) Target started (19/23, NGC 298) 03:07:37       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 03:17:36   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:17:38   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:17:43     Target Aborted (19/23) Target aborted (19/23, NGC 298) due to cloud 03:17:45   Queue Paused Queue paused for Session Suspension 03:17:46 Session Suspended Session suspended 03:18:31   Dome Closed Dome closed (closing time 45s) 03:19:51 Session Resuming Session resuming 03:20:01     Target Cancelled Target cancelled (19/23, NGC 298) due to cloud 03:20:36   Dome Opened Dome opened (opening time 45s) 03:20:38 Session Running Session running 03:20:40   Queue Resumed Observing Queue resumed 03:21:56   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:21:58   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:22:00   Queue Paused Observing Queue pausing for Session Suspension 03:22:01 Session Suspended Session suspended 03:22:46   Dome Closed Dome closed (closing time 45s) 03:46:49 Session Resuming Session resuming 03:47:34   Dome Opened Dome opened (opening time 45s) 03:47:36 Session Running Session running 03:47:38   Queue Resumed Observing Queue resumed 03:47:41     Target Started (20/23) Target started (20/23, WHL0137-08) 03:47:43   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (reducing clarity) 03:49:04   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 03:49:06   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 03:49:08     Target Aborted (20/23) Target aborted (20/23, WHL0137-08) due to cloud 03:49:10   Queue Paused Queue paused for Session Suspension 03:49:12 Session Suspended Session suspended 03:49:59   Dome Closed Dome closed (closing time 50s) 03:53:35 Session Resuming Session resuming 03:54:09     Target Cancelled Target cancelled (20/23, WHL0137-08) due to cloud 03:54:20   Dome Opened Dome opened (opening time 45s) 03:54:22 Session Running Session running 03:54:24   Queue Resumed Observing Queue resumed 03:57:13     Target Started (21/23) Target started (21/23, WDS GRB 34) 03:59:32       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:01:30       Focusing Completed Foc1 AutoFocus Completed (Profile No 18) 04:03:33     Target Completed Target completed (21/23, WDS GRB 34) 04:05:16     Target Started (22/23) Target started (22/23, M31 w/AT2022eng) 04:07:57       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:10:01       Focusing Completed Foc1 AutoFocus Completed (Profile No 19) 04:22:43   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:22:45   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 04:22:50     Target Aborted (22/23) Target aborted (22/23, M31 w/AT2022eng) due to cloud 04:22:52   Queue Paused Queue paused for Session Suspension 04:22:55 Session Suspended Session suspended 04:23:43   Dome Closed Dome closed (closing time 50s) 04:24:12     Target Cancelled Target cancelled (22/23, M31 w/AT2022eng) due to cloud 04:25:43 Session Resuming Session resuming 04:26:28   Dome Opened Dome opened (opening time 45s) 04:26:31 Session Running Session running 04:26:33   Queue Resumed Observing Queue resumed 04:27:16     Target Started (23/23) Target started (23/23, GCVS RX And) 04:29:43       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:31:55       Focusing Completed Foc1 AutoFocus Completed (Profile No 20) 04:34:29   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 04:34:31   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 04:34:37     Target Aborted (23/23) Target aborted (23/23, GCVS RX And) due to cloud 04:34:39   Queue Paused Queue paused for Session Suspension 04:34:42 Session Suspended Session suspended 04:35:30   Dome Closed Dome closed (closing time 50s) 04:45:58     Target Cancelled Target cancelled (23/23, GCVS RX And) due to cloud 04:46:03   Queue Completed Job Queue completed 04:46:06 Session Closing Session closing 04:46:11   Dome Closed Dome already closed (closed at 04:35, closing time 50s) 04:47:20   Dome Parked Dome parked (parking time 61s), Az: 90.0 deg 04:48:38   Telescope Parked Telescope parked (parking time 77s) 04:48:53   Telescope State Scope parked Turn scope off. (Handbox) 04:49:15   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:50:08   Services Stopped Night Services stopped 04:50:10 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files) 04:50:31 Session Finished Session Finished

Session Alerts

Time     Alert Detail -- No Alerts                --

Back to Top

Operational Issues (2022-09-01, S1035)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Various system/application issues during Program Developement (Development Computer, 2022-09-04).  Various processes encountered exception (mspaint, msedge) which triggered the JIT debugging window. Various background tools in Visual Studio stopped working, Visual Studio crashed, Visual Studio stopped responding  (the non-responding Visual Studio instance couldn't been stopped/killed without restarting Computer). An error dialog IPL 2.5 Release - In function iplAllocateImage(): [file iplalloc.c, line 315] for allocate image data. Insufficient memory (status: -4) ErrMode=IPL_ErrorModeLeag) appeared - believed at time to be related to TheSky6 ?.   Issues seem to have all been resolved by restarting the Computer.
  Resolved 2022-09-04 (Development Computer) 
   
• TheSky6 giving TeleAPI error dialog 'Failed to create instance of the scope driver POTH.Telescope'  (Development Computer, 2022-09-05).  Error message ' Failed to create instance of the scope driver POTHTelescope' when trying to connect TheSky6 to telescope'. Whilst the error dialog is showing it holds up progress by the ConnectTheSky6Telescope() routine and freezes ObsServicesThread. This is an occasional issue which seems to occur when TheSky6 permission to access the registry gets removed by the Window System for some reason. Problem might be related to issues with computer prior to restarting the computer (hard restart as windows wouldn't shut down / non responding Visual Studio instance). The usual fix 'Starting TheSky6 once as Administrator' was tried and was again successful. (TeleAPI settings which were blank had to be reset to 'Device Hub Telescope')
  Resolved 2022-09-05 (Development Computer, TheSky6) 
   
• PHD2's Find Star / Guide Method continues to occassionally overlook what seem to be better candidate stars in favour of a very dim star or random patch of warm pixels (21:49) . For Target 1/23 (C/2019 U5 (PANSTARRS)) guide initiation timed out at 21:50:43 (T+51s) with the error message "failed to find a suitable guide star". StartPHD2Guiding loop timed out after 100s, as expected.  PHD2 version was rolled back to 2.6.10dev3 (from 2.6.11) ahead of the session, but it hasn't improved things.  Example showing the issue : Target 13/23 (NGC 5894). Guide Request at 01:22:45.  Resolved in session S1036 by reducing Minimum SNR from 50 to 13.  This now allows PHD2's Find Star to select a guide star is range 13 to 49 which were previously been overlooked in favour of dim star/noise with SNR of only 6 or 7 ('strange but true'). 
  Resolved 2022-09-12 (PHD2 ) 
   
• 23 transient targets in Targets Database with Name "none" (Post-Session).  Targets with Target IDs in range 2378 - 2425 have Target Name "none" . These are all transients without a host (i.e. no Galaxy Host) and have been uploaded to the Targets Database by AstroSN program between 2022-08-02 and 2022-09-05. The last correctly named hostless transients date from around , 2022-07-12, though there is one correctly transient on 2022-08-09 that dates to after the 'name = none' issue appeared on 2022-08-02.  Problem would seem to still be active, as last incorrectly name target was only yesterday (2022-09-05).   Problem might relate to issue in AstroSN 1.8.2 (built 2022-05-11) or AstroSN 1.8.3 (built 2022-08-22), however the start of the issue doesn't match up with date of either version. In case of AT2022rsz AstroSN logs show Transient with Target Name AT2022rsz  was loaded to database on by loading run that started at 2022-08-22 21:03. This time matches corresponds with loaded to database date of 2022-08-22 21:05:43 for 'none /AT2022rsz'.  Problem may not relate to loading, but from later update   AstroSN logs should AT2022rsz  was updated on at least 2022-08-25 21:19 & 2022-09-05 04:13:39.  InsertNewTarget loads T.Name,, which is known to work ok. The routine is called by SaveTargetRecord() which sets T.Name to SN.TargetName.   "none" doesn't appear as setting anywhere in AstroSN or in AstroPlan. Could it be a database table setting  when target table was created which puts "none" in place of a blank "". But database field was define as "Name varchar(30) NOT NULL", which implies that a blank name field would have produced a database insert exception.  UpdateExistingTarget updates database with T.Name. This is also callef by SaveTargetRecord with T.Name set to SN.TargetName. Tracing added to AstroSN which logs the 'Insert 'and Update' SQL commands that are sent to the database. Although there are no new Insert's to be made today (2022-09-06)  the tracing confirms that Updates are using Name = "none".  It shows that Object Type is being loaded (incorrectly) with likes of  "Spiral Galaxy with CV" or "Spiral Galaxy with Transient".  The reference to 'Spiral Galaxy' is wrong !.  Examination of the SN/Transient source file "http://www.rochesterastronomy.org/snimages/snname.html" shows that Host Galaxy field shows 'none' where there isn't a Host Galaxy which finally explains where the "none" name comes from.   Fixed issue in AstroSN 1.8.4 by checking that SN.HostGalaxy <> "none".  After fixing and re-running AstroSN program the number of Transients with name of "none" reduced from 23 down to just 2 (which were then manually corrected) and it was confirmed that issue with Object Type containing Spiral Galaxy had also been fixed.
  Fixed 2022-09-06 (Targets Database, AstroSN 1.8.4 ) 
   
• Weather Station's Ouside Temperature Sensor appears to have begun reading around 2°C too high (2022-09-07). Compared to the observatory temperature (3 different sensors) the outside temperature sensor value is noticed to be consistently reading around 2°C high. The discrepency seems to have developed gradually over the last 7-10 days (there was no sudden jump in temperature).  Normally there are various diuranal difference between outside and inside temperatures but the average daily difference would typically be small, so having a consistent temperature difference (biased to outside sesnor) is anomalous. Weather conditions have been particularly cloudy during the last week, which might have some (small) bearing on temperature difference.  Proposal to temporarily move one of the indoor sensors to the outside in order to prove and issue with the regular outdoor temperature sensor. The outside sensor is important because it is dew point tempearture is used for controlling the dew heaters.  A Outside Temperature trim feature was added to AstroMain, AstroWeather and AstroAllSky and set to -2.0  This worked for a while, but the sensor then started to be reading 'ok' and the trim setting had to be reset to 0.0.
  Closed 2022-09-12  (Weather Station / Temperature Sensor) 

Small Defects

• Reporting of Guide Initiation contains a duplicated report line "Warning SNR of guide star (6) is bad & too low for reliable guiding" (21:51)
  Fixed 2022-09-02 (AstroMain 3.54.1) 
   
• StartPHD2Guiding loop unexpectedly timed out after 48.5s (22:07). StartPHD2Guiding loop has a timeout that is initially set to 100s (which Target 1/23 used up), but for Target 2/23 (IC 1132 w/SN2022prv) the loop unexpectedly timed out after 48.5s.    Log shows guide show a SettleBegin at 22:07:30 (T+19s) and a SettleDone with error "timed-out waiting for guider to settle" at 22:08:01 (T+50s) or 31s after SettleBegin event.  StartPHD2Guiding updates the Timeout setting after seeing SettleBegin event.  It does this by setting timepoint to time of SettleBegin event + SettleTime (10s)  + 20s . This would imply a Loop TimeOut at T+49  (19+10+20) which is close to actual timeout at T+48.5s.  It seems that due to autoselected guide star being very dim, star and lock position became lost during the settling, so the setting period was much long that expected. The adjusted timeout should allow more time to see a SettleDone event before quitting the loop. If SettleDone returns error "timed-out waiting for guider to settle" it is probably appropriate to curtail the loop at that stage rather than continue to any original or adjusted timeout.
  Fixed 2022-09-02 (AstroMain 3.54.1) 
   
• Teething issues with new feature that inserts Target Name into the (PHD2) Log File (21:45).  "Guide TARGET = Target 1/23 (C/2019 U5 (PANSTARRS))" is unexpectedly inserted at 21:45:32.  This is potentially because the preceeding line ("Stop PHD2 Guiding...") contains the triggering search string "guide". The line  "Guide TARGET = Target 1/23 (C/2019 U5 (PANSTARRS))" is unexpectedly inserted at 21:49:29. (This should be a Setup TARGET line only). The line "Guide TARGET = Target 1/23 (C/2019 U5 (PANSTARRS)) appears as expected at 21:49:52, but unexpectedly is repeated at 21:50:01, 21:50:21, 21:50:43 and repeated at regular intervals until 22:02:42.
  Fixed 2022-09-02 (AstroMain 3.54.1) 
   
• Guide History Graph is heavily compressed (frame segments are much thinner than normal and text overposts) width details & times are overposting).   History Graph in Guiding Chart for Target 1/23 (C/2019 U5 (PANSTARRS)) is heavily compressed, frame segments are much thinner than normal and frame numbers and HH:mm times are highly overposted.  PHD2 had selected a very low SNR 'star' (SNR only 6-7) this was most likely a random patch of warm pixels, and AstroMain's Manager disabled guide output.   Settling was Instead of usual Star Lost events if Guiding was active, PHD2 produced a series of LoopingExposure events with status "Star lost - low SNR".  These events are skipped over by AstroMain's Guide Monitor and their time equivalent (based on exposures every 1.5s or so) isn't represented on the History Graph.   Guide initiation timed out at 21:50:43 with the error message "failed to find a suitable guide star". Added handling for event LoopingExposures to RunPHD2GuidingMonitor() loop.   ParseStarLostRecord() routine modified to parse both LoopingExposures and LostStar events.   This involved modifying ParseStarLostRecord() and ParseGuideRecord() routines to get G.Time since guiding started from G.TimeStamp  and TimeStamp0 since the LoopingExposures event doesn't have a "Time" parameter.
  Fixed 2022-09-02 (AstroMain 3.54.1) 
   
• Overall RMS is written as 0.00" on Guding Chart's History Graph in cases where Guide is 0% / Lost is 100%.  When an image/imagset hasn't seen any guidestep events because it only saw StarLost or LoopingExposure events the overall RMS is written as 0.00". It should be blank. Similarly SNR is written as 0.0 and HFD is written as 0.0 on Individual Error Plot graphs - they should be written as '--'.   Though eventually these may be written as actual numbers if SNR & HFD from LoopingExposure events can be recorded.
  Fixed 2022-09-02 (AstroMain 3.54.1) 
   
• When editing NightDate field on AstroPlan's Schedule Builder form the ResetNightDetails() routine is executed after each character change to Night Date field. Fixed in AstroPlan 1.32.3 but adding a condition check to the CheckDateIsValid() function (called by txtNightDate_TextChanged action method) to return False if len(night date string) <> 10. (ie where 'yyyy-mm-dd' string is completed)
  Fixed 2022-09-07 (AstroPlan 1.32.3) 
   
• When entering a session mumber less than '930' into Session number field on AstroMove's session tab the message 'Session S930 is not recognised' appears. Issue prevents using AstroMove's facility to quickly open various folders associated with a session without navigating Windows Explorer. Issue was initially though to apply to all session numbers less than 1000 (like 930), but through debugging and further tests in was shown that the operations works ok for sessions in range 999 to 937 but not less than 937 (like 930) as the expected folders don't appear in the SessionFolders() array list.   This is because the SessionFolders() list is built up based on session folder on the Observatory Computer where session before S937 have been removed.  Added bSearchObsComputer (True/False) parameter to UpdateSessionList() routine to direct the routine on whether to make list based on Observatory Computer or Local Computer.
  Fixed 2022-09-07 (AstroMove 1.9.3) 

• Reduce number of repeated LoopingExposure messages but removing duplicate 'Star Lost' status messages. Change reporting in StartPHD2Guiding loop to only report new LoopingExposure messages.
  Done 2022-09-02 (AstroMain 3.54.1) 
   
• Annotate Guiding's History Graph when a star is selected. Implemented in AstroMain 3.54.1 - added handling for event "StarSelected" to RunPHD2GuidingMonitor() loop, added new routine GuidingChart.DrawStarSelected(), added 'Star Selected' Legend to GuidingChart.DrawTargetBase() routine
  Done 2022-09-02 (AstroMain 3.54.1) 
   
• FitsSummary's  'Group Raw Files' script should deselect working cells after finishing.  Fixed by using  Range("C1:C1").Select at end of script (this normally used code line was missing from 'A4_Group_Raw_FITS' routine.
  Done 2022-09-02 (Excel VBA/FitsSummary) 
   
• Add  'ROI' rectangle onto Guide Frame JPG Pictures. Where a ROI param is used when calling PHD2's "guide" method a rectangular outline representing the ROI should be drawn on the relevant JPG pictures (Guide01_Ref, Guide01_F1, Guide01_F2).
  Done 2022-09-01 (AstroMain 3.54.1)
   
• Ensure that 'Restart PHD2 Service' doesn't connect to Telescope if the telescpe isn't already connected to AstroMain.
  Done 2022-09-02 (AstroMain 3.54.1) 
   
• 'Conditions' Section Live Sessions should move Sun Altitude line to bottom of section. In Pre-Slew, Pre-Imaging and Post Imaging 'Conditions' reporting the Sun Altitude line is placed at the top of the section.  It will be better if this line is placed after the information about sky/weather conditions..
  Done 2022-09-07 (AstroMain 3.54.4) 
   
• Add a temperature trim for Outdoor Temperature Sensor. The outdoor temperature sensor has begun reading temperatures that are around 2deg C too high. As dew temparture is also too high by the same amount, it is causing the observatory's telescope dew heater to run at an excessively high level in order to try to main the telescope OTA at a set amount above the outdoor dew point. A trim of -2 (but user definable) should be applied to the outdoor temperature & outdoor dew points before use in AstroMain.   A similar trim should be applied to the sensor value before plotting on various Weather Charts in AstroMain, and on annotated AllSky Images in AstroAllSky. Since Outside Temperature box is currently generated by Virtual Weather Station directly as vws889.jpg & vws904.jpg, these have had to be replaced by new AstroWeather generated boxes, vwsGraph53.jpg & vwsGraph54.jpg
  Done 2022-09-12 (AstroMain 3.54.6, AstroWeather 1.7.8, AstroAllSky 3.16.1, Website)
   
• 'Late Start' report message from the second attempts at Target 22/23 & 23/23 misleading (04:23 & 04:35). Due to session suspension events due to critical cloud, second observation attempts were made for Target 22/23 (M31 w/AT2022eng) and Target 23/23 (GCVS RX And). Both gave the report message "Late Start:  Warning   Planned start time was missed. Some frames will probably be cancelled". Both targets had in fact started on time during their respective first observation attempt (5 mins early in the case of RX And) and had both been largely completed when they were each suspended.  The report message needs to reflect this scenario, by having some memory/history of the initial attempt. Solution implemented in AstroMain 3.58.1 ( 'T.PriorObservationStatus <> ObservationState.PartiallyCompleted' is checked)
  Done 2022-11-21 (Session, AstroMain 3.58.1) 
   
• Query: "StarLost" events are being generated when GuideStep directly beforehand and directly after showing a guide star with high SNR (>200). Two StarLost events at 22:27:22 during Target 3/23 (C/2022 E3 (ZTF)) in a situation where SNR/HFD immediately beforehand 228 / 3.7.  SNR/HFD immediately after 226 / 4.0, with no evidence of any deteriorating conditions. Could be caused by a sharp deflection in the star due to wind ?
  To review/monitor 2022-09-02 (AstroMain 3.54.x, PHD2 2.6.10/11 ) 

[ Prev | Next ]

Back to Top

AllSky Camera Recalibration

Back to Top