Mobile Robot Control 2020 Group 2: Difference between revisions
Jump to navigation
Jump to search
(→Logs) |
(→Logs) |
||
Line 36: | Line 36: | ||
*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 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. | ||
'''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 | |||
*Functions: what functions should robot perform, ex.: follow the wall, stop and rotate | *Functions: what functions should robot perform, ex.: follow the wall, stop and rotate | ||
*Interfaces: information exchange between software components | *Interfaces: information exchange between software components |
Revision as of 14:14, 1 May 2020
Marzhan Baubekova - 1426311
Spyros Chatzizacharias - 1467751
Arjun Menaria - 1419684
Joey Verdonschot - 0893516
Bjorn Walk - 0964797
Bart Wingelaar - 0948655
Logs
Meeting 1
Date: 28-04-20
Time: 10:00
Platform: MS Teams
Agenda
- Introduction meeting with tutor
- Dicsuss assigmnets 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 first assignment: The design document should be hanged in on may 4th as PDF and text should not be mentioned on wiki.
- Design document is the document that describes how 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
- Functions: what functions should robot perform, ex.: follow the wall, stop and rotate
- Interfaces: information exchange between software components
- Specifications: dimension safety, ex.: minimum distance from the wall
- Discussed algorithm:following the wall until the hallway is found can be explored
- States in the software can give a clearer overview and is easier for debugging
- Localization is more relevant for the hospital challenge.
- Work division: Design Document: Joey, Bart, Arjun; Software exploration: Marzhan, Spyros, Bjorn.
- Next meeting within the group is arrange on Friday 14:00.
- Next meeting with the tutor is set on 5th of May (Tuesday) at 10:00