David's Astronomy Pages Notes - Session 1409 (2026-03-19)

Notes (S1408)

Notes Main

Home Page

Notes (S1410)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (2),  Small Defects (5),  Continuous Improvement (5)
	- Figures (2)
	Images from 2026-03-19  >>

Session Aims & Highlights (2026-03-19)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. ShCap Imaging/Processing.   Continue testing of AstroMain/AstroShCap routines and workflow including Siril scripts

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6 6.0.0.65, CCDSoft 5.00.201, DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3,  Pulsar Dome Firmware 1.51 & Driver 6.3.10
• Pegasus-UI 2.10, Peg-Focuser 2.10, Peg-Switch 2.10, TCF-LSI 3.3.5
• SharpCap 3.2, PHD2  2.6.13, Siril 1.4.1, deCONZ 1.18.2, ASCOM 7.1.0.4707
   
• AstroMain 3.80.28,  AstroPlan 1.46.2, AstroShCap 1.3.20, AstroGuard 1.13.1  (any new items or versions in bold)
  AstroMag 1.5.12, AstroVOE 1.16,  AstroSN 1.16,  AstroProtect 1.10.6,  AstroMove 1.17.7
  AstroAllSky 3.27.6, AstroWeather 1.30.1,   AstroObsCam 1.13.1, AstroNorthCam 1.8.1, AstroLaunch 1.14.6 / 1.14.8

Highlights

• Targets. 24//27 planned targets were completed. 3 targets missed their slots due to replacement by 2 ShCap Targets (M76 & M108) that were injected to the Job Queue as ToO Targets
• ShCap Imaging/Processing.   Images collected from 2 ShCap targets (M27 and M76)
•  Dome. No issues open/closing shutter. Dome was successfully parked at the end of the 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) Note:  The NorthCam Star Count line is unreliable and should be ignored (The AstroNorthCam 'Find' Star method is producing many false positives from clouds)

Actual Weather vs Pre-Session Weather Forecast

Session Event Log

