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

[McIDAS #WAZ-899768]: migrating to goes-13



Hi Ed,

re: change your MCDATA directory from the one for 'mcidas' to your own

> then i can't see any images on /ldm unless i run as mcidas
> do i have to do something like ...
> dsserve.k ADD RTIMAGES/GE-IR 
> DIRFILE=/ldm/gempak/images/sat/GOES-1[2,3]/4km/IR/IR*
> or is the fix in my  .cshrc ...
> setenv MCTABLE_READ "$MCDATA/MCTABLE.TXT;$MCHOME/data/ADDESITE.TXT"
> setenv MCTABLE_WRITE ${MCDATA}/MCTABLE.TXT

The "real" way to fix this is to setup metofis to be able to serve
ADDE datasets through the remote interface.  This step is done by
'root' as follows:

<as 'root'>
-- create the user 'mcadde' with HOME directory the same as 'mcidas',
   but don't make it a login account

cd /home/mcidas
sh ./mcinet2009.sh install mcadde

-- make sure that port 112 is open through the firewall (at least for
   local users)

After remote serving of ADDE datasets is enabled, each user (e.g., you)
can "point" to the remote ADDE interface for datasets you want to access.
For instance, you would run the following to configure your McIDAS
sessions to access RTIMAGES from metofis:

<as 'eryan'>
cd $MCDATA     <- your MCDATA or /home2/eryan/mcidas/data
dataloc.k ADD RTIMAGES metofis.rsmas.miami.edu
etc.

If setting up the remote ADDE interface is not possible (Angel could
easily do this if it is desired), then you have two choices:

- include the 'mcidas' MCDATA directory in your MCPATH ** after ** your
  own MCDATA directory:

  
MCDATA=/home2/eryan/mcidas/data:/home/mcidas/workdata:/home/mcidas/data:/home/mcidas/help

- setup ADDE data serving in your own McIDAS setup (by running DSSERVE to 
create ADDE
  dataset definitions

  This step could be jump started by simply copying the McIDAS ADDE dataset 
definition
  backing store file, RESOLV.SRV, to your MCDATA directory:

  <as 'eryan'>
  cd $MCDATA
  cp ~mcidas/workdata/RESOLV.SRV .

  NB: This approach assumes that you change your MCDATA directory to your own.

Again, the problem you are running into when specifying your MCDATA as if you
were the user 'mcidas' is that you do not have write permission in that 
directory
(and you should NOT have write permission in that directory!).

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: WAZ-899768
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.