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

Renames Unitree configs in locomotion tasks to match properly #714

Merged
merged 10 commits into from
Aug 2, 2024

Conversation

Mayankm96
Copy link
Contributor

@Mayankm96 Mayankm96 commented Jul 23, 2024

Description

There was a slight inconsistency-- we called unitree_a1, unitree_go1, and at the same time h1 and g1. This MR fixes this inconsistency and adds some more docs.

Type of change

  • This change requires a documentation update

Checklist

  • I have run the pre-commit checks with ./isaaclab.sh --format
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have updated the changelog and the corresponding version in the extension's config/extension.toml file
  • I have added my name to the CONTRIBUTORS.md or my name already exists there

@Dhoeller19
Copy link
Collaborator

Shouldn't we go the other way round and remove the unitree prefix?
All the other companies' robots have no company prefix.

@Mayankm96
Copy link
Contributor Author

Mayankm96 commented Jul 26, 2024

Hm I found the name a1, go1 too short. I think it is clearer to have the prefix unitree? But if you prefer the other way, I can make the change accordingly.

@Mayankm96 Mayankm96 added the enhancement New feature or request label Aug 2, 2024
@Mayankm96 Mayankm96 self-assigned this Aug 2, 2024
@Mayankm96 Mayankm96 changed the title Renames H1 and G1 configs to match in locomotion tasks Renames Unitree robot configs to match in locomotion tasks Aug 2, 2024
@Mayankm96 Mayankm96 changed the title Renames Unitree robot configs to match in locomotion tasks Renames Unitree robot configs in locomotion tasks to match properly Aug 2, 2024
@Mayankm96 Mayankm96 changed the title Renames Unitree robot configs in locomotion tasks to match properly Renames Unitree configs in locomotion tasks to match properly Aug 2, 2024
@Mayankm96 Mayankm96 merged commit 692b177 into main Aug 2, 2024
2 of 3 checks passed
@Mayankm96 Mayankm96 deleted the fix/naming-config branch August 2, 2024 12:39
iamdrfly pushed a commit to iamdrfly/IsaacLab that referenced this pull request Nov 21, 2024
…sim#714)

# Description

There was a slight inconsistency-- we called `unitree_a1`,
`unitree_go1`, and at the same time `h1` and `g1`. This MR fixes this
inconsistency and adds some more docs.

## Type of change

- This change requires a documentation update

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./isaaclab.sh --format`
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file
- [x] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there
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

Successfully merging this pull request may close these issues.

2 participants