David's Astronomy Pages Notes - Session 1251 (2024-10-05)

Notes (S1250)

Notes Main

Home Page

Notes (S1252)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (2),  Small Defects (3),  Continuous Improvement (5)
	Images from 2024-10-05 >>

Session Aims & Highlights (2024-10-05)

Main aims

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

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6, CCDSoft5, DeviceHub 6.6.1.1,  MeadeGeneric 1.3.9, UPB 1.5, ASCOM 6.6,   Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus UPB & Motor Focus, TCF-S
• SharpCap 3.2, PHD2  2.6.13, Siril 1.0.6, deCONZ 1.18.2, ASCOM 6.6 SP1
• [ DomeLink 1.0 / 1.1 - not used ]
   
• AstroMain 3.71.4,  AstroPlan 1.42.1,  AstroShCap 1.3.15, AstroGuard 1.10.5 (any new items or versions in bold)
  AstroVOE 1.14,  AstroSN 1.14,  AstroProtect 1.7,  AstroMove 1.13   
  AstroWeather 1.25, AstroAllSky 3.20.6,  AstroObsCam 1.11.4 (not 1.11.5), AstroLaunch 1.11.3

Highlights-

• Targets. 5/26 planned targets observations were completed with 1 further target partially completed. One ToO target (IC 142) was also completed. Other planned targets failed due to Cloud/Session Suspension. One of these (T CrB) was submitted later as a ToO target but it failed due to Airmass Cutoff.
• Focusing.  No issues with focusing. The primary mirror is hold its position
• Dome. No issues opening/closing shutter during session.  Dome closed and parked ok at end of 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 21:25:57 Session Monitoring AutoStart monitoring for Live Session opportunity between 21:25 & 05:20 21:26:27 Session AutoStarting Session autostarting (21:26) 21:26:50   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 21:27:18   Camera1 Connected SBIG Camera connected (Set point -20°C) 21:27:20 Session Created Session Created (Live, 2024-10-05 S01251, ImageSaveNum: 1251001) 21:27:25   Scope Switched On Telescope Power has been switched on via UPB Powerbox. 21:29:23   Services Started Observatory Services started 21:29:30 Observatory (Auto) Observatory placed in Fully-Automated Mode 21:29:33 Session Pending Session pending (2024-10-05) 21:29:35 Session Initiating Session initiating (2024-10-05) 21:29:44   Camera1 Connected SBIG Camera connected (Set point -10°C) 21:29:51   Plan Requested Observing Plan requested from AstroPlan (1.42.1) 21:30:47   Plan Loaded Observing Plan loaded to queue (Plan ID: 1027) 21:31:28   Telescope Connected Telescope connected (TheSky6) 21:31:52 Session Equilibration Session ready to Open Dome 21:32:37   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 21:32:52 Session Running Session running 21:32:54   Queue Started Observing Queue started (26 targets selected) 21:32:58     Target Started (NrZen) Target started (Focus Field 23, HIP 113729) 21:33:12       Dome Unparked Dome unparked 21:36:03       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:38:50       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 21:41:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 21:41:28       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 21:43:37       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 21:45:21       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 21:45:38     Target Completed (NrZen) Target completed (Focus Field 23, HIP 113729) 21:46:19     Target Started (1/26) Target started (1/26, AT2024wpc) 21:51:14     Target Aborted (1/26) Target aborted (1/26, AT2024wpc) due to Priority 1 ToO Target 21:51:18     Target Started (2/27) Target started (2/27, IC 142, ToO) 21:55:59       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:58:43       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 22:14:37     Target Completed Target completed (2/27, IC 142, ToO) 22:14:41     Target Started (3/27) Target started (3/27, GCVS T CrB) 22:16:51       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 22:17:42     Target Aborted (3/27) Target aborted (3/27, GCVS T CrB) due to User Intervention 22:17:44   Queue Paused Queue paused for Session Suspension 22:17:46 Session Suspending Session suspending 22:18:36   Dome Closed Dome closed (Closing time 50s, Zigbee 42s) 22:18:38 Session Suspended Session suspended 22:36:51     Target Cancelled Target cancelled (4/27, NGC 6791) due to cloud 22:56:21     Target Cancelled Target cancelled (5/27, UGC 10984 w/SN2022yqv) due to cloud 23:18:21     Target Cancelled Target cancelled (6/27, AT2023xvp) due to cloud 23:28:18 Session Resuming Session resuming 23:29:03   Dome Opened Dome opened (Opening time 45s, Zigbee 40s) 23:29:05 Session Running Session running 23:29:07   Queue Resumed Observing Queue resumed 23:29:09     Target Started (7/27) Target started (7/27, AT2023hru (CV)) 23:41:31     Target Aborted (7/27) Target aborted (7/27, AT2023hru (CV)) due to User Intervention 23:41:35     Target Started (8/28) Target started (8/28, GCVS T CrB, ToO) 23:41:39     Target Failed (8/28) Target failed due to airmass limit (8/28, GCVS T CrB, ToO) 23:43:25     Target Started (9/28) Target started (9/28, NGC 6884) 23:46:15       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-S) 00:03:54     Target Completed Target completed (9/28, NGC 6884) 00:07:20     Target Started (10/28) Target started (10/28, AT2024vlc) 00:11:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:13:29       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 00:29:55     Target Completed Target completed (10/28, AT2024vlc) 00:29:59     Target Started (11/28) Target started (11/28, NGC 1275 w/AT2024xav) 00:33:36       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-S) 00:49:31     Target Completed Target completed (11/28, NGC 1275 w/AT2024xav) 00:51:40     Target Started (12/28) Target started (12/28, GCVS BL Lac) 00:54:56       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:57:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:01:20     Target Completed Target completed (12/28, GCVS BL Lac) 01:01:58     Target Started (13/28) Target started (13/28, NGC 7048) 01:04:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:07:08       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 01:08:13       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 01:12:18       SoftSuspend Cancelled Soft Suspend is cancelled due to improved conditions 01:15:53       SoftSuspend Called Soft Suspend called due to Deteriorating Conditions (too few stars) 01:22:11     Target Completed Target completed (13/28, NGC 7048) 01:22:13   Queue Paused Queue paused for Session Suspension 01:22:14 Session Suspending Session suspending 01:23:04   Dome Closed Dome closed (Closing time 50s, Zigbee 43s) 01:23:06 Session Suspended Session suspended 01:42:46     Target Cancelled Target cancelled (14/28, AT2024vla) due to cloud 01:57:06     Target Cancelled Target cancelled (15/28, AT2022bvc (CV)) due to cloud 02:09:06     Target Cancelled Target cancelled (16/28, AT2023qou (CV)) due to cloud 02:29:06     Target Cancelled Target cancelled (17/28, AT2024xhn) due to cloud 02:45:14     Target Cancelled Target cancelled (18/28, AT2024wxp (CV)) due to cloud 02:59:15     Target Cancelled Target cancelled (19/28, AT2023ugt (CV)) due to cloud 03:19:34     Target Cancelled Target cancelled (20/28, AT2024vhz) due to cloud 03:41:54     Target Cancelled Target cancelled (21/28, AT2024wqf) due to cloud 03:56:14     Target Cancelled Target cancelled (22/28, AT2024xiu (CV)) due to cloud 04:16:14     Target Cancelled Target cancelled (23/28, NGC 2830 w/AT2024vsu) due to cloud 04:38:34     Target Cancelled Target cancelled (24/28, UGC 4957 w/AT2024vrq) due to cloud 04:50:17     Target Cancelled Target cancelled (25/28, GCVS TV Cas) due to cloud 05:01:21     Target Cancelled Target cancelled (26/28, AT2024vtr (CV)) due to cloud 05:39:53     Target Cancelled Target cancelled (27/28, PGC 3792) due to cloud 06:04:03     Target Cancelled Target cancelled (28/28, GCVS RX And) due to cloud 06:04:07   Queue Completed Job Queue completed 06:04:11 Session Closing Session closing 06:04:16   Dome Closed Dome already closed (closed at 01:23, closing time 50s, zigbee 43s) 06:05:42   Dome Parked Dome parked (parking time 78s), Az: 90.0 deg 06:07:04   Telescope Parked Telescope parked (parking time 76s total) 06:07:19   Telescope State Handbox reads 'Scope parked Turn scope off.' 06:07:41   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 06:09:08   Services Stopped Night Services stopped 06:09:11 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 06:09:23     Dome (Find Park) Find Park started (Search Az 80.0 to 100.0°, Step 1.0°, Wide) 06:10:16     Dome Find Park found (Best Park Az 88.0°) 06:10:23     Dome (Find Park) Find Park started (Search Az 86.0 to 90.0°, Step 0.2°, Narrow) 06:11:24     Dome Find Park found (Best Park Az 88.3°) 06:11:30     Dome Dome has been synced at park position (Az 90.0°, Adjustment: +1.7°) 06:11:32   Dome Parked Dome parked 06:13:07   Dome Charging Dome is parked and re-charging Ok (31mA) 06:13:09 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 21:52:40 Yellow Alert Dome Discrepency Difference between Dome Az and Slave Az is > 1 deg (IC 142) 06:13:07 Green Clear Dome Charging Dome is parked and re-charging Ok (31mA)

