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

20030520: mcidas/tru64 unix/DEC Alpha

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: 20030520: mcidas/tru64 unix/DEC Alpha
  • Date: Tue, 20 May 2003 11:33:19 -0600
>From: "Dan A. Dansereau" <address@hidden>
>Organization: USU
>Keywords: 200305201449.h4KEnaLd000625 McIDAS-X 2002

Hi Dan,

>I am attempting to trak down a problem that I'm having with mcidas on
>the tru64/dec alpha system. I have started with a clean install with the
>latest version in a clean/new directory. The install completes with
>no compile errors

This sounds promising so far :-)

>to the configuring the micidas account, after doing
>the REDIRECT MAKE ( with the LOCAl.NAM ) the following happens:
>
>When I type
>DMAP AREA
>I get the following output
>
>DMAP AREA                                                              
>PERM      SIZE LAST CHANGED FILENAME DIRECTORY                         
>---- --------- ------------ -------- ---------                         
>-rw-   9341360 Apr 01 16:20 AREA9000 /home/mcidas/data                 
>-rw-   1503728 Apr 01 16:21 AREA9010 /home/mcidas/data                 
>-rw-   1503728 Apr 01 16:21 AREA9011 /home/mcidas/data                 
>-rw-   1543904 Apr 01 16:23 AREA9012 /home/mcidas/data                 
>-rw-   1003728 Apr 01 16:23 AREA9013 /home/mcidas/data                 
>-rw-   1003728 Apr 01 16:24 AREA9014 /home/mcidas/data                 
>-rw-    897680 Apr 01 16:24 AREA9015 /home/mcidas/data                 
>-rw-    608288 Apr 01 16:25 AREA9016 /home/mcidas/data                 
>-rw-    565512 Apr 01 16:25 AREA9017 /home/mcidas/data                 
>-rw-    311008 Apr 01 16:25 AREA9018 /home/mcidas/data                 
>-rw-    714288 Apr 01 16:26 AREA9019 /home/mcidas/data                 
>-rw-       768 Nov 25  1996 AREA9982 /home/mcidas/data                 
>-rw-       768 Nov 25  1996 AREA9983 /home/mcidas/data                 
>-rw-      2816 Jun 02  1998 AREA9995 /home/mcidas/data                 
>19001304 bytes in 14 files
>
>which looks ok;

I agree, this looks good.

>when I type LA 9000 9019 I get this:

One quick comment: programs like LA, DF, and others are being sunset.
They were removed from the SSEC distribution of McIDAS about three
years ago, and my documentation encourages users to move away from their
use as quickly as possible.

>LA 9000 9019
>  area  ss  yyyddd hhmmss  lcor  ecor lr er zr  lsiz  esiz z    bands
>  ---- ---- ------ ------ ----- ----- -- -- -- ----- ----- -    -----
>  9000  11   96001      0     1     3  1  1  1  2160  4320 1 1........>
>  9010  11   96001      0   101   151  1  1  1  1000  1500 1 1........>
>  9011  11   96001      0  2899  4000  8  8  1  1000  1500 1 1........>
>  9012  11   96001      0    51     1  4  4  1  1232  1252 1 1........>
>  9013  11   96001      0 -9999     0 20 20  1  1000  1000 1 1........>
>  9014  11   96001      0 -9999     0 20 20  1  1000  1000 1 1........>
>  9015  11   96001      0   -29     1  1  1  1   700  1280 1 1........>
>  9016  11   96001      0  2806  9049  8 16  1   700   864 1 1........>
>  9017  11   96001      0  2494  7961  8 16  1   666   844 1 1........>
>  9018  11   96001      0  5539  8040  8  8  1   480   640 1 1........>
>  9019  11   96001      0    91    89  4  4  1   592  1204 1 1........>
>Done
>
>again I think this is OK; however

Yes, this looks good.  The "correct" (new) way to do this is:

BATCH TOPOADDE.BAT
DSINFO IMAGE TOPO

        Dataset Names of Type: IMAGE in Group: TOPO

