Calibration and align batch operations

[robhawleyastro]

How do you handle dark flats currently?

[kwiechen]

Hi,

@Alejandro: thank you very much for your example data - download was OK. I will need some time trying to update the script. In its current state image metadata is read from the FITS header when the files are added and subsequently grouped. I have removed all other dependencies to read FITS header data of individual files in other parts of the script. So it should be possible to add the data needed (exposure time, image type) using a new dialog window.

@robhawleyastro: dark frame scaling is on by default - I use short exposed dark frames as flat darks. Simply add these and they will be processed.

 Kai

[Josh Lake]

I'm so excited to give this script a try, but I'm still stuck at square zero with getting it to work on my Mac. I've tried both the 32 bit and 64 bit installs and still get errors like this when trying to load any image:

*** Error [222]: /Users/itech/Documents/ Astronomy/PIScripts/CalibrateAlign-007g/CalibrateAlign-engine.js, line 89: TypeError: FrameType[group.Imagetype] is undefined

Do I need some kind of Developer's kit loaded? I know it *can* work on Macs because Jack Harvey is getting it to work... I'm willing to try anything.

[kwiechen]

Please see my previous comment to 0.0.7h

Again, the script needs FITS files from monochrome CCDs with keywords/values in the header to work (IMAGETYP, XBINNING, FILTER, EXPTIME). To get this to work with other files (OSC, DSLR, files without header info) I will need complete example data. If there are any problems please provide me with the camera type, info about software for data aquisition and example data.

Kai

[kwiechen]

@jlake: I have just tested FITS files from other sources. In some cases the IMAGETYP keyword is not present in the header leading to the error above. If other keywords are present it may help to add IMAGETYP/value using the BatchConvertImagetype script posted previously in this thread. However the latest script 0.0.7h will only work with FITS files from mono CCDs.

Best,

Kai

[robhawleyastro]

I do most of my work in narrowband and thus have very little signal.  Would it be possible to have the scripts work in 64-bit? 

Before I start a long discussion on the merits of 64 bit -> I am not sure it will improve the result, but I am sure it will only cost time (not that much) and disk space.

[mmirot]

I have been running it in 64 bit windows. Works fine.

Max

[robhawleyastro]

No I mean could there be a way to use 64 bit math.

I also use the 64 bit version of Pixi exclusively

[robhawleyastro]

The terminology used in Image Calibration is "sample format= 64 bit" and in Integration "generate 64 bit result"

[mmirot]

Rob

64 bit rarely offers any advantage.  Your are actually just filling up your drive and taking much longer to process images.  If you are going to use a 64bit images wait until the integration step. The extra precison is totally unnecessary until this point unless you have a camera able to produce data at 64 bits. Not likely:)

I suggest you post a new thread on this in another forum.

Juan's comments should be informative

Max

[Juan Conejero]

64 bit rarely offers any advantage.

Absolutely. A 64-bit format is only necessary in the context of very large HDR compositions. Note that with 'large' here I don't mean a large set of images necessarily, but a large dynamic range requiring more than 10⁷ discrete values, which is what the 32-bit floating point format provides. In these cases the 32-bit unsigned integer format (2³² or about 10^9.63 discrete values) can be used in PixInsight, except in really extreme cases. We use 64-bit floating point instead because it avoids integer-to-floating-point-to-integer conversions that happen internally in most processes when they work on 32-bit integer images.

Other than these monster HDR compositions and some image analysis tasks, the 64-bit floating point format is normally not necessary.

[Juan Conejero]

Just a note to inform everybody that I'm working on a revision of Kai's script, with the purpose to get it ready for release as an official update. As Kai knows I wanted to start doing this a few days ago, but other commitments have prevented me to do so. Hopefully I'll have a time window today.

[mmirot]

Thanks Juan,

Max

[mmirot]

What are you planning to do ?

Max

[Harry page]

Hi

I dont want to be a damp squib here , but from what I am reading all the files have to have correct fits headers for this script to work 

Never put the correct info in a Fits header in my life , nor will a lot of people if they do not have maxim    I need to be free to select any files I like 

Am I right 

Harry