Update!
I tried with another video, and it worked!
I still need to figure out why, but the intrinsic and extrinsic configurations are ok for all trials.
I hope I can get back here with the augmented TRC file.
Best regards.
Search found 139 matches
- Thu Dec 05, 2024 1:20 pm
- Forum: OpenCap
- Topic: OpenCap pipeline locally
- Replies: 13
- Views: 2691
- Wed Dec 04, 2024 2:29 pm
- Forum: OpenCap
- Topic: OpenCap pipeline locally
- Replies: 13
- Views: 2691
Re: OpenCap pipeline locally
About the camera model, I'm using the same metadata file from the OpenCap session. So it is iPhone14,7 for this data. Is that it? Printing CamParamDict I think is right. The inial values are the same, the last ones are different (I suppose this first ones are intrinsic values): {'Cam0': {'distortion...
- Wed Dec 04, 2024 11:38 am
- Forum: OpenCap
- Topic: OpenCap pipeline locally
- Replies: 13
- Views: 2691
Re: OpenCap pipeline locally
Thanks a lot Scott, As I mentioned, I collected gait data with OpenCap online, downloaded the files, and tried running everything locally. I'm using the already used (online) calibration file "cameraIntrinsicsExtrinsics.pickle". So, do you have any guess where to change the camera model in the avail...
- Mon Nov 25, 2024 1:26 pm
- Forum: OpenCap
- Topic: OpenCap pipeline locally
- Replies: 13
- Views: 2691
Re: OpenCap pipeline locally
Hello, everyone; I made some progress in trying to set up the pipeline to run locally. I'm just focusing on using the already available "cameraIntrinsicsExtrinsics.pickle" in the downloaded data from OpenCap, and redoing a pose estimation (creating the TRC file with augmented markers). So far I'm st...
- Mon Sep 30, 2024 1:40 pm
- Forum: OpenSim
- Topic: Issues related to IAA
- Replies: 6
- Views: 1260
Re: Issues related to IAA
Thanks, Mohammadreza!
Has anyone tried creating the configuration of the InducedAcceleration component with code?
Best regards.
Has anyone tried creating the configuration of the InducedAcceleration component with code?
Best regards.
- Fri Sep 27, 2024 7:03 am
- Forum: OpenSim
- Topic: Issues related to IAA
- Replies: 6
- Views: 1260
Re: Issues related to IAA
UPDATE,
I took a leap of faith and tested in OpenSim 4.5, but I got the same behavior in OpenSim GUI.
Best regards.
I took a leap of faith and tested in OpenSim 4.5, but I got the same behavior in OpenSim GUI.
Best regards.
- Fri Sep 27, 2024 1:31 am
- Forum: OpenSim
- Topic: Issues related to IAA
- Replies: 6
- Views: 1260
Re: Issues related to IAA
UPDATE, To make it clearer: analise3 = osim.AnalyzeTool('analise.xml') iaa = analise3.getAnalysisSet().get(0) CS = iaa.updPropertyByName('ConstraintSet') CSo = CS.updValueAsObject() CS_obj = CSo.updPropertyByIndex(1) # <objects> constraintR = CS_obj.updValueAsObject(0) #<RollingOnSurface ... > const...
- Thu Sep 26, 2024 11:52 pm
- Forum: OpenSim
- Topic: Issues related to IAA
- Replies: 6
- Views: 1260
Re: Issues related to IAA
Hello Mohammadreza, I'm getting the same behavior in OpenSim 4.4. It is definitely a bug. When I load the .xml, the IAA field is changed, clearing the information about the bodies in RollingOnSurfaceConstraint. errorIAA.png And it happens as well if you load the .xml file using the API in Python. I ...
- Wed Sep 18, 2024 10:11 am
- Forum: OpenSim Moco
- Topic: segment power analysis
- Replies: 21
- Views: 5773
Re: segment power analysis
Great. That would be awesome. If I could suggest, I also tried creating the .sto file for all contact forces in the model, and it worked well. Just create the .sto remember to insert [force] [Cop] [torque] for all contact geometry using only the halfplane (changing the signs of forces and torques). ...
- Tue Sep 17, 2024 5:24 pm
- Forum: OpenSim Moco
- Topic: segment power analysis
- Replies: 21
- Views: 5773
Re: segment power analysis
Great! And... It worked!!!! For everyone interested in IAA analysis with OpenSim API after a Moco simulation, here are my top tips: Create a ForceReporter file of your simulation Follow the code in https://github.com/opensim-org/opensim-core/blob/main/OpenSim/Moco/MocoUtilities.cpp#L310 , but change...