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

Hi Jim,

re:
> After some additional fiddling I think I've got the runtime environment for
> mcidasx set up.

OK, great.

re:
> Now I'm trying to display some local area files and having
> some difficulty.  I've pored over the mcidasx manual but I'm not being met
> with any success thus far.
> 
> Could you point me in the direction of a tutorial on how to display local
> area files in mcidasx?

Under the McIDAS portion of the Unidata website under Documentation are
links for:

User's Guide
Learning Guide
Training Workshop

You could slog through this material and figure things out, but I think it
will be quickest if I give a brief overview of how data is accessed in
McIDAS first.

1. access to the forms of data supported by McIDAS is provided through
   the Abstract Data Distribution Enviornment (ADDE)

   ADDE is a server interface for the types of data supported:

   IMAGE, POINT, GRID and TEXT

2. one must create ADDE datasets from the data that s/he wants to
   be able to view/analyze

   An ADDE dataset is exactly like it sounds: sets of data, or
   said another way, sets of data of like kinds

3. McIDAS provides a utility, DSSERVE, that creates a persistent
   table that defines the sets of data/datasets that McIDAS can
   visualize/analyze

   The absolutely best thing about ADDE is that it can provide
   access locally or via remote TCP access.

   Setting up remote access requires some actions to be performed
   by 'root', but local access is done in the local account.

So, what is meant by creating a dataset?

One uses the DSSERVE utility to tell McIDAS where to find sets of
like files, what type of data is in the files, potentially how many
elements there can be in the dataset, and provide a human readable
description for the data.

Let's take a concrete example...

You said that you want to use McIDAS to verify the integrity of
some image files you get/have gotten from the UW/SSEC Data Center.
The first question to be answered is what is the naming convention
that was used for the files?

Examples:

Historically named image files of the form AREAnnnn, where nnnn is
a 4-digit number that can range from 0001 to 9999 (NB: nnnn is
always a 4-digit number!)

AREA0001
...
AREA1234
...
AREA9999

Images that are in the McIDAS AREA file format, but named differently:

10.7_20181009_1845
etc.

Let's assume that you got a number of images from the SSEC Data Center
that are all from the same satellite.  Let's further assume that the
images are all in files that follow the AREAnnnn naming convention.
The easiest thing to do is to create a directory somewhere on a disk
that your McIDAS session can access (meaning read).  Let's call this
directory:

/home/mcidas/workdata/Meteosat-8

Put all of the Meteosat-8 images you got from SSEC in this directory,
and make sure that they are readable by 'mcidas'.

The simplest form of an ADDE dataset for this set of images can
be created from within a running McIDAS-X interactive session as
follows:

DSSERVE ADD MET8/IMAGES AREA TYPE=IMAGE 
DIRFILE=/home/mcidas/workdata/Meteosat-8/AREA* "Meteosat-8 images from UW/SSEC

DSSERVE     - the utility
ADD         - the action which says add a definition to a table (RESOLV.SRV)
MET8/IMAGES - the ADDE dataset name which is composed of a group name of MET8
              and a descriptor of IMAGES
AREA        - the format of the image is AREA
TYPE=IMAGE  - the files are images; NB: this is redundant if the format is AREA
DIRFILE=    - a regular expression that describes the set of images you want 
included
              in the dataset MET8/IMAGES
"Meteo...   - a human readable comment

After doing this, you should then be able to run:

IMGLIST MET8/IMAGES.ALL

and get a listing of all of the images you put in the 
/home/mcidas/workdata/Meteosat-8
directory.

Please let me know that you have been successful in the above.

