[McIDAS #HQH-586893]: mcidas-x download forbidden

Hi Jim,

re:
> OK, so I'm inching closer, I think.  I switched back to tcsh since that's
> what I'm used to using.

OK.  The shell used should have no effect on building or using McIDAS.

re:
> I did miss the bit about adding code to the
> .tcshrc  file that sources mcidas_env.csh and then sourcing it.  So now
> that gets me all those ^MC variables defined but there still seems to be
> one small glitch.

Just so you know, this is the most frequent gotcha that I see reflected
in inquiries we get about McIDAS.

re:
Let me start from a fresh install.
> 
> *Before unpacking*
> [kubuntu-kitchen]:/home/mcidas> ls -l
> total 126780
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Desktop
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Documents
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Downloads
> -rw-rw-r-- 1 mcidas mcidas 129763555 Feb 13 13:20 mcidasx2018.tar.gz
> -rw-rw-r-- 1 mcidas mcidas     17706 Feb 13 13:20 mcinet2018.sh
> -rwxrwxr-x 1 mcidas mcidas      3406 Feb 13 13:20 mcunpack
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Music
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Pictures
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Public
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Templates
> drwxr-xr-x 2 mcidas mcidas      4096 Feb 13 13:16 Videos
> [kubuntu-kitchen]:/home/mcidas> env | grep ^MC
> [kubuntu-kitchen]:/home/mcidas> env | grep Mc
> McINST_ROOT=/home/mcidas
> [kubuntu-kitchen]:/home/mcidas> env | grep VEN
> VENDOR=-gfortran
> [kubuntu-kitchen]:/home/mcidas> ./mcunpack >& out.mcunpack

OK.  Just so you know, setting VENDOR at this point is not needed
at this point if the sequence that I laid out is followed, but it 
doesn't hurt.

re:
> *After unpacking*
> [kubuntu-kitchen]:/home/mcidas> ls -l
> total 127644
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 admin
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 bin
> drwxrwxr-x  3 mcidas mcidas      4096 Feb 14 20:04 data
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Desktop
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Documents
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Downloads
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 etc
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 help
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 inc
> drwxrwxr-x  3 mcidas mcidas      4096 Feb 14 20:04 lib
> drwxrwxr-x  3 mcidas mcidas      4096 Feb 14 20:04 man
> drwxrwxr-x  3 mcidas mcidas      4096 Feb 14 20:04 mcidas
> drwxrwxr-x 21 mcidas mcidas      4096 Feb 14 20:04 mcidas2018
> -rw-rw-r--  1 mcidas mcidas 129763555 Feb 13 13:20 mcidasx2018.tar.gz
> -rw-rw-r--  1 mcidas mcidas     17706 Feb 13 13:20 mcinet2018.sh
> -rwxrwxr-x  1 mcidas mcidas      3406 Feb 13 13:20 mcunpack
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Music
> -rw-rw-r--  1 mcidas mcidas    831036 Feb 14 20:04 out.mcunpack
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Pictures
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Public
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 savedata
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 tcl
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Templates
> drwxr-xr-x  2 mcidas mcidas      4096 Feb 13 13:16 Videos
> drwxrwxr-x  2 mcidas mcidas      4096 Feb 14 20:04 workdata

re:
> This mcidas directory puzzles me.  Both /home/mcidas/mcidas and
> /home/mcidas/mcidas/data are created by the mcunpack script while
> mcidasx2018.tar.gz untar's into mcidas2018.

Hmm... Yes, ~mcidas/mcidas/data is created by mcunpack.  I put it in
there explicitly a number of years ago, but at the moment I can't
remember why.  There needs to be a ~/mcidas/data directory for
the non-'mcidas' user, but there doesn't for the 'mcidas' user.
I ** think ** that I included it in case a site decided to install
the package in an account other than 'mcidas'.  This is NOT
recommended, however.

re:
> Meanwhile, admin/mcidas_env.csh creates a bunch of the ^MC variables that
> point to nothing, at least pre-build:
> 
> [kubuntu-kitchen]:/home/mcidas> env | grep ^MC
> MCBIN=/home/mcidas/bin
> MCCOMPRESS=GZIP
> MCDATA=/home/mcidas/workdata
> MCGUI=/home/mcidas/bin
> MCHOME=/home/mcidas
> MCPATH=/home/mcidas/workdata:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help
> MCSRC=/home/mcidas/mcidas/src
> MCSTRETCH=EXP
> MCTABLE_READ=/home/mcidas/workdata/MCTABLE.TXT;/home/mcidas/data/ADDESITE.TXT
> MCTABLE_WRITE=/home/mcidas/data/ADDESITE.TXT
> MCUPDATE=/home/mcidas/mcidas/update
> MCVER=
> 
> In particular, MCVER is not set because the shell script can't find
> /home/mcidas/mcidas/data/VERSION.TXT.
> Any ideas?

There is a "catch-22" in a brand new installation.  The file VERSION.TXT
will not exist in the ~mcidas/data directory until after the package
is built and installed.  Luckily, this environment variable is there
just for ease of knowing which version is being run after it is installed.
After it is installed, and you either logoff and then logon or re-source
your shell specific definition file, it will be set.

This may sound strange, but lots of users of the various packages that
we make available ask how they can determine which version of the software
is being used.

It seems to me that you should now be able to build Unidata McIDAS-X v2018a:

<as 'mcidas'>
cd ~mcidas/mcidas2018/src
make mcx
make install.mcxall

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: HQH-586893
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.