Calibration and align batch operations

[Harry page]

Hi

I get this error 

PI calibrates the files and saves them ( good so far ) but falls over at the registration 

Harry

[Harry page]

Hi

Bit closer

Harry

[Harry page]

Hi

This is very very close 

Can we make the script remember the last setting when closed i.e what files were selected , better than starting from scratch when redoing the same files

Harry

[georg.viehoever]

Harry, create a process instance (blue triangle) to save the settings.
Georg

[Harry page]

Hi

Yes I did see this  , perhapes a personal thing I like simple to reuse not a game killer though

Harry

[Juan Conejero]

Hi,

Here is version 0.2 of the Batch Preprocessing script. News:

* Added preliminary support for CFA mosaiced images. OSC camera users should have no problems to calibrate and align their images with the script as it is now. DSLR camera users still need to convert their camera raw frames (CR2, NEF, etc.) into FITS files with the standard BatchFormatConversion script before using Batch Preprocessing. Only bias and dark frames need to be converted; flat and light frames will work in their original camera format without problems. These limitations should be removed in the next versions of the script.

* Added new GUI controls to implement CFA support.

* A new check box to enable/disable dark frame optimization (applied to calibration of flat and light frames).

* Published under PCL v1.0 license.

Please test it and report any errors here. Enjoy!

[vicent_peris]

Hi,

Could it be possible to add a crop option to this script? Sometimes it's better to crop the borders of the image just after the calibration process. For instance, if you use an overscan enabled camera, the overscan areas can be extremely noisy after calibration. This can affect the registration and integration process.


Regards,
Vicent.

[mmirot]

I found no defects using add images as long as I started with a dark frame set of the same exposure.
The script created a usable dark master that worked subsequent operations. Other Master are fine too.

Wow...Lots of nice improvements.!

Calibration goes 3x faster without the cache for integration too. Can that work with registration?

I tried to use a single long dark frame selected with optimize checked but the calibration results were incorrect.
 I usually use a set of equal exposure darks so perhaps I am not doing this correctly?

Max

[mmirot]

I would add cosmetic correction to the wish list.
I have annoying hot column.  It would be nice to fix it prior to registration and integration.

Max

[georg.viehoever]

...Yes I did see this  , perhapes a personal thing I like simple to reuse not a game killer though

I agree: the way, for instance,the AnnotationScript keeps the settings from a previous run is also very convenient. Maybe having both would combine the best from both worlds...
Georg

[mmirot]

A prior version preserved both settings and paths . Juan will add this soon ... Trust me


Max

[kwiechen]

Hi Juan,

looks great! It would have lasted a very very long time for me to bring this into a comparable state with tight integration into the PI system.

I have played a little bit with v0.1.

1) The script needs all file slots to be filled and a reference image selected. It should be possible to run the script with calibration frames only

2) The reference image was selectable simply by clicking in the file list in 007h

3) Checking of the masterframe checkboxes select only the first frame in the list as a master. The script fails therefore to calibrate and align with predefined masters (for example with 4 channels LRGB).

I will test v02 with 'fresh' data as soon as possible.

Best,

Kai

[Harry page]

Hi

A save masters check box would be good , to save any newley created master bias / darks / flats for future use 

Harry

[Juan Conejero]

Hi Kai,

Glad you like it.

1) The script needs all file slots to be filled and a reference image selected. It should be possible to run the script with calibration frames only

The script requires you to specify a registration reference image only if the 'Calibrate only' checkbox is unchecked. If you check it, then no registration reference is (should be) required.

By 'all file slots filled' what do you mean besides the reference image?

2) The reference image was selectable simply by clicking in the file list in 007h

It is selectable in 0.1, too, by double clicking one of the light frames. A single click is too prone to mistakes IMO, and we probably will implement more functionality associated with clicking frame items on the treebox structures.

3) Checking of the masterframe checkboxes select only the first frame in the list as a master. The script fails therefore to calibrate and align with predefined masters (for example with 4 channels LRGB).

If the L, R, G and B images have the correct filter identified in their FITS headers, there should be no problem. Can you verify this?.

Of course we have to improve master frame management. How about an option to manually specify a filter for each frame? In this way we'd remove another FITS header dependence, and the script would be more flexible.

I will test v02 with 'fresh' data as soon as possible.

Great. We need lots of tests with different data samples to make this script 100% robust.

[Juan Conejero]

A save masters check box would be good , to save any newley created master bias / darks / flats for future use

Masters are generated during script execution and stored on the 'master' subdirectory of the root output directory.