David's Astronomy Pages Notes - Session 1444 (2026-08-13)

Notes (S1443)

Notes Main

Home Page

Notes (S1444)

	Session Aims & Highlights
	- Observing Result  - Night Summary Plot  - Session Event Log
	Operational Issues
	- Critical Issues (0),  Major Issues (0),  Minor Issues (3),  Small Defects (6),  Continuous Improvement (22)
	- Figures (2)
	Images from 2026-08-13  >>

Session Aims & Highlights (2026-08-13)

Main aims

1. Targets.  Acquire images of a selection of variable stars, nearby stars, comets & deep sky targets as allowed by sky conditions.
2. AstroMain. Check new AstroMain xx.xx  version for any issues or problems following introduction of a number of changes.

 Equipment & Software

• 12" LX200 and ST-10XME
• 80mm APO and ZWO ASI 178MC
• TheSky6 6.0.0.65, CCDSoft5 5.0.201, DeviceHub 7.1.0.4707, MeadeGeneric 1.3.12.522, UPB 3, PulsarDome 6.4.0.0
• Peg-Unity 2.12, Peg-Focuser 2.12, Peg-Switch 2.12, TCF-LSI 3.3.5
• SharpCap 3.2.6482, PHD2 2.6.14, Siril 1.4.2, deCONZ 2.18.2, ASCOM 7.1.0.4707
   
• AstroMain 3.83.5, AstroPlan 1.47, AstroShCap 1.3.23, AstroGuard 1.13.2
  AstroMag 1.5.12, AstroVOE 2.0.1, AstroSN 1.16.1, AstroProtect 1.7, AstroMove 18.2
  AstroAllSky 3.28.1, AstroWeather 1.30.4, AstroObsCam 1.14, AstroNorthCam 1.10.4, AstroLaunch 1.14.9

Highlights

