Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The joint velocity (qdot) in stage 3 is always zero #1

Closed
jgoenetxea opened this issue Sep 21, 2021 · 1 comment
Closed

The joint velocity (qdot) in stage 3 is always zero #1

jgoenetxea opened this issue Sep 21, 2021 · 1 comment

Comments

@jgoenetxea
Copy link

Hi @soshishimada,

Thank you for sharing such an interesting piece of code with the research community. The captured motion looks amazing.

However, there is something that I do not understand in the implementation.

It is about the body joint velocity values computed in stage 3. In the code, the velocity for all the joints is always zero. However, the velocity looks like a key value to calculate the estimated pose in eq.(1) and the desired acceleration in eq.(4). It is also part of c matrix computation. Is this a negligible value?

Moreover, in the same function, the estimated body pose is computed with:

...
            """  Pose update """ 
            q =  pre_q + delta_t * qdot + acc*delta_t * delta_t/2
...

I assume that this is a combination of both functions included in eq. (1). However, the acceleration is divided by 2, but I do not where does it come from.

Kind regards.

@soshishimada
Copy link
Owner

Hi, sorry for the late reply. Somehow I didn't get a notification.

Apparently, I wrote the finite difference part wrongly when I was reimplementing PhysCap. It's updated now. Velocity is updated every iteration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants