Digital Atmosphere work

Post by **Tim Vasquez** » Tue Jul 06, 2004 7:18 am

I've set aside some intensive Digital Atmosphere work for this week starting later today. Just to give everyone a heads up. Keep the bug reports coming (better here on the forum than on E-mail so everyone can compare notes).

Tim

Wally Mayo · Post by **Wally Mayo** » Tue Jul 06, 2004 11:23 am

Sounds great.

Don't forget the item (previously brought up by several folks)...
The check box for "omit highs and lows when plotting ASUS1 bulletins" doesn't work. You might want to change that ASUS1 to ASUS01 to be up to date.

Similarly, I once suggested that there be a check box (or something) that also allows DAWS analysis lows and highs to not appear (just the isolines) as an option. (Less clutter when ASUS01 is plotted OR if manual placement of highs and lows are desired).

But still probably more key is the multiple-site radar "block" (w/a new get operation) that happens after a net upload of an output map.

Fred · Post by **Fred** » Tue Jul 06, 2004 4:24 pm

Data retrieval
In the "Data retrieval window" it is not possible to delete a site (so a test-site is still on #1). Deleting it from the file Digatmos.ur0 (a different file as mentioned in the manual!) does not work. As soon as you open DAWS it's added to Digatmos.ur0 again.

Scripting
In the export the possibility to add a variable in the filename like sysdate and/or systime.

Fred

Post by **Tim Vasquez** » Tue Jul 06, 2004 6:46 pm

But still probably more key is the multiple-site radar "block" (w/a new get operation) that happens after a net upload of an output map.

Don't understand this description.

Similarly, I once suggested that there be a check box (or something) that also allows DAWS analysis lows and highs to not appear (just the isolines) as an option.

Just remove HILO from the pressure analysis lines in your DIGATMOS.MNU script. I think adding a preferences for it when it can be included or excluded in a script would create a layer of confusion (people complaining they don't plot when HILO is in the script, or complaining that they do plot when HILO is excluded).

Tim

Wally Mayo · Post by **Wally Mayo** » Tue Jul 06, 2004 9:41 pm

Sorry, it was in an earlier post, and emailed once. Here's the details...

1. Using schedule script, data retrieval window does not go away after a net upload of a map (well, not automatically - the close box does work). May be related to #2...

But more of more interest...
2. After any upload of map to net by using a schedule script,
if you then change map, change radar set (stations chosen to get NIDS), do a get base reflectivity (or probably any radar data), now it will only get the first site, until DAWS is quit and rerun. Then get radar set will get all of them.

I will try to give more details as I do more runs/tests.

UPDATE after release 1.0m

No change. (I know you weren't hitting this area for "m"- I just found the one line in my script file that causes the symptom:
For #2 (above), whenever I do the one-line simple scripted upload (as a file, not live)...
upload,ftp://[signsignon:password]@ftp.site/ma ... ve\map.gif
and then any subsequent radar ingest stops after ONE site. Have to quit and rerun to regain full (multiple) radar operations.
Interestingly, I can't get that one line (with my signon, etc. of course, to run "live" as a script (not as a file) in the script mode (top entry place).
---
Hope this helps.

On the HILO - yes, of course! Still trying to change mindset to analysis script thinking, and its admittedly better adaptability. (Need the "drawing mode" text creation box to work if I don't use HILO and need to label Highs and Lows manually - i.e. 992mb)
And, the ASUS01 highs/lows checkbox in PREFS will still have to be fixed by you?

Post by **Tim Vasquez** » Fri Jul 09, 2004 7:12 am

All of this is fixed for the upcoming V1.0n.

Tim