ensureMonoBN: Ensure we have monotonic boot numbers for a receiver...

Description Usage Arguments Details Value Note Author(s)

Description

Sensorgnomes are supposed to know how many times they've been booted, and record this bootnum in the name of each file they write. One use of this information is to position batches of files in real time if they were recorded during a boot session when the SG failed to set its clock to GPS time. These files will then appear to have been written in the year 2000. If the boot session before or after the problematic one is correctly dated, that lets us bracket the time interval in which the undated boot session must belong.

Usage

1
ensureMonoBN(src, testOnly = FALSE)

Arguments

src

dplyr:src_sqlite open to an existing receiver database

testOnly

logical scalar; default FALSE.

Details

Unfortunately, this scheme has failed in a few situations:

This function can test for and correct non-monotonic boot counts.

Value

if testOnly==TRUE:

if testOnly==FALSE: return TRUE iff monoBN values were changed for any file.

Note

If testOnly==FALSE, then change might be made to the monoBN field in file records. Any such changes are recorded in the bootnumChanges table.

Author(s)

John Brzustowski jbrzusto@REMOVE_THIS_PART_fastmail.fm


jbrzusto/motus-R-package documentation built on May 18, 2019, 7:03 p.m.