• Antelope Release 5.5 Linux 2.6.32-220.el6.x86_64 2015-04-21

 

NAME

vnd2deployment- produce a deployment table from a virutal network definition file (VND)

SYNOPSIS

vnd2deployment  [-t | -c] file database

SUPPORT


Contributed code: NO BRTT support.
THIS PIECE OF SOFTWARE WAS CONTRIBUTED BY THE ANTELOPE USER COMMUNITY. BRTT DISCLAIMS ALL OWNERSHIP, LIABILITY, AND SUPPORT FOR THIS PIECE OF SOFTWARE.

FOR HELP WITH THIS PIECE OF SOFTWARE, PLEASE CONTACT THE CONTRIBUTING AUTHOR.

DESCRIPTION

vnd2deployment takes an input VND file and tries to map as much information is availalbe into a deployment database table. The deployment table is an extension of the css3.0 schema. A full description of the deployment table can be found by using dbhelp on a css3.0 database, or by reviewing the Description of a Deployment Table section below.

Note, because of lack of information in the VND, not all fields of the deployment table will be filled in! Translating multiple times between a deployment table to a VND and back to a deployment table will not give you the same information.

VND files were originally distributed in Excel format. If you save the Excel spreadsheet as "text Windows" and separate the columns by tabs, you should be able to use this script with the -t option to convert it to a deployment table. Alternatively, the DMC is now providing the VNDs as CSV (comma separated) files and these can be converted using the -c option.

VND files can be downloaded from the DMC website. As of October of 2007, this website was:

http://www.iris.edu/vnets

Description of a VND

From the DMC 2006 December Electronic Newsletter: "A virtual network is group of stations and/or seismic networks, representing an affiliation that goes beyond the traditional bounds of seismic networks to represent an umbrella organization or initiative. Virtual networks associate to recording stations and seismic networks either indefinitely or for some limited period of time. It is a grouping system that reflects growing partnerships between seismic institutions to undertake large projects and act as a single, newly formed entity. The virtual network naming system allows these traditional networks to have their data represented under the auspices of one or more of these initiatives." The fields in the comma separated version of the file are:
VIRTUAL NET,NETWORK,STATION,INSTALL DATE,CERT DATE, 
START DATE,START TIME, END DATE,END TIME,PRIMARY DC, 
SECONDARY DC
They are defined as follows:

Description of a Deployment Table

In an effort to keep track of all information necessary to produce a VND, an extension table to the css3.0 schema was created (see dbschema(5), dbhelp(1), or deployment(5)). The fields in a deployment table are:

OPTIONS

FILES

See Description of a VND for the format of a Virtual Network Definition file. These format of these files is based on an Excel spreadsheet, and as such, I expect it to change at some point.

As a "best practice", the network operations specific schema extension tables might be kept in a directory such as "dbops". Tables such as site, sitechan, network, calibration, stage, etc. normally end up in a directory called "dbmaster" in a real-time operations setting. Waveforms, the wfdisc, arrival, origin, and other event database tables are normally found in the "db" directory. Maintaining a separate "dbops" directory allows a data center to segregate these tables that may be essential for their operations, but not for a generic real-time system.

EXAMPLE

Using the VND downloaded from the DMC and saved as TA_vnet.csv, convert it and save the deployment table as dbops/mydb.deployment.
  % vnd2deployment -c TA_vnet.csv dbops/mydb

SEE ALSO

deployment2vnd(1)
deployment(5)
dbe(1)
dbhelp(1)
http://www.iris.edu/vnets

BUGS AND CAVEATS

Works with current definition of VND file. The format is not well documented and subject to change. The current VND files do not care much about the time, but rather only have resolution to the date level. I suspect that may change at some point. However, the deployment table has a full time description so these fields will not be completely accurate in the output deployment table. Do not attempt to translate a deployment table to a VND and then back to a deployment table. You will lose information in duplicate transformations. There are no current dbverify checks to make sure that the deployment table fields are consistent internally, or to check if the deployment table fields match what is available in the site, sitechan, snetsta, etc.

AUTHOR

Jennifer Eakins
IGPP-SIO-UCSD
Antelope User Group Contributed Software
Printer icon