David's Astronomy Pages Notes - Session 817 (2020-10-08)

Notes (S816)

Notes Main

Home Page

Notes (S818)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (9),  Continuous Improvement (3)
	Images from 2020-10-08 >>

Session Aims & Highlights (2020-10-08)

Main aims

1. New PHD2 Messaging Routines. Check that new PHD2 Messaging Routines are working and there are no critical or unwanted or sideeffects
2. Targets.  Acquire images of a selection of deep sky targets

Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, PHD2,  DeviceHub 4.6.1.11, UPB 1.5 
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.9
   
• AstroMain 3.30.3,  AstroGuard 1.4.5,   AstroPlan 1.16.4,  AstroShCap 1.2.26, AstroVOE 1.4, AstroProtect 1.4.1
  (AstroWeather 1.10.13, AstroAllSky 3.6)

Highlights

• New PHD2 Messaging Routines. New routines for messaging with PHD2 server are working ok, but a defect in the application of new message routines caused autoguide monitoring to believe there was some 22 times more guidestep events than there actually were.

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)

Pre-Session Weather Forecast (API data from darksky.net) Pre-Session Weather forecast showed dry and moderately clear conditons for the first part of the night ( 6-38% cloud cover) with minimum temperature of 6 °C and moderate wind speed (10-12 mph), but becoming cloudy after midnight (64-100% cloud cover) with 60% probability of rain (0.5-0.8mm per hour) at 03:00 to 05:00 and wind strengthening (up to 23 mph by dawn) In the event conditions were dry and clear in first part of night but clouding over at 22:30 with rain at 01:30 to 02:20. A short 30min clear interval occurred at 04:30 to 05:00.  Wind was fairly calm in first part of night but strengthening in second part of night.  Temperature in first part of night was 2.5°C (min) increasing to 8°C later in the night.

Session Event Log

Time     Event Detail 19:48:01 Session Created Live Session Created (2020-10-08 S00817, ImageSaveNum: 817001) 19:49:10   Obs.Manager Started Obs.Manager started 19:49:12   Obs.Overseer Started Obs.Overseer started 19:49:16   Services Started Observatory Services started 19:50:20   Services Started Observatory Services started 19:50:40   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 19:52:36   Services Started Observatory Services started 19:53:33   Telescope Connected Telescope Connected (TheSky6) 19:53:40   Camera1 Connected SBIG Camera Connected (set point -20°C) 19:54:36   Dome Opened Dome opened (opening time 43s) 19:56:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:01:44       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:04:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:05:06       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:08:21       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:10:49       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:11:11       Focusing Checked Foc2 Focusing Check Succeeded 20:53:31 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:53:35 Session Pending Session pending (2020-10-08) 20:53:37 Session Initiating Session initiating (2020-10-08) 20:53:39   Plan Requested Observing Plan requested from AstroPlan (1.16.4) 20:53:53   Camera1 Connected SBIG Camera Connected (set point -20°C) 20:54:10   Plan Loaded Observing Plan loaded to queue (2020-10-08 V1 BEST PLAN, Plan ID: 552) 20:54:13   Camera1 Connected SBIG Camera Connected (set point -20°C) 20:54:18   Telescope Connected Telescope Connected (TheSky6) 20:54:29 Session Equilibration Session ready for dome & camera equilibration 20:54:32   Equilibration Started Dome Equilibration started 20:55:35   Equilibration Skipped Dome Equilibration skipped by user 20:55:37 Session Running Session running 20:55:39   Queue Started Observing Queue started (36 targets selected) 20:57:36     Target Started (1/36) Target started (1/36, C/2020 Q1 (Borisov)) 20:59:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:02:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 21:08:20     Target Completed Target completed (1/36, C/2020 Q1 (Borisov)) 21:10:16     Target Started (2/36) Target started (2/36, NGC 7550) 21:12:11       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:15:15       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 21:31:21     Target Completed Target completed (2/36, NGC 7550) 21:32:38     Target Started (3/36) Target started (3/36, UGC 122) 21:34:29       Focusing Failed Foc1 Focusing Failed - star is too dim (TCF-S) 21:51:59     Target Completed Target completed (3/36, UGC 122) 21:55:00     Target Started (4/36) Target started (4/36, GCVS RX And) 21:57:29       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:00:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 22:02:41     Target Completed Target completed (4/36, GCVS RX And) 22:03:20     Target Started (5/36) Target started (5/36, GCVS BL Lac) 22:05:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:07:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:11:23     Target Completed Target completed (5/36, GCVS BL Lac) 22:11:25     Target Started (6/37) Target started (6/37, NGC 772, ToO) 22:13:19       Focusing Failed Foc1 Focusing Failed - unable to find a star (TCF-S) 22:26:49   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 22:30:43     Target Completed Target completed (6/37, NGC 772, ToO) 22:30:45   Queue Paused Queue paused for SoftSuspend 22:30:47 Session Suspended Session suspended 22:30:49     Target Missed (7/37) Target's time slot was missed (7/37, C/2019 L3 (ATLAS)) 22:31:34   Dome Closed Dome closed (closing time 49s) 22:33:21     Target Cancelled Target cancelled (8/37, 61 Cyg) due to cloud 22:41:51     Target Cancelled Target cancelled (9/37, GCVS CI Cyg) due to cloud 22:57:02     Target Cancelled Target cancelled (10/37, GCVS SS Cyg) due to cloud 23:05:27     Target Cancelled Target cancelled (11/37, WDS GRB 34) due to cloud 23:06:37 User Intervention User request to close and finish session 23:06:40   Queue Aborted Job Queue aborted 23:06:42 Session Closing Session closing 23:06:47   Dome Closed Dome already closed (closed at 22:31, closing time 49s) 23:07:05   Dome Parked Dome parked (parking time 16s), Az: 90.0 deg 23:07:50   Telescope Parked Telescope parked (parking time 41s) 23:08:20   Telescope Switched Off Telescope Power has been switched off via UPB Powerbox. 23:09:09   Services Stopped Night Services stopped 23:09:11 Session Housekeeping Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files) 23:09:13 Session Finished Session Finished

