Mark frame as BAD
Issue #150
closed
As in SGP or BYEOS, mark a frame as bad.
Currently, if a user sees a poor exposure (ruined by clouds or a gust of wind for example), they will manually delete the file from File Explorer (which can be error prone), or include it in their final stack (Subframe Selector is particularly bad with that as it tends to show a higher SNR ratio for frames with clouds in them).
Marking a file as bad would remove that uncertainty, e.g. either delete, or like SGP does, rename the file, prenaming it with BAD.
As NINA has a file history (with HFR if enabled), this could likely be done from there, interface-wise.
Comments (4)
-
-
Right clicking frames in the history and marking them as bad would be a good addition. Automatic rejection is not a good idea because it requires more configuration (RMS threshold).
Behaviour should simply be to rename the file with BAD_%PREVFILENAME% and displaying a red X over the preview image.
It should also work the other way round. Nothing wrong with marking bad frames after the imaging session.
-
repo owner
Issue
#213was marked as a duplicate of this issue. -
repo owner
- changed status to closed
this should be done in post processing. all these post processing tools offer great utility to automate this process of detecting bad images
- Log in to comment
If a user is concerned, they can save the files with the HFR recorded in the name and delete ones that are outside a determined limit at any stage using regular file management. Another option would be to set acceptable HFR boundary values, and NINA can auto-reject (which can mean delete or rename the file) exposures that fall outside of those bounds.
The latter is more in keeping with the spirit of NINA, which is automation of as much as possible. It would in my opinion be counter this spirit to introduce a feature that would require the user to be present to actuate during the course of a running sequence.