'Max HFR' After Auto-Focus Monitor

Issue #854 closed
Jim Waters created an issue

If for any reason the reported HFR is above a ‘user defined value’ after an auto-focus, NINA will wait a ‘predetermined time defined by the user’ in minutes and try again. During this time the pending imaging sub will be postponed. After a ‘predetermined number defined by the user’ loops if the HFR doesn’t fall below the threshold value the active sequence will abort and a warning will be displayed.

At times the seeing goes bad and its pointless to continue imaging. This also protects the user from problems that may occur during an auto-focus session. I consider this ‘Hardening of the NINA’ code and process flow.

Comments (5)

  1. Stefan B repo owner

    Having a max HFR is not a good metric as this will change with sky conditions and equipment. A better quality control is added using the R2 coefficient in 1.11

  2. Jim Waters reporter

    I don’t agree Stefan. The ability to monitor the HFR and decide what to do is an ‘optional’ user feature. Yes - the HFR is somewhat dependent on star density and mainly sky conditions. There's a point at which I no longer what to image and I want the ability to decide what to do - stop imaging, retry or wait. I don’t want to continue imaging when things go to hell. Many times the HFR has creped up to the point where its below the ‘After HFR Increase’ % amount between subs or between AF runs and the subs aren’t usable. I have seen my HFR increase from ~2.5 up to beyond 4.5 and not trigger 'After HFR Increase' - this was on a much earlier NB release. I have deleted many subs because of this. IMO this will be a valuable addition to NINA and should be reconsidered.

    ghilios is considering my request.

  3. Log in to comment