Back to Top

Operational Issues (2024-10-05 S1251)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Cummulative Slew Angle and Av Slew Speed in Dome Path for IC 142 is incorrect after passing Az 360° (21:51). Dome Slew to IC 142 involved a clockwise slew  passing through Az 360°/Az 0°.  Dome Path table recorded in Log file is normal from Az 299.9° to Az 358.7°. But upon reaching Az 1° the cummulative slew angle jumped from 58.8° to 359° and slew sped jumped from 2.22°/s to 13.22°/s.   Desipite this logging error the overall slew angle and overall av. speed for the slew are calculated correctly.   The same problem affected dome slew to C/2022 E2 (ATLAS)  in session S1249 showing that this is not an isolated incident.  Fix implemented in AstroMain 3.71 by a tweak to the Dome SlewAngle calculation in Scope.SlewTheSkyScope() & Dome.SlewDomeToAzimuth().
    .SlewAngle = Dome.Azimuth - Dome.PreSlewAz ' modification to fix bug (SD S1251)
  If (.SlewAngle < 180) Then
    .SlewAngle = Math.Abs(.Az + 360 - Dome.PreSlewAz)
  ElseIf (.SlewAngle > 180) Then
    .SlewAngle = Math.Abs(.Az - 360 - Dome.PreSlewAz)
  Else
    .SlewAngle = Math.Abs(.SlewAngle)
  End If
  Fixed 2024-10-06 (AstroMain 1.71.5)
   
