Add guiding quality as a file name option

Another feature request I would really love - having guide quality as a file name option something like if you select %gq you get a value from great to bad returned based upon the worst guding during the imaging. So it could either return a numeric value - like the maximum correction for PHD (e.g. likely from 0.01 to 5.00) or it could use a descriptor based upon a maximum corrector range - such as:

Under 0.2 = Brilliant
Under 0.5 = Excellent
Under 0.7 = Great
Under 1.0 = Very Good
Under 1.5 = Reasonable
Under 2.0 = Workable
Under 3.0 = Bad
Over 3.0 = Terrible

Many thanks for your consideration,

Matthew

Hi all,

Just wondering if this idea might be doable in the near future :slight_smile:
Thanks,

Matthew

I’m not sure about this one. It seems like a relative / subjective measure to map to textual names. We might consider adding guiding quality as a numerical value though and you could draw your own conclusions as to what that number means to you.

1 Like

Hi Ken,

Many thanks - if you make it a user configurable table - that assigns how good the guiding is - I can generally use that as a glance to do my first poor frames exclusions.

My Seeing/ image scale is about 0.86 arc sec / pixel - so if quiding stays under 0.75 arc seconds that is generally tolerable for 5 minute subs. If it goes above 1-2 arc seconds variance I generally discard the frame. Something that encodes how much drift occured into the file name means I get “truth at a glance” of the likelihood I can use a frame (guide quallity, HFR and number of stars is basically the trifecta of meta data I wish in a file name to give me a first pass accept or reject a frame.

I also use the thumbs up or down a far bit and love it - but if I am remote imaging for hours and away from the control keyboard - I like to be able to get a strong hint as to which frames worked well and which are oopsies.

Then all I need is something that tells me if cloud cover impacted my shots - but I generally use PixInsights sub frame selector process - looking at number and size of stars and eccentricity and medians as hints for which to reject. Something that said 1/3 of the frame got blurred by clouds would be a godsend if I can figure out how to recognise that (which PI or ASTAP may already to as I research it further)

Many thanks,

Matthew