Skip to content

Latest commit

 

History

History
37 lines (27 loc) · 2.98 KB

EXPORT.md

File metadata and controls

37 lines (27 loc) · 2.98 KB
Raw

Exporting Log Data

< Return to homepage

In Control includes a flexible system for exporting log data as a CSV or WPILOG file. The export functions work when viewing a log file or when connected to a live data source. Possible use cases include:

  • Converting a WPILOG file to CSV for analysis in other application.
  • Exporting a WPILOG file based on NetworkTables data, for later access.
  • Saving a WPILOG with a limited number of fields (and duplicate values removed) to reduce file size.

To view options for exporting, click "Data" > "Logs" > "Export Data..." or press cmd/ctrl + E.

Export options

The following options are provided when exporting:

  • Format: Sets the general format of the exported file. See options below.
    • CSV (Table): Comma separated values, where each row represents a distinct timestamp and each column represents a field (plus a column for the timestamp value). Each row can represent a change in multiple fields.
    • CSV (List): Comma separated values, where each row represents a change in a single field with columns for timestamp, key, and value.
    • WPILOG: Standard WPILOG file that can be opened in In Control, Sapphire, etc.
  • Timestamps: Only for "CSV (Table)". Sets the method for creating new rows. See options below.
    • All Changes: Create a new row when any of the included fields are updated. Other columns will show duplicate values.
    • Fixed: Create new rows at a fixed interval, useful for logs without timestamp synchronization (when many fields are being logged with similar, but not identical, timestamps).
  • Period: Only for "CSV (Table)" with fixed timestamps. Sets the period in milliseconds between each row. Typically, this should match the loop cycle period of the robot code.
  • Prefixes: If blank, include all fields. Otherwise, only include fields that match the prefixes provided (separated with commas). See examples below.
    • "/DriverStation/Joystick0": Include all fields starting with "/DriverStation/Joystick0" (data from the first joystick).
    • "/Flywheels,DS:enabled": Include all fields starting with "/Flywheels" or "DS:enabled" (all data from the flywheel, plus the robot's enabled status).
    • "/Drive/LeftPosition,/Drive/RightPosition": Only include the fields "/Drive/LeftPosition" and "/Drive/RightPosition".

Note: Exported log files may not exactly match the original data. The following changes are made:

  • Duplicate values recorded in the original log file are discarded, and are not included in formats like "CSV (List)" and "WPILOG". This effect can be used to reduce the size of WPILOG files with duplicate values, by opening and then exporting again with the "WPILOG" format.
  • When exporting as "WPILOG", all numeric fields are saved using the "double" or "double[]" types.

An example CSV file exported from In Control is shown below, in the "CSV (Table)" format with timestamps set to "All Changes":

CSV table