Hi Mahshida,

I'm pretty sure that will get fixed up straight away if you change the ordering of the columns in your .mot file. Just look at the column order in one that displays appropriately from the example resource folders and then replicate that - it should be a quick fix.

Aaron

Hi Kevin, Not sure if the automatic scaling tool will allow you to do this as I'm unfamiliar, but in traditional scaling you can also add weights to joint coordinates to be a certain value (e.g. 0 degrees if you are confident they are in a neutral position). These coordinate scales also have weights...

Hi Mahshida, I recently learnt that the order of the GRF components in the .mot file (i.e. the force, point and torque data) needs to be a particular way (I think it needs to be 3 x force, 3 x point, 3 x torque) for it to display correctly in the GUI visualiser. I had them in a different order and I...

Hi Matt, Unfortunately no, I don't think we were that precise with how we placed each time - particularly as we were experimenting with camera positions and moving things a little around in the early stages. This is useful info for next time though. As an FYI the calibration of sorts between the sta...

Hi OpenCap Team, I'm wondering if there is a way to check some potential processing and camera issues from recent sessions we've run. Across a session we have some trials that work and others that haven't, and when trying to reprocess these locally the Python console either outputs that the trial fa...

Hi OpenCap Team, I have reviewed this and this forum post, and I can gather that the opencap origin/global coordinate relates to the position of the checkerboard origin. We are collecting opencap data concurrently with a motion capture system and I would like to be able to align the coordinate syste...

Hi Nick, That makes sense given I could get various other types to work but not the Vector. I was trying to compute a new output from a custom class I've created - but have since realised that maybe a Vector isn't the best data type for an output in the end - or I might not end up using an output an...

Hi Mohammad, I don't think the offset times will work and there is now way to set different times from what I understand. I think OpenSim will always look for corresponding time stamps across all different data types. The easy solution here is to edit/synchronise the original data files so that the ...

Hi Moco Team, I'm trying to apply the analyze() command to a Moco trajectory in C++ to get a model component output which is a SimTK Vector type. I get an error ('SimTK::VectorBase<ELT>::TNeg': cannot access private typedef declared in class 'SimTK::VectorBase<ELT>') with the following code: analyze...

Hi Lucy, This might be due to the allowable motion for pelvis rotation, list and tilt. I've had similar issues where the pelvis could only rotate 90 degrees yet it needed to go 180 degrees as a participant was moving in the opposite direction to usual. IK then fits as best it can within the allowabl...