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

20011019: IMGDISP problems (cont.)

>From: Giovanni Leoncini <address@hidden>
>Organization: SJSU
>Keywords: 200110181917.f9IJHA119842 McIDAS IMGDISP ADDE


>thanks for your response!!! ;)

You are welcome.

>now, my first problem:

re: MAP: Unable to find a NAV start point in image
>I followed your instructions, found a Frame1.0 file (how could you 
>possibly know that?) and deleted it,

This is an error that seems to crop up for C shell McIDAS users.

>but MAP gives me the same message.

OK, so we havn't found the problem yet.

>DMAP Frame now gives me this:
>DMAP Frame                                                                    
>WARNING: cannot examine directory /home/mcidas/data: No such file or
>WARNING: cannot examine directory /home/mcidas/data/tutorial: No such file
>or directory  
>WARNING: cannot examine directory /home/mcidas/data/tutorial: No such file
>or directory  
>WARNING: cannot examine directory /home/mcidas/data/tutorial: No such file
>or directory  
>WARNING: cannot examine directory /data3/ldm/surface/front: No such file
>or directory    
>WARNING: cannot examine directory /data3/ldm/surface/front: No such file
>or directory    
>PERM      SIZE LAST CHANGED FILENAME  DIRECTORY                               
>---- --------- ------------ --------- ---------                               
>-rw-      3072 Oct 19 10:15 Frame1.0  /export/home/met171/.mctmp/14507   
>and so on with the temporary files.

This is telling us that your MCPATH setting is incorrect or you have
one or more file REDIRECTions that point to non-existent directory locations.
Neither of these situations, however, would cause the MAP error that you
are reporting.

For review, your MCPATH should be set to look like:



MCDATA -> $HOME/mcidas/data

MCHOME -> ~mcidas

>is there anything I should set?

If your shell is the C shell, edit .cshrc and make sure that MCPATH is set
correctly.  Then, start a McIDAS session and check your file REDIRECTions:


Change the REDIRECTions that contain the directories listed above to
the correct directories (or delete the REDIRECTions that are bad):

REDIRECT ADD <file> "correct_directory

- or -


where <file> is the file with the bad REDIRECTion.

Back to your MAP problem.  The DMAP listing above shows that the Frame1.0
file is in the correct directory: a directory that is created for you
by the McIDAS startup process.  Since the file was correctly created,
you _should_ be able to load images, display maps, etc.

From you new session, run:

SF 1

Does this work?  If not, we still some fundamental problem with your
setup.  If it does, then retry an IMGDISP followed by a MAP.

Just to make sure about the integrity of your McIDAS installation and
your personal environmental settings, try loading an image from a remote
ADDE server:


If this works, we can move on to your specific problem which may have
something to do an improperly setup ADDE dataset.

>2nd problem (maybe)
>> I do not understand this comment, 
>I apologize, I haven't been clear! 
>let me try again:
>when I try to display one of those images
>> >http://metsun1.met.sjsu.edu/~leoncini/images/NCAL_010713_2130
>> >http://metsun1.met.sjsu.edu/~leoncini/images/VIS_010713_0025

The way you list the files makes me uneasy.  In order for McIDAS to
be able to display images, an ADDE dataset has to be made that tells
McIDAS how to associate a dataset group name/descriptor with actual
files.  If this step has not been done, you will not be able to look
at those images.

>mcidas doesn't do anything, no messages of any sort, nothing, but in the
>list of processes I can find the command I type (IMGDISP ...) and

What is the exact IMGDISP command that you are trying to run?  This might
help clear up the dataset definition issue quickly.

>hope it's clear, let me know if not!

Its OK.  As soon as I see your IMGDISP command line, I will know if
we should be looking further at your McIDAS environment setup or ADDE

>thanks again?


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.