• No JPG pictures were generated for IC 142 that was submitted as an immediate ToO Target (21:52).  As target 1/26 (AT2024wpc) was hidden by cloud in western sky it was decided to submit IC 142 (in eastern sky) as a ToO target to make use of the observing time that would otherwise be wasted.  Locate, Guide Frame & Main Frames were successfully collected for IC 142 but no JPG pictures were generated & saved.  Locate JPG Pictures are present for prior target (AT2024wpc) finishing with picture 0008...Locate3 and are followed by pictures for the next target (GCVS T CrB) starting with picture 0022..Locate 1, indicating that pic_id was being incremented through  0009 to 0021 but the job executor didn't save 12 pictures for  IC 142.   JPG pictures for two ToO targets in S1249 and three ToO targets in S1248 were produced ok indicating that there is no systemic problem related to ToO targets.  Log file doesn't indicate any issue,  a normal success message like "Ok   | Converting Image 1251009 to JPG" is generated for each image.  Propose to put this down to being a one -off glitch for the time being and monitor future session for any further occurances of the problem. Meanwhile images from  IC 142 (Target ID: 3365, 1251008-15 ) were re-run on the development computer and no JPG pictures were generated confirming the isssue seen during the live session.  The target was rerun using Visual Studio with Debugging but this showed no issues. Running the .bat file to call ImageMagik showed no error but no JPG was produced. Stripping out commands showed that the problem is being caused by the -ve value '-1477' in the ellipse specification.
     -draw "translate 131,110 rotate 90 fill none stroke DeepSkyBlue ellipse 0,0 8,-1477 0,360"
  This sneeks through because LocateInfo.MinorAxisMins is vcNull (-99) and the ConvertFitsToJpg () code was only testing for LocateInfo.MajorAxisMins not being vcNull (-99). Fixed in AstroMain 3.71.5.  Issue occurred with IC 142 as it has size "0.5 x 0.0" in TheSky6 (i.e. a Minor axis size of 0) which is an error in the IC database in TheSky6
  Fixed 2024-10-07 (AstroMain 3.71.5)

