[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
19990621: more os2/mcidas & solarisx server
- Subject: 19990621: more os2/mcidas & solarisx server
- Date: Mon, 21 Jun 1999 14:27:35 -0600
>From: alan anderson <address@hidden>
>Organization: St. Cloud State
>Keywords: 199906211923.NAA20658 McIDAS ADDE
Alan,
re: test of loading imagery using ADDE vs NFS
>I tried the image load you suggested using the 2 lines listed above and it
>plotted much faster than anything we have seen here before, whether from
>hobbes or waldo.
That has been our and SSEC's experience in a number of cases. The
really great thing about ADDE is that you don't have to be looking at
your own machine to look at data. For instance, try the following:
DATALOC ADD RTIMAGES ADDE.UNIDATA.UCAR.EDU
DATALOC ADD RTPTSRC ADDE.UNIDATA.UCAR.EDU
IMGDISP RTIMAGES/GW-IR STA=KSTC MAG=2 SF=YES EU=IMAGE REFRESH='EG (GRA);MAP H 1
GRA=(GRA)
SFCPLOT T OLAY FRAME
This loads the most recent GOES-West IR image off of our ADDE server onto
your machine. Pretty cool, huh? (Don't forget to set the DATALOCs back
to waldo:
DATALOC ADD RTIMAGES WALDO.STCLOUDSTATE.EDU
DATALOC ADD RTPTSRC WALDO.STCLOUDSTATE.EDU
I use ADDE to monitor the ingestion/decoding status at McIDAS sites that
are running current releases and have installed the ADDE remoter server.
Since I did this for you, I can monitor waldo from here very easily.
>Can you give me a quick steer to the section in the
>documentation that will help me master some of the needed ADDE stuff?
The McIDAS Learning Guide is the place to start learning about ADDE.
You can access this at:
http://www.unidata.ucar.edu/packages/mcidas/mclearn/index.html
Don told me that someone there at downloaded and installed the learning
guide so you would have it locally. If this is true, you can work through
it locally.
>I have poked around some more regarding the access of MD files.
>REDIRECT LIST shows just what I would have expected; I have used the
>file EXAMPLE.NAM just as provided in the 7.4 release to create our
>REDIRECT LIST (with the necessary uncommenting).
OK, good.
>Also MDU LIST 01 40 shows the expected MD files for today, namely
>1
>2
>9
>10
>11
>12
>13
>19
>20
>21
>22
>23
>29
>30
Looks like the list I generated from the 'mcidas' account on waldo:
mdu.k LIST 1 100
MD# CREATED SCHM PROJ NR NC ID DESCRIPTION
----- ------- ---- ---- ---- ---- ------- -----------
1 1999170 ISFC 0 72 4500 1999171 SAO/METAR data for 20 JUN 1999
2 1999171 ISFC 0 72 4500 1999172 SAO/METAR data for 21 JUN 1999
9 1999168 ISFC 0 72 4500 1999169 SAO/METAR data for 18 JUN 1999
10 1999169 ISFC 0 72 4500 1999170 SAO/METAR data for 19 JUN 1999
11 1999170 IRAB 0 8 1300 1999171 Mand. Level RAOB for 20 JUN 1999
12 1999171 IRAB 0 8 1300 1999172 Mand. Level RAOB for 21 JUN 1999
13 1999172 IRAB 0 8 1300 1999173 Mand. Level RAOB for 22 JUN 1999
19 1999168 IRAB 0 8 1300 1999169 Mand. Level RAOB for 18 JUN 1999
20 1999169 IRAB 0 8 1300 1999170 Mand. Level RAOB for 19 JUN 1999
21 1999170 IRSG 0 16 6000 1999171 Sig. Level RAOB for 20 JUN 1999
22 1999171 IRSG 0 16 6000 1999172 Sig. Level RAOB for 21 JUN 1999
23 1999172 IRSG 0 16 6000 1999173 Sig. Level RAOB for 22 JUN 1999
29 1999168 IRSG 0 16 6000 1999169 Sig. Level RAOB for 18 JUN 1999
30 1999169 IRSG 0 16 6000 1999170 Sig. Level RAOB for 19 JUN 1999
31 1999171 ISHP 0 24 2000 1999171 SHIP/BUOY data for 20 JUN 1999
32 1999172 ISHP 0 24 2000 1999172 SHIP/BUOY data for 21 JUN 1999
39 1999169 ISHP 0 24 2000 1999169 SHIP/BUOY data for 18 JUN 1999
40 1999170 ISHP 0 24 2000 1999170 SHIP/BUOY data for 19 JUN 1999
41 1999171 FO14 0 38 600 1999171 NGM MOS for day 20 JUN 1999
42 1999172 FO14 0 38 600 1999172 NGM MOS for day 21 JUN 1999
49 1999169 FO14 0 38 600 1999169 NGM MOS for day 18 JUN 1999
50 1999170 FO14 0 38 600 1999170 NGM MOS for day 19 JUN 1999
51 1999170 SYN 0 8 6000 1999171 SYNOPTIC data for 20 JUN 1999
52 1999171 SYN 0 8 6000 1999172 SYNOPTIC data for 21 JUN 1999
59 1999168 SYN 0 8 6000 1999169 SYNOPTIC data for 18 JUN 1999
60 1999169 SYN 0 8 6000 1999170 SYNOPTIC data for 19 JUN 1999
61 1999170 PIRP 0 24 1500 1999171 PIREP/AIREP data for 20 JUN 1999
62 1999171 PIRP 0 24 1500 1999172 PIREP/AIREP data for 21 JUN 1999
69 1999168 PIRP 0 24 1500 1999169 PIREP/AIREP data for 18 JUN 1999
70 1999169 PIRP 0 24 1500 1999170 PIREP/AIREP data for 19 JUN 1999
81 1999171 WPRO 0 48 35 1999171 Hourly Prof data for 20 Jun 1999
82 1999172 WPRO 0 48 35 1999172 Hourly Prof data for 21 Jun 1999
89 1999169 WPRO 0 48 35 1999169 Hourly Prof data for 18 Jun 1999
90 1999170 WPRO 0 48 35 1999170 Hourly Prof data for 19 Jun 1999
91 1999171 WPR6 0 480 35 1999171 6-min Prof data for 20 Jun 1999
92 1999172 WPR6 0 480 35 1999172 6-min Prof data for 21 Jun 1999
99 1999169 WPR6 0 480 35 1999169 6-min Prof data for 18 Jun 1999
100 1999170 WPR6 0 480 35 1999170 6-min Prof data for 19 Jun 1999
-- END OF LISTING
>all with their expected schema labels and dates. Only unusual part to me was
>that as of 1840Z today, 21 June, the raob files # 13 and 23 already existed
>as raob files for 22 June.
Some data that looked like tomorrow's must have been in the datastream.
>Trying an MDX command as listed in documentation resulted in --MDX-- No
>Data Found.
What MDX command? For the data in the files labeled June 22? If yes, then
ignore it.
>So, some progress. I am going to check on the install steps for our os2
>machines and snoop regarding ADDE.
Try working through the Learning Guide. ADDE is pretty powerful. Just
imagine a situation where your data ingestion system failed (why does
that sound familiar ;-) and you have a class in a half hour that you
wanted to look at realtime data in. With ADDE, you simply have to
point to a cooperating site for the datasets you are interested in and
viola, you can look at data. As more and more active McIDAS sites move
to the current McIDAS distributions AND install their remote ADDE
servers, the more cooperation like this will be possible.
>Thanks
Talk to you later...
Tom