• Targets. 6/x planned targets were completed with 1 target partially completely. Other targets failed due to cloud / session suspension
•  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 22:38:16 Session Monitoring AutoStart monitoring for Live Session opportunity between 22:38 & 03:44 22:38:17   AutoStart Delayed Session delayed due to cloud 22:40:07 Session AutoStarting Session autostarting (22:40) 22:40:13 Session Created Session Created (Live, 2026-08-13 S01444) 22:40:16   CCDSoft Restarting CCDSoft being restarted (to set AutoSave No.) 22:40:38   Scope Switched On Telescope Power has been switched on via UPB Switch 22:42:25   Services Started Observatory Services started 22:42:36 Observatory (Auto) Observatory placed in Fully-Automated Mode 22:42:38   AutoStart Delayed Session delayed due to cloud 22:42:40 Session Pending Session pending (2026-08-13) 22:42:42 Session Initiating Session initiating (2026-08-13) 22:43:01   Camera1 Connected SBIG Camera connected (Set point -5°C) 22:43:04   Plan Requested Observing Plan requested from AstroPlan (1.47) 22:44:49   Plan Loaded Observing Plan loaded to queue (PlanID: 1245) 22:45:32   Telescope Connected Telescope connected (TheSky6) 22:45:56 Session Equilibration Session ready to Open Dome 22:46:42   Dome Opened Dome opened (Opening time 45s, Zigbee 39s) 22:46:44 Session Running Session running 22:46:47   Queue Started Observing Queue started (16 targets selected) 22:46:53     Target Started (NrZen) Target started (Focus Field 19, HIP 93376) 22:47:08       Dome Unparked Dome unparked 22:50:02       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 22:52:26       Focusing Completed Foc1 AutoFocus Completed (Profile No 1, wide) 22:54:02   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:54:04   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 22:54:06       Focusing Aborted Foc1 Focusing Aborted due to HardSuspend 22:54:08     Target Aborted (NrZen) Target aborted (Focus Field 19, HIP 93376) due to cloud 22:54:10   Queue Paused Observing Queue pausing for Session Suspension 22:54:12 Session Suspending Session suspending 22:54:53   Dome Closed Dome closed (Closing time 45s, Zigbee 42s) 22:54:55 Session Suspended Session suspended 22:57:08 Session Resuming Session resuming 22:57:23   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:57:25   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 22:57:27     Target Aborted (1/16) Target aborted (1/16, GCVS CY Lyr) due to cloud 22:57:29   Queue Paused Queue paused for Session Suspension 22:57:53   Dome Opened Dome opened (Opening time 45s, Zigbee 39s) 22:57:55 Session Running Session running 22:57:57   Queue Resumed Observing Queue resumed 22:58:00   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 22:58:02   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 22:58:04   Queue Paused Observing Queue pausing for Session Suspension 22:58:06 Session Suspending Session suspending 22:58:53   Dome Closed Dome closed (Closing time 50s, Zigbee 42s) 22:58:55 Session Suspended Session suspended 23:01:44 Session Resuming Session resuming 23:01:48   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:01:50   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 23:01:52     Target Aborted (1/16) Target aborted (1/16, GCVS CY Lyr) due to cloud 23:01:54   Queue Paused Queue paused for Session Suspension 23:02:29   Dome Opened Dome opened (Opening time 45s, Zigbee 39s) 23:02:31 Session Running Session running 23:02:33   Queue Resumed Observing Queue resumed 23:02:35   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:02:37   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 23:02:39     Target Started (1/16) Target started (1/16, GCVS CY Lyr) 23:02:42     Target Aborted (1/16) Target aborted (1/16, GCVS CY Lyr) due to cloud 23:02:44   Queue Paused Queue paused for Session Suspension 23:02:46 Session Suspending Session suspending 23:03:29   Dome Closed Dome closed (Closing time 45s, Zigbee 42s) 23:03:31 Session Suspended Session suspended 23:06:14 Session Resuming Session resuming 23:06:59   Dome Opened Dome opened (Opening time 45s, Zigbee 39s) 23:07:02 Session Running Session running 23:07:05   Queue Resumed Observing Queue resumed 23:07:07     Target Started (1/16) Target started (1/16, GCVS CY Lyr) 23:10:20       Focusing Started-Foc2 Foc2 Focusing Started (Secondary Scope, using ShCap) 23:12:24       Focusing Completed Foc2 AutoFocus Completed (Profile No 2, wide) 23:14:12       Focusing Completed Foc2 AutoFocus Completed (Profile No 2) 23:14:34     Target Failed (1/16) Target failed due to exceeded time slot (1/16, GCVS CY Lyr) 23:14:38     Target Started (2/16) Target started (2/16, NGC 6070 w/SN2026ejy) 23:19:44       Focusing Skipped Foc1 focusing skipped - star is too dim (TCF-LSI) 23:36:06     Target Completed Target completed (2/16, NGC 6070 w/SN2026ejy) 23:36:10     Target Started (3/16) Target started (3/16, AT2026lck) 23:52:18   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 23:52:20   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 23:52:26     Target Aborted (3/16) Target aborted (3/16, AT2026lck) due to cloud 23:52:28   Queue Paused Queue paused for Session Suspension 23:52:30 Session Suspending Session suspending 23:53:13   Dome Closed Dome closed (Closing time 45s, Zigbee 42s) 23:53:15 Session Suspended Session suspended 23:55:18 Session Resuming Session resuming 23:56:04   Dome Opened Dome opened (Opening time 45s, Zigbee 39s) 23:56:06 Session Running Session running 23:56:09   Queue Resumed Observing Queue resumed 23:56:11     Target Started (4/16) Target started (4/16, NGC 5907 w/SN2026kid) 00:00:00       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:01:00       Focusing Failed Foc1 focusing failed - star lost 00:17:22     Target Completed Target completed (4/16, NGC 5907 w/SN2026kid) 00:17:26     Target Started (5/16) Target started (5/16, NGC 4205 w/SN2026fvx) 00:21:25       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 00:25:37       Focusing Completed Foc1 AutoFocus Completed (Profile No 3, wide) 00:28:07       Focusing Completed Foc1 AutoFocus Completed (Profile No 3) 00:44:12     Target Completed Target completed (5/16, NGC 4205 w/SN2026fvx) 00:44:16     Target Started (6/16) Target started (6/16, MCG +7-28-15 w/SN2025adje) 01:04:51     Target Completed Target completed (6/16, MCG +7-28-15 w/SN2025adje) 01:04:55     Target Started (7/16) Target started (7/16, T CrB) 01:13:17     Target Completed Target completed (7/16, T CrB) 01:13:22     Target Started (8/16) Target started (8/16, AT2026juw (CV)) 01:17:45       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:20:12       Focusing Completed Foc1 AutoFocus Completed (Profile No 4) 01:26:18     Target Completed Target completed (8/16, AT2026juw (CV)) 01:26:23     Target Started (9/16) Target started (9/16, LEDA 214810 w/SN2026lda) 01:30:19       Focusing Started-Foc1 Foc1 Focusing Started (TCF-S) 01:32:48       Focusing Completed Foc1 AutoFocus Completed (Profile No 5) 01:35:52   Critical Cloud Alert Critical Cloud Alert (Obs.Manager will close the Dome) 01:35:54   HardSuspend Called Hard Suspend called due to Critical Conditions (cloud) 01:35:56     Target Aborted (9/16) Target aborted (9/16, LEDA 214810 w/SN2026lda) due to cloud 01:35:59   Queue Paused Queue paused for Session Suspension 01:36:01 Session Suspending Session suspending 01:36:47   Dome Closed Dome closed (Closing time 50s, Zigbee 42s) 01:36:50 Session Suspended Session suspended 01:43:42     Target Cancelled Target cancelled (9/16, LEDA 214810 w/SN2026lda) due to cloud 02:02:26     Target Cancelled Target cancelled (10/16, M72) due to cloud 02:12:44     Target Cancelled Target cancelled (11/16, GCVS BL Lac) due to cloud 02:33:04     Target Cancelled Target cancelled (12/16, IC 5191 w/SN2026myp) due to cloud 02:55:24     Target Cancelled Target cancelled (13/16, UGC 12613) due to cloud 03:17:44     Target Cancelled Target cancelled (14/16, UGC 12856) due to cloud 03:39:44     Target Cancelled Target cancelled (15/16, M31 w/AT2026jnl) due to cloud 04:04:57     Target Cancelled Target cancelled (16/16, Gliese 65) due to cloud 04:05:01   Queue Completed Job Queue completed 04:05:06 Session Closing Session closing 04:05:08   Dome Closed Dome already closed (closed at 01:36, closing time 50s, zigbee 42s) 04:06:00   Dome Parked Dome parked (parking time 42s), Az: 90.0 deg 04:06:42   Telescope Parked Telescope parked (parking time 34s total) 04:07:06   Telescope State Handbox reads 'Scope parked Turn scope off.' 04:08:03   Telescope Switched Off Telescope Power has been switched off via UPB Switch. 04:09:28   Services Stopped Night Services stopped 04:09:31 Session Finishing Session Finishing started (Create Fits Summary, Transfer Files) 04:09:53     Dome (Find Park) Find Park started (Search Az 88.0 to 92.0°, Step 0.2°, Narrow) 04:10:36     Dome Find Park found (Best Park Az 90.0°) 04:13:41   Dome Charging Dome is parked and well charged (96%, 15.0v) 04:13:43 Session Finished Session Finished

