Bad call to API error

Provide a musculoskeletal model of the full thoracolumbar spine and rib cage for researchers to use in their investigations of spine and thorax kinematics and dynamics.
POST REPLY
User avatar
Obidah Alawneh
Posts: 25
Joined: Wed Sep 23, 2020 11:36 am

Bad call to API error

Post by Obidah Alawneh » Wed Jul 21, 2021 2:35 pm

What does this error mean? and how can it be fixed?
Attachments
ERRORFB.JPG
ERRORFB.JPG (211.89 KiB) Viewed 430 times

User avatar
Jacob J. Banks
Posts: 88
Joined: Tue Jul 15, 2014 5:17 am

Re: Bad call to API error

Post by Jacob J. Banks » Wed Jul 21, 2021 2:39 pm

It's pretty difficult for me to say without knowing what your doing/running.
Jake Banks

User avatar
Obidah Alawneh
Posts: 25
Joined: Wed Sep 23, 2020 11:36 am

Re: Bad call to API error

Post by Obidah Alawneh » Wed Jul 21, 2021 2:42 pm

I created a motion file using the motion file from arm 26 as a guide, and then tried to run static optimization using that motion.

The time goes from 0 to 0.1 in a 0.001 increase per step.
The motion loads fine, but when running the StOP I get this error!

Thanks,
Obidah Alawneh

User avatar
Jacob J. Banks
Posts: 88
Joined: Tue Jul 15, 2014 5:17 am

Re: Bad call to API error

Post by Jacob J. Banks » Wed Jul 21, 2021 3:11 pm

I would need to see the .mot, setup file, actuators file, and model.
By 'loads fine' do you mean you can get it to manipulate the model?
Jake Banks

User avatar
Obidah Alawneh
Posts: 25
Joined: Wed Sep 23, 2020 11:36 am

Re: Bad call to API error

Post by Obidah Alawneh » Wed Jul 21, 2021 3:33 pm

Yes that is what I mean by loads fine.

I'm going to attach the motion file. The model is the male full body model that was created by your team.

Also, I am currently running a Static Optimization on a different motion file, I grt a message that says "time=0.11667 Performance=8.86405 Constraint violation=1811.56" is that normal or does that mean there is something wrong? See image attached.

Thanks for your help,
Obidah Alawneh
Attachments
optimization failed.JPG
optimization failed.JPG (40.99 KiB) Viewed 389 times
SEATED_MOTION_ONEFRAME.mot
(37.46 KiB) Downloaded 26 times

User avatar
Jacob J. Banks
Posts: 88
Joined: Tue Jul 15, 2014 5:17 am

Re: Bad call to API error

Post by Jacob J. Banks » Thu Jul 22, 2021 6:21 am

Your .mot file had some little errors in it. It had the incorrect number of rows (should be 101), an extra/redundant L4/L5 AB column (I think that was the column), and blank values in the ankle coordinates. The latter error is what caused things to really crash. I could tell something was wrong prior to SOpt, in as our .mot file wouldn't play.
I also made an actuator file, and saved my SOpt setup (so you can just load it, but you will have to find the correct paths for your computer).
You don't need 101 rows for this sim. I think 2 would do, but 5-10 to be safe.
Jake Banks
Attachments
test2.zip
(135.7 KiB) Downloaded 29 times

User avatar
Obidah Alawneh
Posts: 25
Joined: Wed Sep 23, 2020 11:36 am

Re: Bad call to API error

Post by Obidah Alawneh » Tue Jul 27, 2021 2:20 pm

Thank you so much, it is working as needed!

Really appreciate your help!

POST REPLY