[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20020717: gempak and related ldm setup at stc
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: 20020717: gempak and related ldm setup at stc
- Date: Thu, 18 Jul 2002 12:36:55 -0600
Alan, All the GEMPAK decoders are part of the GEMPAK distribution. If you download a binary distribution, you will find them in the $GEMEXE directory. If you build from source, they will get installed into the $GEMEXE directory along with the other GEMPAK programs ($GEMEXE being the bin/$NA_OS directory under the top of the GEMPAK tree). You can either copy the decoders to the ~ldm/decoders directory or create links to that directory. The pqact.conf examples I provide are assuming you will be able to find the decoders in the ~ldm/decoders directory (for the sake of making things more generic by not having to edit the path in the pqact.conf entries). For instance, the metar decoder is invoked from decoders/dcmetr. Pqact will use the relative path from its $LDMHOME. The output directories in the pqact examples are also relative to your $LDMHOME. Typically, these will be to directories under data/gempak. The one area that you will have to edit from the pqact.conf entries is the location of the GEMTBL and GEMPAK environmental variables (lines that have -e GEMTBL=.....path....and -e GEMPAK=.....path....). As an alternative, I have provided in the GEMPAK 5.6.f distribution a set of templates in the $NAWIPS/ldm/etc directory which will automatically create pqact.conf lines based on your $GEMTBL and $GEMPAK environmental variable settings. To create these, just: cd $NAWIPS/ldm/etc (make sure your GEMPAK environmental variables are set through sourcing the Gemenviron file) Then run: gen_pqact.csh That will produce a pqact.gempak file in that directory that you can edit and append to your pqact.conf file (or, you can have a separate pqact running from ldmd.conf just for the pqact.gempak file). The decoders are only needed on the machine with the LDM....but, if you nfs mount the distribution to your lab machines, you don't have to worry since all the decoders will be in the $GEMEXE directory along with all the other programs. Steve Chiswell Unidata User Support >From: <address@hidden> >Organization: UCAR/Unidata >Keywords: 200207172145.g6HLjlH22949 >This is a multi-part message in MIME format. > >------_=_NextPart_001_01C22DDB.4B8038AF >Content-Type: text/plain; > charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable > >Hi to all the hard working supporters at unidata. > >We are in the early stages of setting up some terminals to run Gempak. =20 >the we being Tony Hansen (address@hidden) and myself. > >We run the LDM on one machine as an ingest box, currently just supplying >MCIDAS data. When we run Gempak, we would like to access the same=20 >LDM machine for the data. We will set it up just as you suggest for=20 >a typical installation. > >Our ldm is ver 5.06 but I believe Tom Y. has updated it so that it = >runs >the latest MCIDAS decoders. > >Looking at the Gempak web page and also looking at a few archive emails, >I have some questions. Can you comment on the following? > >1. I know we will need to modify our pqact.conf file on the LDM. It = >does not > at present have a Gempak section, but we have copied the = >ldmbridge=20 > decoder section from the web and will append that to our = >pqact.conf. > Then we will need to tailor the individual sections to our = >preference; > looks like we mainly will uncomment or comment out the needed = >lines. > > > > > > >2. I am puzzled about setting up the decoders called for in the pqact. > They are listed in the decoders section of the Tutorial, but no = >mention > is made of how they are obtained. > I assume they come with the distribution and then we need to = >install > them in a subdirectory on our ldm eg. ~ldm/decoders ? > That is where the MCIDAS decoders are kept. We do not have = >copies > of them in our present LDM. Are they sent with the Gempak or do = >we > have to get a current version of LDM which is packaged with all = >decoders? > > I note that one can also have the decoders present on the terminal = >running=20 > Gempak, and invoke them manually, but since we run the LDM,=20 > do we need them in both places ( both LDM machine and Gempak = >Machine) ? > > > >Well, those should be easy ones. =20 > >Hope you guys are all doing well. I am semi-retired, so you need to = >put up with >a semi-geezer and his questions. > >Alan Anderson > >ps. in your reply, could you please copy Tony also ? = >address@hidden > > > =20 > >------_=_NextPart_001_01C22DDB.4B8038AF >Content-Type: text/html; > charset="iso-8859-1" >Content-Transfer-Encoding: quoted-printable > ><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> ><HTML> ><HEAD> ><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = >charset=3Diso-8859-1"> ><META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = >6.0.5770.91"> ><TITLE>gempak and related ldm setup at stc</TITLE> ></HEAD> ><BODY> ><!-- Converted from text/rtf format --> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Hi to all the hard working supporters = >at unidata.</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">We are in the early stages of setting = >up some terminals to run Gempak. </FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">the we being Tony Hansen = >(address@hidden) and myself.</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">We run the LDM on one machine as an = >ingest box, currently just supplying</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">MCIDAS data. When we run = >Gempak, we would like to access the same </FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">LDM machine for the data. = >We will set it up just as you suggest for </FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">a typical installation.</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Our ldm is ver 5.06 but I believe = >Tom Y. has updated it so that it runs</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">the latest MCIDAS = >decoders.</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Looking at the Gempak web page and also = >looking at a few archive emails,</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">I have some questions. Can = >you comment on the following?</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">1. I know we will need to modify = >our pqact.conf file on the LDM. It does not</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> at present = >have a Gempak section, but we have copied the ldmbridge = ></FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> decoder = >section from the web and will append that to our pqact.conf.</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> Then we will = >need to tailor the individual sections to our preference;</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> looks like we = >mainly will uncomment or comment out the needed lines.</FONT> ></P> ><BR> ><BR> ><BR> ><BR> ><BR> > ><P><FONT SIZE=3D2 FACE=3D"Arial">2. I am puzzled about setting up = >the decoders called for in the pqact.</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> They are = >listed in the decoders section of the Tutorial, but no mention</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> is made of = >how they are obtained.</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> I assume they = >come with the distribution and then we need to install</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> them in a = >subdirectory on our ldm eg. ~ldm/decoders = >?</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> That is where = >the MCIDAS decoders are kept. We do not have = >copies</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> of them in = >our present LDM. Are they sent with the Gempak or do = >we</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> have to get a = >current version of LDM which is packaged with all decoders?</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial"> I note that = >one can also have the decoders present on the terminal running </FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> Gempak, = >and invoke them manually, but since we run the LDM, </FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial"> do we need = >them in both places ( both LDM machine and Gempak Machine) = >?</FONT> ></P> ><BR> ><BR> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Well, those should be easy = >ones. </FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Hope you guys are all doing = >well. I am semi-retired, so you need to put up = >with</FONT> > ><BR><FONT SIZE=3D2 FACE=3D"Arial">a semi-geezer and his = >questions.</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">Alan Anderson</FONT> ></P> > ><P><FONT SIZE=3D2 FACE=3D"Arial">ps. in your reply, could you = >please copy Tony also ? = >address@hidden</FONT> ></P> ><BR> > ><P><FONT SIZE=3D2 FACE=3D"Arial"> </FONT> ></P> > ></BODY> ></HTML> >------_=_NextPart_001_01C22DDB.4B8038AF-- >
- Prev by Date: 20020717: gdplot2 contouring problem
- Next by Date: 20020718: nmap/dcgrib/Reanlysis
- Previous by thread: 20020717: gdplot2 contouring problem
- Next by thread: 20020718: nmap/dcgrib/Reanlysis
- Index(es):