Next, it is more convenient to further organize the sets of images
(this applies to other data types, but let's focus on imagery for now).
Let's assume that you have images for different wavelength channels;
perhaps AREA0001 - AREA0009 are VISible images.  You can create an
ADDE dataset definition for those VIS images as follows:

DSSERVE ADD MET8/VIS AREA TYPE=IMAGE 
DIRFILE=/home/mcidas/workdata/Meteosat-8/AREA000\. "Meteosat-8 VIS images from 
UW/SSEC

Since McIDAS understands the traditional AREAnnnn naming convention, this
same dataset definition can be made in a slightly different way:

DSSERVE ADD MET8/VIS AREA 1 9 "Meteosat-8 VIS images from UW/SSEC
This tells McIDAS that the set of files is the namespace:

AREA0001
AREA0002
 ...
AREA0009

Notice that I did not include the TYPE=IMAGE keyword since McIDAS understands
that files of type AREA are images.

Please try some of these dataset definitions and then let me know if you
are then able to do things like:

IMGLIST MET8/IMAGES.ALL FORM=ALL

IMGDISP MET8/IMAGES.1; MAP

etc.

> Thanks,
> 
> -Jim
> 
> On Fri, Feb 15, 2019 at 7:01 PM Jim Schlemmer <address@hidden>
> wrote:
> 
> > Yee-ha!
> >
> > I installed all those libraries, used the new makefile, and started from
> > make clobber.  It made and installed without a hitch, or at least any
> > hitches that I'm aware of.
> >
> > See attached screenshot.  And for all your work I offer you this:
> >
> > [image: image.png]
> >
> > -Jim
> >
> > address@hidden> wrote:
> >
> >> Hi Jim,
> >>
> >> re:
> >> > OK, thanks, Tom.
> >> >
> >> > I ran with that makefile and it seemed to cruise past the netcdf stuff.
> >>
> >> Progress, I love it :-)
> >>
> >> re:
> >> > It then hit upon the rocks of the next issue:
> >> >
> >> > gcc -c -g -I. -I../netcdf/libsrc -I../netcdf/include -I../hdf5/src
> >> > -I../hdf5/hl/src -I../hdf/hdf/src -I../hdf/mfhdf/libsrc -I../jpeg
> >> -I../zlib
> >> > -I../tiff/libtiff -I../
> >> > libgeotiff -I../jasper/src/libjasper/include -I../g2clib -I../libpng
> >> > -I../bzip2 enh24.c
> >> > enh24.c:9:10: fatal error: X11/Xlib.h: No such file or directory
> >> > #include <X11/Xlib.h>
> >> >
> >> > I don't think I have the X11 libraries on my system so I'm wondering if
> >> > mcidas is looking for the one in /home/mcidas/mcidas2018/tk/xlib.
> >>
> >> No, you have to install the X develoopment stuff on your machine.
> >>
> >> re:
> >> > I'll try the new makefile but on the chance that the above is an
> >> > independent error, I'll include the makelog from this last run.
> >>
> >> The latest error is being caused by the lack of an X development
> >> installation on your machine.  Since this is not included as part
> >> of the McIDAS distribution, you will need to install it as 'root'.
> >>
> >> Here is the list of things I needed to install on my Ubuntu
> >> v14.04 LTS machine:
> >>
> >> For Ubuntu 14.04
> >>
> >> apt-get update
> >>
> >> Development
> >> --------------------------------------
> >> gcc            - already installed
> >> gfortran       - apt-get install gfortran
> >> gcc-c++        - g++ already installed
> >> byacc          - bison already installed
> >> flex           - flex already installed
> >> libX11-dev
> >> libXt-dev
> >> libXext-dev
> >>
> >> ncurses         - libncurses5 already installed
> >> ncurses-devel   - apt-get install libncurses5-dev
> >>
> >> kernel-devel
> >> kernel-headers
> >>
> >> Fonts
> >> --------------------------------------
> >> xorg-x11-fonts-misc     <- for mctext
> >> xorg-x11-fonts-100dpi   <- for McGUI
> >> xorg-x11-fonts-75dpi    <- for McGUI
> >>
> >> What you may need to install depends on what is already installed on
> >> your machine.
> >>
> >> You should be able to install the packages above and continue the build
> >> where it left off.  At worst, you may need to restart the build from
> >> the beginning:
> >>
> >> <as 'mcidas'>
> >> cd ~mcidas/mcidas2018/src
> >> make clobber
> >> make mcx
> >> make install.mcx
> >>
> >> 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.
> >>
> >>
> >>
> 
> 

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.