-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Moco Feature Request] Expose functionality in MocoTrack::configureStateTracking() and MocoTrack::configureMarkerTracking() #3154
Comments
Hi @nathantpickle, we provide the |
Hi @nickbianco - I have a model that contains a
Because My thought was to just replicate the setup that occurs inside Maybe there's another way around the issue I'm having? |
Ah, I see. Just checking, when you call If that doesn't work, I don't really have a better alternative at the moment. This is definitely a limitation of the current In the meantime, it shouldn't be too hard to convert |
Correct, it fails to return from Thanks for the tip on converting to Python. I'll go that route as a workaround for now. |
No problem @nathantpickle. Let me know if you have any questions about getting your workaround going. I'll leave this issue open until we implement a proper fix. |
Just to follow up, I was able to replicate the functionality I need in Python without too much trouble. Also, I haven't tested this code, but here is roughly what I would expect a utility function to look like. This is the section of code I ended up replicating in Python:
If
Something similar could be done for These are kind of nitpicky changes, but would save people a bit of time if they want to set up state tracking (including derivatives) with a generic |
It would be useful to be able to replicate a MocoTrack optimization using a generic MocoStudy. Pretty much everything in MocoTrack can be easily replicated, except for these two methods, which contain some fairly complicated processing of state and marker trajectories.
Could the functionality in these methods be made available somewhere else, for example in MocoUtilities, so it can be used with a generic MocoStudy?
The text was updated successfully, but these errors were encountered: