David's Astronomy Pages Notes - Session 1092 (2023-01-27)

Notes (S1091)

Notes Main

Home Page

Notes (S1093)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (5)  Small Defects (6),  Continuous Improvement (11)
	Images from 2023-01-27 >>

Session Aims & Highlights (2023-01-27)

Main aims

1. Secondary Scope Imaging/Stacking.  Test out secondary scope imaging with automated in-session stacking of ZWO 178MC frames using and AstroMain's StackCam2Frames() routine, Siril-cli and a Siril script (OSC_stackframes.ssf).
2. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
3. AstroMain. Check new 3.60.13 version of AstroMain for any issues introduced by recent bug fixes and improvements including new Secondary Scope imaging routines.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• CCDApp2, TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.5.414, UPB 1.5, ASCOM 6.6
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.11dev2, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
   
• AstroMain 3.60.13, AstroPlan 1.35.12,   AstroShCap 1.3.14, AstroGuard 1.10.2
  AstroVOE 1.12.2  AstroSN 1.9,  AstroProtect 1.7,  AstroMove 1.9.8
  (AstroWeather 1.19.9, AstroAllSky 3.17.3,  AstroObsCam 1.11.2, AstroLaunch 1.10.7

Highlights

• Secondary Scope Imaging/Stacking. After a couple of teething issues caused by inappropriate preference settings on new Siril installation were resolved in session, the live session proved that the Secondary Scope (Cam2) imaging with automated in-session stacking of ZWO 178MC frames worked A few area of potential improvement were found.
  Targets. x targets out of x planned targets were completed with an additional x targets partially completed. Other targets weren't acquired due to cloud, or weren't attempted due to the session being terminated early due to expected continuation of cloud with rain showers
• AstroMain. There were no new issues introduced by the new AstroMain version (3.60.13)
• Dome Slews. Whilst only one dome slew suffered a fairly lengthy (80s) hold-up, three other slews had minor hold-ups (15-23s) that added up to a total of 2.3 minutes being lost due to hold-ups  (Hold Up Stats: 1/27 slews affected, 4%, 2.3 minutes total hold-up time).

Notes:

• After starting session,  both scope were focused (Near Zenith). Then slew to a starfield new Meridian/Dec 0. Image taken and linked . Sync operation performed in TheSky6 and then a short mapping job was conducted in which 10/12 points mapped successfully.  Scope was parked and then restarted.
  
• User Scripts can be put into a user folder and accessed from Siril UI by specified path on Siril's Preferences/Scripts tab (this means scripts dont have to be put into "C:\Program Files\SiriL\scripts" which requires admin rights

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 18:29:22   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 18:29:35 Session Created Session Created (Live, 2023-01-27 S01092, ImageSaveNum: 1092001) 18:30:29   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 18:32:12   Services Started Observatory Services started 18:32:56   Telescope Connected Telescope connected (TheSky6) 18:33:35   Camera1 Connected SBIG Camera connected (set point -25°C) 18:34:24   Dome Opened Dome opened (opening time 45s) 18:34:25       Dome Unparked Dome unparked 18:35:21     Target Started (NrZen) Target started (Focus Field 3, HIP 14181) 18:37:52       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 18:39:23       Focusing Failed Foc1 focusing failed (failed QC check - Ambiguous) 18:39:24       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 18:41:30       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 18:43:13       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 18:43:31     Target Completed (NrZen) Target completed (Focus Field 3, HIP 14181) 18:46:53   Automapping Started Automapping started (12 points planned) 18:59:03   Automapping Completed Automapping completed (10 points mapped out of 12 points) 19:01:13   Telescope Parked Telescope parked (parking time 66s) 19:01:23   Telescope State Handbox reads 'Scope parked Turn scope off.' 19:01:45   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 19:04:47   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 19:06:42   Telescope Connected Telescope connected (TheSky6) 19:07:25     Target Started (1/1) Target started (1/1, M36). Using SharpCap 19:20:35     Target Completed Target completed (1/1, M36) 19:20:37   Camera1 Connected SBIG Camera connected (set point -25°C) 19:22:52     Target Started (1/1) Target started (1/1, M34). Using SharpCap 19:36:04     Target Completed Target completed (1/1, M34) 19:36:06   Camera1 Connected SBIG Camera connected (set point -25°C) 19:36:07 Obs.Monitor Frozen Obs.Monitor appears to be frozen at around 19:36 in section 'Refresh Dome Picture/Label Dome Azimuth' 19:39:47     Target Started (1/1) Target started (1/1, M34). Using SharpCap 19:54:58     Target Completed Target completed (1/1, M34) 19:54:59   Camera1 Connected SBIG Camera connected (set point -25°C) 19:56:45     Target Started (1/1) Target started (1/1, M36). Using SharpCap 20:09:02     Target Completed Target completed (1/1, M36) 20:09:03   Camera1 Connected SBIG Camera connected (set point -25°C) 20:11:44   Dome Closed Dome closed (closing time 49s) 22:24:59 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:24 & 06:09 22:25:01 Observatory (AutoStart) Observatory placed in Auto-Start Mode 22:25:02 Session AutoStarting Session autostarting (22:25) 22:25:24   Services Started Observatory Services started 22:25:28 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:25:32 Session Pending Session pending (2023-01-27) 22:25:34 Session Initiating Session initiating (2023-01-27) 22:25:36   Plan Requested Observing Plan requested from AstroPlan (1.35.12) 22:26:33   Plan Loaded Observing Plan loaded to queue (Plan ID: 865) 22:26:49   Camera1 Connected SBIG Camera connected (set point -20°C) 22:27:24   Telescope Connected Telescope connected (TheSky6) 22:27:48 Session Equilibration Session ready to Open Dome 22:28:33   Dome Opened Dome opened (opening time 45s) 22:28:38 Session Running Session running 22:28:41   Queue Started Observing Queue started (26 targets selected) 22:28:43     Target Started (NrZen) Target started (Focus Field 7, HIP 34070) 22:31:51       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:34:38       Focusing Completed Foc1 AutoFocus Completed (Profile No 3, wide) 22:36:47       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:36:49     Target Completed (NrZen) Target completed (Focus Field 7, HIP 34070) 22:36:52     Target Started (1/26) Target started (1/26, UGC 3044 w/SN2023cf) 22:41:19       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 22:57:47     Target Completed Target completed (1/26, UGC 3044 w/SN2023cf) 22:58:24     Target Started (2/26) Target started (2/26, Minkowski 1-13) 23:02:46       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 23:21:02     Target Completed Target completed (2/26, Minkowski 1-13) 23:21:06     Target Started (3/27) Target started (3/27, Berkeley 71, ToO). Using SharpCap 23:22:33       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 23:33:11     Target Completed Target completed (3/27, Berkeley 71, ToO) 23:33:15     Target Started (4/28) Target started (4/28, NGC 189, ToO). Using SharpCap 23:34:26   SBIG Camera Take Image failed, Error Code xxx 23:34:28   CCDSoft Issue CCDSoft has encountered an image save issue [0000] 23:34:30   CCDSoft Restarting CCDSoft being restarted (attempt to fix unsaved file issue) 23:34:33   SBIG Camera Reset SBIG Camera being power-cycled 23:37:20   PHD2 Communication PHD2 is potentially stalled ('LoopingExposures' Events not detected) 23:37:43   PHD2 Restarted PHD2 service restarted 23:39:44   CCDSoft Restarting CCDSoft being restarted (user action) 23:39:51   SBIG Camera Reset SBIG Camera being power-cycled 23:43:36   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:43:38   HardSuspend Called Hard Suspend is called due to Critical Conditions (cloud) 23:44:12     Target Aborted (4/28) Target aborted (4/28, NGC 189, ToO) due to cloud 23:44:14   Queue Paused Queue paused for Session Suspension 23:44:15   Camera1 Connected SBIG Camera connected (set point -25°C) 23:44:16 Session Suspending Session suspending 23:45:06   Dome Closed Dome closed (closing time 50s) 23:45:09 Session Suspended Session suspended 23:45:37     Target Missed (5/28) Target's time slot was missed (5/28, 29P/Schwassmann-Wachmann) 23:47:37 Foc1FieldsUpdater Frozen Foc1FieldsUpdater appears to be frozen at around 23:47 in section 'Update Foc1Fields' 23:50:19   CCDSoft Restarting CCDSoft being restarted (user action) 23:50:26   SBIG Camera Reset SBIG Camera being power-cycled 23:51:08   Camera1 Connected SBIG Camera connected (set point -25°C) 23:51:56   SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 23:58:27     Target Cancelled Target cancelled (6/28, AT2023vq) due to cloud 00:20:27     Target Cancelled Target cancelled (7/28, AT2023nf (CV)) due to cloud 00:42:27     Target Cancelled Target cancelled (8/28, NGC 2528 w/SN2023jo) due to cloud 00:56:47     Target Cancelled Target cancelled (9/28, C/2022 A2 (PANSTARRS)) due to cloud 01:17:07     Target Cancelled Target cancelled (10/28, M31 w/AT2023ax) due to cloud 01:42:27     Target Cancelled Target cancelled (11/28, C/2020 V2 (ZTF)) due to cloud 01:54:27     Target Cancelled Target cancelled (12/28, AT2023vp (CV)) due to cloud 02:14:47     Target Cancelled Target cancelled (13/28, IC 1874 w/SN2023fu) due to cloud 02:18:18 Session Resuming Session resuming 02:19:03   Dome Opened Dome opened (opening time 45s) 02:19:05 Session Running Session running 02:19:07   Queue Resumed Observing Queue resumed 02:19:09     Target Started (14/28) Target started (14/28, MCG +5-26-43 w/SN2023af) 02:22:05     Dome Slew Dome slew held up at Az. 246.8, 222.2, 221.7° (Total delay 80s) 02:24:22 Foc1FieldsUpdater Frozen Foc1FieldsUpdater appears to be frozen at around 02:24 in section 'Update Foc1Fields' 02:24:49 TempMonitor Frozen TempMonitor appears to be frozen at around 02:24 in section 'Get CcdTemp Data' 02:34:32   CCDSoft Restarting CCDSoft being restarted (attempt to fix locked thread) 02:34:39   SBIG Camera Reset SBIG Camera being power-cycled 02:35:19     Target Failed (14/28) Target failed due to exception (14/28, MCG +5-26-43 w/SN2023af) 02:35:22   Camera1 Connected SBIG Camera connected (set point -20°C) 02:40:11     Target Started (15/28) Target started (15/28, NGC 3938 w/SN2022xlp) 02:47:01       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 03:02:52       SoftSuspend Called Soft Suspend is called due to Deteriorating Conditions (too few stars) 03:03:31     Target Completed Target completed (15/28, NGC 3938 w/SN2022xlp) 03:03:33   Queue Paused Queue paused for Session Suspension 03:03:35 Session Suspending Session suspending 03:04:23   Dome Closed Dome closed (closing time 50s) 03:04:25 Session Suspended Session suspended 03:21:47     Target Cancelled Target cancelled (16/28, NGC 5548 w/AT2022abcs) due to cloud 03:44:07     Target Cancelled Target cancelled (17/28, NGC 5631 w/SN2022aaiq) due to cloud 04:06:27     Target Cancelled Target cancelled (18/28, NGC 3705 w/SN2022xxf) due to cloud 04:25:11     Target Cancelled Target cancelled (19/28, C/2019 U5 (PANSTARRS)) due to cloud 04:45:31     Target Cancelled Target cancelled (20/28, NGC 5468 w/SN2023cj) due to cloud 05:07:51     Target Cancelled Target cancelled (21/28, UGC 10407 w/AT2022adyb) due to cloud 05:20:09     Target Cancelled Target cancelled (22/28, GCVS BL Lac) due to cloud 05:32:29     Target Cancelled Target cancelled (23/28, AT2023ds (CV)) due to cloud 05:44:29     Target Cancelled Target cancelled (24/28, AT2023fm (CV)) due to cloud 06:07:49     Target Cancelled Target cancelled (25/28, 81P/Wild) due to too few stars 06:09:52 Session Resuming Session resuming 06:10:37   Dome Opened Dome opened (opening time 45s) 06:10:39 Session Running Session running 06:10:41   Queue Resumed Observing Queue resumed 06:10:44     Target Started (26/28) Target started (26/28, HIP 87937) 06:14:00       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 06:17:07     Target Completed Target completed (26/28, HIP 87937) 06:17:11     Target Started (27/28) Target started (27/28, UGCA 402 w/SN2023cv) 06:23:39       Focusing Skipped Foc1 focusing skipped - unable to find a star (TCF-S) 06:40:24     Target Completed Target completed (27/28, UGCA 402 w/SN2023cv) 06:40:28     Target Started (28/28) Target started (28/28, GCVS SS Her) 06:44:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 06:46:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 06:50:05     Target Completed Target completed (28/28, GCVS SS Her) 06:50:08   Queue Completed Job Queue completed 06:50:11 Session Closing Session closing 06:51:01   Dome Closed Dome closed (closing time 45s) 06:51:53   Dome Parked Dome parked (parking time 45s), Az: 90.0 deg 06:53:05   Telescope Parked Telescope parked (parking time 69s) 06:53:20   Telescope State Handbox reads 'Scope parked Turn scope off.' 06:53:43   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 06:55:08   Services Stopped Night Services stopped 06:55:11 Session Housekeeping Session Housekeeping started (Create Fits Summary, Transfer Files) 06:55:21 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 18:58:18 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 180.6° (T+7.8s) 19:07:58 Yellow Alert Anomalous Dome Slew Dome slew resumed at Az 164.0° (T+27.4s) 19:36:39 Red Alert Obs.Monitor Obs.Monitor appears to be frozen in section 'Refresh Dome Picture/Label Dome Azimuth' (last cycle at 19:36:07) 19:36:44 Green Alert Obs.Monitor Obs.Monitor has resumed again (19:36) after 0.6 mins 23:25:23 Yellow Alert Dome Shutter Pulsar Shutter appears to be asleep (last fresh data was at 23:05:20) 23:25:24 Red Alert Dome Alert Shutter Data is being refreshed 23:27:44 Green Alert Dome Shutter Pulsar Shutter has woken up (fresh data started at 23:05:20, outage 22.4 min) 23:27:45 Green Alert Dome Alert Shutter Data has resumed updating 23:34:26 Red Alert SBIG Camera Alert Take Image failed, Error Code xxx 23:34:28 Red Alert CCDSoft Image file [0000] hasn't been saved to disk, possible CCDSoft issue 23:49:20 Red Alert Foc1Fields Updater Foc1FieldsUpdater appears to be frozen (last cycle at 23:47:37) in section 'Update Foc1Fields' 23:50:25 Green Alert Foc1Fields Updater Foc1FieldsUpdater has resumed again (23:50) after 0.0 mins 23:51:56 Green Alert SBIG Camera Take Image command accepted (bSbigDriverException flag is reset) 02:22:05 Yellow Alert Dome Slew Dome slew held up at Az. 246.8, 222.2, 221.7° (Total delay 80s) 02:22:36 Green Alert CCDSoft Image file has been saved to disk following CCDSoft Restart 02:26:06 Red Alert Foc1Fields Updater Foc1FieldsUpdater appears to be frozen (last cycle at 02:24:22) in section 'Update Foc1Fields' 02:27:21 Red Alert TempMonitor TempMonitor appears to be frozen (last cycle at 02:24:49) in section 'Get CcdTemp Data' 02:34:37 Green Alert Foc1Fields Updater Foc1FieldsUpdater has resumed again (02:34) after 0.0 mins 02:34:39 Green Alert TempMonitor TempMonitor has resumed again (02:34) after 9.7 mins

Back to Top

Operational Issues (2023-01-27, S1092)

• Critical Issues (0)
• Major Issues (0)
• Minor Issues (5)
• Small Defects (6)
• Continuous Improvement (11)
  

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Unable to send output of Siril script to a log file.  Unable to find a way of get output of siril-cli to go to a log file when executing via a .bat file.  Problem was put to Siri Forum (discuss.pixls.us) ( https://discuss.pixls.us/t/how-to-send-the-output-of-siril-cli-to-a-log-file-when-not-using-gui/34991 ), where a solution was provided by cissou8.   The problem is caused by using the start command in the line $ 'start siril-cli.exe .... >out.log'  which makes an empty log file but continues to direct output to a new cmd window which disappears once the script has finished not giving any time to read any error messages etc. The solution is to use the line $ 'siril-cli.exe ... >out.log' which correctly sends output to the specified log file. Solution tested 2023-01-29 and built into the .bat file builder in AstroMain's  StackCam2Frames() routine.
  2023-01-29 (AstroMain 3.60.14, Siril-cli)  
   
• Two "Foc1FieldsUpdater appears to be frozen" red alerts were raised (23:47 & 02:24).  In both cases a green (all clear) alert was issued which say "Foc1FieldsUpdater has resumed again .. after 0.0 mins" but the timings show that the outage wasn't  0.0 mins but was around 3 mins in the first case (23:47:37 to 23:50:25) and around 10 mins in the second case (02:24:22 to 02:34:37).  In the second case the issue seem to also affect the TempMonitor which similarly froze for around 10 mins  (02:24:49 to 02:34:39 in section 'Get CcdTemp Data'). TempMonitor's green (all clear) alert however gave the correct outage time  (TempMonitor has resumed again (02:34) after 9.7 mins). Changed the mechanism for obtaining the outage time for Foc1FieldsUpdater in AstroMain 3.61 (uses new variable 'Foc1FieldsFreezePointTime as date'). Closed after review 2023-02-01 (unable to identify/resolve underlying issue)
  Closed after review 2023-02-01 (AstroMain 3.61)  
   
• NightSummaryPlot6 shows the telescope under active operation whilst it was stationary with the tracking off.  Session was started off in manual mode, for a Short Mapping Job and the for acquisition Ad-Hoc targets (M34 & M36). After cloud developed the shutter was closed and the telescope tracking turned off whilst waiting of sky condition to improved.  Later in the evening the session was placed in AutoStart in order to commence automated operations. Between these times, whilst the Telescope Tracking was off,  AstroAllSky's NightSummary Plot shows continuous telescope operation/use.  AstroAllSky need to pick up on the fact that telescope is not tracking and to show the Telescope in a standby/unused state.
  This is best resolved from AstroMain as tracking state is not currently available to AstroAllSky through  ScopeMode needs to be set to Waiting or Suspended whilst it is in this mode which will cause AstroAllSkys DrawNightSummaryPlotLineInfo() routine to draw a narrow (non-active) Telescope Line rather than a thick (active) Telescope Line.  Fix attempted in AstroMain 3.61.
  Fix attempted 2023-02-01 (AstroMain 3.61)
   
• Problem with SBIG (ST-10) Camera Connection from PHD2 (time).  Automated guiding using LX200/ST10 profile seems to fail as it didn't have a connection to the SBIG (ST-10). Problem was spotted by AstroMain and by user at around the same time (which makes diagnosis and problem identification somewhat confusing. A (red) SBIG Camera Alert  "Take Image failed, Error Code xxx"  was raised at 23:34:26 with a (red) CCDSoft Alert "Image file [0000] hasn't been saved to disk, possible CCDSoft issue" issued a moment later at 23:34:28.  Reexamining the report messages it is seems probable that the issue might have been caused because operations were running in parallel as a result of spawning off work to a thread.  Code has been modified so that code user a flag to make it wait for the spawned process to finish before continuing.  Issue with SBIG Camera disconnection from PHD2 is deemed to be closed.
  Closed after review  2023-02-01 (AstroMain 3.60.14+) 
   
• Pulsar Shutter Data appeared to not be refreshed for more than 20 mins (23:05 to 23:27).  A yellow alert "Pulsar Shutter appears to be asleep (last fresh data was at 23:05:20)" was raised at 23:25   A green all-clear "Pulsar Shutter has woken up (outage 22.4 min)"  was issued at 23:27:45.  Examining the Pulsar ASCOM Log shows that Volatile messages continued throughout this period.  There seems to have been a change in data at 23:08 , where 32961 changes to 33009, 33030 and then to 33031. Then at 23:22:57 when 2834 changed to 2833.
    23:08:40.970 Volatile 190.7 1 0.000000 191.7 0 1 960 14968 -3 32961 4017 2835 0
  23:08:41.978 Volatile 191.4 1 0.000000 191.7 1 1 960 14968 -3 33009 4017 2835 0
  23:08:42.986 Volatile 191.7 0 0.000000 191.7 0 1 960 14968 -3 33030 4017 2835 0
  23:08:43.993 Volatile 191.7 0 0.000000 191.7 0 1 960 14968 -3 33030 4017 2835 0
  23:08:45.001 Volatile 191.7 0 0.000000 191.7 0 1 960 14968 -3 33031 4017 2835 0
  After this the shutter data doesn't seem to make any changes until 23:29:19. Similar issue happened 2022-02-14 following S109 (this had the same 22.4 min outage time - a coincidence ?).  Closed after review 2023-02-15 (whilst the cutoff for yellow alert could be raised to 25 mins, it is helpful to collect further statistics on the subject).
  Closed after review 2023-02-15 (AstroMain, Pulsar Dome ) 

Small Defects

• Auto stacking operation using siril-cli failed (output window quickly disappearing).  Siril Script to pre-process and stack frames acquired with ZWI 178MC camera using Sharpcap quickly exiting on Observatory Computer and not producing expected stack as it does on the Development Computer.  Run script via Siril GUI and discovered that script was failing with an error message saying that a 'requires' command was missing from script.   Edited script to include 'requires 1.0.6' which then allowed the script to successfully run. This was a teething issue following the installation of Siril immediately on Observatory Computer.   (On the Development Computer Siril's  'Preferences/Scripts' option ' "Requires" command is mandatory in scripts' was disabled, whilst it was enabled Observatory Computer). 
  Fixed In-Session 2023-01-27 (Siril)  
   
• Autostacking operation using siril-cli not using the correct Debayer Mosaic.  This was a teething issue following the installation of Siril on to the Observatory Computer immediately before the session started. Siril tries to use debayer mosic specified in Fits file header and doesnt get the colours correct.  Fixed using the same fix used on the Development Computer which was to disable the 'Bayer information from file's header if available' option on Siril's Preferences / FITS-SER debayer tab and set 'Bayer/mosaic pattern' option to "RGGB"
  Fixed In-Session 2023-01-27 (Siril)  
   
• Autostart section of website still shows Autostart report from previous session.  The 'Autostart Files' section of website still shows the Autostart Report from the previous session (S1081 from the night before). When a live session is created using Autostart, the new autostart report is saved on Live folder (as 'Session.LatestAutoStartReport.htm') and uploaded to the website where it becomes visible.  But in this instance the live session was created by the user without going through AutoStart, as it was intended to begin the session in manual mode in order to resync the scope position and perform a short mapping run. When session is started this way a blank Autostart file needs to be written which will supercede the report from the previous session.  Investigating code finds that there is already a ResetLiveAutoStartFiles() routine that is called and overwrites the previous AutoStart report and log files with empty files with the same names, but is only called when putting the Observatory directly into Full Automated mode (ie where AutoStart) hasn't been used.  Issue fixed in AstroMain 3.60.14 so that ResetLiveAutoStartFiles() routine is called from AssignObservatorySession() when Session is a new one, SessionType is Live And Mode is Manual.   A flaw was also found in the ResetLiveAutoStartFiles() routine where it uses FileSystem.CopyFile which leads to the new empty file still having a much older lastmodified datetime and AstroPlan doesn't recognise the file as a being new one and therefore doesn't automatically upload it to the website. This was fixed by using a new copy routine based on AstroPlan's CopyFileWithNewDate() routine, which uses FileSystem.Copy as before and follows this by use of a File.SetLastWriteTimeUtc () command to ensure file has a new datetime.
  Fixed 2023-01-28 (AstroMain 3.60.14)  
   
• When finishing up Secondary Scope Imaging report messages are being intermixed.  When finishing Secondary Scope Imaging the report messages from 'Connect Camera' (Cam1) are mixed up with report messages from 'Conditions, Post-Imaging'.  The process of disconnecting the SBIG (ST-10) camera from PHD2 (where it was used for autoguiding) and then reconnecting the camera in CCDSoft (ready for the next target) is likely spawned off as a separate threaded operation that executes in parallel with continuing Job Executor operations. The two operations should be performed as Synchronous tasks (ideally Conditons, Post Imaging should come first ?.  Fix implemented in AstroMain 3.60.14 but requires a live test to check that it works correctly and without sideeffects.
  Fixed 2023-01-28 (AstroMain 3.60.14)  
   
• When the Start Guiding call to PHD2 times-out the Guiding Manger reports this as an 'Error' when it is really just a warning or information message. Although PHD2 reports that guiding hasn't settled with the time-out period this doesn't neccessarily indicate an error that will stop autoguiding operation from being successful. Report message should be moderated accordingly..
  Fixed 2023-01-28 (AstroMain 3.60.14)  
   
• Autoguiding isn't being turned off after Secondary Scope Imaging finishes, but continues on until the end of the target execution.  For Primary Scope Imaging this is fine because the target execution comes very shortly after the completion of the image frames. However for new Secondary Scope Imaging that includes in-session frame stacking using Siril-cli and ConvertZwoPngToJpg picture generation the end of the target execution is deferred by up to 1.5 mins. The associated issue is that Guiding Chart for Secondary Scope Imaged target includes an extra frame in the history chart (eg 21 frames instead of 20 frames).   Guiding Chart is closed out by setting  calling StopPHD2GuidingMonitor() that sets  bStopTargetGuiding = True (or it can be set directly) which is see by RunPHD2GuidingMonitor() which proceeds to call GuidingChart.CloseOutImage(), GuidingChart.CloseOutChart() &  Phd2.StopPHD2Guiding().
  Fix attempted 2023-01-28 (AstroMain 3.60.14)  
   
• AllSky Annotated Plots showing ''0 (Focus Field 3)'  target when the Scope was mapping (18:46 to 18:59).  During the mapping the Annotated Plot shows either 'Scope' (if scope is slewing between points) or "Map Point 1/12" (when it is imaging & mapping a point). etc at the scope's sky position but it also shows '0 (Focus Field 3)' near to zenith. The lattter is where the scope was previously whilst Near Zenith Focusing was being conducted.  The plotting of '0 (Focus Field 3)' indicates that TP.NextTargets(0) continues to have data about the Focus Field 3 after Near Zenith Focusing (Manual) finishes. AstroMain 3.61 fixes the issue by calling TP.HideNextTargets() in RunManualFocusScopeNearZenith() routine after FocusScopeNearZenith() operations have finished. 
  Fixed 2023-02-01 (AstroMain 3.60.14) 

• Query.  Why was Near Zenith (Foc1) Focusing performed later in session when AutoStarting after it was performed at the beginning of the session. Near Zenith (Foc1 & Foc2) focusing was performed using Focus Field 3 at the beginning of the session under manual initiation at 18:35. The shutter was closed by user at 20:10 due to the cloud conditions.  After cloud eventually passed AutoStart was initiated at 22:24 and after starting,  Near Zenith focusing (Foc1) was performed under automated control at  22:28 (Focus Field 7).  Was the call to perform Near Zenith focusing due to a specified timeout in the validity of the original focusing or did the original Foc1 focusing fail ?.  Examine logs show that original Foc1 focusing failed it's QC check due to "Ambiguous result". Closed after review 2023-01-28.
  Closed 2023-01-28 (Session)  
   
• The 'Starting' ObsCam Image should be skipped when the Shutter is open. When restarting the session for some reason (such as after a crash, after reinstalling new version of AstroMain or after simply restarting Automated Mode ), the taking of a 'Starting' ObsCam Image should be skipped when the shutter is open.   It is isn't appropriate to turn on the Aux Light (used for the taking of special ObsCam images) when the shutter is open as it overwrites the original 'Starting' ObsCam Image and attracts unnecessary attention.   Prehaps the Starting Image should also not not be taken when Dome isn't parked, but this would have prevented the capture of any Starting ObsCam picture from the session.
  Done 2023-01-28 (AstroMain 3.60.14)  
   
• The use of ReportComment2B messages can be improved. When reporting receipt of a ToO request and loading of ToO that breaks into a job execution reporting the first line with "< " should be replaced with a simple blank line
     Slewing (Ra/Dec)... ** (Continued below)
   >
   > Received ToO Request Ok 1 observation requested
   > Loading ToO Ok Berkeley 71 (priority 2, c. 22:37 - 23:07) imported at 22:37
   > Inserting ToO Target... Fail Target (Berkeley 71) is deferred due to a Rank 1 'Must Include' target

   **Slewing (Ra/Dec)... Ok Slew Finished (31s overall)
  Done 2023-01-28 (AstroMain 3.60.14)  
   
• Session State should be written in the title of AstroMain's ObsConsole form. At the moment the name of the current open tab is written into the form's title along with session name.   The addition of the tab name provides no significant extra information from what is evident from the form display itself.  It would be far more useful to show the current session state.  Whilst session state can be gleaned from the Manager tab or ObsViewer window or gleaned from the last few report messages visible in the console text box this requires additional steps/action from the user.  .Implemented in AstroMain 3.60.14 including the addition of new ObservatoryManager.UpdateWindowTitle() routine which call a new objconsole.UpdateWindowTitleAction() routine via BeginInvoke call.  Original objconsole.UpdateWindowTitle() routine is preserved but now calls UpdateWindowTitleAction.   Need to monitor sessions for possible sideeffects.
  Done 2023-01-28 (AstroMain 3.60.14)  
   
• Re-factor 'StartingStageNo = StartingStageNo + 1' and 'ClosingStageNo = ClosingStageNo + 1'  (ObsManager). Replace use of these statements bu calls to new routines 'SetNextStartingStage'  and 'SetNextClosingStage'. This allows calls to VM.SessionState() and UpdateWindowTitle() to be included in these routines reducing number of code lines in the ObsManager's main loop.
  Done 2023-01-28 (AstroMain 3.60.14)  
   
• The 'X' disconnect button for Telescope/Dome and TCF-S Focuser should probably be protected by a user confirmation dialog to avoid accidental use during a live session.  Only the TCF-S Focuser wasn't protected.  User confirmation is now required.
  Done 2023-01-28 (AstroMain 3.60.14)  
   
• Extend AstroMain to move/copy stacked ZWO image pictures (.png) to a special subfolder in the Session's Folder and support the linking to these pictures from the Local Files page.  Pictures should probably be re-copied once the session's SharpCap/ZWO Imaging folder has been copied from the Observatory Computer.  Implemented in AstroMove 1.9.12. Pictures (excluding 'result' pngs are put in session's '_ZWO Pictures' folder.
  Done 2023-01-31 (AstroMove 1.9.12)  
   
• Frame reporting during Secondary Scope Image shouldn't use 'Stacked'. The use of 'Stacked' or 'Dropped' is a carry over from the earlier Take Image Set procedure which use LiveStacking where the term (Stacked or Dropped) was relevant, but in the new procedure it is meaningless as all frames are candidates for follow-up stacking in Siril.
  Done 2023-02-07 (AstroShCap 1.3.15)  
   
• Query.  Why did original Near Zenith (Foc1) Focusing fail its QC check.  Examination of logs show that original Foc1 focusing failed it's QC check due to "Ambiguous result".  Looking at the profile (profile01, foc1.Focus_Field_3, see Fig 1) doesn't suggest any data problem, best fit curve looks good. Best Focus was selected at 4273 steps (report as using "Modified Best Focus) .  Measurements 4354 (Curve Fit), 4219 (Mid Point), 4179 (P50), 4179 (Peak),  4192 (Alt, from (mid+P50 + peak)/3 ) and 4286 (Altm from MaxPixel weighted FWHM).  Code to be examined but it lis hypothised that the QC check might have failed because the Difference (81) between Curve Fit (4354) and Chosen Best Focus (4273) was more than a required amount.   'Ambiguous Result' is given when  CalculateBestFocusPosition() returns CurveUsed = False. Replaying the data (1092, 1) produced the same result.  Next step is to replay the data but using Visual Studio's debugger to understand the specific decisions made by the CalculateBestFocusPosition in discounting the curve data.  There were multiple cases of Focus Profile rejection/ambiguous result in Session S1151 (2023-09-29).  S1092/Profile replayed using AstroMain 3.66.6 and the profile now passes (RmsE 0.49)
  Closed 2023-03-21 (Session, AstroMain 3.66.6)  
   
• Explore the use of Siril stacking using the -filter-fwhm option to Explore use of stack command with an option like '-filter-fwhmx=75%'
  To do 2023-01-28+ (Siril, Scripts)  
   
• Consider using a workaround to get the 'Previous Observation' date for Ad-Hoc targets. The Job Executor gets 'Previous Observation date as reports it for each target. However it currently doesn't report a data for Ad-Hoc targets that aren't based on a Target ID.  When Target ID isn't provided (TargetID =0) the Job Executor could instead look up previous observation by a longer database search using TargetName instead of TargetID.
  To do 2023-01-28+ (AstroMain 3.60.14+)  

[ Prev | Next ]

Back to Top