Time     Event Detail 20:04:03 Session Monitoring AutoStart monitoring for Live Session opportunity between 20:04 & 04:23 20:04:04 Session AutoStarting Session autostarting (20:04) 20:04:11 Session Created Session Created (Live, 2026-03-19 S01409) 20:04:13   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 20:04:32   Scope Switched On Telescope Power has been switched on via UPB Switch 20:06:18   Services Started Observatory Services started 20:06:28 Observatory (Auto) Observatory placed in Fully-Automated Mode 20:06:30 Session Pending Session pending (2026-03-19) 20:06:32 Session Initiating Session initiating (2026-03-19) 20:06:54   Camera1 Connected SBIG Camera connected (Set point -20°C) 20:06:57   Plan Requested Observing Plan requested from AstroPlan (1.46.2) 20:07:28   Plan Loaded Observing Plan loaded to queue (PlanID: 1207) 20:08:09   Telescope Connected Telescope connected (TheSky6) 20:08:34 Session Equilibration Session ready to Open Dome 20:09:19   Dome Opened Dome opened (Opening time 45s, Zigbee 41s) 20:09:59 Session Running Session running 20:10:02   Queue Started Observing Queue started (27 targets selected) 20:10:09     Target Started (NrZen) Target started (Focus Field 8, HIP 39357) 20:10:22       Dome Unparked Dome unparked 20:15:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:17:04       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 20:19:06       Focusing Completed Foc1 AutoFocus Completed (Profile No 1) 20:19:14       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 20:21:03       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 20:22:45       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 20:23:06     Target Completed (NrZen) Target completed (Focus Field 8, HIP 39357) 20:23:25     Target Started (1/27) Target started (1/27, C/2024 E1 (Wierzchos)) 20:30:10       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 20:38:38     Target Completed Target completed (1/27, C/2024 E1 (Wierzchos)) 20:38:42     Target Started (2/27) Target started (2/27, AT2026eva) 20:42:08       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 20:44:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 21:00:24     Target Completed Target completed (2/27, AT2026eva) 21:00:28     Target Started (3/27) Target started (3/27, UGC 622 w/AT2026epv) 21:05:16       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:07:24       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 21:23:23     Target Completed Target completed (3/27, UGC 622 w/AT2026epv) 21:23:27     Target Started (4/27) Target started (4/27, AT2026evo (CV)) 21:28:06       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 21:44:13     Target Completed Target completed (4/27, AT2026evo (CV)) 21:44:37     Target Started (5/27) Target started (5/27, C/2022 N2 (PANSTARRS)) 21:48:38       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 21:50:45       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 21:59:02     Target Completed Target completed (5/27, C/2022 N2 (PANSTARRS)) 21:59:06     Target Started (6/28) Target started (6/28, M76, ToO). Using SharpCap 22:01:48       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:04:13       Focusing Completed Foc1 AutoFocus Completed (Profile No 6) 22:23:27       Camera1 Connected SBIG Camera connected (Set point -20°C) 22:23:30     Target Completed Target completed (6/28, M76, ToO) 22:23:32     Target Started (7/29) Target started (7/29, M108, ToO). Using SharpCap 22:28:06       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 22:46:43       Camera1 Connected SBIG Camera connected (Set point -20°C) 22:46:45     Target Completed Target completed (7/29, M108, ToO) 22:46:47     Target Missed (8/29) Target's time slot was missed (8/29, 240P/NEAT) 22:46:49     Target Missed (9/29) Target's time slot was missed (9/29, GCVS SY Cnc) 22:46:51     Target Missed (10/29) Target's time slot was missed (10/29, PCG 1045+4931) 22:47:50     Target Started (11/29) Target started (11/29, PCG 0928+6347) 22:53:08       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 23:09:18     Target Completed Target completed (11/29, PCG 0928+6347) 23:10:11     Target Started (12/29) Target started (12/29, GCVS RZ LMi) 23:14:07       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:16:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 7) 23:21:25     Target Completed Target completed (12/29, GCVS RZ LMi) 23:21:48     Target Started (13/29) Target started (13/29, GCVS CN Leo) 23:25:47       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:27:56       Focusing Completed Foc1 AutoFocus Completed (Profile No 8) 23:35:28     Target Completed Target completed (13/29, GCVS CN Leo) 23:35:32     Target Started (14/29) Target started (14/29, 29P/Schwassmann-Wachmann) 23:39:39       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:42:00       Focusing Completed Foc1 AutoFocus Completed (Profile No 9) 23:53:45     Target Completed Target completed (14/29, 29P/Schwassmann-Wachmann) 23:53:50     Target Started (15/29) Target started (15/29, PCG 0922+2855) 23:57:06       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 23:59:42       Focusing Completed Foc1 AutoFocus Completed (Profile No 10) 00:15:43     Target Completed Target completed (15/29, PCG 0922+2855) 00:15:47     Target Started (16/29) Target started (16/29, M95). Using SharpCap 00:18:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:20:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 11) 00:39:27       Camera1 Connected SBIG Camera connected (Set point -20°C) 00:39:29     Target Completed Target completed (16/29, M95) 00:43:28     Target Started (17/29) Target started (17/29, SHK 57) 00:46:42       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:48:53       Focusing Completed Foc1 AutoFocus Completed (Profile No 12) 01:04:51     Target Completed Target completed (17/29, SHK 57) 01:05:48     Target Started (18/29) Target started (18/29, IC 700 w/SN2025aico) 01:09:13       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:11:21       Focusing Completed Foc1 AutoFocus Completed (Profile No 13) 01:27:18     Target Completed Target completed (18/29, IC 700 w/SN2025aico) 01:27:48     Target Started (19/29) Target started (19/29, SHK 113) 01:31:30       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:33:49       Focusing Completed Foc1 AutoFocus Completed (Profile No 14) 01:49:45     Target Completed Target completed (19/29, SHK 113) 01:50:08     Target Started (20/29) Target started (20/29, SHK 55) 01:56:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:59:01       Focusing Completed Foc1 AutoFocus Completed (Profile No 15) 02:15:35     Target Completed Target completed (20/29, SHK 55) 02:15:39     Target Started (21/29) Target started (21/29, NGC 4914 w/SN2026fjc) 02:19:46       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:21:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 16) 02:37:46     Target Completed Target completed (21/29, NGC 4914 w/SN2026fjc) 02:37:50     Target Started (22/29) Target started (22/29, T CrB) 02:41:23       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:43:31       Focusing Completed Foc1 AutoFocus Completed (Profile No 17) 02:47:50     Target Completed Target completed (22/29, T CrB) 02:47:54     Target Started (23/29) Target started (23/29, UGC 11058 w/SN2026ewd) 02:51:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 02:53:20       Focusing Completed Foc1 AutoFocus Completed (Profile No 18) 03:10:06     Target Completed Target completed (23/29, UGC 11058 w/SN2026ewd) 03:10:10     Target Started (24/29) Target started (24/29, M27). Using SharpCap 03:12:17       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 03:14:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 19) 03:20:18       Dome Unparked Dome unparked 03:25:45       Camera1 Connected SBIG Camera connected (Set point -20°C) 03:25:48     Target Completed Target completed (24/29, M27) 03:25:50     Target Started (25/29) Target started (25/29, GCVS BL Lac) 03:31:31       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:35:43     Target Completed Target completed (25/29, GCVS BL Lac) 03:35:47     Target Started (26/29) Target started (26/29, NGC 7292 w/SN2026fov) 03:39:29       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 03:55:37     Target Completed Target completed (26/29, NGC 7292 w/SN2026fov) 03:57:42     Target Started (27/29) Target started (27/29, NGC 6070 w/SN2026ejy) 04:01:33       Focusing Skipped Foc1 focusing skipped - star is lost (TCF-LSI) 04:17:42     Target Completed Target completed (27/29, NGC 6070 w/SN2026ejy) 04:20:02     Target Started (28/29) Target started (28/29, GCVS AM Her) 04:23:04       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:25:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 20) 04:31:27     Target Completed Target completed (28/29, GCVS AM Her) 04:31:43     Target Started (29/29) Target started (29/29, KIC 8462852) 04:35:10       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 04:38:02       Focusing Completed Foc1 AutoFocus Completed (Profile No 21) 04:42:03     Target Completed Target completed (29/29, KIC 8462852) 04:42:05   Queue Completed Job Queue completed 04:42:07 Session Closing Session closing 04:42:55   Dome Closed Dome closed (Closing time 49s, Zigbee 44s) 04:43:12   Dome Parked Dome parked (parking time 10s), Az: 90.0 deg 04:43:57   Telescope Parked Telescope parked (parking time 41s total) 04:44:21   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:45:18   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:46:42   Services Stopped Night Services stopped 04:46:45 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:47:33     Dome (Find Park) Find Park started (Search Az 80.0 to 100.0°, Step 1.0°, Wide) 04:48:32     Dome Find Park found (Best Park Az 91.0°) 04:48:38     Dome (Find Park) Find Park started (Search Az 89.0 to 93.0°, Step 0.2°, Narrow) 04:49:25     Dome Find Park found (Best Park Az 90.8°) 04:49:31     Dome Dome has been synced at park position (Az 90.0°, Adjustment: -0.8°) 04:49:33   Dome Parked Dome parked 04:49:41   Dome Charging Dome is parked and re-charging Ok (18mA) 04:49:43 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 04:49:41 Green Clear Dome Charging Dome is parked and re-charging Ok (18mA)

