David's Astronomy Pages Notes - Session 1031 (2022-08-23)

Notes (S1030)

Notes Main

Home Page

Notes (S1032)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (3),  Continuous Improvement (3)
	Images from 2022-08-23 >>        [ Local Files >> ]

Session Aims & Highlights (2022-08-23)

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. SH 2-71.  Complete acquistion of images of planetary nebula Sh 2-71 (Deep Sky Challenge Object in Aug 2022 edition of Ast.Now Magazine) following incomplete imaging in last session due to cloud (see Sh2-71 images from S1030).

 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.11
   
• AstroMain 3.53.9,  AstroPlan 1.31.1,   AstroShCap 1.3.12, AstroGuard 1.8.2
  AstroVOE 1.10  AstroSN 1.8.3,  AstroProtect 1.7,  AstroMove 1.9.1
  (AstroWeather 1.17.5, AstroAllSky 3.16,  AstroObsCam 1.9, AstroLaunch 1.9.4)

Highlights

•   Targets. Only 3 out of 21 planned targets were successful acquired. This was due to the development of cloud.
•   SH 2-71.  Cloud unfortuntaely prevented imaging of Sh2-71 in this 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:17:09 Session Monitoring AutoStart monitoring for Live Session opportunity between 23:17 & 03:38 23:17:13 Session AutoStarting Session autostarting (23:17) 23:17:46 Session Created Session Created (Live, 2022-08-23 S01031, ImageSaveNum: 1031001) 23:17:49   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 23:19:33   Services Started Observatory Services started 23:19:40 Observatory (Auto) Observatory placed in Fully-Automated Mode 23:19:43 Session Pending Session pending (2022-08-23) 23:19:45 Session Initiating Session initiating (2022-08-23) 23:19:48   Plan Requested Observing Plan requested from AstroPlan (1.31.1) 23:20:17   Plan Loaded Observing Plan loaded to queue (Plan ID: 793) 23:20:38   Camera1 Connected SBIG Camera connected (set point -10°C) 23:20:45   Telescope Connected Telescope connected (TheSky6) 23:21:09 Session Equilibration Session ready to Open Dome 23:21:55   Dome Opened Dome opened (opening time 45s) 23:22:50 Session Running Session running 23:22:52   Queue Started Observing Queue started (16 targets selected) 23:22:55     Target Started (NrZen) Target started (Focus Field 20, HIP 98535) 23:23:09   Dome Unparked Dome unparked 23:25:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:28:05       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 23:30:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 23:30:14       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:32:27       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:34:13       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:34:31     Target Completed Target completed (Focus Field 20, HIP 98535) 23:36:16     Target Started (1/16) Target started (1/16, IC 1132 w/SN2022prv) 23:40:32       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:42:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 23:59:16     Target Completed Target completed (1/16, IC 1132 w/SN2022prv) 23:59:21     Target Started (2/16) Target started (2/16, 2022 E3 (ZTF)) 00:02:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:04:09       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 00:17:04     Target Completed Target completed (2/16, 2022 E3 (ZTF)) 00:17:08     Target Started (3/16) Target started (3/16, GCVS CY Lyr) 00:19:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:21:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 00:25:48     Target Completed Target completed (3/16, GCVS CY Lyr) 00:25:52     Target Started (4/16) Target started (4/16, SH 2-71) 00:28:41       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:29:12   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 00:29:14   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 00:29:16       Focusing Aborted Foc1 Focusing Aborted 00:29:18     Target Aborted (4/16) Target aborted (4/16, SH 2-71) due to cloud 00:29:20   Queue Paused Queue paused for Session Suspension 00:29:22 Session Suspended Session suspended 00:30:07   Dome Closed Dome closed (closing time 49s) 00:50:56     Target Cancelled Target cancelled (4/16, SH 2-71) due to cloud 01:12:56     Target Cancelled Target cancelled (5/16, NGC 6745 w/SN2022prr) due to cloud 01:34:56     Target Cancelled Target cancelled (6/16, NGC 5875 w/SN2022oqm) due to cloud 01:56:56     Target Cancelled Target cancelled (7/16, NGC 5894 w/SN2022pgf) due to cloud 02:23:04     Target Cancelled Target cancelled (8/16, NGC 7492) due to cloud 02:41:04     Target Cancelled Target cancelled (9/16, GCVS SS Cyg) due to cloud 02:50:25     Target Cancelled Target cancelled (10/16, GCVS BL Lac) due to cloud 03:02:25     Target Cancelled Target cancelled (11/16, AT2022kl (CV)) due to cloud 03:11:23     Target Cancelled Target cancelled (12/16, WDS GRB 34) due to cloud 03:20:14     Target Cancelled Target cancelled (13/16, GCVS RX And) due to cloud 03:39:24     Target Cancelled Target cancelled (14/16, UGC 6983 w/SN2022pru) due to cloud 03:56:24     Target Cancelled Target cancelled (15/16, Nova Cas 2021) due to cloud 04:15:22     Target Cancelled Target cancelled (16/16, GCVS HH And) due to cloud 04:15:27   Queue Completed Job Queue completed 04:15:33 Session Closing Session closing 04:15:38   Dome Closed Dome already closed (closed at 00:30, closing time 49s) 04:17:09   Dome Parked Dome parked (parking time 82s), Az: 90.0 deg 04:18:26   Telescope Parked Telescope parked (parking time 70s) 04:18:41   Telescope State Scope parked Turn scope off. (Handbox) 04:19:03   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:19:56   Services Stopped Night Services stopped 04:19:58 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files) 04:20:01 Session Finished Session Finished

