Author Topic: Are we now enforced to use the XISF format?  (Read 2857 times)

Offline gvanhau

  • PixInsight Old Hand
  • ****
  • Posts: 345
Are we now enforced to use the XISF format?
« on: 2015 October 27 20:30:39 »
Hello

I have set in global preferences that my default format is .fit
Even so, on (some?) proceses like splitcfa that do not allow to select output format they are writing .xisf even if input is .fit.

I dont like .xisf not because it is bad, but because it is incompatible with any other graphic software out there.

Regards
Geert
Geert Vanhauwaert

Offline msmythers

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1178
    • astrobin
Re: Are we now enforced to use the XISF format?
« Reply #1 on: 2015 October 27 20:56:34 »
Geert

I would consider this a bug rather then an enforced standard. In the mean time I know this is not a great solution but the BatchFormatConversion script works well.


Mike

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Are we now enforced to use the XISF format?
« Reply #2 on: 2015 October 28 03:37:40 »
Quote
I have set in global preferences that my default format is .fit

Note that this preferences item refers to the default format used in Save As file dialogs, when saving a newly created image and the Remember File Save file type option is disabled (it is enabled by default). This option does not modify default file extensions in processing tools.

Quote
on (some?) proceses like splitcfa that do not allow to select output format

This is a limitation of the SplitCFA tool (it isn't a bug because a bug cannot happen in a nonexistent feature) that I'll try to fix in a future version.

Quote
I dont like .xisf not because it is bad, but because it is incompatible with any other graphic software out there.

The FITS format has been deprecated in PixInsight. No further development will be done for FITS, except to fix possible incompatibilities with future versions of the FITS standard, if necessary. The XISF format is and will be the native file format of PixInsight, and hence it will be the default format used by all tools included in official PixInsight distributions.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline niteman1946

  • PixInsight Addict
  • ***
  • Posts: 234
Re: Are we now enforced to use the XISF format?
« Reply #3 on: 2015 October 28 05:01:50 »
Not piling on.  This just seems like the right place to add my experience.
Through 2012 my camera was a Canon 450D.  My process was to Calibrate (CR2 to fit), Debayer, Align and Integrate (all as fits).  My Bias, Flats and Darks were fits.
I'm now having to dust off the Canon while my CCD goes back to the manufacturer for cleaning.  With my modern Flats, Bias and Darks in the xisf format, the CR2 Lights will not Calibrate.  However, a BatchConversion of raw to xisf first does then allow the Calibrate to run.
Not a deal breaker, just one more step in the process.
Great software BTW! ;)
Mark

Offline msmythers

  • PTeam Member
  • PixInsight Jedi
  • *****
  • Posts: 1178
    • astrobin
Re: Are we now enforced to use the XISF format?
« Reply #4 on: 2015 October 28 08:57:34 »
Juan

There are tools like ImageCalibration, StarAlignment and ImageContainer that allow the user to choose an output directory and also the file extension. Most if not all the scripts that allow an output directory to be specified also allow the file extension to be specified. Shouldn't this be the same standard that the SpiltCFA tool follows.


Mike