Coordinate Speed Calculation & SOpt frame 1 applied speed
Posted: Fri Apr 15, 2022 1:52 pm
I have 2 semi related questions/I have been struggling with... hopefully 1 post is appropriate.
1) How are the state speeds calculated? Is this just a simple 3pt (central?) method form the coordinates? If so, why can't I match them EXACTLY from the state coordinates?
2) Does the static optimization (SOpt) tool make any corrections to the first and last frames 'states'? It appears that the speed from the first frame is generally quite a bit different from the following (and the same for the last frame with the previous ones), as one would expect since it doesn't have the same amount of data points to work with as other frames would. This is of particular concern when trying to match a custom SOpt (MATLAB fmincon) result with the SOpt Tool result. I can't seem to get the first frame to have a similar 'Optimal Forces' (predicted force divided by predicted activation from SOpt Tool) and corresponding Activations. It would appear that the first frame speed used by the SOpt Tool is not what is calculated from the States Tool and is instead closer to the speeds found in the following frames.
Please advise, as I can't seem to find an answer to either in the source code, documentation, or in this forum.
Jake Banks
1) How are the state speeds calculated? Is this just a simple 3pt (central?) method form the coordinates? If so, why can't I match them EXACTLY from the state coordinates?
2) Does the static optimization (SOpt) tool make any corrections to the first and last frames 'states'? It appears that the speed from the first frame is generally quite a bit different from the following (and the same for the last frame with the previous ones), as one would expect since it doesn't have the same amount of data points to work with as other frames would. This is of particular concern when trying to match a custom SOpt (MATLAB fmincon) result with the SOpt Tool result. I can't seem to get the first frame to have a similar 'Optimal Forces' (predicted force divided by predicted activation from SOpt Tool) and corresponding Activations. It would appear that the first frame speed used by the SOpt Tool is not what is calculated from the States Tool and is instead closer to the speeds found in the following frames.
Please advise, as I can't seem to find an answer to either in the source code, documentation, or in this forum.
Jake Banks