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

Re: 20050810: NMAP2 suggestions



Steve,

I have attached the two .spf files and 2 images from my system. I
started up a new NMAP2 and created a new procedure that I called
"synoptic_analysis_day".  I just did this about 10 minutes or so ago.
The other .spf file is one I called "synoptic_analysis_night". When I
first add the parameters and features I want to look at it is fine. I
opened in a different window another NMAP2 and used the
"synoptic_analysis_day.spf file.  I've sent the two images for you to
look at and obviously one is missing the watch box.  I looked at the
.spf files in an editor and I could not see anything that looked wrong
initially.

When I am saving these files I am saving them in the "Local" directory
which stores them in my "/home/gempak/" directory.


Kevin



PS.....I am changing my mind and not sending the two images. They were
vis images with stuff overlaid and I think they might end up being a
little large for the mail server. 


----- Original Message -----
From: Unidata Support <address@hidden>
Date: Wednesday, August 10, 2005 9:43 pm
Subject: 20050810: NMAP2 suggestions 

> 
> Kevin,
> 
> I haven't had any trouble loading an SPF file with watch boxes. You 
> can open
> up your spf in a file editor and verify the creation time of your 
> proceedure,just in case you were in a different directory when you 
> craeted the file.
> 
> The loopx_sourceX_attr_type should show the first 3 lines for
> the severe, tornado and update lines as "6", "2", and "5" to
> ensure those colors. The <loopx_sourceX_attr_flag> should
> show the flags as they were in miscset.tbl, eg with the color flag 
> off.
> Also for clorification, I suggested removing the gdattim, rather 
> than making 
> it "last" for objective analyses so that you can have a time line 
> for loops,
> rather than the single "last" time, rather than what you ended up 
> doing.
> Steve Chiswell
> 
> 
> >From: "Kevin Polston" <address@hidden>
> >Organization: UCAR/Unidata
> >Keywords: 200508102030.j7AKUljo002825
> 
> >This is a multi-part message in MIME format.
> >--------------090605060304000301080905
> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >Content-Transfer-Encoding: 7bit
> >
> >Hi Steve,
> >
> >Thanks for your help with my problems.  I have mostly good news 
> and a 
> >little bit of still unresolved issues.
> >
> >First,  I did what you said regarding the miscset.tbl.  
> Fortunately I 
> >saved the original file and went ahead and made it the primary 
> file (the 
> >actual miscset.tbl file).  I then closed NMAP2 and restarted it 
> from 
> >NTL.  I loaded in the watches and they looked fine. So I went 
> ahead and 
> >made a procedure (.spf file) to load, including the watches in it. 
> >Everything was fine as I was constructing the procedure. After I 
> saved 
> >the procedure I closed NMAP2 again and then restarted it. I loaded 
> the 
> >procedure but this time no watch boxes appeared. Even when I tried 
> to 
> >load it on a blank map it wouldn't show up. So I closed NMAP2 
> again and 
> >then restarted it...one more time.  This time I just loaded in the 
> >watches without loading in the procedure and they loaded fine.  
> This 
> >makes me wonder if there is a "bug" or something in creating the 
> >procedures. Everything else in my procedure loaded correctly. The 
> only 
> >thing missing was the watch boxes.  So, that's where I'm at with 
> that 
> >issue.
> >
> >The good news though is that I finally figured out the problem 
> with the 
> >objective analysis grids not showing in NMAP2 thanks to you.  The 
> >location where I was storing my OA grids was in the directory  
> >/usr1/nawips/metdat/gempak/oagrids/sfcoagrids.   I moved the 
> "oagrids" 
> >directory into the /usr1/nawips/metdat/gempak/grids/ directory 
> (which is 
> >designated as the $MODEL directory). I made the appropriate 
> changes to 
> >the datatype.tbl file and then went in and made the appropriate 
> changes 
> >to the restore files (taking out GDATTIM = all and replacing it 
> with 
> >DATTIM = last). That seemed to do the trick as the restore files 
> are 
> >displaying just fine now.  The one thing I haven't tried yet is to 
> >create some "OA parameters" (such as the supercell composite or 
> >significant tornado parameter) with the model data....so I can get 
> the 
> >forecast of these indices.  I will probably give that a try either 
> today 
> >or tomorrow and let you know how that goes.
> >
> >So the bottom line is this......the OA grids show up again now 
> which is 
> >good. I can plot watches the way I would like to see them manually 
> >(which is good) but when I try to load in a procedure the watches 
> do not 
> >appear (which is bad).
> >
> >
> >Kevin
> >
> >--------------090605060304000301080905
> >Content-Type: text/x-vcard; charset=utf-8;
> > name="Kevin.Polston.vcf"
> >Content-Transfer-Encoding: 7bit
> >Content-Disposition: attachment;
> > filename="Kevin.Polston.vcf"
> >
> >begin:vcard
> >fn:Kevin Polston
> >n:Polston;Kevin
> >org:NWSTC;Management & Meteorology
> >adr:;;7220 NW 101st Terrace;Kansas City;MO;64153;USA
> >email;internet:address@hidden
> >title:Senior Instructor
> >tel;work:816-880-9594 ext 273
> >tel;fax:816-880-0377
> >x-mozilla-html:TRUE
> >url:http://www.nwstc.noaa.gov
> >version:2.1
> >end:vcard
> >
> >
> >--------------090605060304000301080905--
> 
> --
>
****************************************************************************
<
> Unidata User Support                                    UCAR 
> Unidata Program <
> (303)497-8643                                                  P.O. 
> Box 3000 <
> address@hidden                                   Boulder, 
> CO 80307 <
> --------------------------------------------------------------------
> -------- <
> Unidata WWW Service              
> http://my.unidata.ucar.edu/content/support  <
> --------------------------------------------------------------------
> -------- <
> NOTE: All email exchanges with Unidata User Support are recorded in 
> theUnidata 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.
> 

Attachment: synoptic_analysis_day.spf
Description: Binary data

Attachment: synoptic_analysis_night.spf
Description: Binary data