Use plot_trajectory in broadcasting example
#414
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
willGraham01
commented
Feb 13, 2025
This comment was marked as resolved.
This comment was marked as resolved.
niksirbi
approved these changes
Feb 13, 2025
There was a problem hiding this comment.
Thanks @willGraham01, I just have one comment to ged rid of some redundant lines. After that it's good to merge!
Co-authored-by: Niko Sirmpilatze <[email protected]>
This comment was marked as resolved.
This comment was marked as resolved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Description
What is this PR
Why is this PR needed?
#409
What does this PR do?
Uses the
plot_trajectoryfunction in our broadcasting example to reduce load and also show-off our features.References
Closes #409
How has this PR been tested?
Example still works locally and after being built in the docs.
Is this a breaking change?
Does this PR require an update to the documentation?
Checklist: