Hi Jim,
I first say your note on Saturday, but I was unable to respond then...
re:
> Just a followup and such. I am getting ready to move on the AIX box. I
> downloaded
> and executed the most current source of mcidas today. I thought, "just
> maybe" ... well,
> not so much. It didn't compile. I have attached the makelog for your
> perusal.
A quick look at your log file told me that you do not have a full development
environment
installed on your machine. In particular, the build of the netCDF portion of
the distribution
failed because 'flex' and 'yacc' could not be found:
WARNING: `flex' is missing on your system. You should only need it if
you modified a `.l' file. You may need the `Flex' package
in order for those modifications to take effect. You can get
`Flex' from any GNU archive site.
mv lex.yy.c ncgenyy.c
yacc -d ./ncgen.y
yacc: not found
You need to load both 'flex' and 'yacc' and try the build again from scratch:
<as 'root'>
-- install flex and yacc
<as 'mcidas'>
cd ~mcidas/mcidas2007/src
make clobber
make all
Given that 'flex' and 'yacc' were not installed, it is possible that other
things are missing.
> I have requested a firewall poke for ssh to our development box. That should
> be in place
> in the next day or two. I'll let you know. I am sending the system and
> login information to
> your personal email.
Thanks!
> We have just finished the geography website update. It is
> http://www.geography.du.edu and
> if you go to http://www.geography.du.edu/research/weather/ this is where we
> are getting ready
> to tie McIDAS information.
OK.
> I am hoping to write a script that will produce a well formed XML document
> that we can ingest
> on the DU site as well as this. Currently I need to modify some of the
> scripts to produce
> properly sized graphic files.
The size of the display produced by McIDAS scripts (scripts that run McIDAS
commands) will
be controlled by the '-f' flag specified on the 'mcenv' invocation. For
instance, the following
is the last few lines of ~mcidas/data/mcrun.sh:
cd $MCDATA
mcenv << EOF
# put McIDAS-X commands you want to run here, one command per line.
# Example (note that these lines are commented out!!):
#
# dataloc.k ADD GINIEAST adde.ucar.edu
# eg.k
# imgdisp.k GINIEAST/GE1KVIS STA=KMIA MAG=-2 EU=IMAGE SF=YES
# map.k H
# bar.k
# frmsave.k 1 miamivis.gif
# done
exit
EOF
exit 0
'mcenv' run without any command line flags creates a McIDAS "session" that has
one frame that is 480 lines high by 640 elements wide. The session will support
8 graphics levels and 64 image levels. One can change all of this using
command line flags. For instance, the following would display an image in
a frame that is 600 lines by 800 elements with 16 graphics levels and 128 image
levels:
mcenv -f address@hidden -g 16 -i 128 << EOF
# put McIDAS-X commands you want to run here, one command per line.
dataloc.k ADD GINIEAST adde.ucar.edu
eg.k
imgdisp.k GINIEAST/GE1KVIS STA=KMIA MAG=-2 EU=IMAGE SF=YES
map.k H
bar.k
frmsave.k 1 miamivis.gif
# done
exit
EOF
You can see what flags are supported by 'mcenv' by running 'HELP mcenv'
from a McIDAS-X session, or by running 'help.k mcenv' from the $MCDATA
directory after McIDAS has been installed and confiured.
> Hope you have been doing well
I have been well, thanks. I hope the same is true for you!
> and I look forward to this project.
Me too. I think you are very close to having an environment in which
McIDAS can be built cleanly. After that, configuring the package must
be performed, but we will get to that as needed.
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: HCS-801574
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.