Floating Point range

[robhawleyastro]

I need to move images back and forth from Maxim to PixInsight.  Another thread solved part of the problem by showing how to remap 0,0 to tolerate Maxim conventions.

The other problem I have is floating point range.  By default PixInsight writes floating point in the range of 0.0 to 1.0.  Maxim can read this, but I have to resave the file in Maxim to the range 0.0 to 65535.0 before PinPoint can process the image.

I saw there was an input preference. Is there also a output range preference I have missed?

[Juan Conejero]

Hi,

I saw there was an input preference. Is there also a output range preference I have missed?

PixInsight generates floating point images in the [0,1] range. PixInsight is flexible enough to read floating point FITS images generated in virtually any numeric range. Maxim should also be able to import floating point images in arbitrary ranges, or there should be an easy way to convert them once loaded. For example, if you can multiply all pixels by 65535 there should be no problems to interpret PI floating point data correctly.

[robhawleyastro]

Maxim is indeed able to read the PixInsight 32 bit floating fits (ImagesPlus is not). Maxim can then rescale the image so I can do Pinpoint Astrometry. Getting the precise center of the image is required to accurately display the image in a planetarium program. 

I just wondered if there was a way to avoid the extra step.

Also someone on the Maxim list gave me a visual basic script to restore the missing fields in the FITS header.

Thanks