Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/foxglove/mcap
MCAP is a modular, performant, and serialization-agnostic container file format, useful for pub/sub and robotics applications.
https://github.com/foxglove/mcap
cpp data deserialization golang python robotics serialization swift typescript
Last synced: about 2 months ago
JSON representation
MCAP is a modular, performant, and serialization-agnostic container file format, useful for pub/sub and robotics applications.
- Host: GitHub
- URL: https://github.com/foxglove/mcap
- Owner: foxglove
- License: mit
- Created: 2021-11-19T19:09:38.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-06-28T11:21:35.000Z (3 months ago)
- Last Synced: 2024-07-05T15:50:00.524Z (3 months ago)
- Topics: cpp, data, deserialization, golang, python, robotics, serialization, swift, typescript
- Language: Python
- Homepage: https://mcap.dev
- Size: 129 MB
- Stars: 452
- Watchers: 10
- Forks: 81
- Open Issues: 91
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# MCAP
MCAP is a modular container format and logging library for pub/sub messages with arbitrary message serialization. It is primarily intended for use in robotics applications, and works well under various workloads, resource constraints, and durability requirements.
## Documentation
- [File format specification](https://mcap.dev/spec)
- [Kaitai Struct definition](./website/docs/spec/mcap.ksy)
- [Motivation](https://mcap.dev/files/evaluation.pdf)
- [Support Matrix](https://mcap.dev/reference)
## Developer quick start
MCAP libraries are provided in the following languages. For guidance on each language, see its corresponding README:
| Language | Readme | API docs | Package name | Version |
| --------------------- | ---------------------- | --------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------------------ |
| C++ | [readme](./cpp) | [API docs](https://mcap.dev/docs/cpp) | `mcap` | [](https://conan.io/center/mcap) |
| Go | [readme](./go/mcap) | [API docs](https://pkg.go.dev/github.com/foxglove/mcap/go/mcap) | | see [releases](https://github.com/foxglove/mcap/releases) |
| Python | [readme](./python) | [API docs](https://mcap.dev/docs/python) | `mcap` | [](https://pypi.org/project/mcap/) |
| JavaScript/TypeScript | [readme](./typescript) | [API docs](https://mcap.dev/docs/typescript) | `@mcap/core` | [](https://www.npmjs.com/package/@mcap/core) |
| Swift | [readme](./swift) | [API docs](https://mcap.dev/docs/swift/documentation/mcap) | | see [releases](https://github.com/foxglove/mcap/releases) |
| Rust | [readme](./rust) | [API docs](https://mcap.dev/docs/rust/mcap) | `mcap` | [](https://crates.io/crates/mcap) |
To run the conformance tests, you will need to use [Git LFS](https://git-lfs.github.com/),
which is used to store the test logs under `tests/conformance/data`.
## CLI tool
Interact with MCAP files from the command line using the [MCAP CLI tool](./go/cli/mcap).
Download the latest `mcap-cli` version from the [releases page](https://github.com/foxglove/mcap/releases).
## License
[MIT License](/LICENSE).
## Release process
Release numbering follows a major.minor.patch format, abbreviated as "X.Y.Z" below.
CI will build the appropriate packages once tags are pushed, as described below.
### Go library
1. Update the `Version` in go/mcap/version.go
2. Tag a release matching the version number `go/mcap/vX.Y.Z`.
### CLI
Tag a release matching `releases/mcap-cli/vX.Y.Z`.
The version number is set at build time based on the tag.
### C++
1. Update the version in all relevant files
- cpp/bench/conanfile.py
- cpp/build-docs.sh
- cpp/build.sh
- cpp/docs/conanfile.py
- cpp/examples/conanfile.py
- cpp/mcap/include/mcap/types.hpp (`MCAP_LIBRARY_VERSION`)
- cpp/mcap/include/conanfile.py
- cpp/test/conanfile.py
2. Tag a release matching the version number `releases/cpp/vX.Y.Z`
### Python
There are several python packages; updating any follows a similar process.
1. Update the version in the appropriate `__init.py__` file
2. Tag a release
- For the core mcap library, match the pattern `releases/python/vX.Y.Z`
- For other packages, use `releases/python/PACKAGE/vX.Y.Z`
- For example, `releases/python/mcap/v1.2.3`
### TypeScript
There are several TS packages; updating any follows a similar process.
1. Update the version in the appropriate `package.json`
2. Tag a release matching `releases/typescript/PACKAGE/vX.Y.Z`
- For example, `releases/typescript/core/v1.2.3`
### Swift
Tag a release matching the version number `releases/swift/vX.Y.Z`
### Rust
1. Update the version in rust/Cargo.toml
2. Tag a release matching the version number `releases/rust/vX.Y.Z`
## Citations
If you use MCAP in your research, please cite it in your work. Our suggested
citation format is:
```
@software{MCAP,
title = {MCAP: serialization-agnostic log container file format},
author = {{Foxglove Developers}},
url = {https://mcap.dev},
version = {your version},
date = {your date of access},
year = {2024},
publisher = {{Foxglove Technologies}},
note = {Available from https://github.com/foxglove/mcap}
}
```
Please replace the version and date fields with the version of the software you
used, and the date you obtained it. Citing MCAP will help spread awareness of
the project and strengthen the ecosystem.