David's Astronomy Pages Notes - Session 972 (2022-02-15)

Notes (S971)

Notes Main

Home Page

Notes (S973)

	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 (13)
	Images from 2022-02-15 >>         [ Local Files >> ]
	2022-02-19
	AstroMain -  New 'Observing Conditions' Hub

Session Aims & Highlights (2022-02-15)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by time & conditions.

Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.5.1.9,  MeadeGeneric 1.3.3.373, UPB 1.5, ASCOM 6.5 SP1
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.10
   
• AstroMain 3.49.5,  AstroPlan 1.29.9,   AstroShCap 1.3.12, AstroGuard 1.6.3
  AstroVOE 1.9.2  AstroSN 1.7.3,  AstroProtect 1.6
  (AstroWeather 1.15.3, AstroAllSky 3.14.6,  AstroObsCam 1.8, AstroLaunch 1.8.2)

Highlights

•  Targets.  x targets acquired.
•  HD 84406.  Images of star HD 84406 in UMa successfully taken. Observatory Telescope aligned with the JWST.

Notes:

  Summary Plots & Logs

Observing Plan

Observing Result

Dome & Scope Slewing Performance

Slew/Centering Performance

Guiding Performance Reasons for poor Dec guiding : Black point/Purple Points () - None Red points () - None Orange point (2) - Poor Dec Guiding (North) during Frames 7 & 8 following light cloud/lowered SNR

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 18:15:12 Session Monitoring AutoStart monitoring for Live Session opportunity between 18:15 & 05:29 18:15:13   AutoStart Delayed Session delayed due to wind 19:53:19 Session AutoStarting Session autostarting (19:53) 19:53:56 Session Created Live Session Created (2022-02-15 S00972, ImageSaveNum: 972001) 19:53:59   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 19:55:45   Services Started Observatory Services started 19:55:52 Observatory (Auto) Observatory placed in Fully-Automated Mode 19:55:55 Session Pending Session pending (2022-02-15) 19:55:57 Session Initiating Session initiating (2022-02-15) 19:55:59   Plan Requested Observing Plan requested from AstroPlan (1.29.9) 19:56:33   Plan Loaded Observing Plan loaded to queue (, Plan ID: 730) 19:56:58   Camera1 Connected SBIG Camera Connected (set point -25°C) 19:57:02   Telescope Connected Telescope Connected (TheSky6) 19:57:29 Session Equilibration Session ready for dome & camera equilibration 19:58:14   Dome Opened Dome opened (opening time 45s) 19:58:59 Session Running Session running 19:59:01   Queue Started Observing Queue started (36 targets selected) 19:59:03     Target Started (NrZen) Target started (Focus Field 5, HIP 23569) 20:00:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:03:52       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:05:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:05:54       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:08:05       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:09:51       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:10:09     Target Completed Target completed (Focus Field 5, HIP 23569) 20:11:03     Target Started (1/36) Target started (1/36, GCVS HH And) 20:14:48       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:17:18       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 20:19:18     Target Completed Target completed (1/36, GCVS HH And) 20:19:22     Target Started (2/36) Target started (2/36, 19P/Borrelly) 20:23:12       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 20:24:57   SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 20:31:46     Target Completed Target completed (2/36, 19P/Borrelly) 20:31:48   Queue Paused Queue paused for Session Suspension 20:31:50 Session Suspended Session suspended 20:32:38   Dome Closed Dome closed (closing time 50s) 20:40:53     Target Cancelled Target cancelled (3/36, WDS GRB 34) due to cloud 20:43:23   Queue Aborted Job Queue aborted 20:43:34   Services Stopped Observatory Services stopped 20:43:39 Program Closed Program closed by User 20:44:49 Session Resumed Live Session Resumed (2022-02-15 S00972, ImageSaveNum: 972021) 20:44:54   Obs.Manager Started Obs.Manager started 20:44:56   Obs.Overseer Started Obs.Overseer started 20:45:00   Services Started Observatory Services started 20:46:26   Services Started Observatory Services started 20:46:51   Telescope Connected Telescope Connected (TheSky6) 20:47:59 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:47 & 05:29 20:48:01 Observatory (AutoStart) Observatory placed in Auto-Start Mode 20:48:03   AutoStart Delayed Session delayed due to too few stars 20:48:24 Observatory (Manual) Observatory placed in Manual Mode 20:48:38 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:48:40 Session Pending Session pending (2022-02-15) 20:48:42 Session Initiating Session initiating (2022-02-15) 20:48:50   Plan Loaded Observing Plan loaded to queue (, Plan ID: 730) 20:49:06   Camera1 Connected SBIG Camera Connected (set point -25°C) 20:49:11   Telescope Connected Telescope Connected (TheSky6) 20:49:30 Session Equilibration Session ready for dome & camera equilibration 20:49:32 Wait On Weather Waiting for acceptable conditions 20:49:34 Session Suspended Session suspended 20:49:36   Dome Closed Dome already closed (closure time is unknown) 20:49:38   Queue Started Observing Queue started (33 targets selected) 20:59:58     Target Cancelled Target cancelled (4/36, NGC 958 w/SN2022ao) due to cloud 21:12:00     Target Cancelled Target cancelled (5/36, GCVS GK Per) due to cloud 21:25:15     Target Cancelled Target cancelled (6/36, Nova Cas 2021) due to cloud 21:37:00     Target Cancelled Target cancelled (7/36, AT2022bqs (CV)) due to cloud 21:51:04     Target Cancelled Target cancelled (8/36, 104P/Kowal) due to cloud 22:05:12     Target Cancelled Target cancelled (9/36, C/2019 L3 (ATLAS)) due to cloud 22:17:47     Target Cancelled Target cancelled (10/36, GCVS YZ Cnc) due to cloud 22:25:32 User Intervention User request to close and finish session 22:25:34   Queue Aborted Job Queue aborted 22:25:37 Session Closing Session closing 22:25:42   Dome Closed Dome already closed (closure time is unknown) 22:27:05   Dome Parked Dome parked (parking time 75s), Az: 90.0 deg 22:28:15   Telescope Parked Telescope parked (parking time 66s) 22:28:30   Telescope State Scope parked Turn scope off. (Handbox) 22:28:52   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 22:29:44   Services Stopped Night Services stopped 22:29:46 Session Housekeeping Housekeeping Started (Cleanup FITS, Create Fits Summary, Transfer Files) 22:29:47 Session Finished Session Finished