Session Alerts & Alarms

Time     Type       Name Detail 04:13:41 Yellow Alert Dome Charging Dome is parked and well charged (96%, 15.0v)

Back to Top

Operational Issues (2026-08-13 S1444)

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

[ Prev | Next ]

Critical Issues

• None

Major Issues

• None

Minor Issues

• Observatory Door Zigbee Sensor is again unreachable. Door Sensor was showing as 'Unreachable' in early August and showing a last seen date of 2026-07-31 07:51, with battery at 95%. Visit made to observatory sensor was re-added to deConz Network using the PhosCon app on 2026-10-10 (daytime) , but is again showing as unreachable during the S1444 Session. Although the sensor reconnected and for a while was showing as Open/Closed on 2026-08-10, it became unreachable again, and as of 2026-08-13 was showing as Last Seen/Last Updated 2026-08-10T13:54:04Z (14:54 BST). A new battery was added in May 2026, but came from a possible bad batch.  Alternatively the unit has failed, as happened with Bot Shutter Sensor in May 2026. A spare open/close sensor was installed as new "Observatory Door" sensor with id=27 on 2026-08-14 (see Fig 1) after which AstroMain 3.83.6 was modified to point to the new sensor id (27).
  Resolved 2026-08-14 (Zigbee Network, Observavtory Door Sensor, AstroMain 3.83.6)
   
• CloudSensor Clarity values from Eurotech CloudSensor were unexpectedly low during the session, causing a delayed session start and a number of session suspensions/dome closures. Clarity values (~ 25) in the first part of the session were close to acceptable sky condition thresholds despite the sky being visually devoid of cloud and having AllSky Star Counts of 24 to 36. The issue caused an initial delay in session start and then later on a number of session suspensions.  Nightime ambient temperatures (17°C) and sky temperature (+2 to +1 °C) were noted to be unusually high and likely caused the low clarity values. Clarity Trim of 2.0 was later entered in order to raise clarity values in AstroMain from 25 to 2, and prevent inapproriate session suspension / dome closures. CloudSensor to be checked for anything that might be partially covering or occluding the cloud sensor. Cloud Sensor values to be compared from values from hot spells during summer 2025. CloudSensor case was examined today (2026-08-14)) but there is no dirt or other surface issue with the sensor.  Daytime and nighttime Sky Temperature values over the course of the the last few days have been
    Date                       Daytime               Nighttime
                             Sky Temp (°C)         Sky Temp (°C)     
  2026-08-09                  11 to -11              5 to -10
  2026-08-10                   9 to -11             -6 to -14
  2026-08-11                  11 to -4              10 to 3
  2026-08-12                  12 to 2                3 to 13
  2026-08-13                  19 to 4                2 to 0
  2026-08-14                  17 to 0               10 to -9
  2026-08-15                  12 to -10              7 to -6
  A change in values seems to have occurred around 2026-08-11. It is unclear the general increase in Sky Temperature values (and lowering in Clarity values) relates to a seasonal / hot weather effect or to a developing issue with the CloudSensor system itself. Monitor over the next few days suggest it was a hot weather/hot atmosphere effect.  In clear sky conditions the SkyTemperature has returned to -10°C and Clarity has returned to 30. Issue is closed after review.
  Closed after review 2026-08-15 (Session, CloudSensor)
   
