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

20030522: McIDAS-X v2002 MCGUI (cont.)

>From: "Jennie L. Moody" <address@hidden>
>Organization: UVa
>Keywords:  200305201647.h4KGlULd000828 McIDAS-X MCGUI

Hi Jennie,

>Okay, I was able to turn the text window on/off
>for the Mcidas/Unidata/GUI.

OK, remember that the commands executed from the MCGUI will only be
echoed by the window that is available through mouse button 1 clicks.

>But I still have some
>problem with the way the ADDE is set up....I think
>this is an error for the user mcidas as well as for
>me.  Since dataset are set up to be "served" but
>they are not "located", if this is the right lingo:
>windfall: /home/jlm8h $ su - mcidas
>Sun Microsystems Inc.   SunOS 5.6       Generic August 1997
>You have mail.
>windfall: /home/mcidas $ dataloc.k LIST
>Group Name                    Server IP Address
>ALT                          <LOCAL-DATA>
>ARCHIVE                      <LOCAL-DATA>
>BLIZZARD                     <LOCAL-DATA>
>WNAO                         <LOCAL-DATA>
><LOCAL-DATA> indicates that data will be accessed from the local
>data directory.
>DATALOC -- done

OK, this says that the ALT, ARCHIVE and WNAO datasets will all be
accessed as LOCAL-DATA.  This is OK.

>windfall: /home/mcidas $ dsserve.k LIST
>Group/Descriptor         Type  Format & Range     RT Comment
>------------------------ ----- ------------------ --
>ALT/ARC12E               IMAGE AREA 8276-8300        Archived
>altwv: MRF init
>ALT/ARC12W               IMAGE AREA 8251-8275        Archived
>altwv: MRF init
>ALT/ARC6E                IMAGE AREA 8226-8250        Archived
>altwv: MRF _foreca
>ARCHIVE/GE-WV            IMAGE AREA 2051-2099        Most recent
>48 hours of GOE
>CIMSS/CAPE               IMAGE AREA 1140-1149        CIMSS CAPE
>CIMSS/CTP                IMAGE AREA 1100-1109        CIMSS Cloud
>Top Pressure pr
>MYDATA/PTSRCS            POINT MD   1-9999           All MDXX
>PEL/ETA                  GRID  GRID 1001-1118     Y  Pellston ETA


>When I try to configure my own session (train the GUI), I got the
>following for trying to set RTGRIDS (for example) to local-data:
>(not sure why the update and exit on RTGRIDS tries to add
>everything, but this is the response generated in the Console
>window of the GUI)

The MCGUI tries to see if the DATALOCs in your session are different
from what is set in the ADDE Client Config GUI and then change all
that are different.

>DATALOC: Problem writing strings, probable setup error
>DATALOC failed, RC=2

This tells me that the enviornemnt is not quite setup correct.y.

>I looked at the /home/mcidas/.variables.ksh file and found
>the MCTABLE_READ file, which should be
> /home/mcidas/uvaworkdata/MCTABLE.TXT

The MCTABLE_READ environment variable is typically setup to read more
than one file to find hosts for datasets.  The typical setup would


>windfall: /home/mcidas $ more uvaworkdata/MCTABLE.TXT

These are the settings that Tony must have had in place.

>the other file it should look at 
> /home/mcidas/data/ADDESITE.TXT
>doesn't exist.  

ADDESITE.TXT's entries get created by DATALOCs done by 'mcidas' _if_
its MCTABLE_WRITE is set tp write it:


>I guess this is what I need to fix

Actually, I think the problem has something to do with the message

>DATALOC: Problem writing strings, probable setup error
>DATALOC failed, RC=2

>.....can you
>give me a hint (I know I could go dig around
>reading the manuals, but.....point me in the
>right direction??)

The cause of the "Problem writing stings" error does not jump to
mind immediately.  I have to think that something small is missing
in the environment for 'mcidas' (since the output above is for
'mcidas', right?).  I may need to login and poke around to figure
out exactly what it is.  This may have to wait until tomorrow.


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.