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

[McIDAS #MET-935016]: McIDAS - Cannot get mcunpack to execute -- keep getting message to define McINST_ROOT



Hi Alan,

> Institution: University of Georgia
> Package Version: McIDAS-X 2005
> Operating System: Fedora Core
> Hardware Information: Dell Dimension Desktop
> Inquiry: I just downloaded McIDAS and used the documentation on preparing the 
> McIDAS
> account and then on Building, Testing, & Installing McIDAS.

Very good.

> As directed, I created an account for mcidas and put it in the same group
> as the account for mcadde.

Just to make sure that we are on the same page, the 'mcidas' account is where 
everything
is done.  The 'mcadde' account is an alias for 'mcidas' with the exception that 
it does
not allow logins.
 
> I put the files in a /mcidas subdirectory of the home folder of the mcidas 
> account.
> This should make the path to the files /home/mcidas.

I think that you are off by one directory level.  (For the "files") the 
procedure is:

- create the 'mcidas' account.  Recommended HOME directory for 'mcidas' is 
/home/mcidas.

- as 'mcidas', download the Unidata McIDAS distribution files, 
mcidasx2005.tar.gz,
  mcunpack, and mcinet2005.sh to /home/mcidas

- change the execute permissions on 'mcunpack':

  <as 'mcidas'>
  chmod +x mcunpack

- set the Unix environment variable McINST_ROOT to the HOME directory of 
'mcidas':

  <as 'mcidas'>

  C shell example:

  setenv McINST_ROOT /home/mcidas

  Bourne, Korn, Bash example:

  McINST_ROOT=/home/mcidas
  export McINST_ROOT

- run 'mcunpack' to unpack the McIDAS-X v2005 distribution:

  <as 'mcidas'>
  cd /home/mcidas
  ./mcunpack
  
> I logged on as mcidas and changed the file permissions for mcunpack so that
> it would execute.

Very good.  But I think you are doing this in the wrong directory.  Please see 
above.

> I could NOT access the chs.cshrc file in /ect as a mcidas user to change the 
> script to
> define McINST_ROOT and vendor.  I had to log on as the root user to do this 
> change in code.

The change you need to make is in /home/mcidas/.cshrc, not in /etc/csh.cshrc.  
You should
remove the additions you made to /etc/csh.cshrc.

> I then restarted the machine (cold boot), logged on as mcidas and then 
> attempted to unpack
> with ./mcunpack.  No matter what I do (changing settings based upon searching 
> the unidata
> site and related emails, etc.), I still get the message from the mcunpack 
> script,
> "You must define McINST_ROOT as the full...."  What am I overlooking or doing 
> incorrectly?

Please either define McINST_ROOT from the Unix command line, or define it in 
/home/mcidas/.cshrc.
If you make the change in .cshrc, then logoff and log back in to make the 
changes take effect
(no need to reboot).

After running 'mcunpack', the simplest thing to do next is edit 
/home/mcidas/.cshrc file
and add the following lines:

# McINST_ROOT and VENDOR non-conforming shell defines needed to build McIDAS
setenv McINST_ROOT $HOME
setenv VENDOR -g77
if ( -e $HOME/admin/mcidas_env.csh ) then
  source $HOME/admin/mcidas_env.csh
endif

After adding these lines, logoff and then log back in.  After logging back in, 
verify
that the environment variables have been set:

<as 'mcidas'>
echo $McINST_ROOT

> Many thanks,..Alan Stewart

No worries.  Please let me know how things go.


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: MET-935016
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.