Skip to main content

FRC post match + live match logging reader abstraction

Project description

FRC Vlogger

What is this?

Vlogger is a generic library that provides an abstraction over the various kinds of files and live sources that are used in FRC.
This package is developed and used by FRC Valor 6800 for post match analysis.

Supported Sources

  • WPILog (supports structs and protobufs)
  • NetworkTables4 (supports structs and protobufs)
  • CTRE Hoot (file format does not support custom types)
  • DSLog/DSEvents, unlikely to be added soon
  • Phoenix Diagnostic Server

Motivation

Clients usually just care about the "meat" of the source (that is, the field name, the value, and the timestamp). It usually does not matter to the client where the data came from (i.e. the logic is the same whether it is from a live source or from a log file), and this means that every source should be exposed in a single API that should be a drop in replacement.
Additionally, there is no ready to use package in Python to parse WPILog files or connect to NetworkTables4 servers.
This package was heavily inspired by AdvantageScope's dataSources folder code.

API Structure

Each source is initialized with:

  • A reference to the "connection"
    • For historical logs (i.e. from a log file), this will usually be the path of the log file
    • For live sources (i.e. connecting to a server), this will usually be the hostname of the target machine
  • A list of regexes to match the regexes against. This was a design choice made to improve performance by only parsing fields that are going to be used. While not recommended, a regex of "" can be used to match all fields.
  • Any additional arguments that are required for that specific source. This may be for additional configuration or outside executables (the hoot source uses this) to properly parse the file

Examples

Initializing a generic source

If the file/connection source is not known, it is recommended to use the get_source function to iterate through the sources and performing validation on each.

import vlogger

# "" regex matches with anything, i.e. any field
with vlogger.get_source("my_log.wpilog", [""]) as source:
    for field in source:
        print(field)

Initializing a specific source

If the file/connection source is known, it may be faster and more readable to explicitly initialize the specific source. This example uses the Hoot source, which requires a reference to the owlet executable (if not found in PATH).

from vlogger.sources.wpilog import Hoot

with Hoot("my_log.hoot", ["^MyTargetFields$"], owlet="../my-owlet") as hoot:
    for field in hoot:
        print(field)

Merging sources

Vlogger has the ability to merge multiple sources into one iterable that will be parsed in chronological order. While it has been tested, keep in mind that some sources such as WPILog and even NT4 have been found to itself be store/give data in a non-chronological order. While it has a very low error rate, it is still something to keep in mind when using this feature.

import vlogger

with vlogger.get_source("my_log.wpilog", [""]) as wpilog, \
     vlogger.get_source("my_log.hoot", [""]) as hoot:
    for field in vlogger.merge_sources(wpilog, hoot):
        print(field)

Notes

Vlogger uses the logging library internally to log information about the sources, but by design does not configure the logger at all. This means that program that uses Vlogger has the responsibility of setting up the logger.

Contributing

Contributions are always welcome, especially tasks like adding new sources or fixing bugs. If you are making a big change, please create an issue beforehand to come up with a plan before finishing the code.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

frc_vlogger-1.3.2.tar.gz (12.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

frc_vlogger-1.3.2-py3-none-any.whl (14.3 kB view details)

Uploaded Python 3

File details

Details for the file frc_vlogger-1.3.2.tar.gz.

File metadata

  • Download URL: frc_vlogger-1.3.2.tar.gz
  • Upload date:
  • Size: 12.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.3

File hashes

Hashes for frc_vlogger-1.3.2.tar.gz
Algorithm Hash digest
SHA256 0fa1a4a011f77d393ccb3706c7e55941839546709a283488a56340156534bc5d
MD5 2617a02fe2cd8dcea282afd55a2b8e26
BLAKE2b-256 49edba8514039b2e127d328c965fde816361d52ff5382ad624ce531136e2ccc5

See more details on using hashes here.

File details

Details for the file frc_vlogger-1.3.2-py3-none-any.whl.

File metadata

  • Download URL: frc_vlogger-1.3.2-py3-none-any.whl
  • Upload date:
  • Size: 14.3 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.13.3

File hashes

Hashes for frc_vlogger-1.3.2-py3-none-any.whl
Algorithm Hash digest
SHA256 5e40b1f96eef336ec86ac9051dca9bfc3d47d7f95f52d6d4dc2abeb4a5f54ecc
MD5 9899274bbb7a84712b5cd79d8616bfec
BLAKE2b-256 8fe1268de2965960152e081a8d5b80954e2f0efcf6368d0c2b3cff07069ff510

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page