[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
19990830: McIDAS-XCD at the University of Delaware (cont.)
- Subject: 19990830: McIDAS-XCD at the University of Delaware (cont.)
- Date: Mon, 30 Aug 1999 17:23:05 -0600
>From: Kenji Matsuura <address@hidden>
>Organization: University of Delaware
>Keywords: 199908301644.KAA13280 McIDAS-XCD
Kenji,
>Thank you for looking into the problem.
No problem.
>I just would like to have a working mcidas xcd at this moment. You can
>put everything back to default (or recommended condition). Once I have
>a working xcd, then I think I can modify the configuration gradually to
>meet our needs.
OK, the changes I will make are per the web installation/configuration
instructions accessible under:
http://www.unidata.ucar.edu/packages/mcidas/mcx/mcx-main.html
>So for the time being, if you could set things up and let me know what
>you did, I would really appreciate. I realize that this is dumping
>everything on you, but for now that will probably solve the problem
>faster.
>
>Again, thank you for your assistance.
Below, you will find the blow-by-blow of what I have done on your system.
<as the user 'ldm'>
o ldmadmin stop
o create the data/surface/front directory (for ASUS01 and FSUS02 front
files available in the DDPLUS stream)
o edit ~ldm/decoders/xcd_run and ~ldm/decoders/mcscour.sh to set
MCDATA
o check to make sure that ~ldm/etc/ldmd.conf and ~ldm/etc/pqact.conf
are setup correctly; they are
o copy /export/home/ldm/ldm-mcidas/bin/batch.k to the ~ldm/decoders
directory, and then edit the batch.k to match your system setup:
o set MCHOME to be /export/home/mcidas
o correct typos in batch.k that were fixed in the 7.6.1 release
(MDATA -> MCDATA; $MCGUI: -> ${MCGUI}:)
Copying batch.k to a directory in 'ldm's PATH will allow the system
create the composite imagery defined in the McIDAS routing table,
/export/home/ldm/data/mcidasd/ROUTE.SYS.
<as the user 'mcidas'>
o edit ~mcidas/.cshrc
o add $HOME/mcidas/man to MANPATH:
setenv MANPATH /opt/SUNWspro/man:/usr/man:/home/mcidas/man
o change MCDATA to be /home/mcidas/workdata and put conditional
around setting of MCDATA, MCPATH, etc.
if ( ! ${?MCPATH} ) then
setenv MCDATA $HOME/workdata
setenv MCPATH ${MCDATA}:$HOME/data:$HOME/help
setenv MCGUI $HOME/bin
setenv MCTABLE_READ "${MCDATA}/MCTABLE.TXT;$HOME/data/ADDESITE.TXT"
setenv MCTABLE_WRITE "$HOME/data/ADDESITE.TXT"
setenv XCD_disp_file ${MCDATA}/DECOSTAT.DAT
endif
o make the changes active:
unsetenv MCPATH
source ~/.cshrc
o edit ~mcidas/.mcenv and make changes that correspond to those above
(.mcenv will be used by the McIDAS remote ADDE server if/when you
configure it):
change:
umask 002
path=($HOME/runtime/bin $HOME/bin $OPENWINHOME/bin /bin)
path=($path /opt/SUNWspro/bin /usr/bin /usr/ucb /etc )
path=($path /usr/ccs/bin /opt/bin .)
MCDATA = /export/home/mcidas/workdata
MCPATH = ${MCDATA}:$HOME/data:$HOME/help
MCGUI = $HOME/bin
McINST_ROOT = $HOME/runtime
XCD_disp_file=${MCDATA}/DECOSTAT.DAT
PATH=${MCGUI}:$PATH
export MCDATA MCPATH MCGUI PATH
cd $MCDATA
to:
umask 002
path=($HOME/runtime/bin $HOME/bin $OPENWINHOME/bin /bin)
path=($path /opt/SUNWspro/bin /usr/bin /usr/ucb /etc )
path=($path /usr/ccs/bin /opt/bin .)
MCDATA=$HOME/workdata
MCPATH=${MCDATA}:$HOME/data:$HOME/help
MCGUI=$HOME/bin
PATH=${MCGUI}:$PATH
export MCDATA MCPATH MCGUI PATH
cd $MCDATA
Note the removal of spaces around the equal signs. The spaces are
incorrect for Bourne/Korn shell.
o Remove the configuration files from the XCD output data directory,
leaving SCHEMA, ROUTE.SYS, and SYSKEY.TAB there as they would have
to have been copied there later.
o Change the definition of the McIDAS environment variable XCDDATA
from /EXPORT/HOME/LDM/DATA/MCIDASD to /export/home/ldm/data/mcidasd:
cd ~mcidas/workdata
te.k XCDDATA \"/export/home/ldm/data/mcidasd
o create copies of EXAMPLE.NAM, DSSERVE.BAT, DATALOC.BAT as per online
instructions:
cd ~mcidas/data
cp EXAMPLE.NAM LOCAL.NAM
cp DSSERVE.BAT LSSERVE.BAT
cp DATALOC.BAT LOCDATA.BAT
Next, edit the copies of the above files to match your system setup.
o restore the REDIRECTions just set in LOCAL.NAM to the 'mcidas' account:
cd ~mcidas/workdata
redirect.k REST LOCAL.NAM
Each account that will run McIDAS-X will need to have this last step
done. The only difference for users other than 'mcidas' is that
their McIDAS-X working directory will be ~user/mcidas/data instead of
~mcidas/data.
o define the datasets set in LSSERVE.BAT:
cd ~mcidas/workdata
batch.k LSSERVE.BAT
o restore the data location setup in LOCDATA.BAT:
cd ~mcidas/workdata
batch.k LOCDATA.BAT
o setup XCD:
o run the XCD.BAT and XCDDEC.BAT McIDAS BATCH files:
cd ~mcidas/workdata
batch.k XCD.BAT
batch.k XCDDEC.BAT
o enable the ROUTE PostProcess creation of composite imagery:
cd ~mcidas/workdata
route.k REL C
route.k REL N
<as user 'ldm'>
o restart the LDM:
ldmadmin start
o reenable scouring of XCD produced data files:
cd ~ldm/etc
<edit scour.conf and modify the LDM scouring of files in the
/export/home/ldm/data/mcidasd directory; use LDM scouring to
cull the *.[dca|eta|ngm|ord] files but nothing else!>
setenv EDITOR vi
crontab -e
<uncomment the mcscour.sh invocation line so will scour with
the McIDAS routines in mcscour.sh>
I feel that it is better to scour using the McIDAS scouring commands.
This way, you don't have to have a 'mcidas' cron job that touches
SCHEMA, ROUTE.SYS and SYSKEY.TAB on a regular basis.
<as user 'mcidas'>
o wait for a couple of minutes and then verify that XCD decoders are
producing output data files:
cd ~mcidas/workdata
mdu.k LIST 1 100
MD# CREATED SCHM PROJ NR NC ID DESCRIPTION
----- ------- ---- ---- ---- ---- ------- -----------
2 1999242 ISFC 0 72 4500 1999242 SAO/METAR data for 30 AUG 1999
12 1999242 IRAB 0 8 1300 1999242 Mand. Level RAOB for 30 AUG 1999
22 1999242 IRSG 0 16 6000 1999242 Sig. Level RAOB for 30 AUG 1999
32 1999242 ISHP 0 24 2000 1999242 SHIP/BUOY data for 30 AUG 1999
52 1999242 SYN 0 8 6000 1999242 SYNOPTIC data for 30 AUG 1999
62 1999242 PIRP 0 24 1500 1999242 PIREP/AIREP data for 30 AUG 1999
72 1999242 NLDN 0 1000 1000 1999242 NLDN data for 30 Aug 1999
-- END OF LISTING
o since the GRID decoding is turned off in the installation configuration
files, and since the point source decoding, etc. appears to be working
correctly, turn on the GRID decoding:
cd ~mcidas/workdata
decinfo.k SET DMGRID ACTIVE
Things NOT done, but are recommended:
o setup the McIDAS ADDE remote server. This needs to be done by 'root':
sh ~mcidas/mcidas7.6/mcinet7.6.sh install mcadde
'root' will also have to create an account for the user 'mcadde' that:
o has the same HOME directory as 'mcidas'
o is in the same group as 'mcidas'
o has as its default shell, /bin/false (so nobody can logon as 'mcadde')
'mcadde' will use the settings in ~mcidas/.mcenv (modified above)
and will allow users to go through the remote ADDE interface for data.
This will get to be very important as we drop support for non-ADDE
routines next summer (please review:
http://www.unidata.ucar.edu/packages/mcidas/mcx/sunset.html
for information on what commands will be dropped from McIDAS-X 7.70.
o reexamine the creation of the *.[dca|eta|ngm|ord] data files in the
/export/home/ldm/data/mcidasd directory. The FOUS reports you are
saving in those files can be extracted from the XCD text spool files
(*.XCD). This would help clean things up a bit.
You will have to keep an eye on disk space now that all of McIDAS-XCD
decoding has been turned on. McIDAS files, especially GRID files, can
get to be quite large. I noticed that climate had about 1.5 GB of
space in /export/home, but this can evaporate pretty quickly if scouring
fails for a day for some reason.
Please let me know if you see any problems or have questions.
Tom
>From address@hidden Tue Aug 31 10:25:26 1999
Thank you for having spent a lot of time for us. It is good to see that
something is working even though I did not do it.. I am trying to figure
out what you have done and what they mean. I am hoping that I won't
bother you anymore.
Thank you again.
Kenji
