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

[McIDAS #SMX-272962]: mcidas question

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [McIDAS #SMX-272962]: mcidas question
  • Date: Mon, 04 Oct 2010 09:40:31 -0600
Hi Sepideh,

re:
> Can you please send me the commands that u used to define the data 
> sets,because i
> have a lot of other files that i have to use them.

OK, here is the DSSERVE invocation to define the TEST/GOES7 data in your account
on tormenta:

<login as 'sepide' on tormenta>

cd $MCDATA
dsserve.k ADD TEST/GOES7 AREA DIRFILE=/home//sepide/mcidas/ir/goes07.1990.001.* 
\"GOES-7 IMAGES

Quick notes:

- you should _always_ be in your McIDAS working directory when you run McIDAS 
commands.
  Your McIDAS working directory is defined by the Linux environment variable 
MCDATA.
  The first command above puts you in the directory defined by MCDATA.

- the actual executable for McIDAS commands are named using the convention 
'command.k' (e.g.,
  dsserve.k is the name of the executable for the DSSERVE command).  You can 
execute McIDAS
  commands from the Linux command line by using their actual name.  The example 
above does
  exactly this.

- the '"' (quote mark) in the DSSERVE command _must_ be escaped (put a '\' 
before the
  quote) when running from the Linux command line.  The same quote field is 
_not_
  escaped when running from the McIDAS Text and Command window.

  For instance:

  from the Linux command line:

  dsserve.k ADD TEST/GOES7 AREA 
DIRFILE=/home//sepide/mcidas/ir/goes07.1990.001.* \"GOES-7 IMAGES

  From the McIDAS Text & Command window:

  DSSERVE ADD TEST/GOES7 AREA DIRFILE=/home//sepide/mcidas/ir/goes07.1990.001.* 
"GOES-7 IMAGES

re:
> I really appreciate your help

No worries.  We are always glad to help when we can.

re:
> I want to convert the area file into netcdf files.

OK, this is easily done.  The process of converting from images in AREA
file format to images in netCDF format in McIDAS is:

- create an input dataset of images in AREA file format (this was done, for 
example
  by the DSSERVE command above)

- create an output dataset of images in netCDF format.  Here is one example that
  should work nicely for you:

<as 'sepide' on tormenta>
cd $MCDATA
dsserve.k ADD NCDF/GOES7IR NCDF 1 9999 TYPE=IMAGE \"GOES-7 images in netCDF 
format

- copy from the input dataset to the output dataset.

  Here is an example of copying a thermal IR image from the input dataset to
  the newly created output dataset:

imgcopy.k TEST/GOES7 NCDF/GOES7IR BAND=8 SIZE=500 1000 LAT=40 105

  Note:

  - copies data from BAND 4 of the input dataset.  BAND 8 for your GOES-7
    images is 11.2 um Night cloud detection, sfc temp data.  You can see
    this from an IMGLIST listing:

imglist.k TEST/GOES7 FORM=BAND
Image file directory listing for:TEST/GOES7
 Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
     sensor                                 Lat  Lon    Lat   Lon
 --- -------------  ------------  --------  ---- ----  ----- ----- ------------
   6  GOES-7 IR      1 JAN 90001  06:31:00    -9  108
   Band: 7    12.7 um Water vapor detection             7.05  3.01   545 x 3822
   Band: 8    11.2 um Night cloud detection, sfc temp   7.05  3.01   545 x 3822
   Band: 12   3.9 um Sfc skin temp., cloud detection    7.05  3.01   545 x 3822
imglist.k: done

 - the command copies 500 lines and 1000 elements from the original image
   centered on the Lat,Lon point 40N 105W

   NB:

   Longitudes in McIDAS are specified in the west positive convention (exactly
   opposite of most other applications; this is historical baggage that must
   be dealt with by the user)

re:
> I have some specified stations,

What is the list of stations you have?  Their location may be available in
the McIDAS station database.

Example of using the STNLIST command to list out information about the station
KDEN:

stnlist.k KDEN
IDN   ID     Station Name         Data Types        ST CO LAT        LON        
 ELE
----- -----  -------------------- ----------------- -- -- ---------- ---------- 
 ----
72565 KDEN   DENVER INTL AIRPORT  M 36 T         EG CO US   39:52:00  104:40:00 
 1655
Number of stations listed: 1
stnlist.k: Done

If one or more of your stations does not have an ICAO identifier (e.g., KDEN 
above),
you may be able to find it using the MATCH= keyword of STNLIST.

For example:

stnlist.k MATCH=DENVER
IDN   ID     Station Name         Data Types        ST CO LAT        LON        
 ELE
----- -----  -------------------- ----------------- -- -- ---------- ---------- 
 ----
 ---  APA    DENVER                           V     CO US   39:34:00  104:53:00 
 1793
 ---  BKF    DENVER                           V     CO US   39:46:00  104:53:00 
 1726
 ---  BOU    DENVER/BOULDER                W        CO US   40:00:00  105:15:48 
    0
 ---  CHY    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  DEN    Denver TDWR                  N         CO US   39:43:41  104:31:34 
 1738
 ---  DEN    DENVER INTL AIRPORT                F   CO US   39:52:00  104:40:00 
 1655
 ---  DEN    DENVER                           V     CO US   39:46:00  104:53:00 
 1625
 ---  DQQ    DENVER                           V     CO US   39:34:00  104:51:00 
    0
 ---  EVS    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  FTG    DENVER/BOULDER               N         CO US   39:47:12  104:32:45 
 1676
 ---  FTG    DENVER                           V     CO US   39:48:00  104:35:00 
    0
 ---  GQW    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  HMX    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  KAPA   DENVER CENTENNIAL AI M    T         EG CO US   39:34:00  104:51:00 
 1793
72565 KDEN   DENVER INTL AIRPORT  M 36 T         EG CO US   39:52:00  104:40:00 
 1655
72469 KDNR   Denver / Stapleton I M   R             CO US   39:47:00  104:52:00 
 1626
 ---  LTT    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  RRV    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  SPO    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  SSH    DENVER                           V     CO US   39:46:00  104:53:00 
    0
 ---  ZDV    DENVER                           V     CO US   39:48:00  104:53:00 
    0
 ---  K45    DENVER                           V     IA US   42:38:00   92:21:00 
    0
 ---  E57    DENVER CITY                      V     TX US   32:58:00  102:52:00 
    0
Number of stations listed: 23
stnlist.k: Done

re:
> i have to locate them and take their albedo
> from channel 1(visible) and brightness temperature from channel 4 (infrared)

The images you currently have in the TEST/GOES7 dataset do not have channel 1 
(VIS) or
channel 4 (infrared) data.  They have long wave IR (12.7 um); thermal IR (11.2 
um)
and shortwave IR (3.9 um) data.

Comment:

- perhaps you have other data from a more recent GOES satellite?

  For instance, channel 1 on GOES-12 is 0.65 VIS, and channel 4 is 10.7 um IR

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: SMX-272962
Department: Support McIDAS
Priority: Normal
Status: Closed