Mobile Robot Control 2020 Group 2: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Logs) |
||
| Line 27: | Line 27: | ||
---- | ---- | ||
Agenda | Agenda | ||
*Introduction meeting with tutor | *Introduction meeting with the tutor | ||
* | *Discuss assignments to be completed | ||
*Discuss preliminary design and algorithm | *Discuss preliminary design and algorithm | ||
| Line 39: | Line 39: | ||
*Gitlab should be used. | *Gitlab should be used. | ||
*Wiki: At the end of every meeting a clear list has to be made of actions that should be done. | *Wiki: At the end of every meeting a clear list has to be made of actions that should be done. | ||
*Important dates and information about first assignment: The design document should be hanged in on may 4th as PDF and text should not be mentioned on wiki. | *Important dates and information about the first assignment: The design document should be hanged in on may 4th as PDF and text should not be mentioned on the wiki. | ||
*Design document is the document that describes how software will look like, which includes requirements, functions, components, specifications and interfaces. | *Design document is the document that describes how the software will look like, which includes requirements, functions, components, specifications and interfaces. | ||
*Requirements: robot's speed constraints and etc. | *Requirements: robot's speed constraints and etc. | ||
| Line 74: | Line 74: | ||
*Questions about odometry data | *Questions about odometry data | ||
*Question on identifying exit | *Question on identifying exit | ||
*Questions on | *Questions on GitHub | ||
*Discuss work to be done | *Discuss work to be done | ||
| Line 83: | Line 83: | ||
*The robot overshoots on rotating to the right. This is much worse than when rotating to the left. | *The robot overshoots on rotating to the right. This is much worse than when rotating to the left. | ||
*The tutor is going to look into the simulator since it might be a bug in there. He will let us know as soon as possible. | *The tutor is going to look into the simulator since it might be a bug in there. He will let us know as soon as possible. | ||
*Take into account that the exit ''could'' be aligned with the | *Take into account that the exit ''could'' be aligned with the sidewall of the room meaning there is only one corner to identify instead of 2. | ||
*Gitlab tutorial is online and should help us figure it out. | *Gitlab tutorial is online and should help us figure it out. | ||
*Group members have to use git clone to get the master repository on their pc. | *Group members have to use git clone to get the master repository on their pc. | ||
*Slip is not enabled by default. It has to be enabled in the config file when needed in simulation. | |||
---- | ---- | ||
Work division | Work division | ||
*Wall following | *Wall following algorithm -> Bjorn and Marzhan | ||
*Wall finding and exit scanning -> Spyros and Arjun | *Wall finding and exit scanning -> Spyros and Arjun | ||
*Wall alignment and exit corridor movement -> Bart and Joey | *Wall alignment and exit corridor movement -> Bart and Joey | ||
| Line 95: | Line 96: | ||
---- | ---- | ||
Next meeting | Next meeting | ||
* Friday May 8th | * Friday, May 8th, 2 pm group meeting on progress (without tutor). | ||
* Monday May 11th | * Monday, May 11th, 11 am final meeting before escape room challenge (with the tutor). | ||
Revision as of 10:21, 5 May 2020
Group members
Marzhan Baubekova - 1426311
Spyros Chatzizacharias - 1467751
Arjun Menaria - 1419684
Joey Verdonschot - 0893516
Bjorn Walk - 0964797
Bart Wingelaar - 0948655
Design Document
Design document for the escape room challenge can be found here:
File:Mobile Robot Control Design Document Group2.pdf
Logs
Meeting 1
Date: 28-04-20
Time: 10:00
Platform: MS Teams
Agenda
- Introduction meeting with the tutor
- Discuss assignments to be completed
- Discuss preliminary design and algorithm
Meeting notes
- The tutor's role is to guide and answer questions. The tutor is present at the weekly meetings.
- Robot description: the unit of the laserdata distance is [m] and the angle is in radians; the robot is about 40*20cm.
- Gitlab should be used.
- Wiki: At the end of every meeting a clear list has to be made of actions that should be done.
- Important dates and information about the first assignment: The design document should be hanged in on may 4th as PDF and text should not be mentioned on the wiki.
- Design document is the document that describes how the software will look like, which includes requirements, functions, components, specifications and interfaces.
- Requirements: robot's speed constraints and etc.
Meeting 2
Date: 01-05-20
Time: 14:00
Platform: MS Teams
Agenda
- Discuss the progress
- Discuss the design document
Meeting notes
- "Specifications and Requirments" section of the document design was discussed
- Finite State Machine was reviewed
- Action: meet on Monday (4th of May) to proof-read the report
Meeting 3
Date: 05-05-20
Time: 10:00
Platform: MS Teams
Agenda
- Questions about odometry data
- Question on identifying exit
- Questions on GitHub
- Discuss work to be done
Meeting notes
- The robot overshoots on rotating to the right. This is much worse than when rotating to the left.
- The tutor is going to look into the simulator since it might be a bug in there. He will let us know as soon as possible.
- Take into account that the exit could be aligned with the sidewall of the room meaning there is only one corner to identify instead of 2.
- Gitlab tutorial is online and should help us figure it out.
- Group members have to use git clone to get the master repository on their pc.
- Slip is not enabled by default. It has to be enabled in the config file when needed in simulation.
Work division
- Wall following algorithm -> Bjorn and Marzhan
- Wall finding and exit scanning -> Spyros and Arjun
- Wall alignment and exit corridor movement -> Bart and Joey
Next meeting
- Friday, May 8th, 2 pm group meeting on progress (without tutor).
- Monday, May 11th, 11 am final meeting before escape room challenge (with the tutor).