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

 

NAME

mk_dmc_files - generate network or single station dataless or VND file with comment on changes

SYNOPSIS

mk_dmc_files 
	[-v]
	[-z]
	[-C]
	[-m]
	[-p pf]
	[-d output_dir]
	[-N net]
	[-s sta]
	[-f output_file]
	[-o orb]
	{-D | -V vnet}
	dbin dbtrack [comment]

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

mk_dmc_files is designed to create and track the updates a network operator makes to a dataless SEED volume, virtual network definition (VND). When changes were made and what they were is important for dynamic networks such as the USArray Transportable Array.

This script generates either (1) a single station or combined network dataless SEED volume or (2) a virtual network definition file. It allows for a comment on why the update was made to be tracked in an extension table, dmcfiles. The output table can then be queried to retrieve the comment for products such as webpages. Of course, the results of such a query can only be as good as the comments that are entered. The output dmcfiles extension table is also used by the ims2dmc program. mk_dataless_seed is called to generate the dataless volume. deployment2vnd is called to generate a Virtual Network Definition file.

OPTIONS

ENVIRONMENT

Need to have sourced $ANTELOPE/setup.csh and environment variable $PFPATH set.

PARAMETER FILE

Below is the default mk_dmc_files parameter file.


# mk_dmc_files.pf

vnd_dir         vnd        # year based directories are created under here
dataless_dir    dataless   # station or year based directories are created under here
sta_dataless_dir        dataless_sta            # station based directories will be created under here

product_dir             /anf/TA/products        # path where data products are stored.
                                                #       i.e. ending location would be a station dataless volume is:  $product_dir/$dataless_sta/$sta/
                                                # Only used with -C option.  If left blank, products appear in ./ under appropriate vnd|dataless|sta_statless directories

mailto                  someone@ucsd.edu,someone@iris.washington.edu    # comma separated list of email recipients, overridden by command line -m

# comment must be a single line less than 180 characters

default_comment	&Literal{
Metadata change
}


This is a very basic parameter file that specifies default output directories and a basic comment.

EXAMPLE

Generate a dataless for station 109C and keep it in compressed format after a datalogger swap. Do not transfer it via orbxfer2.


% mk_dmc_files -D -z -s 109C dbmaster/ta_only 
	dbops/usarray "109C datalogger swap"

% ls dataless_sta
109C/

% ls dataless_sta/109C/
DATALESS.TA_109C.2011.04.01

Generate a VND for the _US-TA virtual network after adding two new stations. Store it in the local vnd_dir specified in the default parameter file. Transfer it via orbxfer2.


% mk_dmc_files -V _US-TA -o anfexport:meta \
	dbmaster/anf dbops/anf "Added X21A Z22A"

Generate a single station dataless, store it in a product directory and inform people why the dataless was generated. The dataless will end up in the directory: /raid/data/products/TA/dataless_sta/L08A and will not be transferred via orbxfer2.


% mk_dmc_files -m -C -D -s L08A anfexport:meta \
	dbmaster/anf dbops/anf "L08A station closed"

% pfecho mk_dmc_files 
dataless_dir    dataless_all
default_comment &Literal{
Metadata change
}
mailto  jeakins@ucsd.edu,someone@iris.washington.edu
product_dir     /raid/data/products
sta_dataless_dir        dataless_sta
vnd_dir vnd

Generate a complete dataless for a network after adding two new stations. Store it in a data products directory on your raid system, but transfer using orbxfer2 with only the dataless_dir appearing for the receiver.


% mk_dmc_files -D -C -o anfexport:meta 
	dbmaster/ta_only dbops/usarray "Added X21A Z22A" 

In the above case the file generated would be something like /raid/data/products/dataless/2008/DATALESS.TA.2008.03.25. It would appear in the anfexport:meta orb as a source that looked like:

   anfhost/xfer/76596/DATALESS.TA.2008.03.25

If a downstream user was connected to the anfexport:meta orb with orbxfer2 in the receiver mode and chose to have the directories preserverd, they would receive the file on their host as:

   dataless/2008/DATALESS.TA.2008.03.25

DIAGNOSTICS

Errors from the system calls to mk_dataless_seed(1) or deployment2vnd(1) are not trapped properly by the elog routines.

Make sure your input database has no egregious errors.

SEE ALSO

mk_dataless_seed(1)
deployment2vnd(1)
orbxfer2(1)
dmcfiles(5)
db2ims(1)
ims2dmc(1)

BUGS AND CAVEATS

Earlier versions (prior to 5.1-64) required arguments after the -m and -C options. Those arguments have been pushed into the parameter file.

This is an in-house script necessary for the functionality of the USArray Transportable array. Please let me know if you find it useful, or seriously lacking in features that might help your group's needs.

If there is no reader attached to the specified output orb with -o, the program hangs until a reader is attached. To avoid this behavior, the wait_match parameter in the orbxfer2.pf file must be blank.

The 4.9 and earlier versions of orbxfer2 had a bug such that compressed files pushed into the orb would retain there file names (i.e. myfile.gz), but would actually be uncompressed before placement in the orb. The receiver would then get myfile.gz out of the orb, but it would be an uncompressed file. I believe this bug has been resolved.

If there are permissions problems with the output orb used with -o, the transfer of the file to the orb may fail silently. Review the orbserver logs to see if there is a problem.

All of the different directory options are confusing. I included them rather than choosing a single method that I commonly use. I would be interested to hear of other ways people might use this program and modifications that might be required or clarifications that you would find helpful.

See the current SEED manual for a full description of a dataless SEED volume.

Converse with the DMC regarding the format of the VND files.

AUTHOR

Jennifer Eakins
Univ. of California, San Diego
Antelope User Group Contributed Software
Printer icon