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

[McIDAS #CJO-774097]: Mcidas 2007 build

Hi Bill,

re:
> Since Feb 19, we have not been able to access any of the RTGRIDS or
> RTGRIBS datasets on the ADDE servers.  DSINFO GRID gives a few
> descriptions of a few datasets (AWMSRC or whatever, then that places
> like GOES datasets have no grids etc) then just totally hangs-dead.
> Exiting mcidas leaves DSINFO running as a process.  I've moved DATALOC
> around to various sites with no success.

Hmm... This is very strange indeed.  I just did some quick spot checks
of current data availability in the RTGRIDS dataset on adde.ucar.edu, and
think things are OK:

DATALOC LIST RTGRIDS

Group Name                    Server IP Address
--------------------         ----------------------------------------
RTGRIDS                      ADDE.UCAR.EDU

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done
 
DSINFO G RTGRIDS

        Dataset Names of Type: GRID  in Group: RTGRIDS

Name         NumPos   Content
------------ ------   --------------------------------------
ALL           1310    Real-Time Grids
ECMWF           10    Real-Time ECMWF Grids
GFS            300    Real-Time GFS/AVN Grids
MDR             10    Real-Time MDR Grids
MISC            10    Other Real-Time Grids
NAM            120    Real-Time ETA Grids
NGM             40    Real-Time NGM Grids
RUC             80    Real-Time RUC Grids
UKMT           110    Real-Time UK Met Grids

DSINFO -- done
 
GRDLIST RTGRIDS/GFS
Dataset position 1      Directory Title= ALL  00Z GFS 0  HR<=VT<=24 HR
PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME    GRID  PRO
---- ---------- ------------ -------- ---- ---- ------------ -------- ----- ----
U      700 MB   20 FEB 08051 00:00:00  GFS    0 20 FEB 08051 00:00:00     1 PS
Number of grids listed = 1
GRDLIST - done
 
GRDLIST RTGRIDS/GFS DAY=52
Dataset position 2      Directory Title= ALL  00Z GFS 0  HR<=VT<=24 HR
PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME    GRID  PRO
---- ---------- ------------ -------- ---- ---- ------------ -------- ----- ----
Z      300 MB   21 FEB 08052 00:00:00  GFS    0 21 FEB 08052 00:00:00     1 PS
Number of grids listed = 1
GRDLIST - done
 
GRDLIST RTGRIDS/RUC DAY=52
Dataset position 2      Directory Title= ALL  00Z MAPS
PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME    GRID  PRO
---- ---------- ------------ -------- ---- ---- ------------ -------- ----- ----
WP     700 MB   21 FEB 08052 00:00:00 MAPS    0 21 FEB 08052 00:00:00     1 LAMB
Number of grids listed = 1
GRDLIST - done
 
GRDLIST RTGRIDS/MISC DAY=52
Dataset position 2      Directory Title= Misc. Grids for 21 FEB 2008
PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME    GRID  PRO
---- ---------- ------------ -------- ---- ---- ------------ -------- ----- ----
PCP  SFC        21 FEB 08052 12:00:00    x    6 21 FEB 08052 18:00:00     1 PS
Number of grids listed = 1
GRDLIST - done

GRDLIST RTGRIDS/GFS PAR=Z LEV=500 DAY=52
Dataset position 2      Directory Title= ALL  00Z GFS 0  HR<=VT<=24 HR
PAR  LEVEL      DAY          TIME     SRC  FHR  FDAY         FTIME    GRID  PRO
---- ---------- ------------ -------- ---- ---- ------------ -------- ----- ----
Z      500 MB   21 FEB 08052 00:00:00  GFS    0 21 FEB 08052 00:00:00     3 PS
Number of grids listed = 1
GRDLIST - done
 
SF 1
 
GRDDISP RTGRIDS/GFS PAR=Z LEV=500 DAY=52
GRDDISP: Done with graphic frame 1
GRDDISP - done

Please give me some representative GRIDLIST and/or GRDDISP command lines you are
running so I can check the RTGRIDS data availability further.

By the way, I am aware that ADDE grid serving (RTGRIBS) on adde.cise-nsf.gov
is not working.  I just did a quick check of idd.unl.edu, and see that there
is something amiss with its serving.  I will investigate...

> Sooo...since I'm still running Mcidas 2005, and we've corresponded
> before that I need to upgrade, and I've been procrastinating for years,
> now is the time.  Grabbed, unpacked, etc, Mcidas 2007, and a 'make mcx'
> ends with the stuff below after about 1400 lines.

OK.

> I'm still at Fedora Core 4 and the compilers that come bundled with
> that, an old castoff machine, and I suspect that's the issue.   It looks
> like perhaps the C compiler or FORTRAN compiler may have added options
> not previously recognized.

Exactly.

> At this point I am busily examining what to
> do to update to the latest Fedora release.  Just wanted to check if you
> had any recommendations for upgrade do's and don'ts.  I note that the
> current Unidata pages indicate support for Core 6 and the Fedora website
> lists release 8.  So any advice, solicited or otherwise,  is always most
> welcome.

We try to keep current with Fedora releases, and Fedora 8 is the current
version that is supported by RedHat/Fedora.  Fedora 6 is no longer getting
code updates, so it is best to not move to it.  Looks like we need to update
our web page(s) to reflect the fact that we no longer recommend moving
to Fedora Core 6 and previous releases.

I recommend upgrading to Fedora 7 or 8, and I would strongly lean towards 
Fedora 8
since it is the current release. I must quickly add, however, that we have not 
upgraded
from Fedora Core 4 to Fedora 8; we have upgraded from Fedora Core 5 and 6 to 
Fedora 8
on office machines with good success.  Also, we just upgraded my home 
development platform
from Fedora Core 6 to Fedora 8.  I say 'we' since the machine I am using is old
enough to not support booting from a DVD drive, and Fedora 7 & 8 uses DVD
media for its distribution.  Because of this, I had to bring my machine into
the office so I could do a web-based update.  We did run into several snags
doing the upgrade, but those were because:

1) we booted a Fedora Core 6 CD and then ran the upgrade

