|
Hi Shane,
The FITS standard doesn't specify the range of values that is valid in floating point data, so integer and unsigned FITS files are compatible between different applications but floating point FITS files may not be. It is likely that the calibrated files out of PRISM are floating point and use a different range of values to PixInsight (which uses 0..1).
If you save the calibrated images from PRISM as 32-bit unsigned then that will probably work. Alternatively, you can tweak the floating point data range that PI expects on input in the Format Explorer.
Cheers,
Rick.
|