Author Topic: FITS incompatibility  (Read 2400 times)

Offline Mark de Regt

  • Newcomer
  • Posts: 39
FITS incompatibility
« on: 2015 March 30 12:09:39 »
I had been using CCDStack for many years, before recently switching to PI.

So I have extensive libraries of master calibration frames, created in CCDStack.

I am finding that when I process raw data, in PI, using the CCDStack master calibration frames, they don't work right in PI.  If I re-create the masters in PI, all is well.

Is this to be expected?

Thanks.

Mark

Offline Carlos Milovic

  • PTeam Member
  • PixInsight Jedi Master
  • ******
  • Posts: 2172
  • Join the dark side... we have cookies
    • http://www.astrophoto.cl
Re: FITS incompatibility
« Reply #1 on: 2015 March 30 13:03:10 »
It depends how you saved the masters. If it is using 32 floating point, then most probably it is an incompatibility generated by the use of a non-normalized dynamic range. You may load the masters with a permisive policy, manually divide them by 65535 (using PixelMath), and then save again. Also make sure that it has no pedestal values...


Regards,

Carlos Milovic F.
--------------------------------
PixInsight Project Developer
http://www.pixinsight.com

Offline Mark de Regt

  • Newcomer
  • Posts: 39
Re: FITS incompatibility
« Reply #2 on: 2015 April 01 10:00:23 »
Ok