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

send option isn't documented anywhere #9

Closed
danielasun opened this issue Apr 3, 2018 · 2 comments
Closed

send option isn't documented anywhere #9

danielasun opened this issue Apr 3, 2018 · 2 comments
Labels
enhancement New feature or request

Comments

@danielasun
Copy link
Collaborator

danielasun commented Apr 3, 2018

send=True is used in the vrep interface to advance to the next timestep at the conclusion of the command.

This feature isn't documented anywhere.

Here is the function in question from vrep_interface.py:

    def set_command_position(self, ids, commands, send=False):
        for i,c in zip(ids,commands):
            vrep.simxSetJointTargetPosition(self._sim_Client_ID, self.joint[i]['sim_handle'], c,
                                            vrep.simx_opmode_oneshot)
        if send:
            self.send_command()
@danielasun danielasun added the enhancement New feature or request label Apr 3, 2018
@danielasun
Copy link
Collaborator Author

Not sure if this should be default True or False. If send is always True, it forces users to use the actuation commands at the end of their control loop because it's advancing the timestep.

@danielasun
Copy link
Collaborator Author

send is now default False, it's not obvious that self.send_command() should be triggered by using set command position in a simulator.

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