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

[McIDAS #QNI-213974]: IMGCHA problems

Hi Paul,

I had a couple of minutes yesterday to logon to weather.cod.edu to see what I 
could
see.  Here are items that jumped out at me (the first comments were from 
yesterday;
newer ones follow after them):

- first, I am guessing that weather.cod.edu is _not_ the machine to be
  logged onto since I do not see McIDAS being executed from the LDM
  that is running there.

  Question:

  - should I be looking at the setup on climate.cod.edu?

- the MCDATA directory for the user 'mcidas' was set to be /workdata.  Since
  this directory does not exist, I think that this is a mistake caused
  by defining environment variables needed by McIDAS in ~mcidas/.bashrc
  and by sourcing ~mcidas/admin/mcidas_env.sh in ~mcidas/.bash_profile

  I suggest that the defines in ~mcidas/.bashrc be removed -- they are
  not needed because of the sourcing of ~mcidas/admin/mcidas_env.sh
  in ~mcidas/.bash_profile.

- VENDOR is defined in ~mcidas/.bash_profile to be '-g77'.  There does
  not appear to be a 'g77' Fortran compiler installed on your machine,
  but there is a 'gfortran' compiler.

Comments from Wednesday, February 9:

- I logged onto climate.cod.edu as 'mcidas' and believe that this
  is where I should have been all along

- when I checked the DATALOC table (DATALOC LIST) I see that RTPTSRC
  was being gotten from adde.ucar.edu.  This reinforces my view that
  climate.cod.edu is the correct machine to be investigating.

- I changed the DATALOC table to point at the locally decoded POINT
  data:

  cd $MCDATA
  dataloc.k ADD RTPTSRC LOCAL-DATA

  I then verified that I can get current data:

mcidas@climate:~/workdata$ sfclist.k KDEN 24
 Day Time StCo  Stn   T  Td  Dir Spd Gus AltSet  Vis  Weather  Ceil
     hhmm        id  [F] [F]     [ kts ]  [mb]   [mi]
---- ---- ---- ----- --- --- --- --- --- ------ ----- -------- -----
   8 2353 COUS KDEN    3  -4 340   3     1021.7  2.00 S-       8/011
S  9 0035 COUS KDEN    1  -4 360   4     1022.3  2.00 S-       5/015
   9 0053 COUS KDEN    1  -5 340   5     1022.7  2.00 S-       5/019
S  9 0057 COUS KDEN    1  -6 360   4     1022.7  3.00 S-       5/022
S  9 0115 COUS KDEN    0  -6 350   4     1023.4  6.00 S-       5/060
   9 0153 COUS KDEN    0  -5 020   4     1023.7 10.00          8/110
S  9 0221 COUS KDEN    0  -6 020   4     1023.7  4.00 S-       5/025
S  9 0225 COUS KDEN    0  -6 040   3     1023.7  1.80 S-       5/025
   9 0253 COUS KDEN    1  -4 020   4     1024.0  1.80 S-       5/025
S  9 0258 COUS KDEN    1  -4 030   4     1024.0  6.00 S-       5/025
S  9 0337 COUS KDEN    1  -6 010   4     1024.4  2.50 S-       8/027
   9 0353 COUS KDEN    0  -5 360   5     1024.4  2.50 S-       8/027
S  9 0354 COUS KDEN    0  -6 360   5     1024.4  4.00 S-       8/027
S  9 0423 COUS KDEN    0  -6 350   4     1024.4  6.00 F        5/030
   9 0453 COUS KDEN    1  -4 330   4     1024.4  8.00
S  9 0526 COUS KDEN    0  -6 290   6     1024.0  7.00
   9 0553 COUS KDEN   -1  -6 260   3     1024.4  8.00
   9 0653 COUS KDEN   -3  -8 260   3     1024.4  7.00
   9 0753 COUS KDEN   -5  -9 250   4     1024.7  5.00 F
S  9 0821 COUS KDEN   -6  -9 240   6     1024.4  1.50 F        8/001
S  9 0836 COUS KDEN   -6  -9 250   6     1024.4  1.50 F        5/006
S  9 0845 COUS KDEN   -6  -9 260   6     1024.4  3.00 F        5/006
   9 0853 COUS KDEN   -4  -8 260   5     1024.4  4.00 F        5/006
   9 0953 COUS KDEN   -6 -10 230   8     1024.7  7.00          5/006
S  9 0959 COUS KDEN   -6 -11 230   8     1024.7  8.00
   9 1053 COUS KDEN   -5 -11 240   9     1024.0  9.00
   9 1153 COUS KDEN   -6 -12 230  10     1024.4  9.00
   9 1253 COUS KDEN   -5 -13 230   9     1024.4  8.00
   9 1353 COUS KDEN   -5 -13 220  12     1024.0 10.00
   9 1453 COUS KDEN   -3 -11 220  11     1024.0 10.00
   9 1553 COUS KDEN    1  -8 230  14     1023.7 10.00
   9 1653 COUS KDEN    6  -5 220  10     1023.4 10.00
   9 1753 COUS KDEN   11  -3 210  10     1023.4 10.00
Number of reports = 33
sfclist.k: done

So, _if_ you were having problems accessing surface data from the
'mcidas' account previously, it appears that the problem has been
cleared-up.

Questions:

- did you do anything to get the 'mcscour.sh' scouring working
  again from the LDM account on climate?

- are you still seeing problems that you want me to look into,
  or have you figured out and corrected the problem that had
  been there?



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