Tracing of federate interactions #1632
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit fab6dc5.
…into tracing-federates
…federates communication. This version accounts for network latency and clock synchronization
…tter trace position in reactor-c
cmnrd
requested changes
Mar 13, 2023
…into tracing-federates
lhstrh
approved these changes
Mar 24, 2023
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR (co-authored by @ChadliaJerad) adds tracepoints for interactions between federates and the RTI plus a visualization tool for the resulting traces. A major goal is to enable optimizing coordination of federated programs by reducing the number of RTI-federate interactions. It adds a command-line utility called
fedsdthat generates sequence diagrams (augmented with physical time) for federate interactions with the RTI (see an example below).This PR relies on the tracing-federates branch of reactor-c, which should be merged first. To use it, PR #1642 must also be merged first (or else you have to manually edit the launch script to add the
-toption to the RTI).The
fedsdutility and the other utilities inutil/tracingshould probably be split off into a separate repo dedicated to analysis and visualization of LF programs, but that should be done in a separate PR and should be accompanied with setting up regression tests for that repo.Example federated program:
Running this generates three
.lft(trace) files. Then running:produces a visualization of the trace. A segment is shown below showing the one message flowing from ping to pong and back again: