Calibration and align batch operations

[Harry page]

Hi

The dark has used bzero note , I think this is causing the problem over the bias which is not 

Harry

[Harry page]

Hi

One for you to look at PI will open the same  file diffentley if the fits option "signed integer" option is checked or unchecked even if there is no Bzero in the fits header


Harry

[ian straton]

Hi, I'm new to PI so might need a bit of hand holding here, I tried using this script to calibrate and register some images I took recently however having loaded the file lists and hit run I got the following error message: "<file path> The DSLR_RAW format cannot perform incremental file read operations."  and the script failed.

I am using a canon 550d which outputs the cr2 RAW format.

Its not clear to me whether this is a bug in the script or whether I have to convert my RAW files to another format before using this script?

[georg.viehoever]

Ian, make sure you have the latest updates.

[ian straton]

huh, PI updated itself earlier today but I just checked manually and there were two more updates available, installed those, restarted PI and now the script works! yay!

[troypiggo]

I'm having trouble with this latest version.  I took a bunch of lights, flats, and biases last night.  Already had a dark library.  All images taken with Maxim.  Ran Batch Preprocessing before I went to bed.  When I woke up there was an error, and was getting the little B&W pizza wheel in OSX PI so couldn't save the history.  Had to quit PI.

Started PI up again.  The bias, dark, and flat masters had been created successfully by the looks.  But the first calibration of light frames looks like where it failed.  Tried running Batch PP again using the masters this time.  Failed again with the attached error messages.

[troypiggo]

Sorry to followup my own post.  Maxim has added parenthesis in the filename.  I think that may have something to do it.  I have a lot of files to rename, but will see if that fixes it.

Edit: Yep, renaming the files worked.  Sorry for the detraction.

[kwiechen]

Hi,

I have been using this script and its predesessors for a while to calibrate and align the frames from my mono CCD. Compared to the routines in MaximDL, I used before, PIs tools gave much better results using the default settings in terms of noise and accuracy of alignment (no more colored and misaligned stars). The script was primarily written to reduce the time for preprocessing with PI.

Now I have tested Juan's wunderful integration and additions to use OSC and DSLR data. The script works without any problems and the final integration gives again much better results compared to DSS (chrominance noise, artefacts and outlier rejection) when using simply default settings. Thank you very much to Alejandro Tombolini for the DSLR test data - it was really a pleasure to work with it.

Best,

Kai

[cornyyy]

Hi Kai, Vicent and Juan,

thanks for your help. I think i figured out the problem with the orange-blue color.

If i use the skript in total and doing the integration in final i´ll get this freaky colors.
If I check the calibrate only button, doing the debayering as next and finally the registration i´ll get normal collors. So I think the problem should be solved when changing the steps of debayer first and alignment as the second step?

Cheers Cornel

[Harry page]

Hi

CCD stack, maxim and Astroart can calibrate my light with these frames , so Pi is not getting the correct information out of my Images , Why I leave to you 

Regards Harry

[georg.viehoever]

Version 0.4a attached....

This update is still working very nicely for me. Dont know what happens to Harry and some others. My wishlist:
- same as in http://pixinsight.com/forum/index.php?topic=3654.msg28079#msg28079
- the calibrated files contain FITS keywords generated from RAW, such as DATE-OBS, EXP-TIME. They are lost in the debayered files. I would like to see them transported to the debayered images (should be a property of the debayer process).
- I see the BITPIX value is "-32". Is this intentional?
Georg

[Juan Conejero]

IMPORTANT NOTE: This version of the Batch Preprocessing script does not work with the current core version (1.7.5.779) due to a bug. Please use version 0.4a of the script until we release a new version of the PixInsight Core application (tomorrow). The latest versions of the FITS and Debayer modules will also work with version 0.4a of the script.

New version 0.5 attached:

* Improved diagnostic messages.

* Added a FITS orientation option. The script preserves now the original orientation of most images by default.

* Several minor bug fixes.

Related updates:

* With the latest version of the FITS format module, the Batch Preprocessing script should be compatible with signed integer calibration frames generated by some camera control applications (i.e., Harry's data set works with this version of the script).

* The latest version of the Debayer tool preserves all existing FITS header keywords and adds a few COMMENT and HISTORY keywords with information on the applied mosaic pattern and debayering algorithm.

Hope you like it.

[georg.viehoever]

When trying to use the latest version (0.5, all updates applied), I got a message about something wrong with FITS when the console displayed
"Writing master bias frame:
C:/Users/Public/Pictures/Astro/2011_03_08_orion_85mm/fits/master/bias-BINNING_1.fit"
On a second run it worked...

I like the blue triangle!

Georg

[Juan Conejero]

Hi Georg,

Is this error something I have to worry about, or just a sporadic error? Have you seen a similar problem again?

[georg.viehoever]

Yes, I am afraid  it is reproducible. Restarted fresh PI, did the run again. Error dialog is "FITS: Invalid Image Identifier".
Georg