I guess I'm looking for a fast and easy way inside of PixInsight to be able to tell the temperature and exposure length of the images. When I start my projects they may span over the course of the year. I use ACP Expert which allows me to add targets and imaging specifications such as when to image (moon presence), hours before and after Meridian crossing, minimum altitude, and so on. I decide on length of exposure, number of exposures to take, filters, and so on. To fulfill these requirements it may takes months or longer to complete these tasks depending on weather, other targets and their priorities. Experts looks at start the listed targets and decides on the most opportune and then does a series, defined by time by you, and then looks at the list again. It may continue with this target or move to another one that has become better for the time and conditions. It's all based on your priorities assigned to each target. The idea s to image the best targets at the best time, usually when it's high and near the Meridian. But again the constraints you use determine all this. So long story short, completing any given target can take a long period of time spanning many months. Which means that imaging conditions such as outside temperature may change dramatically which will change the dark frames you'll need to use to calibrate. You may also be taking images with high dynamics that require multiple length exposures to display properly. One such target might be M42. You may have 10 min, 5 min, and 1 min exposure in order to bring out the Trapezium area. Point is what I'd like to be able to do without having to open each image and open the FITS Header is be able to see the exposure time and temperature display in processes like Image Calibration where it makes a big difference. I can open and cull them using another program but that just adds more work that might be easily solved in PI. Maybe allow the user to adjust what image properties are displayed in Image Calibration.
Is this possible without causing a great deal of trouble? Just some thoughts as I process images for IC405 that was started back in March of 2015 and am currently adding additional data to complete.
Thanks,
Steve
