MultiImage.fits

[NKV]

Hi.
BatchFormatConversion.js See screen1 in attachment.

PixInsight directly load the file without problem. The file is 8 images in one fits.
But if i try to save one of 8 images i get error. See screen2 in attachment.

Link to the file. http://m1eaoq.1fichier.com/en/

Best regards,
Nikolay.

[NKV]

PI x64 same problem.
Also I not understand why in see PCL Win32 System Exception on PixInsight x64 core version under Win7 x64 ?
See screen in attachment.

[pfile]

if it is the "new" BFC script that supports format hints, then juan explicitly took out the multi-fits support. i cant remember now if the new types used to represent the image (the ones that support format hints) can't support multi-fits, or if it was just 'laziness'. i had hacked on this script a little bit and released it to juan before even trying to add multi-fits support and he didn't seem interested in fixing that up.

if it's the old script, then it did have support for multi-fits.

not sure about the exception you are getting.

[NKV]

The BFC script from latest PI core distribution.

Any way latest PI core can't handle the file correctly. See post #2

[terry0905]

Hi,

Thank goodness I'm not the only one geting the PCL Win32 System Exception but I get it in PixInsight x64 core version under Win7 x64, and on PixInsight x32 under Windows 7 x32 and Windows XP. I thought it was just me!

Terry

[Juan Conejero]

We have two different topics here:

- The error you're getting is due to the PCOUNT keyword. Just remove it and the images should be writeable without problems (unless they have additional errors). I am downloading the file right now so I'll check.

- The structured exception handling system on Windows, aka Win32 exception system, is the same on 32-bit and 64-bit versions of Windows. For example, there is a Win32Exception class in .NET 4 and also in PCL (don't look deeper; this is probably the only similarity between .NET and PCL --- so I hope! ).

[NKV]

- The error you're getting is due to the PCOUNT keyword. Just remove it and the images should be writeable without problems (unless they have additional errors). I am downloading the file right now so I'll check.

Is it problem of the file? PCOUNT keyword is standard or not? Why PixInsigt can't correctly process file with PCOUNT keyword?

Please check the file.
Note: The file from www.eso.org

[Juan Conejero]

The PCOUNT keyword is used to define the length of a FITS extension. See for example:

http://archive.stsci.edu/fits/fits_standard/node39.html#SECTION00941200000000000000

FITS extensions are the way multiple images can be stored in a single FITS file. The PCOUNT keyword shouldn't occur in the primary FITS HDU, so if it exists it should be removed before attempting to write a single-HDU FITS file. The PCOUNT keyword is present in this case because the original file has FITS extensions. Later I'll open the file and will see what happens exactly.

This is the first time we have seen this problem. Anyway, I'll modify the FITS support module to perform these actions automatically.

[NKV]

Anyway, I'll modify the FITS support module to perform these actions automatically.

Thanks!