[McIDAS #JTG-722928]: installation error

Hi Justin,

re:
> I didn't create any sort of directories under the user "awips." I just used
> the bash_profile to point to those directories under the mcidas directory.

OK. That was most likely the cause of the problem you ran into.

re: login
> Yes, I will send you the emails with the access information. Thank you for
> taking a look.

No worries.

I just got into your machine and made a couple of quick changes:

<as 'mcidas'>

I deleted all of the specific McIDAS environment variable defines
and left the file with the recommended setup to source the appropriate
environment file for user 'mcidas'.

<as 'awips'>

I deleted all of the specific McIDAS environment variable defines
and left the file with the recommended setup to source the appropriate
environment file for a non-'mcidas' user, and then logged off and
then back in (su - mcidas).

I created the ~awips/mcidas/data directory structure:

cd ~awips
mkdir -p mcidas/data

After logging off and logging back on as 'mcidas', I verified
that the needed environment variables had bee properly set,
and then I made a couple of quick tests:

<as 'awips'>

cd $MCDATA

dataloc.k LIST           <- this was empty as expected

dataloc.k ADD RTIMAGES ATM.UCAR.EDU  <- get RTIMAGES from atm.ucar.edu

dsinfo.k IMAGE RTIMAGES
        Dataset Names of Type: IMAGE in Group: RTIMAGES

Name         NumPos   Content
------------ ------   --------------------------------------
ANTARCTIC     9999    Antarctic Thermal IR POES Composite
ANTARCTICIR   9999    Antarctic Thermal IR POES Composite
ANTARCTICVIS  9999    Antarctic Visible POES Composite
ANTARCTICWV   9999    Antarctic Water Vapor POES Composite
ARCTIC-IR     9999    Arctic Thermal IR POES Composite
ARCTIC-IRL    9999    Arctic Longwave IR POES Composite
ARCTIC-IRS    9999    Arctic Shortwave IR POES Composite
ARCTIC-VIS    9999    Arctic Visible POES Composite
ARCTIC-WV     9999    Arctic Water Vapor POES Composite
GE-1KVIS      9999    GOES-East 1 km 0.63 um Visible
GE-39         9999    GOES-East 3.9 um short IR
GE-CO2        9999    GOES-East 13.3 um IR (CO2)
GE-IR         9999    GOES-East 10.7 um IR
GE-IRTOPO       10    GOES-East IR/TOPO Composite
GE-VIS        9999    GOES-East 0.63 um Visible
GE-VISTOPO      10    GOES-East VIS/TOPO Composite
GE-WV         9999    GOES-East 6.5 um IR (Water Vapor)
GEW-39        9999    GOES-East/West 3.9 um Composite
GEW-CO2       9999    GOES-East/West CO2 Composite
GEW-IR        9999    GOES-East/West IR Composite
GEW-IRTOPO      10    GOES-East/West IR/TOPO Composite
GEW-VIS       9999    GOES-East/West VIS Composite
GEW-VISTOPO     10    GOES-East/West VIS/TOPO Composite
GEW-WV        9999    GOES-East/West H2O Composite
GLOBAL-IR    99999    Global Thermal IR composite images
GLOBAL-WV    99999    Global WV composite images
GW-39         9999    GOES-West 3.9 um short IR
GW-CO2        9999    GOES-West 13.3 um IR (CO2)
GW-IR         9999    GOES-West 10.7 um IR
GW-IRTOPO       10    GOES-West IR/TOPO Composite
GW-VIS        9999    GOES-West 0.62 um Visible
GW-VISTOPO      10    GOES-West VIS/TOPO Composite
GW-WV         9999    GOES-West 6.5 um IR (Water Vapor)
MDR           9999    Manually Digitized Radar
MDRTOPO         10    MDR/TOPO Composite
MOLL-IR       9999    Global Mollweide IR Composite
MOLL-IRTOPO     10    Mollweide IR/TOPO Composite
MOLL-WV       9999    Global Mollweide WV Composite

DSINFO -- done

This simple exercise proves that your McIDAS build works.

Comment:

DATALOC (the binary is ~mcidas/bin/dataloc.k) is used to "point" one's
McIDAS session to a server for a specified dataset.  RTIMAGES is a
standard Unidata dataset that is comprised of the image sectors that
are distributed in the Unidata-Wisconsin datastream (IDD feedtype
UNIWISC aka MCIDAS).

NB:

- McIDAS routines can be run from the command line

  My two examples above exercised this.

- invoking a McIDAS routine creates a McIDAS environment that
  lasts for the duration of the command's execution

  The environment is composed of two shared memory segments that
  are used by McIDAS routines.  The share memory segments are
  torn down when the single command finishes

- you will want/need to configure McIDAS to either/both serve locally
  held data or to "point" at remote servers to access data

  The relevant McIDAS commands are DSSERVE (defines a dataset) and
  DATALOC (defines which server to access for a particular dataset).
  Creation of a dataset definition can be done user-by-user or by
  the user 'mcidas' which should be though of as 'root' for McIDAS.
  'mcidas' can create dataset definitions (via a series of DSSERVE
  commands) that can be used by all McIDAS users.  The simplest
  way for the datasets defined by 'mcidas' to be used by all McIDAS
  users is by setting up the ADDE remote server and having the user
  "point" at the local machine.  This is what essentially is happening
  on each remote ADDE server that you can access.  Data sets were defined
  in the 'mcidas' account on each server, and the ADDE server was setup
  to be able to serve the data to remote connections.  ADDE listens
  on port 112, so that will need to be opened up for this to work on
  your machine (opened to the machine(s) that you want to allow to
  ask for data or for the world).

- the Unidata McIDAS distribution contains a McIDAS BATCH file
  named LOCDATA.BAT  that is a template to be used to setup
  where a McIDAS session will get its data

  The intention is for a user to make a copy of LOCDATA.BAT in
  his/her McIDAS working directory (e.g., ~awips/mcidas/data),
  edit the file and specify where to get the various datasets, and
  then make the DATALOC defines active.  The last step, for example,
  is done as follows:

<as 'awips'>
cd $MCDATA
cp ~mcidas/data/LOCDATA.BAT .
-- edit LOCDATA.BAT and setup where to get various datasets
batch.k LOCDATA.BAT

  After this, a McIDAS session will be setup for access to all of the
  datasets correctly defined in LOCDATA.BAT.

- if you want to run the Unidata McIDAS GUI (MCGUI), then you will want
  to run:

mcidas -config

  The first thing to do is to setup the display size and how many frames
  you want.  My suggestion is that the McIDAS display size (which is
  fixed for a McIDAS session (it is more complicated than this, but
  too much information too early can be off putting :-)) to something
  that fits nicely in your display.  My other suggestion is to setup your
  session with at least 20 frames

The questions to you now are:

- what are your intentions for your McIDAS installation?

  Meaning do you want to setup decoding of data received via the
  LDM?

  Do you want to just use data from one or more remote servers?

NB:

- change your root password as fast as you can!!!!!!!!

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: JTG-722928
Department: Support McIDAS
Priority: Normal
Status: Closed