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

[McIDAS #NJA-425146]: Interesting in McIDAS X Free



HI Boris,

re: You do not want to overwrite these files.
> Thank you very much for the help.

No worries.

re:
> A question then as to know the block number to allocate to each of my copied
> files to my group STORM/SOUNDER?

Setting up the STORM/SOUNDER dataset to be potentially named/populated
with the full range of possible AREA files (which is AREA0001 - AREA9999)
is not bad per se.  In fact it has the benefit that the dataset position
like STORM/SOUNDER.3000 maps directly to the AREA file name, AREA3000
in this case.  If you defined STORM/SOUNDER to be some subset of possible
AREA file numbers (like 4000-4999), then the mapping between dataset
group/descriptor.pos would not be so obvious.  STORM/SOUNDER.1 would
be AREA4000 in this case.  What I wanted to draw your attention to was
the possibility of running into a McIDAS "gotcha" (problem that is hard
to explain to a new McIDAS user).

My advice is to keep your definition for STORM/SOUNDER, but limit yourself
to writing to/creating files in the range 3000-7999.

re:
> IMGCOPY OGOES12/SNDR STORM/SOUNDER.3000 DAY=2004094 BAND=ALL
> 
> run  DMAP AREA300 and I get the following:
> 
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas/bufr: No such file or 
> directory
> WARNING: cannot examine directory /data/ldm/mcidas/grib: No such file or 
> directory
> WARNING: cannot examine directory /data/ldm/mcidas/bufr: No such file or 
> directory
> WARNING: cannot examine directory /data/ldm/mcidas: No such file or directory
> WARNING: cannot examine directory /data/ldm/mcidas/bufr: No such file or 
> directory
> 
> -rw-  11686608  Dec 08 19:50  AREA3000 /home/boris/mcidas/data
> 11686608 bytes in 1 files
> 
> which means that my file AREA3000 has been copied successfully and review
> the directory (hom/boris/mcidas/data) where it was copied and this file is
> actually there.

Yes, exactly.

re:
> But the warnings mean? I consider this warning and install
> something more?

What is happening is the following:

DMAP uses two McIDAS concepts to locate data files:

- MCPATH directories
- REDIRECT redirections

Since your MCPATH (listed below) does not contain the /data/ldm/mcidas
directory, it means that you created a file REDIRECTion that contains
/data/ldm/mcidas.  I assume you did this while working through the
configuration steps that we discussed a few emails back.  Apparently,
the directory /data/ldm/mcidas does not exist on your machine (true?).
You can get rid of these annoying warnings in either of two ways:

- create the directory /data/ldm/mcidas (make sure that it is both
  readable and writable by the user running McIDAS ('boris'?)

- change the file REDIRECTions to get rid of the reference to
  /data/ldm/mcidas (and all of its subdirectories)

  This option is pretty easy to do.  McIDAS file REDIRECTions are
  saved in the file $MCDATA/LWPATH.NAM for each user.  This is a
  simple ASCII text file that you can modify directly with your
  favorite text editor (I use 'vi'; others use 'emacs'; still others
  use something like 'gedit').  Edit $MCDATA/LWPATH.NAM and
  change all occurrences of /data/ldm/mcidas to a directory that
  actually exists.

Comment:

- the 'gotcha' you ran into is a classic problem in McIDAS.  It is
  something that I discuss in detail when I give McIDAS training
  workshops.  I am sorry that you ran into this because it is 
  hard to understand for a new user!!

re:
> effectively  file AREA9996 was successfully copied to the directory
> /home/boris/mcidas/data

For the IMGCOPY command you list above, AREA3000 was successfully created
in your MCDATA directory, /home/boris/mcidas/data.  I assume that your
previous invocation of IMGCOPY created the file AREA9996 in the same
directory.

re:
> effectively the value of MCPATH is configured correctly 
> (/home/boris/mcidas/data:/home/mcidas/data:/home/mcidas/help)

Yes, this is correct.

re:
> MCPATH correct

Yes.

re:
> I set the file AREA3000 to ADDE dataset corresponding and McIDAS V open it
> without any problem

Very good.  This tells me that you are running McIDAS-V and McIDAS-X on
the same machine (true?).

re:a I can help
> I accept your help, because I had problems installing the remote server
> ADDE. In fact I have already created the mcadde account as remote server
> account ADDE. My problem is when I do the following:
> 
> address@hidden mcidas # sh ./mcinet2009.sh  install mcadde
> the following message appears:
> mcinet2009: ERROR: Needs to be restarted xinetd With The comand: service 
> xinetd restart
> 
> execute the order indicated and the following message appears:
> address@hidden mcidas # service xinetd restart
> stop xinetd: ok
> start xinetd: ok
> 
> Rerun the file  mcinet2009.sh and get the same error

I believe I still have the login information you provided to me earlier.
I will logon to your machine (assuming I can find the information)
sometime today and take a look.
re: I recommend copying the data from the SSEC server to your local machine
so you can access the data as much as you like without getting charged

> understood

Very good.

re:
> Thanks

No worries.

I must tell you that I am impressed with how much of McIDAS you have understood
on your own!  McIDAS is a somewhat difficult package to become expert in
especially if you have not had the benefit of attending a training workshop.
The good news is that after a little practice, the concepts in McIDAS become
familiar and easy to understand, AND you should find that you can do pretty
much anything you want in McIDAS (except display things in 3D).

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: NJA-425146
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.