>From: address@hidden
>Organization: Western Michigan
>Keywords: 200003251752.KAA09200 McIDAS-X installation
Elen,
>Sorry I did not send the whole name of the workstation. Here it goes:
>
>s418.lab2.cc.wmich.edu
>
>I forgot how to get the IP address. Can you tell me how?
Now that I have access to the machine, I can get the IP address. This
is done using the program nslookup:
nslookup s418.lab2.cc.wmich.edu
Server: medusa.lab2.cc.wmich.edu
Address: 141.218.20.90
Name: s418.lab2.cc.wmich.edu
Address: 141.218.93.42
The reverse lookup is done by using the IP address and seeing if the
same name comes up:
nslookup 141.218.93.42
Server: medusa.lab2.cc.wmich.edu
Address: 141.218.20.90
Name: s418.lab2.cc.wmich.edu
Address: 141.218.93.42
Looks good. The reason for doing this is related to LDM security.
>Otherwise I
>have to wait for John Tucker to come back to work tomorrow. It is past
>five over here. But I will work late tonight.
No problem with the name/IP address. I did, however, run into another problem.
I started the McIDAS-X build:
<login as the user 'mcidas'>
<FTP the distribution to ~mcidas>
<FTP mcinstall>
<edit .cshrc and setup McIDAS environemnt variables>
source .cshrc
cd mcidas7.6/src
make all
Everything went smoothly until I got:
compile mapsav.for: done
compile mapurx.for: FAILED (See
'/home7/ldm/mcidas/mcidas7.6/src/makelog' for details.)
A tail on makelog shows:
./mccomp -O -vendor -I. -I../netcdf/libsrc -c mapurx.for
cd /tmp/Mu19263
ln -s /home7/ldm/mcidas/mcidas7.6/src/mapurx.f .
ln -s /home7/ldm/mcidas/mcidas7.6/src/fileparm.inc .
f77 -c -O mapurx.f
mapurx.f:
mapurx:
mv mapurx.o /home7/ldm/mcidas/mcidas7.6/src
mv: /home7/ldm/mcidas/mcidas7.6/src/mapurx.o: write: Disc quota exceeded
compile mapurx.for: FAILED
Disc quota exceeded! McIDAS-X requires at least 250 MB of disk to be
built, so I need the disk quota changed in order to continue on s418.
The next thing is where do you want data ingested by the LDM and decoded
by McIDAS-XCD and ldm-mcidas to be put? A quick look at the file
systems on s418 shows that there are three file systems that could
be used, /ilya1, /ilya2, or /ilya3:
~>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 96031 18339 68089 22% /
/dev/dsk/c0t0d0s6 603599 356360 186880 66% /usr
/proc 0 0 0 0% /proc
/dev/dsk/c0t0d0s3 288855 190770 69200 74% /var
/dev/dsk/c0t0d0s4 480919 21 432807 1% /tmp
/dev/dsk/c0t1d0s0 3939604 31310 3514334 1% /ilya1
/dev/dsk/c0t2d0s0 3939604 20829 3524815 1% /ilya2
/dev/dsk/c0t3d0s0 3939604 1366944 2178700 39% /ilya3
/var/cache/.cfs_mnt_points/medusa:_usr_local
3715752 2162664 1515928 59% /usr/local
medusa:/acct 2053576 1359240 632736 69% /acct
medusa:/home7 15506280 14858096 493128 97% /home7
/var/cache/.cfs_mnt_points/medusa:_opt
4129128 745104 3342736 19% /opt
/var/cache/.cfs_mnt_points/medusa:_home3
10326520 6631384 3591872 65% /home3
medusa:/var/mail 1523912 877208 585752 60% /var/mail
/var/cache/.cfs_mnt_points/medusa:_home2
7740648 5646696 2016544 74% /home2
After doing this list, I noticed that the home directory for the user
'mcidas' is not on a file system local to s418:
pwd
/home7/ldm/mcidas
and:
medusa:/home7 15506280 14858096 493128 97% /home7
Am I on the correct machine?
>You are right. I can do the surface maps, meteograms and the upper air
>staff using McIDAS.
Right. So, you do want me to install and configure McIDAS-XCD?
>Elen
Tom
**************************************************************************** <
Unidata User Support UCAR Unidata Program <
(303)497-8644 P.O. Box 3000 <
address@hidden Boulder, CO 80307 <
---------------------------------------------------------------------------- <
Unidata WWW Service http://www.unidata.ucar.edu/ <
**************************************************************************** <
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.