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

Re: difax scripts and ps files (fwd)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: difax scripts and ps files (fwd)
  • Date: Tue, 31 Oct 2000 10:08:51 -0700 (MST)
===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Fri, 27 Oct 2000 10:39:20 -0500
From: Pete Pokrandt <address@hidden>
To: Jeff Weber <address@hidden>
     Linda Miller <address@hidden>,
     David Fitzgerald <address@hidden>, address@hidden,
     address@hidden, address@hidden, address@hidden,
     address@hidden
Subject: Re: difax scripts and ps files 


In a previous message to me, you wrote: 

 >Pete, 
 >
 >I had envisioned you feeding: 
 >
 >sunshine.ssec.wisc.edu
 >motherlode.ucar.edu
 >sleet.wunderground.com
 >datoo.srcc.lsu.edu
 >
 >These are our 4 top tier primary feed nodes...
 >
 >This way, you will not be overwhelmed. 
 >Upon your wishes, others "could" feed directly from you, if your bandwidth
 >is holding up. I think ingesting it to the top tier machines would prove
 >most efficient and least demanding on Wisc's resources. You would have
 >more control doing a point to point transfer, but I believe you are not
 >concerned with controlling the access of this data within the Unidata
 >community-correct me if wrong here-.
 >
 >Opinions..?
 >

Jeff and all,

Feeding the primary nodes from mapmaker and then fanning the data
out that way sounds like a good idea.  We have no concerns regarding
the widespread distribution of these maps, we're just glad to be
able to help out!

I'd suggest that probably sending them out using the DIFAX identifier
would make more sense than the EXP, since DIFAX is not being used
for real DIFAX maps anymore (correct?)  That way, EXP can be left
open for truly experimental new feeds, and not get in the way of
the distribution of the 'genuine imitation DIFAX charts' as Ben
referred to them (I love that title :)

Sound reasonable?  If the DIFAX feed type is the way to go, let
me know so I can change that in my pqinsert commands.

Pete

--
+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
^ Pete Pokrandt                    V 1447  AOSS Bldg  1225 W Dayton St^
^ Systems Programmer               V Madison,         WI     53706    ^
^                                  V      address@hidden       ^
^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
^ University of Wisconsin-Madison  V       262-0166 (Fax)             ^
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+