A few beginner questions about Moco
Posted: Wed Dec 07, 2022 12:50 pm
Hi there,
I'm new to using Moco and I've been through the documentation and some of the example files, and after going through those I had a few questions I wanted to ask. For context, I'm primarily working with 3D gait data, so I was looking through the MocoTrack and MocoInverse examples for 3DWalking in Matlab.
First, what is the main advantage of MocoTrack? Does the addition of the cost error make the results from MocoTrack more reliable or accurate than what we get from MocoInverse?
Second, when thinking about the workflow, I noticed that for muscle-driven tracking and inverse example problems, the example files reference a 'coordinates.sto' file, but it's not clear where this coordinate file comes from. I noticed that after running the RRA tool on the data that I was working with that there was a file named '3DGaitModel2354-RRA_2_Kinematics_q.sto', which had the same 'Coordinates' heading on it as the 'coordinates.sto' file used in the MocoTrack/Inverse examples. Is that '3DGaitModel2354-RRA_2_Kinematics_q.sto' file the one that's being referenced in the MocoTrack/MocoInverse examples? If so, does that mean that you need to run the RRA tool on your data before using Moco, or is there another way to generate that 'coordinates.sto' file?
Third, what would the best way be to check that your Moco results are 'good', so to speak? Are there error values of sort that we can reference?
Thanks again for the help.
I'm new to using Moco and I've been through the documentation and some of the example files, and after going through those I had a few questions I wanted to ask. For context, I'm primarily working with 3D gait data, so I was looking through the MocoTrack and MocoInverse examples for 3DWalking in Matlab.
First, what is the main advantage of MocoTrack? Does the addition of the cost error make the results from MocoTrack more reliable or accurate than what we get from MocoInverse?
Second, when thinking about the workflow, I noticed that for muscle-driven tracking and inverse example problems, the example files reference a 'coordinates.sto' file, but it's not clear where this coordinate file comes from. I noticed that after running the RRA tool on the data that I was working with that there was a file named '3DGaitModel2354-RRA_2_Kinematics_q.sto', which had the same 'Coordinates' heading on it as the 'coordinates.sto' file used in the MocoTrack/Inverse examples. Is that '3DGaitModel2354-RRA_2_Kinematics_q.sto' file the one that's being referenced in the MocoTrack/MocoInverse examples? If so, does that mean that you need to run the RRA tool on your data before using Moco, or is there another way to generate that 'coordinates.sto' file?
Third, what would the best way be to check that your Moco results are 'good', so to speak? Are there error values of sort that we can reference?
Thanks again for the help.