[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[McIDAS #HLZ-722478]: Problem displaying Himawari visible image



Hi Kwan,

re:
> Here is the file.  We are provided with these 'experimental' images
> operationally (from the Proving Ground I believe).

OK, I have the file (AREA2005), and am taking a look at it now.

The thing I did not notice previously jumped out at me when I
looked at a full IMGLIST listing:

IMGLIST MYDATA/IMAGES.2005 FORM=ALL
Image file directory listing for:MYDATA/IMAGES
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
2005  HIMAWARI-8    20 FEB 16051  00:00:00   -17  180
   Band: 3    No Information Available                  2.00  1.92   225 x  300
     proj:    0 created: 2016056 232911  memo: HIMAWARI Projected Full Disk
     type:VISR     cal type:REFL
     offsets:  data=     768 navigation=  256 calibration=    0 auxiliary=    0
     doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
     valcod:          0 zcor:  0 avg-smp: N
     start yyddd: 2016051  start time:     0  start scan:    0
     lcor: 5331  ecor:  6533  bytes per pixel: 1  ss: 86
     Resolution Factors (base=1):   Line=    2.0   Element=    2.0
IMGLIST: done

I have not seen this before, so I will have to do some code diving
to learn about it.

By the way, I got the same error when I tried to IMGDISP the image:

IMGDISP MYDATA/IMAGES.2005
IMGDISP: Units requested are not available for this image
IMGDISP: done
IMGDISP failed, RC=2

(later)

I just looked at the calibration module for Himiwari imagery, and
I see the following:

c --- Verify that the output calibration type
      elseif (
     &        (cal_output(1:4) .ne. 'TEMP') .and. 
     &        (cal_output(1:3) .ne. 'RAD')  .and. 
     &        (cal_output(1:3) .ne. 'RAW')  .and. 
     &        (cal_output(1:3) .ne. 'ALB')  .and. 
     &        (cal_output(1:4) .ne. 'BRIT')
     &       ) then
          kbxini         = -1
      else
          src_byte_size  = io_size(1)
          dest_byte_size = io_size(2)
          cal_flag       = 0
          kbxini         = 0
      endif

This means that McIDAS does not understand a calibration type of REFL for
Himiwari imagery.

It would be interesting to learn more about the origin and history of
the AREA file you sent.  Can you check into this more?


> Kwan
> 
> address@hidden> wrote:
> 
> > Hi Kwan,
> >
> > re:
> > > I have a Himawari visible image which, for some reason, could not be
> > > displayed using IMGDISP (2015 version).  It reported this error, "Units
> > > requested are not available for this image".
> > >
> > > imglist.k HIMA/IMG.2 FORM=ALL
> > > Image file directory listing for:HIMA/IMG
> > > Pos Satellite/         Date       Time      Center      Res (km)
> > > Image_Size
> > > sensor                                 Lat  Lon    Lat   Lon
> > > --- -------------  ------------  --------  ---- ----  ----- -----
> > > ------------
> > > 2    20 FEB 16051  00:00:00   -17  180
> > > Band: 3    No Information Available                  2.00  1.91   225 x
> > > 300
> > > proj:    0 created: 2016056 194928  memo: HIMAWARI Projected Full Disk
> > > type:VISR     cal type:REFL
> > > offsets:  data=     768 navigation=  256 calibration=    0
> > > auxiliary=    0
> > > doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
> > > valcod:          0 zcor:  0 avg-smp: N
> > > start yyddd: 2016051  start time:     0  start scan:    0
> > > lcor: 5342  ecor:  6538  bytes per pixel: 1  ss: 86
> > > Resolution Factors (base=1):   Line=    2.0   Element=    2.0
> > > imglist.k: done
> > >
> > > imgdisp.k HIMA/IMG.2 1
> > > imgdisp.k: Units requested are not available for this image
> > > imgdisp.k: done
> >
> > Hmm... the Band: 3 line above
> >
> > Band: 3    No Information Available                  2.00  1.91   225 x 300
> >
> > makes me suspicious that the SATBAND file that has new Himawari data is
> > not being used or the satellite ID in the image is wrong.
> >
> > re:
> > > Was there something missing here?
> >
> > Perhaps, but I am not sure.  Another user has been using the Unidata
> > McIDAS-X v2015 release with Himawari imagery successfully, so your
> > report is new and unexpected.
> >
> > Can you make the image you are experimenting with available?  Since its
> > size is only 225x300, it is likely small enough to be sent as an email
> > attachment.  If it is big and the indicated size is wrong, it would
> > point to a much deeper problem somewhere.
> >
> > Question:
> >
> > - where did you get this image?
> >
> > Cheers,
> >
> > Tom
> > --
> >
> > ****************************************************************************
> > Unidata User Support                                    UCAR Unidata
> > Program
> > (303) 497-8642                                                 P.O. Box
> > 3000
> > address@hidden                                   Boulder, CO
> > 80307
> >
> > ----------------------------------------------------------------------------
> > Unidata HomePage                       http://www.unidata.ucar.edu
> >
> > ****************************************************************************
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: HLZ-722478
> > Department: Support McIDAS
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: HLZ-722478
Department: Support McIDAS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.