Name         NumPos   Content
------------ ------   --------------------------------------
CONF             1    North America (Conformal)
GLOB             1    Global (Mercator)
GOESE            1    GOES-East (75W)
GOESW            1    GOES-West (135W)
MDR              1    US Radar projection
MERC             1    North America (Mercator)
MOLL             1    Global (Mollweide)
NPOLE            1    Northern Hemisphere
QUAD             1    NW Quadrasphere
SPOLE            1    Southern Hemisphere
WHEMI            1    Western Hemisphere

DSINFO -- done

IMGLIST TOPO/ALL.ALL
Image file directory listing for:TOPO/ALL
 Pos Satellite/         Date       Time      Center   Band(s)
     sensor                                 Lat  Lon
 --- -------------  ------------  --------  ---- ---- ------------
   1  TOPOGRAPHY     1 JAN 96001  00:00:00     0    0 1
  11  TOPOGRAPHY     1 JAN 96001  00:00:00    40  105 1
  12  TOPOGRAPHY     1 JAN 96001  00:00:00    45  105 1
  13  TOPOGRAPHY     1 JAN 96001  00:00:00     0  100 1
  14  TOPOGRAPHY     1 JAN 96001  00:00:00   -90  105 1
  15  TOPOGRAPHY     1 JAN 96001  00:00:00    90  105 1
  16  TOPOGRAPHY     1 JAN 96001  00:00:00     0    0 1
  17  TOPOGRAPHY     1 JAN 96001  00:00:00    23   71 1
  18  TOPOGRAPHY     1 JAN 96001  00:00:00    25  138 1
  19  TOPOGRAPHY     1 JAN 96001  00:00:00    40   98 1
  20  TOPOGRAPHY     1 JAN 96001  00:00:00    26  100 1
IMGLIST: done

>when I type 
>DF 9011 1 AY 0 0 -3 EU=TOPO SF=yes

The "correct" way of doing this is now:

IMGDISP TOPO/CONF MAG=-3 EU=TOPO
Beginning Image Data transfer, bytes= 170228
IMGDISP: loaded frame  1
IMGDISP: done
EU: Restoring TOPO.ET      to frame(s)=   1
EU: Done

>I get the following:
>
>DF 9011 1 AU 0 0 -3 EU=TOPO SF=YES                                     
>BEGIN TV LOAD PROCESSING FOR FRAME  1                                  
>Processing completed for frame= 1
>
>But no image on the screen,

I just ran this command on our Compaq Tru64/OSF1 5.1 system using
Unidata McIDAS v2002 and did get the display on the screen with no
problem.  It is possible that you somehow toggled your image display
off.  Try toggling the display using the ALT-K toggle.  Does the image
appear?

>if I follow this with a 
>MAP NA
>it draws the NA map on the screen.

OK, this says that the navigation has correctly been written to the
frame directory and that MAP can use it correctly.  This looks good.

>I think that I have followed the directions on the web site
>right down to the letter - but I remeber getting a image at this
>step on the prior release.

Hmm... The directions for testing McIDAS v2002 are different from
what your are doing above.  In the v2002 instructions:

http://www.unidata.ucar.edu/packages/mcidas/2002/mcx/test_mcx.html

users are advised to create the TOPO dataset (using DSSERVE) and loading
an image using IMGDISP.  Is it possible you are looking at the testing
instructions from an older version of McIDAS?

>So - Is this a problem, or can I ignore it and go on??

I would say that your system _should_ be able to display images loaded
using DF, because my test system is.  I would recommend, however, that
you follow the procedures in the v2002 testing page above as
that tests the supported portions of the distribution.

Please let me know if you continue to have problems on that Tru64 machine.

On another note, I see that USU is running LDM-6.0.10 on
climatemine.ser.usu.edu, but your main IDD node allegan is still running
LDM-5.  You will not get the benefit of LDM-6 until you upgrade allegan
since it is that machine that is getting the data off of the IDD for
your site.  Is there anything we can do to help you upgrade to the
most recent LDM release (which is now 6.0.11) on allegan?

Tom