carmichaelong

Having some feedback/output on what's being done behind the scenes could also help. For instance, the radians issue was found because of the `tracke_states.sto` file. While the input had `inDegrees=yes`,...

Oops, output file = `tracked_states.sto` file. That's a typo.

Definitely. Will plan on trying to get a minimal example for C++ this week.

I didn't explicitly call `unseal()` from MATLAB. I was running `exampleMocoTrack` as is, and that error occurs, pointing at https://github.com/opensim-org/opensim-moco/blob/master/Moco/Bindings/Java/Matlab/Examples/exampleMocoTrack/exampleMocoTrack.m#L194 Maybe an `unseal()` call needs to be added to the...

`Invalid_Number_Detected` also occurred for me in the C++ example for the muscle driven part of `ExampleMocoTrack`

I definitely thought about this a lot, but all I ever ended up realizing was it was depended on the user's application. Could always just do a clamp step right...

Oh you meant including core side as well. A (possibly) relevant discussion about this type of thing can be found in https://github.com/opensim-org/opensim-core/issues/2035.

I don't know the exact differences or reasons for different versions of the geometry. However, in general, it often can make sense to have different files for models. For instance,...

Also need to keep in mind that we decided to keep 3.0+ style models rather than convert to 4.0+ models in the repo

This was official 4.4 off the simtk website.