• AstroNorthCam StarCounts are unexplicably dropping from around 25-26 to 0 even though images appear visually similar (2026-08-14 23:25). NorthCam Star Count dropped from 26 stars at 23:24:30 to 0 star as 23:25:15 and thereafter.  This was anomously as the images from 23:20 to 23:24 are very similar to images from 23:25 to 23:30 .  Stars are visible in images from the entire period and backgrounds sky brightness and level of cloud cover is visually the same throughout. This is annoying as it impacts the quality of sky monitoring charts (such as the NightSummaryPlot6.jpg and Sky Summary Plots) and the use of NorthCam StarCount by AstroMain's ObsManager. Cloud only begins to cover the NorthCam View at around 23:37. AllSky Star Count only reduces to small numbers at 23:54.  The image at 23:24:30 was the last image to be copied to the session's 'Objects' folder.  Although images at 23:24:45 and 23:25:00 have star counts annotations of 25 and 26 , this is likely a 'delay' and they didn't actual contain any detected stars otherwise they would have been copied to the 'Objects' folder. After check log files, it is proposed to see if images from 23:24 to 23:26 can be retrospectively run through AstroNorthCam's Star Detection routines to try to establish what might be happening, and whether the issue can be resolved. Running the 23:25:15 image through the FindStarsInImage() routine from with Visual Studio showed that routine was returning 0 stars as the routine was failed with "Index was outside the bounds of the array" exception at the line 'With Box(iBox)' when iBox reached 2001 when Box was declared as 'Dim Box(2000) As TObjectBox'    Fixed in AstroNorthCam 1.10.5 by increasing the size of Box array to have the declaration 'Dim Box(10000) As TObjectBox'.
  Fixed  2026-08-16 (AstroNorthCam 1.10.5)

Small Defects

• A Spider EggSac is creating a image artefact / blotch on AllSky Camera images and South Sky Panoramas.  Spiders in the AllSky Camera hemispher have likely laid an eggsac or otherwise excreted on theh AllSky Camera lens producing an oval blotch of darker values in the SW direction  (see Fig 2).  Although spiders were cleared out and although an initial attempt was made to remove the 'blotch' from the lens it was not successful.  AllSky Camera lens to be cleaned with special attention to the SW direction. Lens cleaned again today (2026-08-14).
  Fix attempted  2026-08-14 (AllSky Camera)
   
• A series of false star detections is impacting the Observatory's NorthCam StarCount (2026-08-14). The Tapo NorthCam camera faces roighly due north and is used fro general sky monitoring and for recording images and videso of Aurora Activity (Northern Lights) and Norticulcent Cloud (NLC).  NorthCam images are also analysed in real time to provide a Star Count which supplement sky quality information from CloudSensor and AllSkyCamera which also has it own realtime StarCount.  False star detection impacts the quality and usefulness of the NorthCam StarCount.  On 2026-08-14 there were a series of false star detection at around 21:54, 21:56 to 22:00. 22:05, 22:00.  These false detections are generally associated with high contrasting cloud & background sky, particularly in low altitude areas close to the horizon.  The particular false-star detection causing pattern frequently occur is a semi-linear trend parallel to the horizon and numerous false detections (30-80) occur with a small region of sky.  False Star images need to be captured and used to update the neural net used by AstroNorthCam for confirming candidate stars. A separate continuous improvement ticket is raised to limit the number of probable false stars being added to the candidate star list from the same region of sky. A further continuous improvement ticket is raised to capture false star snapshots to enable more neural net training.  Fix implemented in AstroNorthCam 1.10.5 with introduction of new FilterClusters() function.
  Fixed  2026-08-16 (AstroNorthCam 1.10.5)
   
• Observatory Computer operations interrupted by Windows Update/Computer Restart (2026-08-17).  Whilst looking at observatory/shutter graphs on Observatory website at 2026-08-17 21:15 it was noticed that there had been no new graph lines from Observatory Computer (Shutter, ObsEnv) since 10:30 in the morning. Investigation showed that the Observatory Computer programs had been shutdown and the computer restarted following Windows Update (Security Update, Net Frame Security Update, Malicious Software Removal Tool).  Computer was logged into remotely and Observatory Programs including AstroMain and AstroPlan restarted. Outage was around 11 hours. .
  Resolved  2026-08-17 (Observatory Computer)
   