Session Alerts

Time     Alert Detail 19:57:49 PHD2 Alert No. of incomplete PHD2 stream reads has exceeded 5 20:14:00 PHD2 Alert No. of incomplete PHD2 stream reads has exceeded 20

Back to Top

Operational Issues (2022-02-15, S972)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to autostart session for a whole due to Wind condition (18:15). Feed  of data from Wind Sensor was intermittent and although Obs.Manager tab was showing an older value of 13.4 mph for wind which would have been acceptable,  the hourly wind forecast or actual weather value from DarkSky.Net was showing ~ 20 mph, which was probably blocking the start of session.  Would be helpful to understand what the precise block on session start was.   Eventually resolved itself at 19:53 when wind sensor began giving values of 2.5 to 3.8 mph.  CanOpen() routine returns False when WeatherData.WindSpeed > 20.  Monitor logs shows WeatherData.WindSpeed was 'stuck' on 20.4  between 14:38 and 19:40.  This is a period of several hours.  Value of 20.4 equated with a single rogue wind gust value.  A separate continuous improvement item is raised so that the current wind-speed from the weather forecast can be used in cases where the wind speed reading is evidently frozen or stuck for more than 30 mins.
  Resolved in-session  2022-02-15 (Session) 
   
• Incomplete PHD2 data stream reads occurred at start of session (19:57 & 20:14).  This is known occasional issue, when beginning a session without previously closing down AstroMain since the last live session.  Issue can have an effect of updating the reporting of PHD2 data and can effect guiding or execution of AstroMain program.  Issue was noticed because of the recent addition of session alerts (yellow and red alerts) to warn the user when the problem occurs.  Resolved by closing and restarting AstroMain.  It would be helpful to find a solution where the issue can be solved (ideally automatically) without having to restart AstroMain and the Session.  Closed 2023-02-15 as the issue hasn't been seen for several months (probably fixed/resolved.).
  Resolved in-session 2022-02-15, Closed 2023-02-15 (Session)    
   