Small Defects

• T CrB was submitted as a ToO target but then failed due to a Airmass Cutoff.  The planned T CrB observation failed due to cloud , and the target was submitted by user later on (after sky had cleared) as an immediate ToO target when it lay at Altitude 10.0° (Airmass 5.6).  This was picked up by AstroMain which aborted the current target and progressed to T CrB, but the Target failed during Pre-Slew checks due to AstroMain's Airmass Cutoff value (3.3) and wasn't observed. This wasted the opportunity to finish taking images of the preceding target.  AstroMain's airmass cutoff (currently set at 3.30) is applied in situations where the target names starts with 'GCVS' indicative of a variable target. The ToO submission form should either warn or not allow submission of a target (esp. a Main Variables target) if such a target will lie at low altitude and at a position which will fail Airmass Cutoff check. Fix implemented in AstroPlan 1.42.2, ToO submission is not allowed by GCVS targets where its current airmass is > 3.3, and a warning is given when ever the target is currently below 12° altitude.
  Fixed 2024-10-06 (AstroPlan 1.42.2)
   
• Targets with low Dec value are not getting onto Observing Plans.  It is noticed that a number of Hickson targets and other deep sky target are not getting onto Observing Plans and therefore not imaged even though they might might have a Must-Include Tier 1 and Tier 2 rating. Investigating it is noticed that if such targets typically have a C1 or C2 Sky Constraint to ensure they are only acquired under dark or relatively sky conditions. However this also means they taken on an airmass constraint of 2.5 (for C1 Sky Constraint) or 3.5 (for C2 Sky Constraint).  For targets with low Dec value it inevitably that they they have airmass even when they lie close to Meridian (ie highest sky position). For Hickson and Globular Cluster projects, a P1 sky constraint has been defined that could use a relaxed airmass threshold of 5.0 (later reset back to 2.5) and targets in these projects have been updated to use the P1 contraint.   Whilst a temporary measure could be to relax the airmass threshold for C1 and C2 Sky Contraint to a value of say 5.0 which would allow a lot more targets to become available for scheduling, it isn't ideal as it permits imaging of a high Dec target to be imaged with high (non-optimal) airmass.  Eventually resolved by implementation of a separate Continuous Improvement ticket that disables the normal airmass threshold associated with the Sky Constraint when hour angle of target is between -2h and +2h.
  Fixed 2024-10-08 (Targets Database)
   
• AstroMain's parsing of vma2 reference is only importing 2 decimal places from C and K reference mag. For C Star & K Stars with reference mags 10.843 & 11.779 respectively in "..\Reference\ProjectStars.txt" only 10.84 and 11.77 are imported by file parsing.
  Fixed 2024-10-08 (AstroMain 3.71.5)

Continuous Improvement

• Review the thresholds used for targets to fulfill the differing needs associated with low Dec and high Dec targets. Scheduling a low Dec target needs a relaxed airmass threshold otherwise it might never be scheduled/imaged whilst scheduling a high Dec target needs a stricter airmass threshold to ensure that it will be imaged under low airmass which will give best chance to get good images. At the moment the airmass contraint is fixed for a given Sky Constraint C1, C2, C3,  with C1 historically using AM 2.5 threshold, C2 using AM 3.5 threshold and C3 using AM5 threshold.  Using C3 to allow a low Dec target to be image down to AM 5 however means accepting brighter sky conditions which may be unsuitable for the target that are frequently fairer dim. Different thresholds can be defined for different projects or even for a specific target, but this does get around the need to allow AM to be relaxed for low Dec targets but not high Dec ones without compromising on Sky Brightness Thresholds. Solution implemented in AstroPlan 1.42.2, so that the normal airmass threshold associated with the Sky Constraint is relaxed to 6.0 when the hour angle of target is within the range -2.0 to +2.0 (ie when it lies in the southern sky).
  Done 2024-10-08 (AstroPlan 1.42.2)
   
