-
Notifications
You must be signed in to change notification settings - Fork 190
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
Add Stack Pyramid task and motionplanning solution #683
base: main
Are you sure you want to change the base?
Conversation
Previously max_episode_steps configuration doesn't work because config["eval_env_cfg"] is set based on find(max_episode_steps), which isn't compatible for AsyncVectorEnv. Instead, assuming make_eval_envs make envs with the correct args.max_episode_steps, we can use args.max_episode_steps
…jectory Generation
@@ -16,7 +16,7 @@ | |||
@register_agent() | |||
class Panda(BaseAgent): | |||
uid = "panda" | |||
urdf_path = f"{PACKAGE_ASSET_DIR}/robots/panda/panda_v2.urdf" | |||
urdf_path = f"{PACKAGE_ASSET_DIR}/robots/panda/panda_v3.urdf" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this changed?
def __init__( | ||
self, *args, robot_uids="panda_wristcam", robot_init_qpos_noise=0.02, **kwargs | ||
): | ||
self.num_cubes = 6 # 3 + 2 + 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this variable is not used
z_offset = torch.abs(offset[..., 2] - self.cube_half_size[2]) | ||
xy_flag = xy_offset <= 0.05 | ||
z_flag = z_offset <= 0.05 | ||
logger.debug(f"NEXT TO Distance XY: {xy_offset}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the print statements and logging
@@ -0,0 +1,69 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't usually have per env specific tests. this should be removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. As a side question, I'm curious if there's a reason environments generally don't have per-environment tests?
My rationale for unit testing environment implementation was that it could help ensure the environment works correctly with current and future code changes. However, among different RL environments / framework, I've only come across one instance of environment-specific testing in Gymnasium, specifically in this file:
**Success Conditions:** | ||
- the blue cube is static | ||
- the blue cube is on top of both the red and green cube (to within half of the cube size) | ||
- the blue cube is static |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
repeated line
…es, and reversed change for updating panda version
Thanks for the comments! They should be addressed now, please take a look |
No description provided.