Back to Top

Operational Issues (2026-03-19 S1409)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Session commenced with AllSky Camera dewed over and couldn't be resolved. Noting that the AllSky Camera Images were showing dew with very few detectable stars the Session was started with relaxed thresholds. Given that the same issue had affected the previous session (S1408, 2026-03-17) a visit was made to the AllSky Camera and a ladder used to examine the camera's hemisphere. This showed that the hemisphere was covered in fine dew/condensation . The outside of the Observatory was similarly covered by a heavy due.  There was little/no dew inside the hemisphere. Both sides the hemisphere (interior and exterior) where wiped dry.   Almost immediately there was a major improvement in the clarity of the AllSky Images and the number of stars detected.  However over the course of the next 10-15 minutes the clarity and star count worsened, with the probable re-dewing of the camera. AllSky Heater is reported to be on. Conditions at the time : Temperature 6-7°C, Outside Humidity 91-93%. Wind 3-8mph dropping later to 2 mph.  Looking outside the followin morning showed a very heavy dew on the lawn. When the camera was checked the following day (around midday), the dew had cleared from the exterior of the camera hemisphere and the observatory exterior. There was some mild condensation inside the hemisphere which was wipped dry. Ticket closed (for now)
  Closed 2026-03-20 (Session, AllSky Camera)
   
• AstroMain dialog boxes seeking user confirmation that are frequently hidden by the Console Form, causing delay and confusion to the user.  Issue is due to MessageBox and MsgBox calls not having an owner. Fixed in AstroMain 3.80.29, MessageBox.Show (..) and MsgBox(..) converted to use MessageBox.Show(objconsole, ..), except for calls from MainForm which use MessageBox.Show(me, ..).
  Fixed  2026-03-20 (AstroMain 3.80.29)

Small Defects

• Jpg image of M76 taken with TS80/178MC is upside down - ie north down instead of north up (22:23) . Target 6/28 (M76) was injected into the night's observations as an ToO target and acquired using TS80/178MC and frames processed a runtime using Siril script.   The Jpg picture is upside down, noticed when looking at position of the bright star HIP 8063 (mag 6.7) relative to M76 and comparing positions in TheSky6 (See Fig 2a) .The image created by Siril (M76.20260319.Set1.g200.30x30s.color.50pc.png) has the correct North-Up orientation which demonsrates that the issue resides in AstroMain's ConvertZwoPngToJpg() routine. The same bug occured with the next ShCap target (M108). The issue is a hangover from the past when png files where previously generated by SharpCap which produced North-Down source image (which require rotating), compared to current workflow where the source image produced by Siril scripts is already in North-Up orientation and doesn't need fixing).  Fixed in AstroMain 3.80.29 (see Fig 2b)
  Fixed 2026-03-20 (AstroMain 3.80.29)
   
• The time annotated on Jpg pictures for M76 is incorrect.  The time shown on the Jpg picture for the ShCap target M76, (produced by ShCap/Siril) is 22:23.  This later than the time period that the frames were actually acquired (22:05:54 to 22:21:07).   It would seem that 22:23 was the time that .png file was created or was time where the jpg picture.  It should be the mid-point of the 30 frames.  Examining the code in ConvertZwoPngToJpg() shows that date/time is written by reference to current local time:
     Description + ", " + Now().ToString("yyyy-MM-dd HH:mm") + " LT"
  In the equivalent ConvertFitsToJpg() routine the date/time is written by reference to current UT time.
  Setting aside the issue of wheher the ConvertFitsToJpg' method is correct, in the case of ZwoFiles where the picture file is produced several minutes after the mid-time of the Light Frame collection  the date in clearly misleading.  Fixed in AstroMain 3.80.29 - ImageTime (in UT) is added as a parameter to ConvertZwoPngToJpg() routine and used in place of the current local time.
    Description + ", " + ImageTime.ToString("yyyy-MM-dd HH:mm") + " UT"
  (Note:  StackCam2Frames() routine has been moved to ShCapOps.StackCam2Frames).
  Fixed  2026-03-20 (AstroMain 3.80.29)
   
• Number of ShCap Frames to Stack is incorrect (22:21). After the acqusition of 30 light frames for Target 6/28 (M76), the SharpCap Result was reported and correctly stated the 30 frames had been completed.  During the following preparation to stack frames, the 'Verify frame set' step incorrectly reported that there was 60 frames to stack.  The number of frames recorded in the ImageSet.xml file is correct (30). The same issue occured with the next ShCap target (M108). Fixed in AstroMain 3.80.29
  Fixed 2026-03-20 (AstroMain 3.80.29)
   
• The Stack ShCap Frames process was incorrectly reported to have failed. During the execution of the Siril Scipt in Siril_CLI, the TakeSecondaryScopeFrames() routine monitors the size of the Siril log and the appearance of file products (stacked.fit and 2 png files).  Although the script was successfully completed, the monitor deemed that the Script has likely failed  and reported "Create Stacked Image  Failed  (siril.log filesize hasn't changed in 10s). The routine that tries to find and report possible failure points misleading sees the following two lines as suspicious and worthy of reporting.
    line 328  Found 46 stars in reference, channel #1    
  line 833  Total: 0 failed, 30 registered.
  The same issue affected the following ShCap target (M108) and has previously been noted to affect the image set reprocessing on Development Computer. Fixed in AstroMain 3.80.29 - StackCam2Frames() was looked out for appearance of 'result.fit' when it should have been looking out for 'stacked.fit'.
  Fixed  2026-03-20 (AstroMain 3.80.29)
   
• Temperature of ShCap Image Set isn't being recorded (. Although tested ok on the Observatory when taking Dark Setsthe previous day, the Cam2 (178MC) Temperature wasn''t recorded during the aquisition of a ShCap Image set of Target 6/28 (M76), Temperature was null (-99) in the ImageSet.xml file. As a consequence the TempDiff (difference between Light Frames and MasterDark is incorrect and the recommedation to acquire a new dark set at -99°C is obviously wrong. Investigating show that the temperature of first 5 frame is reported (13°C), but is 'null' for the remaining 25 frames. The same pattern is seen during the following M108 target (again just the first 5 frames have a reported temperature (9.7°C) ). The ObsPics pictures recorded every 30s demonstate that the Cam2 temperature values become null during the course of ShCap imaging. The first 5 frames likely correspond to a 'grace period' (seen with a yellow flag on the ObsPIcs). In reality the Cam2.temperature became null immediatly the moment that the camera was connected in SharpCap.  It is possible that temperature of Camera2 (178MC) is recorded ok when it is connected to PHD2 but isn't being recorded when the camera is connected to SharpCap. Issue was possiblily not seen when taking dark frames on 2026-03-18 as the camera was being swapped between SharpCap and PHD2. Since temperature was being obtained from the camera via SharpCap during the Dark Frame acquisition shows that there is no fundamental barrier to reading temperatures from SharpCap via ShCap server.   Possibly the monitoring routine isn't swapping to look at SharpCap camera temperature, after previously reading the PHD2 camera temperature.  Investigated show that Camera temperature is read within the Cam2.ReadTemperature() routine which either calls Phd2.GetCcdTemperature or ShCap.GetCameraTemperature, depending on what application the camera is supposedly currently connected within.  However there is a flaw in the logic whereby if Phd2.CameraConnected = True it calls Phd2.GetCcdTemperature but misses the situation where teh camera connected in PHD2 is the SBIG ST10-MXE when it is being used as the camera for 178MC imaging in SharpCap. This explains why the issue wasn't seen when taking Dark Frames , when PHD2 was not connected to any camera (specifically the SBIG ST-10XME).  The routine needs to know specifically what camera is connected in PHD2. Fixed in AstroMain 3.80.29 - an  extra condition
     ... and (Phd2.ProfileMode = "Cam2" Or Phd2.CameraName = "ZWO ASI178MC")
  has been added to the Phd2 guard in Cam2.ReadTemperature() routine.
  Fixed (AstroMain 3.80.29)

Continuous Improvement

• Add facility to AstroMove to copy 178MC's MasterDark files to the Observatory Computer. With the newly developed use of MasterDarks to correct light frames taken with the 178MC camera (Camera2) , the MasterDarks which are built on the House Computer (i.e. the Development/Analysis Computer) need to be uploaded to the Observatory Computer to allow Siril Scripts to correct light frames at runtime and permit first pass automatetd processing of Image Sets, the generation of stretch .png files and the production and upload of .Jpg equivalents to the Observatory Web Site.  Whilst this could be done manually on the occasions where this is performed, it would be handy to have this become a one click process.  The possibility of downloading Dark Frame ShCap sets from the Observatory Computer to the House Computer should also be explored. Implemented in AstroMove 1.18.
  Done  2026-03-21 (AstroMove 1.18)
   
• Add facility to AstroMove to copy Session Result pictures into local web folder. After each session the key runtime/result files are copied into the ExpressionWeb, this is tedious operation for the user,  as it involves selecting 8-10 specific files out of a total of some 120 files in the Session Logs folder an moving them into WebExpression.  The operation is particularly difficult to do if done from an Ipad remotely connection to the Development/Analysis Computer. As the files have a particular name format, this calls out for a 'one-click' process. It is proposed to add such a facility to AstroMove.   The user will need to make the additional step of Refreshing File in ExpressionWeb, but this is still a big saving. The facility should warn the use when there are multiple versions of the  SkyConditions file. The possibility of including a similar but separate facility to upload 'spaceweather/aurora' files to the web folder should also be explored. Implemented in AstroMove 1.18.
  Done 2026-03-21 (AstroMove 1.18)
   
• Extend AstroMain's Page Builder to be able to enter, store and display Acquistion Notes. Proposal is to be able to store Acquisition Notes with a Target Image Blocks. This has already been done for Process Notes.  Page Builder also need to be modified to write Acquisition Notes and Process Notes to Target's Section with WebPage and/or Html Snippet.   Implemented in AstroMain 3.80.31
  Done 2026-03-27 (AstroMain 3.80.31)
   
• Extend AstroMain's Page Builder to be able to store and display link to larger image. On older, manually created session pages, it was possible to enter a lhyperlink such as [Larger Image] allowing an alternatiive image variant to be seen. Currently in AstroMain 3.80.28 there is no provision to add such as a link. It is proposed to add this as a feature. Implemented in AstroMain 3.80.31 with alternate file name and link name being added onto a new "More" tab due to lack of room on the 'ImageBlock" tab
  Done 2026-03-27 (AstroMain 3.80.31)
   
• Create a process to create Custom ROI MasterDarks and MasterFlats from Full Frame MasterDarks and MasterFlats.  To reduce disk usage from taking Full Frame images using TS80/178MC when the target object occupies just a small part of the field, a smaller CaptureArea could be taken. But to support this MasterDarks and MasterFlats would normally need to be acquired using the same CaptureArea as the Light Frames. This is not feabile. Instead it is proposed to create Custom Support Frames by cropping Full Frame MasterDarks and Full Frame MasterFlats. A trial process / routine has been developed and tested on 2026-03-27 but now needs integrating with live image capture and processing.
  In Progress 2026-03-27 (AstroMain 3.80.31)

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top