Description Usage Arguments Details Value
Comparing Hyfe performance to a groundtruth, such as a set of labeled detections, requires that the two sets of events are synchronized. Even if Hyfe's system time differs from the labeler's clock by a second or two, that offset can complicate and confuse the performance evaluation process.
1 2 3 4 5 6 7 8 9 |
reference_times |
A vector of numeric timestamps (seconds since 00:00:00 UTC on January 1, 1970). These are the reference times to which the Hyfe detection times will be compared. For example, the timestamps of a labelled sound can serve as a reference time. |
reference_labels |
A numeric vector of labels the same length as |
hyfe_times |
A vector of numeric timestamps of Hyfe detections. |
filter_to_3 |
If |
toplot |
If |
verbose |
Print status updates to the Console? |
hyfe_predicitons |
A logical vector of predictions the same length as |
This functions synchronizes Hyfe detections to the set of reference/label times.
This function uses a three-stage iterative method for identifying the offset that reduces the total offset error between reference times and Hyfe times. The first stage tests for hour-scale offsets, such as timezone differences. The second stage tests for minute-scale offsets. The final stage tests for half-second scale offsets. These three offsets are summed and returned.
A numeric estimate of Hyfe's time offset, in seconds, from the reference times. A negative number indicates that Hyfe is ahead of the reference times. In most cases, your next step in analysis will be yo add the return of this function to your Hyfe times.
Note that this output is almost always a single number, but sometimes two (or more) different offsets can yield an equal reduction in error and therefore be equally viable offsets. In those instances, all viable offsets are returned.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.