Author Topic: Skipping image with invalid dimensions (1) in HDU #2 (Read 5808 times)

Don · « **on:** 2012 June 19 19:00:05 »

I see this error in the process console every time I run Image Integration or Star Alignment. The processes seem to work OK despite the message. Here is an extract from the process console for an Image Integration:

K:/temp/registered/debayer_M17_LIGHT_180s_400iso_20120616-02h06m37s376ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
Reading FITS: 32-bit floating point, 3 channel(s), 3474x2314 pixels: 100%
MRS noise evaluation: done.
Scale factors : 1.00762 1.00468 1.00476
Zero offset : +3.042696e-004 +1.267437e-004 +6.959937e-005
Noise estimates : 2.022e-004 1.445e-004 1.394e-004
Weight : 1.00881 1.01178 1.00757

Again, the integration seems to work OK. But can someone tell me what the message about invalid dimensions means?

Thanks,

Don

Geoff · « **Reply #1 on:** 2012 June 19 19:11:02 »

Try running it with three copies of the same image and see if you still get the error. Obviously the dimensions of the three copies will be identical.
Geoff

Don · « **Reply #2 on:** 2012 June 19 19:52:10 »

Yes, same error with five copies of the same image. It doesn't actually skip any images, all five were integrated, but the same error message appeared for each one:

ImageIntegration: Global context

Opening files:
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
* Retrieved data from file cache.
Scale factors : 1.00000 1.00000 1.00000
Zero offset : +0.000000e+000 +0.000000e+000 +0.000000e+000
Noise estimates : 1.952e-004 1.393e-004 1.346e-004
Weight : 1.00000 1.00000 1.00000
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
* Retrieved data from file cache.
Scale factors : 1.00000 1.00000 1.00000
Zero offset : +0.000000e+000 +0.000000e+000 +0.000000e+000
Noise estimates : 1.952e-004 1.393e-004 1.346e-004
Weight : 1.00000 1.00000 1.00000
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
* Retrieved data from file cache.
Scale factors : 1.00000 1.00000 1.00000
Zero offset : +0.000000e+000 +0.000000e+000 +0.000000e+000
Noise estimates : 1.952e-004 1.393e-004 1.346e-004
Weight : 1.00000 1.00000 1.00000
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
* Retrieved data from file cache.
Scale factors : 1.00000 1.00000 1.00000
Zero offset : +0.000000e+000 +0.000000e+000 +0.000000e+000
Noise estimates : 1.952e-004 1.393e-004 1.346e-004
Weight : 1.00000 1.00000 1.00000
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
** Skipping image with invalid dimensions (1) in HDU #2
* Retrieved data from file cache.
Scale factors : 1.00000 1.00000 1.00000
Zero offset : +0.000000e+000 +0.000000e+000 +0.000000e+000
Noise estimates : 1.952e-004 1.393e-004 1.346e-004
Weight : 1.00000 1.00000 1.00000

Integration of 5 images:
Pixel combination ......... average
Output normalization ...... additive + scaling
Range rejection ........... range_low=0.000000 range_high=0.980000
Pixel rejection ........... linear fit clipping
Rejection normalization ... scale
Rejection clippings ....... low=yes high=yes
Rejection parameters ...... lfit_low=5.000 lfit_high=2.500

* Using 1207 concurrent pixel stack(s) = 351.90 MB

* Integrating channel 1 of 3:
Integrating pixel rows: 0 -> 1206: 100%
Integrating pixel rows: 1207 -> 2313: 100%

Pixel rejection counts:
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
1 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
2 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
3 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
4 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
5 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)

Total : 367140 0.913% ( 367140 + 0 = 0.913% + 0.000%)

* Integrating channel 2 of 3:
Integrating pixel rows: 0 -> 1206: 100%
Integrating pixel rows: 1207 -> 2313: 100%

Pixel rejection counts:
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
1 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
2 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
3 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
4 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
5 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)

Total : 367140 0.913% ( 367140 + 0 = 0.913% + 0.000%)

* Integrating channel 3 of 3:
Integrating pixel rows: 0 -> 1206: 100%
Integrating pixel rows: 1207 -> 2313: 100%

Pixel rejection counts:
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
1 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
2 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
3 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
4 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)
K:/temp/m17/temp/do_flats_again/debayer_M17_LIGHT_180s_400iso_20120616-02h24m40s984ms_c_r.fit
5 : 73428 0.913% ( 73428 + 0 = 0.913% + 0.000%)

Total : 367140 0.913% ( 367140 + 0 = 0.913% + 0.000%)

MRS noise evaluation: done.
Computing noise scaling factors: done.

Gaussian noise estimates:
?sR = 1.952e-004
?sG = 1.393e-004
?sB = 1.346e-004

Reference SNR increments:
??s0R = 1.0000
??s0G = 1.0000
??s0B = 1.0000

Average SNR increments:
??sR = 1.0000
??sG = 1.0000
??sB = 1.0000

60.856 s

georg.viehoever · « **Reply #3 on:** 2012 June 19 23:33:01 »

Apparently there is more data in your FITS files than just the image. What is the source of your data?

HDU is a header data unit, see http://fits.gsfc.nasa.gov/fits_primer.html . You may want to use one of the utities in http://fits.gsfc.nasa.gov/fits_utility.html to see what's there.

Georg

Juan Conejero · « **Reply #4 on:** 2012 June 20 01:42:28 »

Hi Don,

This is a warning message, not an error. It means that your images contain an extension header/data unit (HDU) with a one-dimensional image. We know this from the (1) part of the warning message. In this additional HDU, the XTENSION keyword has the value 'IMAGE' and the NAXIS keyword is equal to one. So this is actually a vector, not an image. PixInsight does not work with these (more specifically, if NAXIS=2, NAXIS1=n and NAXIS2=1, then we'd have an nx1 image that PI would load without problems) .

You can safely ignore this warning; it just tells you that your images have something that is being ignored by the ImageIntegration process. However, I am very curious to know where these images come from

Raymond · « **Reply #5 on:** 2012 June 20 04:01:21 »

Hi
I have a similar problem but from different processing steps while integrating images of the sun using FFT-Registration.
My files come from a Canon 500d; extension .cr2.
First I use the BatchFormatConversion Skript to create .fit (format: same as input images) files.
The FFT-Registration Skript seems to work correctly, but with the following message:

=== Registering image 1 of 3 === Reading image: C:/Users/Raymond/Pictures/Astrophotography/2012_06_18_Sun/series_1/process_pixi/IMG_6067.fit ** Skipping image with invalid dimensions (1) in HDU #2 Reading FITS: 16-bit integers, 3 channel(s), 4770x3178 pixels: 100% *** Evaluating FFT translation: *** Translation corrections: dx : -4.63 px dy : -1.52 px *** Applying translation: Translate dx=-4.626, dy=-1.522, Bicubic spline interpolation, c=0.30: 100%

As mentioned, there seems to be no problem with the resulting image.
I hope this can help you.

Juan Conejero · « **Reply #6 on:** 2012 June 20 04:13:38 »

Then this looks like a bug in the latest version of the FITS module that I published last week, since the origin of the image is PI. The bug is harmless but I'm going to find and fix it ASAP. Thanks for the heads up.

Juan Conejero · « **Reply #7 on:** 2012 June 20 04:27:47 »

Hmm, this is strange, I can't reproduce it. Could you upload one of these FITS files (preferably to endor.uv.es if you have an account)?

Don · « **Reply #8 on:** 2012 June 20 05:38:36 »

Hi Juan,

I have placed a ZIP file contain the FITS file from my second post in this thread on a server where you can reach it. You can download it from:

http://dandjreed.homedns.org/astro/PI_Files.zip

The source of the FITS file is PixInsight. It is a calibrated, debayered and registered image, originally produced by my Canon Digital Rebel XT (350D). The original .CR2 file is included in the ZIP file also. The .CR2 file was acquired using BackyardEOS.

Let me know if it would help for me to send other files. While re-reading my two posts in this thread, I recognize that I didn't make one thing clear - this message appears during Image Integration and during Star Alignment for every image, every time I use PixInsight. I had deduced that it wasn't a fatal error because the processes complete successfully despite the message.

Thanks for reply. I'm a new PixInsight user, having used Iris for several years. I'm very favorably impressed with the software and the support.

Thanks,

Don

pfile · « **Reply #9 on:** 2012 June 20 08:48:49 »

i have this problem also, but it does seem harmless. my fits files also were generated by PixInsight.

Juan Conejero · « **Reply #10 on:** 2012 June 20 17:54:58 »

This bug is now fixed in version 1.0.10 of the FITS format support module, which I have just released as an update. Sorry for the inconvenience.

This forum is closed since 5 March 2020

PixInsight Forum is now available at:

https://pixinsight.com/forum/

News:

Author Topic: Skipping image with invalid dimensions (1) in HDU #2 (Read 5808 times)

Don

Skipping image with invalid dimensions (1) in HDU #2

Geoff

Re: Skipping image with invalid dimensions (1) in HDU #2

Don

Re: Skipping image with invalid dimensions (1) in HDU #2

georg.viehoever

Re: Skipping image with invalid dimensions (1) in HDU #2

Juan Conejero

Re: Skipping image with invalid dimensions (1) in HDU #2

Raymond

Re: Skipping image with invalid dimensions (1) in HDU #2

Juan Conejero

Re: Skipping image with invalid dimensions (1) in HDU #2

Juan Conejero

Re: Skipping image with invalid dimensions (1) in HDU #2

Don

Re: Skipping image with invalid dimensions (1) in HDU #2

pfile

Re: Skipping image with invalid dimensions (1) in HDU #2

Juan Conejero

Re: Skipping image with invalid dimensions (1) in HDU #2