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

Standardise path segment format and the respective interpreters #85

Open
abinashmeher999 opened this issue Dec 10, 2015 · 2 comments
Open

Comments

@abinashmeher999
Copy link
Member

The task is to standardise the path segment that will be given by the planner to the controller to realise. The controller will be a separate module that will take the path segment as the input and make sure the bot stays on and follows along the path segment. The controller is a different module to be able to facilitate different controllers possible for different kind of drives. So, by changing the controller only the same path segment can be realised on a different drive.

The basic task of the controller will be to take the path segment and give such velocities to all the wheels so that the bot follows the path segment.

@abinashmeher999 abinashmeher999 added this to the Mahindra RISE Prize milestone Dec 10, 2015
@abinashmeher999
Copy link
Member Author

@parthamishra1996 Are you still working on this? If yes, the first step would be to make a barebones module.

@parthamishra1996
Copy link
Contributor

The breakdown of the task:-

  • Separate the velocity generator from the planner, as the planner should only publish the path.
  • Merge the velocity generator with the controls(this will be specific to the controls).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants