sgFindTags: find tags in an SG stream

Description Usage Arguments Value Author(s)

View source: R/sgFindTags.R

Description

A stream is the ordered sequence of raw data files from a receiver corresponding to a single boot session (period between restarts). This function searches for patterns of pulses corresponding to coded ID tags and adds them to the hits, runs, batches etc. tables in the receiver database. Each boot session is run as a separate batch.

Usage

1
sgFindTags(src, tagDB, resume = TRUE, par = NULL, mbn)

Arguments

src

dplyr src_sqlite to receiver database

tagDB

path to sqlite tag registration database

resume

if TRUE, tag detection resumes where it last left off for each given item in mbn. Typically, a new batch of data files arrives and is added to the receiver database using sgMergeFiles(), and then sgFindTags is called again to continue processing these new data. When running archived data retroactively, it is better to set resume=FALSE, otherwise if bootnums are not monotonic, then tag event histories will be scrambled leading to searching for the wrong tags at the wrong times. This has often been the case for Beaglebone White receivers, since they had no internal memory for storing the bootcount, and relied on writing it to the SD card; updating to a new SD card would typically reset the boot count.

par

list of non-default parameters to the findtags code; defaults to NULL

mbn

integer monotonic boot number(s); this is the monoBN field from the files table in the receiver's sqlite database.

Value

a list with these items

Author(s)

John Brzustowski jbrzusto@REMOVE_THIS_PART_fastmail.fm


jbrzusto/motusServer documentation built on May 19, 2019, 8:19 a.m.