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.
Hi Francisco, re: <login as 'mcidas'> cd $MCDATA which mcenv > The commands gave me the following output: > mcidas@geologia-desktop:~$ cd $MCDATA > mcidas@geologia-desktop:~/workdata$ which mcenv > /home/mcidas/bin/mcenv Very good. re: output from env run from within 'mcenv' shell which mcenv mcenv env > Ok, here is the output: > > mcidas@geologia-desktop:~/workdata$ which mcenv > /home/mcidas/bin/mcenv > mcidas@geologia-desktop:~/workdata$ mcenv > mcidas@geologia-desktop:~/workdata$ env > CXXCPP= > SHELL=/bin/bash > TERM=xterm > XDG_SESSION_COOKIE=39beefa1a6c440ec043ca5184c939f82-1286900839.797704-214004421 > SSH_CLIENT=136.145.159.71 40454 22 > CPPFLAGS=-DNDEBUG -Df2cFortran > MCHOME=/home/mcidas > SSH_TTY=/dev/pts/0 > MCCOMPRESS=GZIP > USER=mcidas > LS_COLORS=rs=0:di=01;34:ln=01;36:hl=44;37:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01; 35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36: > McINST_ROOT=/home/mcidas > MCTABLE_WRITE=/home/mcidas/data/ADDESITE.TXT > PATH=/home/mcidas/bin:/home/mcidas/bin:/home/mcidas/bin:/home/mcidas/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/>sbin:/bin:/usr/games > MAIL=/var/mail/mcidas > PWD=/home/mcidas/workdata > F90= > LANG=en_US.UTF-8 > PS1=\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\u@\h:\w\$ > CXX= > SPEECHD_PORT=7561 > MCDATA=/home/mcidas/workdata > HOME=/home/mcidas > SHLVL=2 > MCTABLE_READ=/home/mcidas/workdata/MCTABLE.TXT;/home/mcidas/data/ADDESITE.TXT > CFLAGS=-O > FC=gfortran > VENDOR=-vendor > LOGNAME=mcidas > SSH_CONNECTION=136.145.159.71 40454 136.145.123.167 22 > MCGUI=/home/mcidas/bin > XCD_disp_file=/home/mcidas/workdata/DECOSTAT.DAT > LESSOPEN=| /usr/bin/lesspipe %s > MCPATH=/home/mcidas/workdata:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help > MCENV_POSUC=4456458 > CC=gcc > LESSCLOSE=/usr/bin/lesspipe %s %s > MCENV_NEGUC= > FFLAGS=-O -Wuninitialized -fno-automatic -fno-range-check > _=/usr/bin/env > mcidas@geologia-desktop:~/workdata$ Hmm... the output above may be self-contradictory; we need to run a test to find out: - please make sure that no 'mcenv' instance is running before re-running the test above. The easiest way to do this is to logoff and then log back on, and then run 'env' from a 'mcenv'-created shell. The thing that is contradictory to me is illustrated by the MCPATH and MCENV_POSUC values above: MCPATH=/home/mcidas/workdata:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help MCENV_POSUC=4456458 If the instance of 'mcenv' created the shell (environment), then MCPATH should look like: before running 'mcenv' MCPATH=/home/mcidas/workdata:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help MCENV_POSUC -- undefined after running 'mcenv' MCPATH=/home/mcidas/workdata:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help:/home/mcidas/.mctmp/4456458 MCENV_POSUC=4456458 The fact that /home/mcidas/.mctmp/4456458 was not added to the end of MCPATH indicates that 'mcenv' did not modify MCPATH like it should. The fact that MCENV_POSUC is define says that some instance of 'mcenv' did run. re: > I noticed mcenv is not adding the shared memory id to the end. However > it has created the directory: > > mcidas@geologia-desktop:~/.mctmp$ ls > 1376292 4456458 4522013 I would understand if you were running in the C Shell, but since you are running in BASH, I am left scratching my head. The reason? When running in the C Shell, .cshrc gets read when 'mcenv' runs (sourced). This is the reason that the method I recommend for setting the McIDAS environment for the user 'mcidas' has one _not_ define environment variables directly. Rather, I suggest that one sources a file from the McIDAS distribution to set needed environment variables. This process is described in the Unidata McIDAS Users Guide: Unidata HomePage http://www.unidata.ucar.edu McIDAS HomePage http://www.unidata.ucar.edu/software/mcidas Unidata McIDAS-X Users Guide http://www.unidata.ucar.edu/software/mcidas/current/users_guide/toc.html Installing McIDAS-X on Unix or Mac OS X Workstations http://www.unidata.ucar.edu/software/mcidas/current/users_guide/InstallingMcIDAS-XonUnixorMacOSXWorkstations.html#63755 Preparing the mcidas Account http://www.unidata.ucar.edu/software/mcidas/current/users_guide/PreparingthemcidasAccount.html#22841 re: reference to Lucid > Sorry about this one I should have been more specific, I was referring > to Ubuntu 10.04 Lucid Lynx. Its a Long Term Support (LTS) Release, > thats why I chose to use it as my server. OK, it is just the name of the Ubuntu release. No problem... By the way, if we can't resolve things through the back and forth email exchanges, I am happy to logon to your machine and check things out. To do this, I would need the login information for the 'mcidas' account sent to my private email address, address@hidden, in the following way: one email with the name of your machine and another email with the password for the 'mcidas' account. Each email should _NOT_ reference information in the other email (i.e., don't include the user name or password in the same email as which machine they are valid for). 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: DPX-653014 Department: Support McIDAS Priority: Normal Status: Closed