Verify cost term components #393
Open
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.
Added a function after parsing treatment optimization settings that parses the cost and constraint terms and verifies that they are valid.
No verification is done for bodies or markers because those are not immediately available after parsing. We could potentially play with some opensim API calls to get all of the bodies and markers in use and verify those fields as well.
If there is an incompatible cost or constraint term, an error message is displayed in the command window. I do not have any errors currently, but I can do that if we want.
@SpencerTWilliams I think we should still have a dry run of computeGpopsEndpointFunction so that we can make sure everything works and give error messages in places that we want instead of inside gpops.