hi Doug,
the most flexible approach would be to allow the user to add custom fields to AD database: name of the field, type, format could be a minimum set. And then choose the source for these data, like CSV file, json, xml or even direct connection to a server. Filtering, sorting and plotting these data would be then straightforward.
It requires some restructuring of the code but it will be a nice improvement that will allow AD to be a single point of information for image metadata.

As of now I'm following another similar request by a github user (Rick) that suggested to import PHD2 guiding data through its log. It will allow to correlate guiding performance vs eccentricity or Alt/Az etc.
I'm not a PHD2 user so it's quite difficult to test. For example I'm not able to recreate the RMS calculation to have the same result as PHDLogViewer. Seemed to be easy but it's not.

A note about the filename as identifier key: names could change, files could be moved and different images could have the same file name. I chose a different approach that prevents these issues: hashing the file itself (a part of it, for performance reason). But for our understanding saying that file name is a key it is ok, I was just more specific because you're quite into the software details.

ferrante

Read More...