• AstroVma's GaiaImport routine is not gracefully ending but raises a WebException due to a TimeOut.  When try to retrieve Gaia properties for Groombridge Star A in order to create a GaiaDR3 Astrometric Model, the server was slow and led to a unhandled System.Net.WebException with message "The operation has timed out"  at  GaiaImport.FetchGaiaDR3 in GaiaImport.vb:line 35.  The exception was picked up by Visual Studio, and program continued, but would be crashed the program if running in production environment.  The exception should be caught and a "Timed Out" string written to the result text field Fixed in AstroTrigParallax 1.3.4. .
  Fixed  2026-08-23 (AstroVma 1.3.6)
   
• AstroVma's GaiaImport routine causes UI to be unresponsive whilst running.  'Get GaiaDR3 Params' buttons on the Astrometric Component form and the Astrometric Model form are used to pull data from the Gaia Database for the specified Gaia DR3 Source ID using the a “TAP ADQL synchronous query”  in FetchGaiaDR3() routine, where
   TAP = Table Access Protocol,  ADQL = Astronomical Data Query Language
  There can sometime be a long delay whilst query results are awaited and sometimes the operation times out.  Currently in AstroVma 1.3.5 the FetchGaiaDR3() runs on the UI Thread, and cause AstroVma UI to be unresponsive until the routine returns. The routine should be run Async to allow the UI to remain responsive.  Fixed
  Fixed  2026-08-23 (AstroVma 1.3.6)
   
• Bright light from KR Groups commerical site is illuminating the N and NW parts of the AllSky Camera images.  A bright security light pollutes the area, and since its installation has polluted the AllSky Camera view but has been largely mitigated by the installation of light occluding length of wood attached on the fence around 1.5 in front of the AllSky Camera.  A rook recently landed on the 'post' and has nudged its position enough to cause light from the Security Light to shine on the NW and N part of the AllSkyCamera hemisphere (see Fig 2).  It is necessary to adjust the light occluding post so that it fully blocks out security light from reaching the AllSky Camera. To implement .
  To fix  2026-08-14 (AllSky Camera)

Continuous Improvement

• Create a graph that cross-plots star distances modelled by GA vs those from Gaia. Observations of selected nearby stars (like Barnards Star, 61 Cyg and Ross 248) have been made over the last 20 years (2006 to 2026) and using this data '5 Param' models have been built that estimate Star Parallax and thus Star Distance.  It is proposed to cross-plot these distance estimates vs distance measurements based on GaiaDR3 Parallaxes in Excel using the Model based Parallax information for GA Best and GaiaDR3 are stored in the observatories Astrometry Database and presented in Distance (l.y.) format in AstroVMA.  Chart created in Excel 2026-08-14 (See Fig 3).
  Done  2026-08-14 (Excel, AstroVma, 1.1.3)
   
• Introduce Two-Star (Binary Star) Separation Graphs and related support.   For binary star systems with Star A and Star B astrometric data (like 61 Cyg A and 61 Cyg B) it is useful and appropriate to be able to create a graph showing Separation (in arcsec) vs time (where Separation could be Total Separation, Separation in RA or Separation in Dec) or Separation in Dec vs Separation in RA (in arcsec) . Requires modification/ extension to AstroMain and AstroVMA. Data plotting implemented in AstroMain 3.83.6.  Model plotting implemented in AstroMain 3.83.7. Separation Distances in AU, and Separation Vector plotting (NS vs EW) added in AstroMain 3.83.7 on 2026-08-16.
  Done 2026-08-15 (AstroMain 3.82.7, AstroVMA 1.1.4)
   
• Limit the number of likely false stars for being added to AstroNorthCam's Candidate Star List.  NorthCam images are also analysed in real time by AstroNorthCam to provide a Star Count which supplement sky quality information from CloudSensor and AllSkyCamera which also has it own realtime StarCount.  False star detection impacts the quality and usefulness of the NorthCam StarCount.  False detections are generally associated with high contrasting cloud & background sky, particularly in low altitude areas close to the horizon.  These  frequently occur is a semi linear trend parallel to the horizon and cause a clump of  false detections within a small region of sky, sometime amounting to 30-80, which can some time pass neural-net star checking, seriously impact the NorthCam SkyCount.  It is proposed that AstroNorthCam's find candidate star prevent mutliple candidates being added when they lie very close together.  This should be done either as the candidate star list is populated or as a following filtering process.  The process shouldn't affect the addition of 'real' star candidates, as the brighter stars are not typically clumped in images. Iimplemented in AstroNorthCam 1.10.5 with introduction of new FilterClusters() function.
  Done  2026-08-16 (AstroNorthCam 1.10.5)
   