• Create new routine to align images on brightest star.   Create new routine AlignFramesByBrightestStar() that copies images from Reduced Folder to Aligned Folder and then aligns images on brightest star referenced to the first frame. Implemented in AstroMain 3.71.5  .  Added new button routine:  btnObjAlignOnBrightestStar with title "Align Brightest". Added new enum members : AnalysisStage.AlignOnBrightestStar = 20 & AnalysisStage.FindBrightestStar = 21   Added new routine: AlignFramesByBrightestStar().  Added new checkbox:  cboxObjBrightestStar with title "By Brightest Star".    Whilst a button ("Align Brightest" has been added and it functions ok, the workflow route is that user checks the "By Brightest Star" checkbox, and then uses "Align" button which calls AlignFramesByBrightestStar() routine.  After combining & saving image, Link operation is entered quietly (bConfirm = false) and Brightest Star 'linking' is used to find brightest star, and proceed to build spectra, with it automatically set to use the brightest star x/y as the zero order star for making rotated ".rot"  fit file and the final spectra chart.
  Done 2024-10-08 (AstroMain 3.71.5)
   
• Extend AstroMain's Image Builder so that it can add a scale bar in Angstrom's for rotated spectra images. Image Builder can currently add a scale bar in arc mins  (e.g. '1 arc min').  When dealing with a rotated spectral image, an arc min scale bar is not appropriate and it is proposed to instead use a scale bar in Angstroms should be used e.g. 1000 A°. Implemented in AstroMain 3.71.5.
  Done 2024-10-08 (AstroMain 3.71.5)
   
• Extend AstroMain's VMA Analysis to measure the magnitude of T CrB star in images which can't necessarily be image linked.  B & V band images of T CrB  are being collected to track changes in the brightness of this recurrent nova which could become 'nova' in 2024-2026.  Currently the star is at around mag +10 and is being monitored by reference to star '98' (000-BBW-796) and check star '112' (000-BBW-805).  Typically images contain the 3 required stars (C, K & V) but few other stars such that image linking is unreliable, and analysis to date has required performing Show Inventory and getting each star's Instrumental Magnitude via 'Cursor Information' dialog, and then manually typing the Inst.Mag into a workbook, for calculation of Calc.Mag (B), Calc.Mag(V) and B-V for T CrB and the check star.  Target Centering normally ensures that T CrB, reference star & check star are positioning in roughly but not exactly the same location on image.  It would be a lot easier if AstroMain's VMA tool could perform this task.  A prototype implemention is included in AstroMain 3.71.5.  Two 'T CrB'  lines (B ,V) have been added to the reference file  "C:\Data\Ccd Imaging\Analysis\Reference\ProjectStars.txt" . The AnalyseVmaImage() routine is modified to recognise "GCVS T CrB" images and bypass image linking. AnalyseVariable_vma2() routine modified to recognise 'T CrB' cases and by-pass Object Ra/Object Dec lookup that would otherwise be used.  GetRawMag() routine is modified to recognise 'T CrB'  cases and call the GetBisqueMag_TCrB() subroutine instead of the normal GetBisqueMag_Mod() subroutine.  The GetBisqueMag_TCrB() subroutine, recognises the 'T CrB' specific and assigns a rough X/Y location for the particular star being analysed (C, K or V) and then finds the brightest star within a 40 pixel offset from the rough X/Y location and uses that star's inst. magnitude. The calculated line distances between the 3 stars (i.e. C-K, K-V & V-C) are summed, and checked that they are close to that expected.  Data is written out to the vma2 results file for onward import and analysis in a T CrB photometry workbook.
  Done 2024-10-08 (AstroMain 3.71.5)
   
• Create a photometry database / tables for holding photometric results with appropriate Forms and Charting facility.   New AstroSuite tool 'AstroPhot, new database photometry.sqlite'.
  To do 2024-10-08 (Database, AstroPhot)

[ Prev | Next ]

[ Prev | Next ]

Back to Top