Machine Vision: Gripper behavior inconsistent with guidance documentation

[Chenrun-DONG]

Hi contributors,
While working on the Machine Vision (MV) exercise, I discovered an inconsistency regarding the GripperSet() function with guidance document.

The guidance document for GripperSet states:

"— 100 = fully open, 0 = fully closed."

However, the actual behavior in the Gazebo simulation is the exact opposite:

Setting it to 0 causes the gripper to open，Setting it to 100 causes the gripper to close.

Within the HAL.py implementation, there is a clear contradiction between the function's header and its body:

def GripperSet(relative_closure, wait_time):
    """Set gripper closure percentage (100% full open, 0% full closed)""" # 
    # ...
    if EXECUTION["Success"] == True:
        if relative_closure == 0:   <-- Detach happens when relative_closure == 0
            detach()  # Automatic object dettach from gripper when full open (0%) # 

To Reproduce

import HAL
# Expected: Open. Reality: Closes.
HAL.GripperSet(100, 2.0) 

# Expected: Close. Reality: Opens and triggers detach().
HAL.GripperSet(0, 2.0)

Screenshots
Guidance document states:

[Chenrun-DONG]

I noticed that guidance documentation refers to the variable as percentage_open, the actual parameter name in the GripperSet function is relative_closure.

It appears that the guidance text and the function's docstring still follow the percentage_open logic (where 100 is open), but the actual implementation treats the input as the "degree of closure" (where 100 is closed). This seems to be a minor oversight from a migration process, but it creates some confusion for students completing this exercise.

I think it would be more appropriate to update the guidance document to match the actual variable name and simulation behavior.

[javizqh]

This exercise is currently being updated, so that kind of behavior may appear. Thanks for noticing, we will take it into consideration when finishing the new version