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

19990212: McIDAS-X 7.40 - Gridplot cmd in PANels (cont.)

>From: address@hidden
>Organization: SMSU
>Keywords: 199902121845.LAA13194 McIDAS-X 7.40 GRIDPLOT PANEL

Bill,

re: string for coutour intervals defined by string reference
>You might need to educate me here.  The above command, with the .2,
>is from mcidas's output, which says to me that mcidas turned the 
>?PINT into .2  What am I missing in a string definition that will allow
>mcidas to put .2 in its output, but not correctly interpret the .2?

I misinterpreted your earlier message.  This message seems to be caused
from the '.' of the .2.  I verified that GRIDPLOT would not run as:

GRIDPLOT PCP SFC .2 USA 12 X 30 GRIDF=5043 GRA=1 PAN=1 COLOR=3 UNIT=IN

but would run correctly as:

GRIDPLOT PCP SFC 0.2 USA 12 X 30 GRIDF=5043 GRA=1 PAN=1 COLOR=3 UNIT=IN

>TE ?PINT ".2
>is the definition in an earlier batch file (which also defines the
>strings for the GRID files).  Is there a different way of defining a
>string to be used as a number?

See if specifying it as 0.2 does the job for you like it did for me
here (note, I am using version 7.5, so there may be a difference).

>I mean, this all worked before, and
>I simply don't understand what to do differently.

Try 0.2.

re: frame panelization
>The frame is panelized.  We make 13 separate products each with 4
>panels.  Only 2 or 3 of them fail.  They are all initiated from the same
>BAT file(s) (depending on time of day).  PANEL 2 2 is one of the first
>commands, right after EG; EG I;

OK, I had thought that the failure was coming from the frame not being
panelized; sorry.

>after that I learned, the hard way, that
>EG I has to become EG I PANEL=1 4.    I 

In the Unidata version of EG, you can specify erasing of both the graphics
and image portions of the frame in one go:

EG B PANEL=1 4

(the 'B' is the operative thing to note).

>have had to fight with the new panelization stuff for a
>couple of days and believe I have it correct.

It looks that way.

>Nothing like making mistakes to provide a fella with an education.

I can second that comment!!!  For the past week, I have been trying to
setup a PC to boot:

Windows NT 4.0
Solaris x86 2.7
RedHat Linux 5.2

What a major pain !@@#%!@#$

>As I said, most of the
>panelized products work.  There are panelized products which come out
>quite correctly in the same .BAT file.

Now I am at a loss.  If some things work, all things should work.  Could
you send me the BATCH file section in which some things work and others
do not?

>So your example below, as far as I can see, represents something we are
>already doing,

Yup, my misunderstanding of your situation.

>with the exception of the the FRAME identifier in 
>PANEL 2 2 1.

The default frame identifier is set to current frame.

>The mcenv for the .BAT files has only one from defined.

OK.  This may be the wrinkle that I was not taking into account.  The
question is whether things are different when done from a ROUTE PP BATCH
invocation.

>So at this point, I'm out of brains, altitude and airspeed.

Me too.

>And another thing.  Does a scour parameter of 1 day work in mcidas?

Which scour?

>Will you actually get 24 hours of existence?

There are several different scouring routines in McIDAS, so the answer is
dependent on what you are trying to scour.  Scouring of XCD files (like
*.XCD, *.IDT, etc) work a little differently than you might expect.
MDXX and GRID scouring work as expected.

Tom