• Obs.Monitor appears to be frozen in section Monitor TheSky6 Scope on 6 occasions within 30 minute period (2022-02-18).  During general operation of AstroMain on 2022-02-18 the Obs.Monitor appeared to freeze on 6 occasions between 17:43 and 18:13 with outages of 0.6 to 1.5 minutes. In each case the Obs Overseeer reported that the Obs.Monitor was frozen in the 'Monitor TheSky6 Scope' section.  Issue is similar to other instances of the same problem seen during two live sessions in the last 2 weeks (S967 2022-02-08 & S968 2022-02-09).  It's unclear why the routine stalls in this section as the only thing the section does is enquire whether TheSky6.Telescope is connected or not and write the result to a VM (virtual model) field.  Telescope isn't thought to have been connected at this time (no ASCOM logs to support any connection at this time), which should rule out a telescope related issue.  Maybe an issue with TheSky6 running slow or not responding for some reason?  Extra tracing was added to AstroMain 3.50 (2022-02-18) in order to try to understand the issue better.  No repeat of the problem since Feb 2022.   Issue closed after review (2022-02-18), but continue to monitor for any future instances of the issue.
  Unexplained issue  2022-02-18  (TheSky6 Telescope / AstroMain)

Small Defects

• The description of Session Event "Plan Loaded" contains unnecessary text " ," in brackets. The Plan Loaded text reads "Observing Plan loaded to queue (, Plan ID: 730)".  The ", " should be removed.  This is a historic defect going back multiple sessions.  The code shows the design is to write txtActivePlan.Text before the comma but this appears to always be blank.  Code modified to remove the unnecesary reference & comma.  Retrospective changes to database was using AstroPlan's CorrectSpecificEventsData() routine.  Retropsective change made to SessionEvents_xxx.htm files and Session Notes pages haven't been made.
  Fixed  2022-02-16 (AstroMain 3.49.6) 
   
• Dome "closing time is unknown" was reported & logged during session closing. Although Dome recognised as being already closed, the time of last closure and the closing time is not given, it is stated as being "unknown".  This is due to a current design limitation which caused the respective values for LastShutterCloseTime and LastShutterCloseSecs to be lost during an AstroMain program restart at 20:44 which was  between the time when the shutter was closed (20:32) following weather related session suspension and the time when the session was eventually closed (22:25).  Issue is fixed through a separate continuous improvement ticket that has been raised to allow closing time to be written to Session.dat file & later recalled from the .dat file  when restarting a session.
  Fixed 2022-02-16 (AstroMain 3.49.6)
   
• SkyConditionsTab01.png is null (blank) file and doesn't show the first Sky Conditions tab from the session. . Issue occurred before in S939 (2021-12-05) where it is unclear if this is an issue of AstroMain, AstroPlan or session circumstances. In the S972 session the problem appeared to be related to restarting the AstroMain program ?  When Session Initialises the TabNo is set to 1 (SkyConditionsTabNo = 1). When a Session restarts the TabNo is incremented:  (SkyConditionsTabNo = SkyConditionsTabNo + 1).   AstroMain code modified so that  the  MoveSkyConditionsTabFiles() routine is no longer called. This prevents a blank SkyConditions picture (without data) from overwriting a previous picture (with data).  AstroPlan / WebSite updated to upload/display up to 4 SkyCondition pictures (previously only 3 pictures were uploaded).
  Fixed 2022-02-16 (AstroMain 3.49.6,  AstroPlan 1.29.10, Website) .
   
• AstroWeather's Data tab isn't showing expected Nearest Storm & Next rain values for Current Weather.  AstroMain is shooing Nearest Rain  < 5 miles, Next 15 min  : Rain (0.1mm, 99%)  Next Rain : Rain Now (100% ), but AstroWeather data tab shows 0.0 miles,   '---' , 0.0 hours.
  Fixed 2022-02-16 (AstroWeather 1.15.4) .
   
