SubframeSelector does not preserve PCL (and other useful) properties

[johnpane]

The DeBayer process writes PCL:CFASourceFilePath, which is later used by DrizzleIntegration to find the CFA file to perform a CFA drizzle.

      PCL:CFASourceFilePath     
         owner                    Core
         type                     String
         attributes               wr-pst-
         value                    /Users/pane/NOT BACKED UP/2017-10-18 ic1396/JFP_9305_c.xisf

However, if the debayered images are run through SubframeSelector, writing the "accepted" images with weights keywords, the PCL properties are not preserved. As a result, DrizzleIntegration does not find the CFA file and drizzles the debayered version of the file (i.e., it is not performing a CFA drizzle).

It also drops other properties that would be useful to carry through, such as Instrument and Observation.

[johnpane]

I see that SubframeSelector has been rewritten as a process module and has code to preserve the properties.

[johnpane]

I compiled and installed the new SubframeSelector process module and indeed, it preserves the properties.

The next step, StarAlignment copies the critical CFA source information into the .xdrz files, so CFA drizzle now works.

But, StarAlignment does not propagate the properties in the .xisf file. It would be useful for the Instrument and Observation properties to be carried all the way through the workflow,or, at least to the point of integration. At integration, the question is what to save given these properties might differ for every subframe.

[acmalko]

I see that SubframeSelector has been rewritten as a process module and has code to preserve the properties.

Hi,
has this process module been published ?

[pfile]

not officially but in the thread about it (you can search) there are links to binaries for windows and osx.

rob

[acmalko]

Found !
https://pixinsight.com/forum/index.php?topic=11780.0