Session Alerts

Time     Alert Detail -- No Alerts                --

Back to Top

Operational Issues (2020-10-08 S817)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (9)
• Continuous Improvement (3)

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• CCD Temperature Plot shows inappropriate jumps when SBIG Camera is disconnected/reconnected following use by PHD2 (BUG). This is a consequence of new routines that disconnect SBIG Camera from CCDSoft in order to use it for guiding in PHD2.  It seems that jumps are causes by  CCD Temp curve plotting to/from -99 (vcNull ) values. Problem fixed by testing that neither current or last curve value has the null value. 
  Fixed 2020-10-09 (AstroMain 3.30.4).
   
• History / Time Graphs diplayed on GuideCharts are plotting incorrectly (BUG). This is presumed to be due to a subtle impact of the switch over to using new PHD2 Messaging routines or due to prior use of Cam1 profile, before switching back to Cam2 profile.  Guide Summary, Guide Error graphs, and the guiding itself seem to be working ok.  The graph seem to show 12-17 bars  for each guide event ?  Comparing Guide Run for BL Lac (3 x 60s frames) from the new session with that from an earlier session (S814)  shows a 'n'  (no. of guide frames) value of 1339 (average of 1 every 0.134s)  compared to a normal value of 59  (average 1 every 3s , i.e. 1.5s guide exposure + 1.5s for download, measurements & guide movements). This is a x22 or x23 increase.     BL Lac images acquired from 22:07:51 to 22:11:21 (3.5 mins gross). Examining the PHD2 Message Log  shows 66 genuine Guide Step events during this time (ie around the number expected), but for each one there is a varying number of repeating {Event} lines, spaced roughly 130ms (0.13s) apart lasting from the moment each geninue GuideStep Event was received until the next is received. In total there are 1342 of these lines logged (ie approximately the same as the 'n' value of 1339 recorded).   The guide monitor is clearly seeing each of these duplicated steps as a guide step and responds accordingly, and this explains the symptoms seen on the charts.  Code indicates that the Listening Loop is operating correctly, reading new messages off the server stream and performing high level parsing (Event or Response) and appropriate posting, in this case to Event message is posted to the LatestEvent variable).   This suggest the problem is in the 'Guider' object.  StartPHD2Guiding appears to be operating correctly, using PHD2.GetEvent function to pull the event from LatestEvent variable (which resets the variable to "" or empty string so that it can't be used twice), however the RunPHD2GuidingMonitor routine is pulling the event from GetMessage which in turns pulls data from the LatestMessage variable, which isn't reset after being read and therefore get's used multiple times). Issue fixed by modifying RunPHD2GuidingMonitor routine to pull the event using PHD2.GetEvent function.
  Fixed 2020-10-09 (AstroMain 3.30.4).
   
• No. of AllSkyStars (19 to 23) is relatively low given the Sky Clarity (QUERY). Is this RA Hour issue related to the distrubtion of reference stars or has calibration deteriorated ?  Although S816 and S817 both had clear sky AllSkyStar counts of around 20,   session S815 (2020-09-29) had clearsky counts of 35+ stars, suggesting that is current be a RA / distribution issue but more likely a sky transparency difference.
  Closed 2020-10-09 (Session).
   
• Two events are being saved in database for each  'Program Closed by User' event (BUG).
  Fixed 2020-10-09 (AstroMain 3.30.4).
   
• Last Dome Movement showing 'Alert' when time since last Dome Movement (1.0 min ago) is entirely within normal range (BUG). Last Dome Movement is reported with a new added post slew reporting section, subtitled 'Dome Postion Check'.  The last azimuth change is also shown twice.
    Last Dome Movement          Alert     Last Azimuth Change 20:57:48 (1.0 mins ago)
                                Ok        Last Azimuth Change 20:57:48 (1.0 mins ago)
  Fixed 2020-10-09 (AstroMain 3.30.4).
    
• It's becoming increasing problematic to keep using Internet Explorer (ISSUE). More and more online pages are refusing to display in IE11 or have problems with display.  Although Microsoft Edge has some things I don't like compared to IE11 it's benefits now outweigh its downsides. Microsoft edge is now made default browser.
  Resolved (Development Computer).
   
• When copying the entire contents (Cntl A, Cntl C) of a  session events table 'SessionEvents_817.htm' opened in Edge the font family becomes 'Times New Roman' when pasted into Session Events section of Session's Web Page in WebExpression.   This was not an issue with Internet Explorer.   When table is created the table tag should be set as <table style="font-family: Arial">. Solution checked in IPAD/Safari and confirmed not to produce any unwanted side effects.
  Fixed 2020-10-09 (AstroPlan 1.16.5).
   
• Computer Time on Observatory Computer and AllSky/Weather Computer are 120s different (2020-10-09).  Investigating showed that the computer time on new AllSky/Weather computer are not getting updated by Dimension 4.  It seemed that it didn't have sufficient privaledges.   Dimension 4 shortcut placed in Users StartUp programs, with it set to 'Run as Administrator'.  Ideally AstroWeather should flag up any differences in time between the two computers to allow investigation to take place at an earlier point. Fixed attempted 2020-10-09, but provided a short term fix only and one reliant on user action each time an observatort computer was restarted.  A further computer time issue associated with 22s error on computer time on Observatory Computer affecting precision of Telescope Slews was reported in session S1003 (2022-04-22, S1003).  Issue believed tob finally fixed by upgrading Dimension4 to version 5.31 (2013) on all observatory computers on 2022-04-24 and setting it up to run as a service (all using the server ntp2.uk.uu.net).
  Fixed 2022-04-23 (AllSky/Weather Computer).
   
• Images from Target C/2020 Q1 (Borisov) not linking despite having plenty of stars.  Although reduced images (7x45s) were of good quality and had plenty of stars (~ 340) the images failed to link.   In constrast locate Frames (2 x 5s, with ~95 stars) linked ok. Detailed link attempt also failed. Issue seems that there are 'too many stars'  (too many non-catalogue stars compared to catalogue stars).  Whilst alternate extraction parameters would probably work, those settings would be inappropriate for other images with few stars.  Ideally the Image Link routine could spot the problem and run the image link using substituted SExtractor parameters.  Later stacked image (7x 45s) was able to link using Simple Linking.  Individual images (hot pixel repaired) also stack ok using Simple Linking but still wouldn't link using GSC or UCAC Star Linking.  Possible role for ASTAP tool here as a alternate plate solver.
  Known issue affecting some dense starfields. Continuous Improvement ticket raised   (CCDSoft/TheSky). 

Continuous Improvement

• Only log repeat occurances of where ObsMonitor is unable to read objPowerBox.GetSwitch(cSwitchPower1).  It is expected that there are occasions where  SwitchLock IsOn and the Obs.Monitor is unable to read objPowerBox.GetSwitch(cSwitchPower1).   RunObservatoryMonitoring routine to be modified to only log read objPowerBox.GetSwitch(cSwitchPower1)  failures where it occurs on two consecutive monitoring cycles. A single occurance will no longer be logged.
  Done 2020-10-09 (AstroMain 3.30.4).
   
• Develop Image Linking method where alternate sextractor parameters can be substituted. This is to get round the issue that a good quality 45s images with plenty of stars (~ 340),  such as those from C/2020 Q1 (Borisov) in S817 failed to link. The possible block to achieving this will be whether CCDSoft re-reads the sextractor file between linking attempts or only upon program start-up.   Alternatively drop back to simple linking.  Solved partly by preempting CCDSoft link issues by sending images with lots of stars to Plate Solve using ASTAP. This is suitable for centering during live sessions, but is unsuitable for later image analysis when it is required to extract a calibrated magnitude of a given star position (for adhoc photometry). A new request to 'Add facility to more easily change the Detection Threshold used by CCDSoft's Source Extraction facility' was made following session S905 (2021-08-13).   This New Feature is in progress (AstroMain 3.40.1, 2021-08-16).
  Partly Resolved (but in a different way) 2021-05-22 (AstroMain / ASTAP )  
   
• Monitor Computer Time on Observatory & AllSky/Weather Computer and possibly also the Development Computer and flag up any material differences.  This is to flag up any issues that might arise with automatic time keeping and prevent the 120s computer time difference noted on 2020-10-09.  One way would be to use the PowerShell/Cmd/Batch command 'net time \\computername >time.txt' and extract the date/time from the result
  Time on another computer  e.g.   'net time \\laptop7'  gives Current time at \\laptop7 is ‎2020-‎10-‎09 12:49:31. The format of net time output includes null characters,  ?2020-?10-?09 etc ,  which need to be allowed for when parsing the data/time.
  To Do (AstroMain, AstroWeather)

[ Prev | Next ]

Back to Top