Michael Sherman
Michael Sherman
Could this be addressed by just good examples & tutorials? Or is the current feature set just too awful?
[Capturing a 1:1 discussion w/Alejandro] Thoughts on how to present multibody modeling elegantly 1. User defines Plant structure via Links and Joints, producing a directed (parent->child) graph, plus some disconnected...
Assigned to Russ for disposition
This PR still needs a feature reviewer assigned.
Maybe "PublishTiming" instead of "HybridPublish" for the enum?
Per f2f discussion, a minor correction to the spec above: The current behavior looks like this: time t -> unrestricted update(t) -> discrete update(t) -> advance time -> publish(t +...
Implementation note: Looking at the AdvanceTo code, the (maybe non-intuitive) modification we want to make is to modify the behavior here: ```c++ // At this point merged_events_ has any publish...
Terminology suggestion: PublishTiming: BeginningOfStep, EndOfStep I think that would be easier for users to understand than pre- and post-publish.
Would be great to get a PR for this!