[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[McIDAS #LRM-158233]: IMGLIST: ADIRSERV failed on exec of hdfadir
- Subject: [McIDAS #LRM-158233]: IMGLIST: ADIRSERV failed on exec of hdfadir
- Date: Wed, 29 May 2013 18:20:59 -0600
Hi João,
re:
> Sorry for the late answer, busy week.
No worries. I am currently in Cartagena, Colombia participating in
a PASI workshop, and I don't have much free time either :-(
re: after redoing your DSSERVE command
> I get the same error as before:
> Image file directory listing for:GOES15/VIS_4KM
> imglist.k: ADIRSERV failed on exec of hdfadir
> imglist.k: done
OK.
re: Can you make one or a couple of images available to me
> Yes I can.
> Visit 146.164.46.6 on an FTP client. Login as anonymous and use any
> password.
>
> The files mentioned in this email are in: sat/GOES-15/4km/VIS
I just FTPed two of the VIS files (VIS_20130526_1600 and VIS_20130526_1630)
and took a look. These are not HDF files, they are McIDAS AREA files.
I created the ADDE dataset on the machine to which I FTPed them as
follows:
<as 'mcidas'>
cd $MCDATA
dsserve.k ADD TEST/AQUAMET AREA
MASk=/data/ldm/pub/decoded/mcidas/RTIMAGES/HDF/VIS_\* \"Test images from Aquamet
I then listed them AND displayed them in my McIDAS session here in my
hotel room. The images are definitely not HDF files, they are McIDAS
AREA files in which the data block has been PNG compressed. You can see
this using 'od':
od -c VIS_20130526_1600 | less
0000000 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 \0 270 \0 001 271 372
0000020 \0 002 q \0 \0 \0 \n 030 \0 \0 037 - \0 \0 \0 \0
0000040 \0 \0 005 x \0 \0 006 314 \0 \0 \0 001 \0 \0 \0 004
0000060 \0 \0 \0 \b \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 \0
0000100 \0 001 271 372 \0 002 t 352 \0 \0 \0 001 377 377 377 377
0000120 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000140 R T G V A R \0 \0 \0 \0 \0 \0 \0 \0 \0
0000160 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
0000200 \0 \0 004 271 \0 \0 013 \0 \0 \0 001 \0 \0 \0 \0 \0
0000220 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
...
0005760 211 P N G \r \n 032 \n \0 \0 \0 \r I H D R
0006000 \0 \0 006 314 \0 \0 005 x \b \0 \0 \0 \0 ! 237 247
0006020 251 \0 \0 \0 I D A T x 234 274 274 313 216 #
0006040 I 262 , ( * 252 j 346 036 221 Y 325 u 016 p 357
...
These images were evidently created by the process that creates the
Unidata-Wisconsin datastream images for the IDD (IDD feedtype UNIWISC
(aka MCIDAS)). I wrote the code that does the compression AND modified
Unidata McIDAS to be able to understand the images in this compressed
format. We also modified GEMPAK to be able to use the compressed
images directly, so Unidata users do not have to do anything to
use the UNIWISC images.
In order to uncompress the images, you will need to download the
ldm-mcidas package of decoders from our anonymous FTP server:
machine: ftp.unidata.ucar.edu
user: anonymous
pass: your email address
directory: pub/ldm-mcidas
file: ldm-mcidas-2012.tar.gz
To build the ldm-mcidas decoders, you will need McIDAS built and
installed and the LDM built and installed; I believe that you
meet both of these requirements. If you send me the particulars
of the machine on which you want to build the ldm-mcidas decoders,
I will send you a list of the environment variables you will
need to set to build the decoders. I will also send you the
LDM pattern-action file action(s) you will need to run to
automatically do the decoding on your system.
re:
> Thanks for the help.,
No worries.
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: LRM-158233
Department: Support McIDAS
Priority: Normal
Status: Closed
