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

[McIDAS #YNR-509460]: ADDELIST.TXT errors



HI Carol,

re:
> I've been having lots of great success running mcidas as the ldm user in
> our new setup. Until now, we've only been using local data, so we weren't
> adding any external servers to our ADDE list. Now, we are interested in
> getting the HIMAWARI data from CIRA. Greg got the group/descriptors all
> setup as the mcidas user on our server. Here is an output of imglist for
> band 13 as the mcidas user.
> 
> address@hidden data]$ imglist.k CIRA-H2/FLDK FORM=ALL BAND=13
> Image file directory listing for:CIRA-H2/FLDK
> Pos Satellite/         Date       Time      Center      Res (km)
> Image_Size
> sensor                                 Lat  Lon    Lat   Lon
> --- -------------  ------------  --------  ---- ----  ----- -----
> ------------
> 143  HIMAWARI-8     8 JUN 20160  16:40:00     0 -141
> Band: 13   10.4 um IR Surface/Cloud-top Temp         2.00  2.00  5500 x
> 5500
> proj:    0 created: 2020160 164000  memo: HIMAWARI-8 Full Disk
> type:WARI     cal type:RAW
> offsets:  data=    1280 navigation=  256 calibration=  768 auxiliary=
> 0
> doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
> valcod:          0 zcor:  0 avg-smp: A
> start yyddd: 2020160  start time:164000  start scan:    0
> lcor:    1  ecor:     1  bytes per pixel: 2  ss: 86
> Resolution Factors (base=1):   Line=    4.0   Element=    4.0
> imglist.k: done
> 
> Then as the ldm user, I'm using a mcenv_setup script to get all the
> necessary attributes from the mcidas user's mcidas environment.
> Unfortunately, now when I run this script I get these errors from the new
> CIRA dataset.
> 
> 102 typhoon:/usr/local/ldm/scripts->
> /usr/local/ldm/scripts/setup_mcenv_him.sh himawari_fd_C13.log 1200 1600
> /usr/local/ldm/scripts/configs/acclip_fd_ir_13.cfg
> /home/mcidas/data/ADDESITE.TXT: line 6: ADDE_ROUTE_CIRA-H2=
> RAMMB-AHI2.CIRA.COLOSTATE.EDU: command not found
> /home/mcidas/data/ADDESITE.TXT: line 8: HOST_RAMMB-AHI2.CIRA.COLOSTATE.EDU=
> 129.82.109.12: command not found
> 
> Here is the whole ADDESITE.TXT file.
> 
> ADDE_ROUTE_EOLGOESR=LOCAL-DATA
> ADDE_ROUTE_BOMHIM=LOCAL-DATA
> ADDE_ROUTE_RTGOESR=LOCAL-DATA
> ADDE_ROUTE_RTGOESS=LOCAL-DATA
> ADDE_ROUTE_MYDATA=LOCAL-DATA
> ADDE_ROUTE_CIRA-H2=RAMMB-AHI2.CIRA.COLOSTATE.EDU
> HOST_LOCALHOST=127.0.0.1
> HOST_RAMMB-AHI2.CIRA.COLOSTATE.EDU=129.82.109.12
> 
> I have the following lines of code in my mcenv_setup script to get the ADDE
> table.
> MCTABLE_READ=$MCDATA/MCTABLE.TXT;$MCHOME/data/ADDESITE.TXT

I think that your definition for McTABLE_READ needs to be surrounded by 
quotes:

MCTABLE_READ="$MCDATA/MCTABLE.TXT;$MCHOME/data/ADDESITE.TXT"

If the quotes are left out, then the semi-colon will be interpreted by
the shell as a command separator.

re:
> 
> ... where $MCHOME = /home/mcidas
> 
> Thus, the mcidas user can properly read the CIRA-H2 group, but when I try
> to set up the same environment for the ldm user, the ldm user can't read in
> the CIRA-H2 group.
> 
> Is this some kind of permission issue that ldm user can't read the CIRA
> dataset?

No.

re:
> Thanks for your help in advance.

Try changing your McTABLE_READ definition to what I showed above and let
me know the outcome.

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: YNR-509460
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.



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.