Update README.md#127
Conversation
6979cb5 to
5d1e23d
Compare
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
5d1e23d to
e8b3f0c
Compare
| - **SteadyTime**: Monotonic time for duration measurements and timeouts | ||
| - **HighResSteadyTime**: High-precision monotonic time for precise timing applications | ||
| - **VehicleTime**: PTP-synchronized time for distributed automotive applications requiring initialization | ||
| - **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads |
There was a problem hiding this comment.
I'm not sure, we need to mention it here.
it is the implementtion details, not the actual fucntionality
| - **HighResSteadyTime**: High-precision monotonic time for precise timing applications | ||
| - **VehicleTime**: PTP-synchronized time for distributed automotive applications requiring initialization | ||
| - **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads | ||
| - **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data |
There was a problem hiding this comment.
it is being used currently in PTP based timebase. I havea feeling, the current formulation is missleading
There was a problem hiding this comment.
not sure I understand your point but updated the wording to "timebase"
| - **Unified API**: Type-safe `Clock<Tag>::GetInstance().Now()` returns `ClockSnapshot<TimePoint, Status>` with atomic time + metadata reads | ||
| - **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data | ||
| - **Time Infrastructure** | ||
| - **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker |
There was a problem hiding this comment.
why do we need to mention here message broker?
| - **Event Subscription**: `Subscribe<EventType>()` / `Unsubscribe<EventType>()` for status changes and PTP protocol data | ||
| - **Time Infrastructure** | ||
| - **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker | ||
| - **TimeSlave**: PTP protocol implementation with offset calculation and rate adjustment |
There was a problem hiding this comment.
it is not the PTP protocol implementaiton only.
Could you elaborate bit more?
There was a problem hiding this comment.
added more detail
| - **Time Infrastructure** | ||
| - **TimeDaemon**: Plugin-based time distribution daemon with IPC message broker | ||
| - **TimeSlave**: PTP protocol implementation with offset calculation and rate adjustment | ||
| - **Test Utilities**: Mock backends and `ScopedClockOverride` for comprehensive testing |
There was a problem hiding this comment.
That is applicable to the interfaces only, but iun the full list.
Suggerstion, to update the list in general
There was a problem hiding this comment.
Moved to clock domain section
| > NOTE: This is just proposal, the final decision is on module maintainer how | ||
| > the module code needs to be built. | ||
| ```bash | ||
| bazel test //... |
There was a problem hiding this comment.
here as well, suggest to specify the score and examples subfoldeers in oder to minimize the risk not to touch the filex, which should be not be run.
also add the config
| bazel test //tests/... | ||
| **Linux AArch64**: | ||
| ```bash | ||
| bazel build --config=time-arm64-linux //... |
There was a problem hiding this comment.
here and everywhere: add the sibfolders
| - **Rust:** `clippy`, `rustfmt`, `Rust Unit Tests` | ||
| - **CI/CD:** GitHub Actions for automated builds and tests | ||
| ```bash | ||
| bazel test --config=time-x86_64-linux --config=asan_ubsan_lsan --build_tests_only //... |
There was a problem hiding this comment.
Does the asan_ubsan_lsan donfig alrady contains the time-x86_64-linux one?
There was a problem hiding this comment.
Looking at .bazelrc, I think no, it just sets sanitizer flags, debug symbols and test filters
| ## 💡 Examples | ||
|
|
||
| - A **centralized docs structure** is planned. | ||
| Working examples demonstrating clock usage patterns, testing approaches, and integration techniques. See [examples/](examples/) for complete usage examples. |
There was a problem hiding this comment.
I would believe, i nthe examples/ there is no documentation available. at lease in the root folder.
then either need to add docs there or add some usefull info and explanation here
There was a problem hiding this comment.
added more detail
| │ ├── time/ # Clock domains (SystemTime, SteadyTime, etc.) | ||
| │ ├── time_daemon/ # Time distribution daemon | ||
| │ ├── time_slave/ # PTP synchronization implementation | ||
| │ └── ts_client/ # Time status utilities (internal) |
There was a problem hiding this comment.
it is not hte utility
it is the library to communicate with time slave
Improvement
Description
Updates README.md to contain relevant info for the repo. Uses lifecycle as a guide.
Related ticket
closes #124 (improvement ticket)