2) we simultaneously wanted to move away from the older Fedora Core use
   of a /boot partition

3) we did not tell the installation process to update the boot loader
   configuration

Item 3) was a BIG mistake.  It is what caused both of our system administrators 
to
become involved in the upgrade AND for the upgrade to take two days of work to
figure out what went wrong.

So, as per your request, I recommend that you:

- stick with use of the /boot partition for the boot stuff
- have the upgrade process update the boot loader
- consider purchasing a new disk and starting from scratch.  Installing from 
scratch
  is typically much easier than upgrading from an older distribution.  The only
  hitch with this is you need to make sure to install all of the development
  libraries (e.g., X, ncurses, compilers, etc.).

> Thanks for your help.

No worries.  Please keep reading...

re:
> ./mccomp -O -vendor -I. -I../netcdf/libsrc -I../hdf/hdf/src
> -I../hdf/mfhdf/libsrc -I../jpeg -I../libpng -I../zlib -I../tiff/libtiff
> -I../libgeotiff -I../jasper/src/libjasper/include -I../g2clib -c
> convdlmf.f
> 
> mccomp: Using default optimizations
> 
> rm -f convdlmf.o
> 
> gfortran -c -O -Wuninitialized -fno-automatic -fno-range-check -O -I.
> -I../netcdf/libsrc -I../hdf/hdf/src -I../hdf/mfhdf/libsrc -I../jpeg
> -I../libpng -I../zlib -I../tiff/libtiff -I../libgeotiff
> -I../jasper/src/libjasper/include -I../g2clib convdlmf.f
> 
> f951: error: unrecognized command line option "-fno-automatic"
> f951: error: unrecognized command line option "-fno-range-check"
> 
> compile convdlmf.f:            FAILED

I ran into this (and more) while in putting on a McIDAS training workshop at 
the CPTEC
installation in Brazil at the beginning of December.

If you want to continue to build McIDAS v2007 on Fedora Core 4, you can do the 
following:

<as 'mcidas'>
cd ~mcidas/admin
-- edit mcidas_env.csh or mcidas_env.sh (choose the one that corresponds to the 
shell you
   are using: mcidas_env.csh for Csh and Tcsh; mcidas_env.sh for Bash, Sh, or 
Ksh)

   modify the FFLAGS definition under the gfortran section:

change:

else if ( "$VENDOR" == "-gfortran" ) then
  # echo Setting -gfortran compilation options...
  setenv CC       gcc
  setenv CPPFLAGS "-DNDEBUG -Df2cFortran"
  setenv CFLAGS   "-O"
  setenv CXX      ""
  setenv CXXCPP   ""
  setenv FC       gfortran
  setenv FFLAGS   "-O -Wuninitialized -fno-automatic -fno-range-check"
  setenv F90      ""

to:
else if ( "$VENDOR" == "-gfortran" ) then
  # echo Setting -gfortran compilation options...
  setenv CC       gcc
  setenv CPPFLAGS "-DNDEBUG -Df2cFortran"
  setenv CFLAGS   "-O"
  setenv CXX      ""
  setenv CXXCPP   ""
  setenv FC       gfortran
  setenv FFLAGS   "-O -Wuninitialized"
  setenv F90      ""

  After making this change, logoff and then log back in again to make the 
FFLAGS definition
  active.

cd ~mcidas/mcidas2007/src
make clobber
make mcx

Please let me know if changing FFLAGS was sufficient to get you going.

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