[Feature Request] New file types for Kleinkram

[tutunarsl]

Context

In many instances robotics data is coupled with common files such as ".svo2, .yaml, .tum". These types are affiliated to results, runtime parameter or configuration files that are needed for post processing.

Request

Enabling CLI and fronted to accept different file types that are tightly coupled to robotic data. Priority is to support upload of these files and

Technical details

To be supported immediate types: .yaml, .svo2, .tum, .db3

Types that can have a preview, .yaml, .tum, these files contain text data while .svo2 is a serialized formats.

On demand I can provide data to test

[wp99cp]

Also consider adding db3.

[wp99cp]

Version 0.51.0 adds experimental support for the requested filetypes .yaml, .svo2, .tum, and .db3. You can upload files via CLI using the --experimental-datatypes in the normal upload command.

Example:

klein upload --experimental-datatypes --create -p "some-project" -m "some-mission" /path/to/a/file.db3

Known Limitations:

• files are uploaded to the mcap bucket
• files cannot be uploaded via the web interface
• files are not linked, e.g. yaml and mcap file does not get linked together
• limited health checks, especially no data validation (etags get computed though)
• combine YAML and YML file type
• remove experimental-datatypes flag from CLI