Session Alerts

Time     Alert Detail -- No Alerts                --

Back to Top

Operational Issues (2022-08-23, S1031)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Bad Guiding during Target 1/16.  Target 1/16 (IC 1132 w/SN2022prv) suffered from bad guiding due to multiple lost star events (Av RMS Error 30", Guide 20%, Lost 80%). Stars were badly trailed and images were unsuable.  PHD2 autoselected a poor guide star, one with SNR of only 7, that easily became lost, when there bright guide stars available.  Minimum Star SNR for Autofind is set to 50.   Problem seems to be is that when there are stars with SNR > 50 AutoFind will select one of them, but when there aren't any stars >50, is chosen a random star rather picking one with highest SNR.  Possible mitigations/solutions : a) try to get PHD2 developers to change the AutoFind routine, b) to have AstroMain's Guiding Manager intervene and increase exposure time (say from 1.5s to 3s),  c) to have AstroMain's Guiding Manager intervene and reset the Lock Position onto a star with better SNR.  Option c) implemented in AstroMain 3.53.10 by setting lock position to that of brightest star when the SNR of the auto-selected guide star is < 30.
  Fixed 2022-08-24  (AstroMain 3.53.10, PHD2) 
   
• CCD typically not cooled down to CCD Set Point temperature when first couple of Locate images are taken. Locate images of Near Zenith Focus Field are typically being taken with CCD Temperature some 1-3°C above set point temperature.  This doesn't affect operations at all or impact imaging of targets (which are taken at least 20 minutes later) but it lead to the raw frames from Near Zenith Focus Field Centering to be grouped in an 'OtherT' folder (like 'OtherT 3x3 5s C') which then necessiates some additional preparation when performing reduction on images the following day.  The usual workaround is to manually transfer the files from OtherT folder to nearest equivalent folder (-5c 3x3 5s C). This is inconvenient.  In S1031 session the first Locate image was taken at 22:24:08. With the camera connection / camera cooling initiated at 23:20:41 this was only 3.5 minutes beforehand. Potential solutions are   a) check CCD Temperature and wait a couple of minutes or so at Near Zenith Focus Field until CCD Temperature has reached / stabilised at intended set point, b) Connect camera and initiate cooling earlier c) relax the temperature tolerance when grouping raw frames into 5°C interval sets.  Solution a) implemented in AstroMain 3.53.10 by calling CheckForStableCCDTemperature() routine ahead of taking Centering Pictures for NearZenith Focus Field target. Tested during S1032 Session during which the first Locate frame for Near Zenith Focus Field was 0.6°C below the set point and was till grouped into a OtherT folder (this compares with 2.7°C above the set point temperature from the first locate frame in S1031 Session).  FITS_Summary . group raw frames routine in Excel changed so that Temperature Groups use a tolerance of +/-0.7°C instead of earlier  tolerance of +/-0.5°C.
  Fixed 2022-08-24 (Session, AstroMain  3.53.10, FitsSummary/Excel) 
   
• ObsCam picture of observatory interior at end of session was poor/corrupted. ObsCam picture when observatory checked the following morning was not of the usual quality, the main image was very pale with detail being almost invisible and annotation is duplicated, with the duplicate being written upside down relative to the principal annotation.  Issue resolved for now by restarting AstroObsCam and reconnecting to ObsCam camera, but occured again in the next S1032 session. Problems with instability with camera connection / program operations are an ongoing problem which still need be permanently resolved. ObsCam pictures ok in 2022-08-24 from to 16:28:29, but the next picture at 2022-08-25 03:01:20 is corrupted.  No pictures captured during first part of S1032 session (01:45 to 04:16, with first target at 02:57 with it's start of guiding/focusing at 03:01 (which corresponds to first corrupt ObsCam picture).  AstroObsCam loops show regular cycling pattern wherby the Viewing Loop might startout taking say 595ms,   but then more or less progressively increase by 300ms or so per loop, reaching say 5436ms, and which point 5s condition is passed and log message 'bLockCapture has been true for > 5s' is reported.   Looping cycles then contine at say 666ms before progressively increasing again.  Eventually program makes an intervention and disconnects/reconnects the Camera.  Following loops are then typically in range 727--831ms.  until eventually it increases again and reaches say 5474ms.  Pattern then repeats until 16:35:58. Then a break in log until 18:00:23, when log records Parsing Telecomms DataRecord messages every 2s, but with no Viewing Loop cycles.  At 01:51:31 there is a change in TeleComms Data Record  with figures like 9444444 or 4444 sometimes 'wrapping' to next line. Looks to be a duplicate of the last part of last row, rather than a new element. The extra numbers appear fro some datarecords dumps but not others. No pattern !.   Starting around 02:03:28, the log shows 2 or 3 extra lines of numbers (duplicating last parts of the datarecord). The number of lines of extra character progressively increases till it eventually reaches some 17-25 lines by time 10:59 when the program flipped to the next night date.  'Locked'  field (with lock times of 1000-5500ms) is displayed when the program's window is dragged around the screen for > 2-3s.   Issue is still occasionally happening 18 months later (eg S1200, 2024-03-21).
  Resolved but need a longer term solution 2022-08-24 (AstroObsCam) 

Small Defects

• File name of GuideFrame2 Fits image doesn't reflect actual exposure time.   Name of F2 Guide Frame  (eg Guider.20220823.235909.Guide01_F2_0.0s.IC_1132.FIT)  suggests that exposure time was 0.0s instead of the actual exposure time of 1.5s.  Fixed in AstroMain 3.53.10 using Exposure = Phd2.GetExposure.
  Fixed 2022-08-24 (AstroMain 3.53.10) 
   
• Report message "Running AstroMain"  is written twice at the start of session's report file, once either side of Contents section.  Message is written just once in original report but has become duplicated when inserting lines from the Contents.htm file.  Fixed in AstroMain 3.53.10 so that second message line isn't written anymore.
  Fixed 2022-08-24 (AstroMain 3.53.10) 
   
• Report message lines "Checking CCD Regulation"  and "Checking CCD Temp." are written twice out in 'Starting' section. Lines are written out by calls to ReportCCDTemperature() routine at the bottom of 'Autosave Settings' section and the top of the  'Equipment Status' section. Fixed in AstroMain 3.53.10 so that the first pair of message lines aren't written anymore.
  Fixed 2022-08-24 (AstroMain 3.53.10) 

• Have AstroMove to copy 'AutoGuide' subfolder from Observatory Computer.  This can be done at present for marking the 'New' folder for copying/transfer to Development Computer. Whilst _Focus folder gets copied to Session/Raw folder during Housekeeping the _AutoGuide folder doesn't. 
  Closed 2022-08-24 (AstroMove)
   
• Make a number of additional cosmetic and minor technical improvements to Report File messages.
  Done 2022-08-24 (AstroMain 3.53.10) 
   
• Make Start Services automatically attempt to restart TCF-S Focuser1 service if there is a problem when first starting the service. In the event that there is a connection/communication problem with the TCF-S Focuser/Driver the follow-up section should call RestartFocuser1Servuce()  routine.
  Done 2022-08-24  (AstroMain 3.53.10) 

[ Prev | Next ]

Back to Top