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

[McIDAS #RDQ-637778]: Re: New Questions Regarding My Research



Hi Rod,

re:
> I did this:
> 
> IMGDISP G13/IR27APR11.5 1 LAT=30:00 86:30 EU=IMAGE SF=YES MAG=1
> 
> Beginning Image Data transfer, bytes= 184288
> IMGDISP: loaded frame  1
> IMGDISP: done
> EU: Restoring IMAGE.ET to frame(s)= 1
> EU: Done
> 
> MAP LALO COUNTY=ALL STATE=MS AL GA MCOL=8
> MAP: Completed frame 1
> 
> MAP FILE=OUTVHPOL MCOL=1
> MAP: Completed frame 1
> 
> SATANGLES DEV=T angles.out
> 
> But doesnt work even with the original image why? Am I doing something
> wrong?

I just ran the same set of commands:

IMGDISP G13/IR27APR11.5 1 LAT=30:00 86:30 EU=IMAGE SF=YES MAG=1
MAP LALO COUNTY=ALL STATE=MS AL GA MCOL=8
MAP FILE=OUTVHPOL MCOL=1
SATANGLES DEV=T angles.out

and the file $MCDATA/angles.out was created without problems.

Here are some things to remember:

- you need to move the cursor over the point you are interested in

- because of the DEV=T keyword, you will not see output from
  SATANGLES echoed back to the Command and Text window

- you can view the output file created using the SEE command in
  McIDAS:

  SEE angles.out

  Or, you can see the contents of the output file from your
  Linux terminal window:

  cat $MCDATA/angles.out

re:
> Also I dont know if the equation I sent you from Dan Lindsey
> got through you or not?

Yes, I got the message.  Yesterday I played around with using PRDUTIL
to calibrate one of the effective radius images, but I ran into an
unexpected snag.  Here is the snag at the first step:

PRDUTIL ADD G13/ERAD27APR11.1 1 PROD 1095783 515872 0 255 ERAD 10000 -2139062144
PRDUTIL: Source area must be type PRD
PRDUTIL failed, RC=2

What this was telling me is that the dataset to be worked on must be
stored in files that follow the AREA file naming convention.  I sort
of expected this, so I was not thwarted by this for very long.  Here
is what I did to work around the problem:

From the Linux command line:

cd $MCDATA
cp 
/mnt/hgfs/McIDAS-X/workdata/GOES-EastEffectiveRadius/2011117171500_effrad.area 
AREA2000

From a McIDAS session:

PRDUTIL ADD LOC/AREAS.2000 1 PROD -1095783 515872 0 255 ERAD 10000 -2139062144
Image file directory listing for:LOC/AREAS
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
2000  G-13 IMG      27 APR 11117  17:15:00    35   87
   Band: 1    0.63 um VIS Cloud and Surface Features    5.56  2.46   600 x 1400
     proj:    0 created: 2011180 222034  memo: RT GVAR
     type:PRD      cal type:BRIT
     offsets:  data=    3328 navigation=  256 calibration= 2816 auxiliary=    0
     doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
     valcod:          0 zcor:  0 avg-smp: N
     start yyddd: 2011117  start time:171521  start scan:  406
     lcor: 3361  ecor: 10733  bytes per pixel: 1  ss:180
     Resolution Factors (base=1):   Line=    4.0   Element=    4.0
IMGLIST: done

  Current Calibration Block Segments In File:
                   Output         Input
              Product  Product  Brit  Brit
     Num Type low      high     low   high  Units Scale Missing Val
     --- ---- -------- -------- ----- ----- ----- ----- -----------
      1: PROD -1095783   515872     0   255  ERAD 10000 -2139062144

Comment:

- I store the images you made available to me on a "remote" file system:

  /mnt/hgfs/

  I stored the images in /mnt/hgfs/McIDAS-X/workdata/GOES-xxxxxx
  directories:

  GOES-xxxxxx:

  GOES-EastVisible         - the VIS images
  GOES-EastIR              - the IR images
  GOES-EastEffectiveRadius - the effective radius images

  Of course, this does not match your setup at all, so you would have
  to change your procedure to the following:

From the Linux command line:

cd $MCDATA
cp archive/27apr2011/2011117171500_effrad.area AREA2000

From a McIDAS session:

PRDUTIL ADD LOC/AREAS.2000 1 PROD -1095783 515872 0 255 ERAD 10000 -2139062144

The second snag, which I have not figured out yet, is this added
calibration is causing problems with an IMGPROB probe of the image:

SF 1
IMGDISP MYDATA/IMAGES.2000
 
IMGPROBE LIST POINT MODE=N
IMGPROBE: Units requested are not available for this image
IMGPROBE: Unable to setup search conditions

IMGPROBE: Done
IMGPROBE failed, RC=1

Again, this failure is totally unexpected and will cause me to do
some digging in the server code to find out what is going on.


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: RDQ-637778
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.