• Add a 'Store' button to PageBuilder's GraphTab. Photometric and Astrometrics Charts are created from the graph tab of AstroMain's Page Builder . Graphs created from the PageBuilder Form are saved in the current target's 'Store' Folder. It would be convenient if there was a 'Store' button place on the same tab to quicky open up the store folder to check/access graphs created.   Functionality it would operate in an identical manner to the 'Store' button on AstroMain's ImageSets form (ie 'OpenStoreFolder(VM.ObjectName, 1)' . Implemented in AstroMain 3.83.7.
  Done 2026-08-17 (AstroMain 3.82.7)
   
• Modify AstroNorthCam's main image pipeline to move forward call to FindStarsInImage() and use the images own Star Count number in image annotation.  Currently in AstroNorthCam 1.10.6 and earlier versions the Star Count number posted on Main Images comes from analysis of the previous image or one prior to that and is therefore out of date by 15-30s. It is proposed to modify the acquistion/processing pipeline to call FIindStarsInImage() as the current image is being prepared in order to access and post the Star Count number that is associatated with the current image. This requires not only changes to the position of the call to FinStarsInImage, but also changes to how the Annotation Text is performed (moving it to a subroutine) and also how image bitmaps are created/ passed  to FindStarsInImage(). Implemented in AstroNorthCam 1.10.7, original call to FindStarsInImage() routine now relocated into CompileNighttimeImage() function.   NorthCam's 'Create Nighttime FrameBundle/Images' section modified to send Star Count to AstroAllSky at an earlier point, objConsole's UpdatePictureBoxes() routine modified to pass an extra parameter (bUpdateMain picture box). FindStarsInImage() routine modified to pass FrameDate_Local and SunAlt. The drawing of Image Title annotation handled by new DrawNorthCamImageTitle() routine.
  Done   2026-08-17 (AstroNorthCam 1.10.7)
   
• Add support for calculation and graphing of positional angle (PA) between the components of binary star system.  AstroVMA and AstroMain have been recently extended to included support for calculation and graphing of separation, separation_EW and separation_NS.  It is proposed to extend functional to include calculation and graphing of positional angle (PA) in degrees.  Implemented in AstroVMA 1.1.5 and AstroMain 3.83.8 with new axis type 'PositionalAngle'.
  Done 2026-08-19 (AstroVMA 1.1.5 , AstroMain 3.83.8)
   
• Modify PageBuilder's 'Get Transient Info' routine 'GetTnsInfo()' to wrap remarks text to limit line length to 95 chars. Remarks string scapped from TNS Discovery Report by 'ExtractTnsFields() routine can sometimes be a long string, which results in wide table width/text field when Session's Image page is viewed in a browser.  Line breaks can be manually inserted in PageBuilder's 'txtTransientInfo' field but this annoying step which has to be repeated for each session that images the specific transient target involved.  It is proposed to modify GetTnsInfo() to include a call to a new function WrapTnsText() to wrap the remark text to a maximum line length of 95 characters. Implemented in AstroMain 3.83.8.
  Done 2026-08-19 (AstroMain 3.82.8)
   
• Modify AstroNorthCam's FindStarsInImage() to require a high confidence threshold in lower zone of sky. Currently in AstroNorthCam 1.10.7 and earlier version the StarConfidenceThreshold (typically set to 45) is used across the whole sky area.  The lower part of the sky is prone to false star detections due to high contrast cloud edges in some sky conditions.  Why FilterClusters() coding has been added to reduce the number of closely spaced detections and there is a plan to improve neural-net training  for NN-star evaluation, a solution needs to be adopted now for this problem. It is proposed to add functionality to the FindStarsInImage() routine to reduce the number of these false star detections by adding a text box to define the y coordinate for the top of the lower zone and modifying the condition for a valid star to be
  If (y < StarDetectionLowerZoneY And StarConfidence > StarConfidenceThreshold) Or ' added LowerZone conditon 2026-08-20 (CI S1444) StarConfidence > StarConfidenceThreshold + 12.5 Then
  The Y value for top of lower is typically set to 400, and in this lower zone the effective confidence threshold is 57.5 (45 + 12.5) Implemented in AstroNorthCam 1.10.8 (v2) on 2026-06-20.
  Done   2026-08-20 (AstroNorthCam 1.10.8)
   
• Create an adjunct to AstroNorthCam to more easily find and view associated NorthCam images.  AstroNorthCam produces a variety of NorthCam image products : Normal views, Daytime Objects, Daytime Object Pics, Nighttime Objects (stars), Metaframe Min/Max/Var/..., Videos.  Located in different folders which are diffficult to traverse and cojoin/view images from different folders. It is proposed to create a NorthCam image viewer to fill a definite gap and thereby maximise the information in NorthCam image suite and minimize existing frustrations.  A working implementation of a new 'Multi-Channel Frame Viewer' tool was added in AstroNorthCam 1.11 on 2026-08-21. Each of the 4 picture boxes represents a user specifed channel.   The time point for the frames shown can be changed using Prev/Next buttons, left/right arrow keys or by scrolling a cursor on day or night keogram shown at top of the window. Different sessions can be selected. Separate tickets have been raised for additional features (PopUpView Window and Frame Stepping Navigation).  A new option was added on 2026-08-23 to display images with gamma correction.
  Done  2026-08-21 (AstroNorthCam 1.11)
   
• Introduce a new Single Image window type to AstroNorthCam that shows the full-size view of one of 4 channel images shown on the Multi-Channel Frame Viewer.  A new tool (Multi-Channel Frame Viewer) was introduced in AstroNorthCam 1.11 which shows on one expanded window up to 4 frames from different image type or channels that represent are from a common or related time point.  These are shown in picture boxes of width 600 px.  These are smaller than the natural resolution of the image frames, which is 1080px for NorthCam frames and varying size for AllSky Images (FIshEye View and Panorama views).  It is proposed to add new functionally to bring up one of the 4 images from the ImageViewer window in a new window with the image shown at full size. Implemented in AstroNorthCam 1.11.1 A new window (of type frmViewerPopup) is instigated by double clicking on one of the 4 images, and the image is shown at full size.  The frame shown advances (or retreats) in line with the image shown on the CompositeViewer window, and also responds to left/right arrow key presss.
  Done  2026-08-22 (AstroNorthCam 1.11.1)
   
• Extend AstroNorthCam's new 'Multi-Channel Frame Viewer' to include Frame Stepping.  A new tool (Multi-Channel Frame Viewer) was introduced in AstroNorthCam 1.11 which shows on one expanded window up to 4 frames from different image type or channels that represent are from a common or related time point.  Currently frames are stepped through based on a specified time increment (15s, 30s, 1m, 5n, 10m, 20m, 60m).   It is proposed to extended feature to include stepping through frames, by frame number for a specific channel. To be added in AstroNorthCam 1.11.1 A new window (of type frmViewerPopup) is instigated by double clicking on one of the 4 images, and the image is shown at full size.  The frame shown advances (or retreats) in line with the image shown on the CompositeViewer window, and also responds to left/right arrow key presss.
  Done  2026-08-23 (AstroNorthCam 1.11.1)
   
• Modify AstroPlan's Target Form to show number of sessions that target has completed set of observations.  The Target Form's History tab in AstroPlan 1.47 shows a list of the sessions where observations of the target object have been completed.  It would be useful to show a count of the number of Observation Sets that have been completed (and not rejected) and the number partially completed. There was a recent need to know the number of observations sets made for each star /star system in the Nearby Stars Project.  To be implemented in AstroPlan 1.47.1.
  Done  2026-08-23  (AstroPlan 1.47.1)
   
• Hide 'Get GaiaDR3 Params' button on Astrometric Model form if Model Family is not 'GaiaDR3'. The use of 'Get GaiaDR3 Params' button will overwrite any existing param data.  This could cause the loss of existing GA based param data if the currently selected model belongs to the 'GA Best' model family.  It is proposed to restrict the visibility and potential use of the button to avoid such an issue. Implemented in AstroVma 1.1.6.
  Done  2026-08-23 (AstroVma, 1.1.6)
   
• Modify AstroPlan's Target Form to show number of sessions that target has completed set of observations.  The Target Form's History tab in AstroPlan 1.47 shows a list of the sessions where observations of the target object have been completed.  It would be useful to show a count of the number of Observation Sets that have been completed (and not rejected) and the number partially completed. There was a recent need to know the number of observations sets made for each star /star system in the Nearby Stars Project.  To be implemented in AstroPlan 1.47.1.
  Done  2026-08-23  2026-08-23 (AstroPlan 1.47.1)
   
• Carry out an analysis of Perseid meteor numbers from NorthCam images acquired on 2026-08-13 (session S1444). AstroNorthCam's Metaframe Max frames from the clear night on 2026-08-13 are noted to record mutiple meteor traces.. Each frame covers a 10 minute interval. It is proposed to create a web page 'images-2026-08-13_meteors.htm' with some of the Metaframe images from the night and make a graph of meteor count vs time.  To do .
  To do  2026-08-25 (Website)
   
• Capture more NorthCam False-Star snapshots and update neural net training.  False star detections are impact the NorthCam StarCount numbers. In the evening of 2026-08-14, the number of individual false star detections (30-80) were at time outweighed the number of real star detections (15-26). Whilst the number of false-stars entering the candidate star list can be reduced by new code to prevent clumped candidates, AstroNorthCam's neural net for distinguishing real star needs to be retrained with more 'false star' examples.  To do this more False Star image snapshots need to be captured.  This may required turning on an existing option in the program and adding a new option to do this. Checking the program shows that there is a 'Save Star Pics To File' checkbox on the 'Objects' tab. To implement in AstroNorthCam 1.10.5
  To do  2026-08-16 (AstroNorthCam)
   
• Make a review of the benefits or otherwise of replacing the Observatory's existing Eurotech CloudSensor with a Lunatico AAG CloudWatcher Cloud Detector.  To do .
  To do  2026-08-20 (Observatory Protection)
   
• Perform Photometric Reanalysis of image sets taken of KIC 8462852 (Tabby's Star).  Tabby's Star has made the new recently due to the discovery in older data of a large exoplanet transit in Sep 2019, reported to be around 9 times mass of Jupiter and 1.7 times diameter of Jupiter.   Object interpreted to be planet rather than a brown star, and is is consider likely to be responsible for disrupting comets and asteroids leading to frequent but irregular dimming of the light for the star due to dust.  Images of Tabby's Star have been taken since 2020, and whilst some of the images have been analysed by quicklook photometry, it is proposed to go back and reanalyse the entire suite of images and plot the data in AstroMain's new photometric graph plotting tool.. Aliases: KIC 8462852, 000-BLS-628, Tabby's Star, Boyajian's Star, GSC 3162:665, TYC 3162-665-1 ,  Comparison Star:   Check Star
  To do  2026-08-25 (Photometry, AstroMain, AstroVma)
   
• Reorganise TapoCam file structure to make it more atomic with session folders for each night date. Currently as at 2026-08-24 Session folders (such as "2026-08-23") are held in separate locations for different images types : 'Main' frames in ./Sessions,  'Stars' frames in ./Stars,   'Objects' in ./Objects,  "Metaframe" frames in ./Metaframe/Sessions.  It is proposed that there shall be a single Session folder for each Night Date,  contain subfolders for ./Main, ./Stars, ./Objects, ./Metaframe.  This is a more consistent atomic structure, permitting for direct deletion of an entire session after so many days (currently 14 days) or archiving of an entire session folder.  The change involves multi-changes within AstroNorthCam (including file saving, file reading, video creation, session deletion, Multi-Channel Frame Viewing), plus some minor change to AstroMove.  Existing folders/file need to be migrated into new structure. The switch over in TapoCam structure shall be made aftre careful planning during a time when AstroNorthCam's code base is stable, upon entry to the refactoring process. To implement in AstroNorthCam 1.12. AstroMove 1.19
  To do  2026-08-28 (AstroNorthCam 1.12, AstroMove 1.19)
   
• Add facility and new folder structure to allow AstroNorthCam's Single Pane Viewer to save an NorthCam image to a gallery folder and option copy it to Store folder and to web folder / images.  AstroNorthCam is currently setup to auto-delete session folders & files after 14 days.  It would be useful if particularly interesting images could be saved to a galley folder, potential organised by type: eg clouds, sunsets, stars, aurora, meteors, birds, night objects etc.  To implement in AstroNorthCam 1.12.  It is proposed to enable this via a button on the new SingleFrameViewer form.
  To do  2026-08-28 (AstroNorthCam)
   
• Extend AstroTrigParallax to support modelling of binary star orbits from astrometric observations. 61 Cyg A/B is a system that has been observed for some 20 years, and has a good dataset from which Parallax and Proper Motion have been modelled and compares well with models from GaiaDR3.  From this dataset graphs have been produced showing the slow but changing separation between the A and B stars.  The orbital period is evidentally long some 670 years based on online sources. It is proposed to perform modelling to identify the range and likely period of the two stars based on my own observations. Thils will involve the creation of new GA modelling tool in AstroTrigParallax, with likely additional of a new BinaryStarModel table in Astrometric Database and UI support from AstroVMA. It is not proposed to begin this in immediate future, and therefore the ticket item is placed on hold for the time being.
  On Hold  2027-01-01 (AstroTrigParallax, AstroVMA, AstroMain)
   
• Examine whether it is feasible to include a set of NorthCam images into a 'adhoc' section in Session Images web page buil by AstroMain's Page Builder.  The AstroMain's image builder and page builder tools are built around building a web section for Image Set subfolder held in an Observing Session folder, where source files are .FIT files.  During the S1444 session  (2026-08-13), NorthCam Metaframe_Max frames were noted to show reasonably large numbers of meteors.  Images of these might Ideally be added  as a special section to the 'images-2026-08-13.htm' web page built in AstroMain, without a way of doing this using PageBuilder, it was necessary to manually create/build a custom page 'images-2026-08-13_meteors.htm' . It is proposed to review how a custom section can be included with PageBuilder ttool to handle this kind of situation.
  To do  2026-08-25 (AstroMain)
   

[ Prev | Next ]

Back to Top Issue,  Back to Top

[ Prev | Next ]

Back to Top Issue,  Back to Top