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

Allow separate configuration of tasks and constraints #4

Open
1 of 2 tasks
dmronga opened this issue Mar 7, 2022 · 0 comments
Open
1 of 2 tasks

Allow separate configuration of tasks and constraints #4

dmronga opened this issue Mar 7, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@dmronga
Copy link
Contributor

dmronga commented Mar 7, 2022

Currently, what is known as a "task" in WBC literature is entitled "constraint" in the software. This is a legacy from the iTaSC software, where this naming scheme has been used. In fact, using a QP solver, tasks are usually included in the cost function, so this naming is actually wrong. Also, "constraints" of a QP solver are currently hard coded in the WBC scene, i.e., they are not configurable.

  • Rename "Constraint" to "Task" (this should not effect .yml config files in Rock)
  • Add configuration option for hard constraints, e.g., joint velocity. This is specific to the type of WBC used. Constraints should be generic as tasks, so that we can also constraint sth. like self collisions or CoM position
@dmronga dmronga added the enhancement New feature or request label Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant