<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello Ali,<div><br></div><div>With a minor modification where I replaced the name of the Trillium 40 response file (from Trillium-40-NEW to trillium_40), I cat'd your attached *.DBBUILD files together and successfully ran dbbuild:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>% cat *D > my-dbbuild</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>% dbbuild -b test my-dbbuild</div><div><div><span class="Apple-tab-span" style="white-space:pre"> </span>% dbverify test </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>0 problems</div><div><br></div><div>I can't tell you if the information in your files is correct, but the dbbuild batch file setup seems ok. If you have a response file for "Trillium-40-NEW" it needs to reside in your distribution under: $ANTELOPE/data/instruments/sensors/ and with the name Trillium-40-NEW.pf. Please note that the current version of Antelope is 4.10 and that there was a recent correction to the default trillium_40 response. There have also been numerous updates to the dbbuild program since the 4.8 release.</div><div><br></div></div><div>I am uncertain what your next concern/question is. You did not attach the dbbuild files for the 5 stations from the AE network (I assume AJN, ALN, MSF, SHM, and UMQ). Presumably you want all of the stations in your operational dbmaster (DN_*, AE_*, II_*, etc.). If you need to maintain a separate "dn" database for only stations that have the "DN" network code, I would strongly suggest changing your setup (see below). Alternatively, the 4.10 version of Antelope has an updated mk_dataless_seed program that allows you to subset a database to generate a single station dataless SEED volume.</div><div><br></div><div>Below is a portion of a write-up that I put together based on operations for the USArray TA where metadata is gathered from multiple networks as well as maintained for all TA stations past and present (currently 632). It details a way to generate a single dbmaster from separate regional networks using both dbbuild and dataless SEED volumes. It involves a different setup than you have, but perhaps it will answer your concerns. Once you understand the "Directory structure", you can probably skip everything until the section "How to merge all network dbmasters" unless you want to see some specifics about screen out stations from a dataless SEED volume provided by another regional/global network operator. Note that due to the complexity of the network that I deal with, I have made no attempt to put all of the commands into a Makefile.</div><div><br></div><div>--Jennifer Eakins</div><div><br></div><div><br></div><div><br></div><div>=====================================</div><div><br></div><div><!--StartFragment-->
<div class="MsoNormal"><span style="font-size:14.0pt"><b><i>Directory structure<o:p></o:p></i></b></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">I have found that for complex and dynamic databases such as
the TA, you need to have a “working” area separate from
rtsystems/project/dbmaster/.<span style="mso-spacerun: yes"> </span>This
allows you to take your time in making changes to the TA database, as well as
keep track of changes to the regional networks in an area that is (hopefully)
less dynamic than the TA stations.<span style="mso-spacerun: yes"> Separating out the TA stations, also allows for generation of a network specific dataless SEED volume that does not include stations that are the responsibility of another. </span></div><div class="MsoNormal"><br></div><div class="MsoNormal">I recommend that the person in charge of metadata updates and collection create a staging area:</div>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="text-indent:.5in">/your/path/rtsystems/project/pre-dbmaster/</p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Within the pre-dbmaster directory you will find separate
directories for each regional network, global network, and the TA
stations.<span style="mso-spacerun: yes"> For example</span>:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><span class="Apple-style-span" style="font-family: Courier; font-size: 13px; ">% cd
pre-dbmaster/</span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">% pwd<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">/your/path/rtsystems/project/pre-dbmaster<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">% ls<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">all_merge/<span style="mso-spacerun:
yes">
</span>CONTRIB_NETWORKS_merge/<span style="mso-spacerun: yes"> </span><o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">az_dbbuild/<span style="mso-spacerun:
yes">
</span>iu_only/<span style="mso-spacerun:
yes"> </span><o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">bk_only/<span style="mso-spacerun:
yes"> </span><o:p>ta_dbbuild/</o:p></span></div><div class="MsoNormal"><span style="font-size:10.0pt;font-family:Courier">ci_only/<span style="mso-spacerun:
yes"> </span><o:p></o:p></span></div>
<div class="MsoNormal"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div><div class="MsoNormal"><br></div><div class="MsoNormal"><span style="font-size:10.0pt"> <o:p></o:p></span></div>
<div class="MsoNormal">The following is a brief explanation of what each directory
contains.<span style="mso-spacerun: yes"> </span>Additional details will
be provided in the “Regional networks” and “TA network” descriptions section of
this document.</div>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">all_merge -
contains the final combined regional, backbone, and TA dbmasters.<span style="mso-spacerun: yes"> </span>The db in this directory will
eventually replace the dbmaster in /your/path/rtsystems/project/dbmaster/ </p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">CONTRIB_NETWORKS_merge
- contains the combined regional and global dbmasters.<span style="mso-spacerun: yes"> </span>The db in this directory will
eventually be combined with the database in ta_dbbuild to form the dbmaster in
all_merge. </p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">az_dbbuild -
contains a dbbuild file and the dbmaster for the three Anza stations, MONP,
MONP2, and PFO. </p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">bk_only -
contains a single dataless SEED volume for the entire BK (BDSN) network, a pf
for sorting what stations are contributing, as well as the dbmaster created for
the stations that contribute to the TA. </p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">ci_only -
contains a directory with single station dataless SEED volumes for the CI
network (SCSN), a pf for sorting what stations are contributing, as well as the
dbmaster created from these individual dataless volumes.</p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">iu_only -
contains a dataless SEED volumes for the IU network (GSN maintained by ASL), a
pf for sorting what stations are contributing, as well as the dbmaster created
for the station that contributes to the TA.</p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"> </p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"><o:p></o:p></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt">ta_dbbuild -
contains multiple directories including backups of previous builds, a directory
containing “individual” dbbuild files, a dataless directory with past dataless
SEED volumes, and the dbmaster created from the individual dbbuild
databases.<span style="mso-spacerun: yes"> <span class="Apple-style-span" style="font-size: 19px; font-style: italic; font-weight: bold; "></span></span></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"><font class="Apple-style-span" size="6"><span class="Apple-style-span" style="font-size: 19px;"><b><i><br></i></b></span></font></p><p class="MsoNormal" style="margin-left:99.0pt;text-indent:-63.0pt"><font class="Apple-style-span" size="6"><span class="Apple-style-span" style="font-size: 19px;"><b><i><br></i></b></span></font></p><!--StartFragment-->
<div class="MsoNormal"><span class="Apple-style-span" style="font-size: 19px; font-style: italic; font-weight: bold; ">Regional networks</span></div><div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Each regional network has it’s own way of distributing
metadata, mostly in the form of a dataless SEED.<span style="mso-spacerun: yes">
</span>Some are available via ftp, others only by http download.<span style="mso-spacerun: yes"> </span>They can be distributed as a single
dataless for the entire network, or individual station dataless.<span style="mso-spacerun: yes"> </span>I will try to describe where I obtain
the dataless for each network, and how I build the dbmaster for that individual
network.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><b>AZ (Anza) stations:<span style="mso-spacerun: yes">
</span>MONP, MONP2, PFO<o:p></o:p></b></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">UCSD (Vernon group) operates the Anza network (network code
AZ) and is responsible for the metadata.<span style="mso-spacerun: yes">
</span>As of December 2007, we are not maintaining single station dataless, or
even an updated whole network dataless, for the Anza network.<span style="mso-spacerun: yes"> </span>So, in order to get the proper metadata
for these contributing stations, I created a dbbuild file that would cover the
stations of interest.<span style="mso-spacerun: yes"> </span>Note that
this database does not have the proper install times for PFO and MONP, but
cover only the epochs when the stations were in use for the TA (i.e. after
3/01/2004).<span style="mso-spacerun: yes"> </span>Eventually, the plan
is for the entire Anza network to switch to using single station dataless SEED
volumes (hopefully 2009).<span style="mso-spacerun: yes"> </span>At
that point, the procedures below will not be necessary, and there will be a
“pick up” point described for obtaining the dataless SEED volumes.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">No updates should be necessary here, but if there is a
sensor or datalogger swap at one of these sites, follow these procedures:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l3 level1 lfo1;tab-stops:list .5in">Make a
backup directory and copy previous dbmaster and dbbuild files to it:</li>
</ol><p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/az_dbbuild<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv az_monp_pfo* response 2009-042<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l3 level1 lfo1;tab-stops:list .5in">Edit
the my-dbbuild file and add in the changes</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier"> <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% vi my-dbbuild<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.25in"> <o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l3 level1 lfo1;tab-stops:list .5in">Run
dbbuild to generate newly updated database:</li>
</ol><p class="MsoNormal" style="margin-left:.25in"><span style="font-size:10.0pt;
font-family:Courier"> <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.25in"><span style="font-size:10.0pt;
font-family:Courier">% dbbuild –b az_monp_pfo my-dbbuild<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">You should now have a database, az_monp_pfo, which is ready
for merging with the other regional networks. </div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><b>BK (BDSN) stations:<span style="mso-spacerun: yes">
</span>BDM, CMB, CVS, FARB, GASB, HOPS, HUMO, JCC, JRSC, KCC, MCCM, MNRC, MOD,
ORV, PACP, PKD, POTR, WDC, WENL, YBH<o:p></o:p></b></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">UCB operates the BDSN network (network code BK) and is
responsible for the metadata.<span style="mso-spacerun: yes"> </span>As
of December 2007, the BK network is no longer contributing to the TA.<span style="mso-spacerun: yes"> </span>The stations listed above include all
stations that ever contributed to the TA.<span style="mso-spacerun: yes">
</span>Some stations contributed for the entire time range that BK contributed,
others only for a short time.<span style="mso-spacerun: yes">
</span>Regardless of how long they contributed, metadata for all of the above
stations has to be included.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Berkeley produces a network-based dataless SEED volume.<span style="mso-spacerun: yes"> </span>It is available via http pickup from:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><a href="http://www.ncedc.org/ftp/pub/doc/BK.info/BK.dataless.seed">http://www.ncedc.org/ftp/pub/doc/BK.info/BK.dataless.seed</a></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">or from ftp pickup via:</div>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp </span><span style="font-size:10.0pt"><a href="http://www.ncedc.org"><span style="font-family:Courier">www.ncedc.org</span></a></span><span style="font-size:10.0pt;font-family:Courier"><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd pub/doc/BK.info<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% get BK.dataless.seed<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">As this network is no longer contributing it should be
“static” and no updates needed.<span style="mso-spacerun: yes">
</span>However, here are the procedures if some future update is needed.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2;tab-stops:list .5in">Make a
backup directory and copy previous dbmaster and dataless files to it:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/bk_only<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv bk_tmp* BK.dataless.seed response 2009-042<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2;tab-stops:list .5in">Collect
the updated dataless SEED volume via one of the above methods:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp <a href="http://www.ncedc.org">www.ncedc.org</a><o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.25in"> <o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo2;tab-stops:list .5in">Run
seed2db:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% seed2db –respdir response –stagedir \<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">response/stage_BK –chansift netstachanlocs.pf \<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">BK.dataless.seed bk_tmp<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Note that I use a network specific stage directory.<span style="mso-spacerun: yes"> </span>This helps in later merging of the
databases.<span style="mso-spacerun: yes"> </span>Also see that we use a
netstachanlocs.pf file.<span style="mso-spacerun: yes"> </span>This file has
a list of accepted net_sta_chans that will be selected from the dataless SEED
for conversion into a css3.0 db:<span style="mso-spacerun: yes">
</span>it should not need to be modified for a “closed” network like this one.<span style="mso-spacerun: yes"> The netstachanlocs.pf file looks like:</span></div><div class="MsoNormal"><br></div><div class="MsoNormal"><br></div><div class="MsoNormal"><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>accept &Tbl{</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_[BL]H.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_L[KD]S.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_UEP.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_UKI.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_UM.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_LOG.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_BDM_ACE.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_[BL]H.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_L[KD]S.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_UEP.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_UKI.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_UM.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_LOG.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>BK_CMB_ACE.*</font></div><div class="MsoNormal"><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>...</font></div><div><font class="Apple-style-span" face="Courier"><span class="Apple-tab-span" style="white-space:pre"> </span>}</font></div></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">There are multitudes of complaints about the FIR delay for
these dataless.<span style="mso-spacerun: yes"> </span>I have not tracked
them down.<span style="mso-spacerun: yes"> </span>Here is an example of the error:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*: SEEDERROR - Improbable value for FIR delay.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*:<span style="mso-spacerun: yes"> </span><span style="mso-spacerun: yes"> </span>Resetting stage 3 FIR delay from
0.00(0.000000) to 2.27(0.000071) for BK_BDM_LHE 1999:337:19:26:00.000 ->
2000:066:00:01:00.000.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*: SEEDERROR - Asymmetric FIR coefficients in wrong
order.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*:<span style="mso-spacerun: yes">
</span>Reversing order of stage 4 coefficients for BK_BDM_LHE
1999:337:19:26:00.000 -> 2000:066:00:01:00.000.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*: SEEDERROR - Asymmetric FIR coefficients in wrong
order.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
16:00:22 seed2db *complain*:<span style="mso-spacerun: yes">
</span>Reversing order of stage 5 coefficients for BK_BDM_LHE
1999:337:19:26:00.000 -> 2000:066:00:01:00.000.<o:p></o:p></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">You should now have a database, bk_tmp, which is ready for
merging with the other regional networks.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><b>CI (SCSN) stations:<span style="mso-spacerun: yes">
</span>ADO, ARV, BBR, BC3, BCC, BEL, BFS, CIA, CWC, DAN, DEC, DNR, DVT, EDW,
EDW2, FMP, FUR, GLA, GMR, GOR, GRA, GSC, HEC, IRM, ISA, LUG, LRL, MLAC, MPI,
MPM, MPP, MUR, NEE, NEE2, OSI, PDM, RCT, RRX, SBC, SCI2, SCZ2, SDP, SDR, SHO,
SRMM, SNCC, SWS, TIN, TUQ, VES, WER<o:p></o:p></b></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Caltech operates the SCSN network (network code CI) and is
responsible for the metadata.<span style="mso-spacerun: yes"> </span>As
of December 2007, CI is still a contributor to the TA.<span style="mso-spacerun: yes"> </span>The stations listed above include all
stations that ever contributed to the TA.<span style="mso-spacerun: yes">
</span>Some stations have contributed for the entire time range of the
deployment (i.e. BBR), others only for a short time (ADO), and some stations
were closed and replaced (i.e. NEE2).<span style="mso-spacerun: yes">
</span>Regardless of how long they contributed, metadata for all of the above
stations has to be included.<span style="mso-spacerun: yes"> </span>Early
on in 2004, some stations event contributed 100 sps data rather than the
standard 40 and 1sps.<span style="mso-spacerun: yes"> </span>Because of
this, all metadata must be kept.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Caltech produces a single station dataless SEED volume.<span style="mso-spacerun: yes"> </span>They are available via http pickup
from:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><a href="http://www.data.scec.org/ftp/stations/seed/">http://www.data.scec.org/ftp/stations/seed/</a></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">or from ftp pickup via:</div>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp scec.gps.caltech <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd pub/stations/seed<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% get dataless.CI.BBR<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">At some point, I started writing a script that would check
for remote dataless files that had been updated more recently than those I had
locally, but I never got it to work consistently.<span style="mso-spacerun:
yes"> </span>Thus, it is left as a (rather tedious) human process to see
if there are any newly updated dataless that need to be retrieved.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Assuming that there were updates, here are the procedures:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3;tab-stops:list .5in">Make a
backup directory and copy previous dbmaster and dataless files to it:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/ci_only<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv ci_tmp* response 2009-042<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in">** Note that I do not save a backup
of any dataless.</p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3;tab-stops:list .5in">Collect
the updated dataless SEED volume via one of the above methods:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd CI_dataless<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp scec.gps.caltech<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.25in"> <o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo3;tab-stops:list .5in">Run
seed2db within a foreach loop:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd ../<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% foreach file (CI_dataless/*dataless*)<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in;text-indent:.5in"><span style="font-size:10.0pt;font-family:Courier">echo $file<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;
font-family:Courier">seed2db –respdir response –stagedir \ <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;
font-family:Courier">response/stage_CI –chansift chansift.pf \ <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:1.0in"><span style="font-size:10.0pt;
font-family:Courier">$file ci_tmp<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier"><span style="mso-spacerun: yes"> </span>end<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Note that I use a network specific stage directory.<span style="mso-spacerun: yes"> </span>This helps in later merging of the
databases.<span style="mso-spacerun: yes"> </span>Also see that we use a
chansift.pf file.<span style="mso-spacerun: yes"> </span>This file has a
list of accepted net_sta_chans that will be selected from the dataless SEED for
conversion into a css3.0 db:<span style="mso-spacerun: yes"> </span>it
might need to be modified if a station is closed and replaced with a new
one.<span style="mso-spacerun: yes"> </span>The only likely change would
be the addition of a new station:<span style="mso-spacerun: yes">
</span>if a station is closed/removed, we track its removal from the TA by
modifying the deployment table (more on that later).<span style="mso-spacerun:
yes"> </span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">There are multitudes of complaints about the FIR delay for
these dataless.<span style="mso-spacerun: yes"> </span>I have not tracked
them down.<span style="mso-spacerun: yes"> </span>Here is an example of the error:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:56:44 seed2db *complain*: SEEDERROR - Improbable value for FIR delay.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:56:44 seed2db *complain*:<span style="mso-spacerun: yes">
</span>Resetting stage 3 FIR delay from 319.50(0.015975) to 0.00(0.000000) for
CI_BBR_BHE 2000:166:22:00:00.000 -> 2004:085:04:39:00.000.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:56:44 seed2db *complain*: SEEDERROR - Improbable value for FIR delay.<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:56:44 seed2db *complain*:<span style="mso-spacerun: yes">
</span>Resetting stage 4 FIR delay from 79.50(0.079500) to 0.00(0.000000) for
CI_BBR_BHE 2000:166:22:00:00.000 -> 2004:085:04:39:00.000.<o:p></o:p></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">You should now have a database, ci_tmp, which is ready for
merging with the other regional networks.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><b>IU (ASL GSN) stations:<span style="mso-spacerun:
yes"> </span>TUC<o:p></o:p></b></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">ASL (Arizona Seismic Lab) operates the IU portion of the GSN
network (network code IU) and is responsible for the metadata.<span style="mso-spacerun: yes"> </span>As of December 2007, IU is a
contributor of a single station to the TA.<span style="mso-spacerun:
yes"> </span>I am not aware of any mechanism (email or otherwise) that informs
downstream users of any possible changes to the dataless.<span style="mso-spacerun: yes"> </span>Changes are infrequent, so perhaps
checking quarterly for any updates is adequate.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">ASL produces single station dataless SEED volumes.<span style="mso-spacerun: yes"> </span>They are only available via ftp </div>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp aslftp.cr.usgs.gov <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd pub/dataless<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% get IU.dataless<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:Courier"> <o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Assuming that there was an update to TUC (you can look at
the listing for the individual dataless to see if there was an update), here
are the procedures:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo4;tab-stops:list .5in">Make a
backup directory and copy previous dbmaster and dataless files to it:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/iu_only<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv iu_tmp* response 2009-042<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in">** Note that I do not save a backup
of any dataless.</p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo4;tab-stops:list .5in">Collect
the updated dataless SEED volume via one of the above methods:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% ftp aslftp.cr.usgs.gov<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo4;tab-stops:list .5in">Run
seed2db:</li>
</ol>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% seed2db –respdir response –stagedir \ <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">response/stage_IU –chansift chansift.pf \<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">IU.dataless iu_tmp<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Note that I use a network specific stage directory.<span style="mso-spacerun: yes"> </span>This helps in later merging of the
databases.<span style="mso-spacerun: yes"> </span>The chansift.pf file is
necessary as this network dataless has additional stations/channels that do not
contribute to the TA, and we do not need them in our database.<span style="mso-spacerun: yes"> </span>Errors look like:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:49:45 seed2db *complain*: SEEDERROR - Product of stage gains
(3692614771.6232) does not equal final sensitivity (3641000000.0000) for
IU_TUC_LHE_00 1998:309:19:00:00.000 -> NULL.<o:p></o:p></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">There seems to be a problem if you attempt to use the
individual dataless (i.e. DATALESS.IU_TUC.seed).<span style="mso-spacerun:
yes"> </span>The errors from using the single station dataless look like:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:53:49 seed2db *notify*: seed2db : $Revision: 1.21 $ $Date: 2007/02/14
18:12:02 $<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:53:49 seed2db *log*: scan_int: Failed integer input: '-r--r-'<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:53:49 seed2db *log*: sdblk_parseblk: scan_int(logical_sequence,'-r--r-')
error at 0 bytes offset<o:p></o:p></span></div>
<div class="MsoNormal"><span style="font-size:9.0pt;font-family:Courier">2007-363
15:53:49 seed2db *fatal*: SEEDERROR - sdblk_parseblk (DATALESS.IU_TUC.seed)
error.<o:p></o:p></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">You should now have a database, iu_tmp, which is ready for
merging with the other regional networks.<span style="mso-spacerun: yes">
</span></div>
<div class="MsoNormal"> </div><div class="MsoNormal"><!--StartFragment-->
<div class="MsoNormal"><span style="font-size:14.0pt"><b><i>TA network<o:p></o:p></i></b></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">This is by far the most complicated portion of the usarray
dbmaster.<span style="mso-spacerun: yes"> </span>The complications result
from the shear number of stations, potentially up to 400 TA installed at any
time, over 2000 stations by the end of the project, and the dynamic nature of
the network with stations operating for two years or less and both
installations and removals occurring constantly.<span style="mso-spacerun:
yes"> </span>However, we are lucky in that there are only two datalogger
configuration and three different sensor types.<span style="mso-spacerun:
yes"> </span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">The procedure for updating the TA dbbuild file has undergone
multiple revisions as the network has grown.<span style="mso-spacerun:
yes"> </span>Initially, I used a single dbbuild file that contained
information in chronologic order for all stations.<span style="mso-spacerun:
yes"> </span>This grew hard to manage and I moved to a single file sorted
alphabetically and then by time.<span style="mso-spacerun: yes">
</span>This also proved unwieldy and aggravating (i.e. if any mistakes were
made during an update for a single station, the entire dbbuild run had to be
redone).<span style="mso-spacerun: yes"> </span>I briefly used a
technique where I ran dbbuild only on a “dbbuild-snippet” that contained only
the updated information.<span style="mso-spacerun: yes"> </span>This was
a speedy way of updating, but some updates tended to get lost or not propagated
to the main dbbuild file and I found it was not workable for some revisions
needed for earlier epoch times.<span style="mso-spacerun: yes"> </span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">The current method I employ is to maintain ~30 dbbuild files
containing all stations which match a single letter/number.<span style="mso-spacerun: yes"> </span>For instance, A04A, A05A, etc. through
A21A are found in the AXXX-dbbuild file.<span style="mso-spacerun: yes">
</span>Each station grouping has it’s own database generated by running
dbbuild, and then all databases are grouped together into a ranged database and
finally into a combined TA-only database. I am not convinced this is the best way to do this (in terms of time/efficiency), but it seems to avoid some aggravating mistakes.</div>
<div class="MsoNormal"> <o:p></o:p></div>
<span style="">If you look at the current build area, you will see
backup directories (i.e. 2008-357/), a database called ANF_TA-only, a directory
called dataless/, a directory called individual_dbbuild/, some scripts
(build_all and merge_grp_dbs), and a few other miscellaneous files and
directories.<span style="mso-spacerun: yes"> </span>The short summary is
that the ANF_TA-only is the “final” TA station only database from which I build
a dataless SEED volume to pass to downstream users.<span style="mso-spacerun:
yes"> </span>The dbbuild files are found in the individual_dbbuild
directory with the results from each individual dbbuild run found in
individual_dbbuild/$letter/.<span style="mso-spacerun: yes"> </span>The
output dataless SEED volume is gzip’d and saved in the dataless directory.<span style="mso-spacerun: yes"> </span></span><!--EndFragment-->
</div><div class="MsoNormal"><br></div><div class="MsoNormal"><... skipping over many gory details on building the ANF_TA-only database...></div><div class="MsoNormal"><br></div><div class="MsoNormal"><!--StartFragment-->
<div class="MsoNormal"><span style="font-size:14.0pt"><b><i>How to merge all
network dbmasters<o:p></o:p></i></b></span></div>
<div class="MsoNormal"> <o:p></o:p></div>
<div class="MsoNormal">Now that you have all of the contributing networks and the
TA network databases up-to-date, you can merge them in preparation of replacing
the main dbmaster on anfops.<span style="mso-spacerun: yes"> </span>Here
are the steps:</div>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Prep
for merge of all contributing networks:</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd CONTRIB_NETWORKS_merge/ <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv usarray.* response/* 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Merge
all contributing non-TA networks:</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% dbmerge ../az_dbbuild/az_monp_pfo usarray<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span class="Apple-style-span" style="font-family: Courier; font-size: 13px; ">% dbmerge ../bk_only/bk_tmp usarray</span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% dbmerge ../ci_only/ci_tmp usarray<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% dbmerge ../iu_only/iu_tmp usarray<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"> </p><p class="MsoNormal" style="margin-left:.5in"><o:p></o:p></p><p class="MsoNormal" style="margin-left:.5in">You now
have a rebuilt database in CONTRIB_NETWORKS_merge that contains all
contributing networks.<span style="mso-spacerun: yes"> </span>In theory,
these stations do not get updated often so it is convenient to keep it separate
from the “all_merge” db.</p><p class="MsoNormal" style="margin-left:.5in"><b> <o:p></o:p></b></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Prep
for all_merge:</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/pre-dbmaster/<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cd all _merge/ <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv usarray.* response/* 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cp ../CONTRIB_NETWORKS_merge/usarray.* .<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cp –R ../CONTRIB_NETWORKS_merge/response .<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Merge
in TA data:</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% dbmerge ../ta_only/ANF_TA-only usarray<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"> <o:p></o:p></p><p class="MsoNormal" style="margin-left:.5in">We’re almost done!<span style="mso-spacerun: yes"> </span>Now we need to stop various real-time
systems and then update the main dbmaster.<span style="mso-spacerun:
yes"> </span></p><p class="MsoNormal" style="margin-left:.5in"><... procedure below is different for ANF/TA. Simplified instructions follow...> <o:p></o:p></p>
<ol style="margin-top:0in" start="5" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Stop any processes that access the dbmaster directory. This includes any analyst processing via dbpick or dbloc2, orbassoc, and possibly orbdetect</li>
</ol><p class="MsoNormal" style="margin-left: 0.5in; "><span style="font-size: 10pt; font-family: Courier; ">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left: 0.5in; "><span style="font-size: 10pt; font-family: Courier; ">/your/path/rtsystems/project/<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"> <span class="Apple-style-span" style="font-family: Courier; font-size: 13px; ">% orb2db_msg pause</span></p><div><font class="Apple-style-span" face="Courier" size="3"><span class="Apple-style-span" style="font-size: 13px;"><span class="Apple-style-span" style="font-family: Helvetica; font-size: 12px; "><p class="MsoNormal" style="margin-left: 0.5in; "> <span class="Apple-style-span" style="font-family: Courier; font-size: 13px; ">% vi rtexec.pf</span></p><div><font class="Apple-style-span" face="Courier" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div></span></span></font></div><p class="MsoNormal" style="margin-left:.5in">This orb2db_msg command pauses the orb2db and orb2dbt processes for the realtime systems who's rtexec.pf resides in the pwd. When you edit rtexec.pf, turn off the orbdetect and orbassoc processes (change "yes" to "no" or "1" to "0").<o:p></o:p></p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="6" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Now
that the real-time systems are no longer running processes that look at the
dbmaster, it can be updated.</li>
</ol><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier"> <o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">/your/path/rtsystems/project/dbmaster/<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mkdir 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cp usarray.* 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% mv response/* 2009-042<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cp ~/rtsystems/pre-dbmaster/all_merge/usarray.* .<o:p></o:p></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;
font-family:Courier">% cp –R ~/rtsystems/pre-dbmaster/all_merge/response .<o:p></o:p></span></p>
<div class="MsoNormal"> <o:p></o:p></div><p class="MsoNormal" style="margin-left:.5in">You will have to say “yes” to
overwrite the usarray.* files.<span style="mso-spacerun: yes"> </span>It
is also somewhat redundant to make a backup of the dbmaster files here if you
have already made one in the all_merge area.</p>
<div class="MsoNormal"> <o:p></o:p></div>
<ol style="margin-top:0in" start="7" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1;tab-stops:list .5in">Make sure the orb2db and orb2dbt processes are allowed to continue. </li></ol></div></div><div><p class="MsoNormal" style="margin-left: 0.5in; "><span style="font-size: 10pt; font-family: Courier; ">% pwd<o:p></o:p></span></p><p class="MsoNormal" style="margin-left: 0.5in; "><span style="font-size: 10pt; font-family: Courier; ">/your/path/rtsystems/project/<o:p></o:p></span></p><p class="MsoNormal" style="margin-left: 0.5in; "> <span class="Apple-style-span" style="font-family: Courier; font-size: 13px; ">% orb2db_msg pause</span></p><div><font class="Apple-style-span" face="Courier" size="3"><span class="Apple-style-span" style="font-size: 13px;"><span class="Apple-style-span" style="font-family: Helvetica; font-size: 12px; "><p class="MsoNormal" style="margin-left: 0.5in; ">Remember to edit your rtexec.pf to turn your orbdetect and orbassoc process back on.</p><div><br></div></span></span></font></div><div><div>On Feb 10, 2009, at 12:25 AM, Ali Shaaban Megahed wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div lang="EN-US" vlink="purple" link="blue"><div><span style="font-size: 12pt; "><font face="Times New Roman"><span class="262085306-10022009">Hi All </span><span class="262085306-10022009"> </span><span class="262085306-10022009"> </span><span class="262085306-10022009"> </span></font></span></div><div class="Section1" dir="rtl"><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><span style="font-size: 12pt; "><span class="262085306-10022009">I am using Antelope 4.8 for real time data acquisition, analysis and share data with neigbooring networks. It is my first time to update the database with new stations, the database consists of 4 stations ASU, HAT, NAZ, FAQ which belong to DN network as shown in the attached Makefile and the other stations as shown in other.pf file.</span></span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><span style="font-size: 12pt; "><span class="262085306-10022009">we are trying to share data with AE network which is consists of 5 stations (attached the sta.DBBUILD files) which I need to add to the database, I do not have the dataless seed file for these stations so<span class="Apple-converted-space"> </span></span></span><span style="font-size: 12pt; ">I prepared the STA-DBBUILD files for the 5 stations of AE network, I just add the information to the STA1.DBBUILD and rename the files by the stations name as attached,<span class="Apple-converted-space"> </span><span class="262085306-10022009">could you </span>please check them…</span></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; ">The Makefile attached after I modify it with the AE network stations…….the problem is that the new stations are not belong to DN network to add their names at the end of makefile….</span></font></div><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><span style="font-size: 12pt; "><span class="262085306-10022009">Could you p</span>lease send me your recommendation after you check the attached files…</span></div><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "> </p><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; ">Best wishes</span></font></div><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; ">Ali</span></font></div><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font face="Times New Roman"><span style="font-size: 12pt; "></span></font> </p><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009">Seismologist</span></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009">Dubai Seismi Network</span></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009">Survey Dapartment</span></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009">Dubai Municipality, Dubai, UAE</span></span></font></div><div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009"><a href="mailto:asmegahed@dm.gov.ae" style="color: blue; text-decoration: underline; ">asmegahed@dm.gov.ae</a></span></span></font></div><p class="MsoNormal" dir="ltr" style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; text-align: right; direction: rtl; unicode-bidi: embed; font-size: 12pt; font-family: 'Times New Roman'; "><font><span style="font-size: 12pt; "><span class="262085306-10022009"></span></span></font> </p></div><pre style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10pt; font-family: 'Courier New'; ">Our Vision
To create an excellent city that provides the essence of success and comfort of living.
Disclaimer:
This Electronic Mail and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to whom they
are addressed. If you are not an addressee, or have received the message
by error, please notify the sender via E-Mail or over the telephone and
delete this e-mail. You are not authorized to read, copy, disseminate,
distribute or use this E-Mail or any of its attachment in any way. Any
views or opinions presented in this email are solely those of the author
and do not necessarily represent Dubai Municipality. The recipient should
check this email and any attachments for the presence of viruses/worms.
Dubai Municipality accepts no liability for any damage caused by any
virus/worms transmitted by this email.
Dubai Municipality, Dubai, UAE, <a href="http://www.dm.gov.ae/" style="color: blue; text-decoration: underline; ">http://www.dm.gov.ae/</a>
</pre><span><AJN-DBBUILD></span><span><ALN-DBBUILD></span><span><MSF-DBBUILD></span><span><UMQ_DBBUILD></span><span><SHM-DBBUILD></span><span><Makefile></span><span><other.pf></span>_______________________________________________<br>Antelope mailing list<br><a href="mailto:Antelope@brtt.net" style="color: blue; text-decoration: underline; ">Antelope@brtt.net</a><br><a href="http://brtt.net/mailman/listinfo/antelope_brtt.net" style="color: blue; text-decoration: underline; ">http://brtt.net/mailman/listinfo/antelope_brtt.net</a><br></div></span></blockquote></div><br></div></body></html>