• The Foc2 Ref Frame for Near Zenith Focus Field (Focus Field 5) unexpectedly shows cyan coloured target ellipse. An ellipse wouldn't be expected in this situation and hasn't previously been seen in other sessions.  It is supposed that LocateInfo hasn't been cleared of previous data (prehaps the session). Fix attempted (.CircleRadiusMins , .MajorAxisMins , .MinorAxisMins , .PositionAngle  set to vcNull  in the  InitialiseLocateInfo() routine)
  Fixed fix 2022-02-25 (AstroMain 3.50.4) 
  

• Add shutter closing time to the Session's 'session.dat' file to allow information to be carried over if the session/program is restarted.  Add LastShutterCloseTime and LastShutterCloseSecs to the session.dat file  This is to prevent instances of  "closing time is unknown" being reported and being logged in the session events table.  bWriteSessionData to be raised upon closing dome to ensure latest values get written to file.
  Done 2022-02-16 (AstroMain 3.49.6)
   
• Create a button routine in AstroPlan settings/database that will archive Completed Supernova targets and Completed Transients targets. Completed supernova to be moved from 'Supernova' (ProjectID=15) to 'Supernova (Inactive)' (ProjectID=44).   Completed transients targets to be moved from 'Transients' (ProjectID=51) to Transients (Inactive)' (ProjectID=52).   Completed CV transients to be moved from 'CV Transients'' (ProjectID=47)  to 'CV Transients (Inactive)' (ProjectID=53).  Button (btnArchiveSupernovaeAndTransients) and associated routines (ArchiveSupernovaeAndTransients()  and ArchiveCompletedTargetsByProject(SrcProject, DestProject) added to AstroPlan 1.29.10.  Upon execution  90 supernovae, 12 transients and 162 CV transients were archived.
  Done 2022-02-16 (AstroPlan 1.29.10) .
   
• AllSky/Weather Computer should supply current wind speed from the weather forecast API to Observator Computer (AstroMain) so that it can be used when the wind sensor readings are frozen/stuck.  This is to avoid the issue where a session (like S972, 2022-02-15) can not be started due to a wind speed reading from the Weather Station being stuck on an old value that is in excess of 20 mph. CurrentWindSpeed is already supplied to AstroAllSky from AstroWeather.  CurrentWindSpeed added to Synopsis Record in AstroAllSky which was then cascaded into changes in AstroMain & AstroGuard.
  Done 2022-02-16 (AstroWeather 1.15.4 / AstroMain 3.50 / AstroAllSky 3.15 . AstroGuard 1.7)
   
• AstroWeather to supply AstroAllSky with current wind direction (bearing) from the weather forecast API. This is to allow in future the supply of wind direction data to AstroMain when the wind sensor readings are frozen/stuck. At moment AstroMain uses winddirection (1) as a proxy for currentwinddirection.
  Done 2022-02-17 (AstroWeather 1.16).
   
• AstroMain to use Synopsis.CurrentWindSpeed in situations where wind sensor is evidently frozen/stuck for more than 15 mins.  This is to avoid the issue where a session (like S972, 2022-02-15) can not be started due to a wind speed reading from the Weather Station being stuck on an old value that is in excess of 20 mph, or equally starting a session or reopening the dome when it is blowing a gale (30 mph+) and the wind sensor reading is stuck on say just 5 mph.  Synoposis.CurrentWindSpeed added to AstroAllSky 3.15 and AstroMain 3.50.  It should be noted that the API CurrentWindSpeed is typically some 40% hgher than wind sensor reading. 
  Done  2022-02-17 (AstroMain 3.50 )
   
• Add flag to AstroMain/Manager tab to indicate station wind data from weather station has frozen. New field  txtFrozenFlagWind used to indicate that Station wind data has been frozen for more than 15 mins (indicated with 'F') . 
  Done  2022-02-17 (AstroMain 3.50 )
   
• Add WindScaleFactor to AstroMain Settings and a SU.WindScaleFactor variable to downgrade the Synopsis.CurrentWindSpeed that comes from WeatherForecast API.   This is to bring the Wind Speed into closer alignment with the typically lower speeds measured by the Weather Station Anemometer.
  Done  2022-02-18 (AstroMain 3.50 )
   
• Add Forecast.Currently.WindSpeed (API Wind Speed) to WindSpeed Graphs.   This is to monitor the general level of the WindScaleFactor (WeatherStation.WindSpeed / Currently.WindSpeed).   vwsGraph4.jpg (8h), vwsGraph49.jpg (16h),  vwsGraph9.jpg (5d). Requires recording of WeatherForecast.WindSpeed to file.  AstroMove (1.8.6) modified to download 'CurrWeatherData.dat' from Observatory Computer.
  Done  2022-02-18 (AstroWeather 1.16.1 , AstroMove 1.8.6)
   
• Add Target Status field and Active/Inactive Flag to ImageSets/Targets tab. This allows a quick assessment of whether a target (such as a supernovae) is still an active one or has been completed.
  Done   2022-02-18 (AstroMain 3.50 )
   
• Add Green 'X' button to ImageSets/Reduced tab that will close existing explorer windows and open Reduced folder.  This saves one extra button click.
  Done  2022-02-18 (AstroMain 3.50 )
   
• Use Forecast.Currently.WindDirection (WindBearing) to fill in Wind Direction Arrows on WindSpeed Graphs when Station.WIndDirection is unavailable.  Code modified for vwsGraph4.jpg (8h), vwsGraph49.jpg (16h) &  vwsGraph9.jpg (5d).
  Done 2022-02-19 (AstroWeather 1.16.2)
   
• Add Button Routine to AstroMain's ImageBuilder that will open the currently referenced picture file to PaintShopPro. This will saves opening or bring to front the target's store Folder, visually seraching for the required picture .png file and dragging/dropping it into PaintShopPro before additional edits can be made. Implemented in AstroMain 3.50.1 using 
  PaintShopProPath = "C:\Program Files (x86)\Paint Shop Pro 5\Psp.exe"
System.Diagnostics.Process.Start(PaintShopProPath, """" + ImagePath + """")
  The one limitation is that a new PaintShopPro instance is started each time the button routine is run, an existing PaintShopPro instance isn't used.
  Done  2022-02-18 (AstroMain 3.50 )
   
• Complete building of a Environment Hub class/object for accessing environmental, weather and other properties that are critical/useful to observatory operations.  A classEnviroment class has been previously been created (in Environment.vb) but has limited use at present. Implementing a fully functional 'Environment' Hub object would have the benefit of hiding the detail of how sensor values are read into AstroMain program from the main program threads (Obs.Manager, Job Queue and GUI).  Development of the new class and its gradual adoption can run in parallel to existing objects/arrays/process, which should reduce risks to live sessions.
  Done  2022-02-20  (AstroMain 3.50.1)
   
• Examine use of Profile.RegisteredDevices, Profile.IsRegistered & Profile.Registered methods  to check/remove POTH. Using ASCOM.Utilities.Profile class investigate issues where POTH.Hub is sometime still selected by TeleAPI..Telescope  even though POTH has been notionally removed from the system (Development Compter).  Also look at using Profile.Tracing & using the ASCOM Diagnostics Tool.   ASCOM Diagnosis log file had 54 references to 'POTH'.  
  Profile.IsRegistered ("POTH.Telescope") was True.  Profile.UnRegister ("POTH.Telescope") was used after which Profile.IsRegistered ("POTH.Telescope") became False and POTH.Telescope disappeared from Ascom's Profile Explorer.  It was noted that Profile.IsRegistered ("POTH.Dome") and  Profile.IsRegistered ("POTH.Focuser") both returned False, even though keys for these devices were listed in Profile Explorer and they both appear in Dome Chooser and Focuser Chooser .   Keys for these POTH devices was then deleted after which they no longer appeared in Device Chooser menus.  Rerunning the ASCOM Diagnosis produced a log file with a reduced but still significant number (24) of references to 'POTH'.  Most of these are explainable in terms of ASCOM  and legacy references, and DeviceHub's slaving mode.
  Done  2022-02-21 (ASCOM Profile)

[ Prev | Next ]

Back to Top

2022-02-19

AstroMain -  New 'Observing Conditions' Hub (2022-02-19)

Back to Top