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

 

NAME

fill_gaps - build database combining rt data with baler data to fill gaps

SYNOPSIS

fill_gaps [-v] [-V] [-T]
                [-n net ]
                [-r reject_stas ]
                [-s sta_match ]
                [-b clean_baler_db ]
                [-o dbout ]
                dbin [dmc_gap_db] start_time end_time

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

fill_gaps is designed to build the best possible waveform database, combining data collected from a real-time system with data retrieved from on-site storage devices. fill_gaps assumes there are valid wfdisc, calibration, and gap tables from the rt system. It also requires a clean wfdisc of baler data with no waveform overlaps made by build_baler_data. fill_gaps creates a directory named filled_gaps where temporary databases are made with proper links to the waveforms. The final step is to execute a series of trexcerpt commands for each jdate from the gap table between start_time and end_time. If the optional [dmc_gap_db] database is specified, then these gaps are also filled in the output database.

OPTIONS

ENVIRONMENT

needs to have sourced $ANTELOPE/setup.csh.

PARAMETER FILE

None.

RETURN VALUES

0 if successful, 1 if not.

SEE ALSO

build_baler_data(1)
baler_request(1)
baler2db(1)
gap_status(1)
replay_data(1)
rt_baler_info(1)

BUGS AND CAVEATS

fill_gaps should only be run after baler data are collected, combined and cleaned by build_baler_data.

AUTHOR

Frank Vernon

Antelope User Group Contributed Software
Printer icon