Jack, Max,
thank you for this contribution and feedback!
@Jack: can I integrate this nice doc into the help label of the next script version?
@Max: I have sorted the wish list a little bit:
1. Persistent setting and paths. They should remain the same next time script is run
< I will try to add this to the next version.
2. Single image or an image named master in fits key word automatically identified as a master. No need to check use master
<There should be no problem to add a new custom keyword MASTERFRAME or something like this with a corresponding value and reuse these files automatically.
3 Images that don't contain the key words. Most of us use MaxIm and other programs that contain the standard Fits key words for time, bin, and filter. However, there will be a few with the odd acquistion program that does not put these in.
<For older data not containing the fits header keywords, I would prefer to extend the small BatchConvertImagetype script to set all keywords necessary to be handled by the CalibrateAlign
script.
4 Handle color camera images.
<I have never used PI to process OSC/DSLR data. Can you please give me some details regarding the difference when calibrating/integrating OSC images compared to monochrome data? Is it necessary to debayer/split these images into different channels before? If we have
DSLR images how can I get for example the exposure time? To handle images from color cameras I can provide a mode ignoring image metadata (binning is meaningless from my point of view,
filter information can be taken from the debayer pattern)
5 Dark flat option or scaling darks for longer duration flats.
<Dark frame scaling is already set by default in this script. The dark flats can be added to the dark tab and will be used.
6 Add integration. Unselect align or integration processes when desired too
<I can try to add this - the integration control is separated in the script code and it may be possible to add this dynamically for all filter settings to the Light tab.
This was removed from the initial version because I thought about using different sets of integration parameters for well sampled L data and more or less poorly sampled RGB data.
<But I am not convinced that this is a good solution. This excellent document (Jordi Gallego, Image integration techniques: Increasing SNR and outlier rejection with PixInsight, slides for a
presentation given at the VI Seminario de Astrofotografía de Cielo Profundo, Madrid, November 20th, 2010.) shows the importance of fine-tuning integration parameters
7: Add cosmetic correction module to script. It can be helpful to remove fixed hot columns and pixels after calibration.
I need less sigma rejection when I do this for my hot columns.
<The CosmeticCorrection module is not installed in the last version of PI (Windows 7, x64), so I can not test this.
8. Deselect individual fits files from list in addition to clear all
9. Select the reference image from the image list , double click or default to first file ( easier than set path)
<Points 8 and 9 will require some rewrite of the internal structure. The TreeBox is only updated to provide visual feedback to the user in the current state of the script.
10. I use a rotator so matching the fits key rotator ' xxx.xx ' position in degrees between flats and lights would be vary helpful. ( in addition to filter)
<Is there a 'standard' to handle this? And here I will need some test data.
Best,
Kai
