Nick Bianco

### Brief summary of changes Added property `normalize_tracking_error` to `MocoContactTrackingGoal` to allow users to normalize the 3D contact tracking error based on the contact tracking data. ### Testing I've completed...

Add setters to `DataTable.h` to make setting columns scripting-friendly

2

### Brief summary of changes This PR introduces the methods `setDependentColumnAtIndex` and `setDependentColumn` (two signatures each) for setting dependent columns in `DataTable`s. These are more scripting-friendly, whereas the `upd`-based methods...

### Brief summary of changes Updated `report.py` to provide a more flexible way to provide a list of colors for each of the plotted trajectories. ### Testing I've completed -...

It is currently not possible to use Moco after building with `OPENSIM_WITH_CASADI` enabled and `OPENSIM_WITH_TROPTER` disabled because the Ipopt install is tied in with the tropter install scripts (look [here](https://github.com/opensim-org/opensim-core/blob/524cb877dcea6d67ce7e68ad994792623c80663a/Vendors/CMakeLists.txt#L2),...

[Moco] Fix intermediate callback function for `MocoCasADiSolver`

2

Currently, setting the 'output_interval' property for `MocoCasADiSolver` causes problems to immediately fail. Reported by Reed Gurchiek.

Suggested by @psbiomech.

Provided an option that allows data tables specified programmatically by users in `MocoTrack` and `MocoInverse` to get serialized when the `MocoStudy` is saved to an XML file. Based on conversation...

### Brief summary of changes - Include `PathWrap` objects in `ModelFactory::replaceMusclesWithPathActuators` - Add `ModOpReplaceMusclesWithPathActuators` to ModelOperators.h ### Testing I've completed - Added test to `testModelProcessor.cpp` ### CHANGELOG.md (choose one) -...

`MocoContactTrackingGoal` has the method `setProjection()` which allows users to specify which components of the contact force to track. This should be implemented in all MocoGoals tracking 3D data (e.g., `MocoAngularVelocityGoal`,...

Add default bounds for all Components with auxiliary state variables

1

In Moco, we automatically [set bounds for actuators with activation dynamics](https://github.com/opensim-org/opensim-core/blob/959fc82e6d8ff484bfd15839a6e89545142490f3/OpenSim/Moco/MocoProblemRep.cpp#L461) based on the bounds on the control for that actuator. For components with non-activation state variables (i.e., "auxiilary" state...