https://cstwiki.wtb.tue.nl/api.php?action=feedcontributions&user=Ydouven&feedformat=atomControl Systems Technology Group - User contributions [en]2024-03-28T23:09:31ZUser contributionsMediaWiki 1.39.5https://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=63929Robotics Lab Map2019-02-06T14:56:25Z<p>Ydouven: /* Students */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:YanickDouven.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtes'''<br />
| style="text-align:center;" | '''Roy Cobbenhagen'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | j dot scholtes (at) tue dot nl<br />
| style="text-align:center;" | a dot t dot j dot r dot cobbenhagen (at) tue dot nl<br />
| style="text-align:center;" | y dot g dot m dot douven (at) tue dot nl<br />
| style="text-align:center;" | W dot J dot P dot Kuijpers (at) tue dot nl<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''5'''<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:MDolatabadi.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WHoutman.JPG|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:CLopez.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jos Elfring'''<br />
| style="text-align:center;" | '''Marzieh Dolatabadi'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
| style="text-align:center;" | '''Cesar A. Lopez M.'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | W dot Houtman (at) tue dot nl <br />
| style="text-align:center;" | c dot a dot lopez dot martinez dot (at) tue dot nl<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Part-Time Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''TNO'''<br />
| style="text-align:center;" | '''autopilot'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''RoPod'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''6'''<br />
| style="text-align:center;" | '''7'''<br />
| style="text-align:center;" | '''8'''<br />
| style="text-align:center;" | '''9'''<br />
| style="text-align:center;" | '''10'''<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Peter van Dooren<br />
| style="text-align:center;" | Martijn Schipper<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Rik van der Struijk<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | p.v.dooren@student.tue.nl<br />
| style="text-align:center;" | m.a.schipper@student.tue.nl<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Tech United @Home'''<br />
| style="text-align:center;" | '''CCP for Non-Cubic Rooms'''<br />
| style="text-align:center;" | '''Sonar Analysis for Mobile Robots'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Constrained WBC Solved Using QP With Multiple Simultaneous Tasks''' <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''11'''<br />
| style="text-align:center;" | '''12'''<br />
| style="text-align:center;" | '''13'''<br />
| style="text-align:center;" | '''14'''<br />
| style="text-align:center;" | '''15'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:melvindewildt.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Stefan Driessen'''<br />
| style="text-align:center;" | '''Menno Bouma'''<br />
| style="text-align:center;" | '''Melvin de Wildt'''<br />
| style="text-align:center;" | '''Casper Beumer'''<br />
| style="text-align:center;" | '''Daniël Bos'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | s.p.h.driessen@student.tue.nl<br />
| style="text-align:center;" | m.bouma@student.tue.nl<br />
| style="text-align:center;" | m.s.d.wildt@student.tue.nl<br />
| style="text-align:center;" | c.t.j.beumer@student.tue.nl<br />
| style="text-align:center;" | d.j.m.bos@student.tue.nl<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Dynamic obstacle avoidance'''<br />
| style="text-align:center;" | '''Trajectory Control for Mechanical Systems with Simultaneous Impacts'''<br />
| style="text-align:center;" | '''Path planning on the ROPOD'''<br />
| style="text-align:center;" | '''Trajectory Control for Mechanical Systems with Simultaneous Impacts'''<br />
| style="text-align:center;" | '''Automatic flower counting using Multiple Hypothesis Tracking'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''17'''<br />
| style="text-align:center;" | '''18'''<br />
| style="text-align:center;" | '''19'''<br />
| style="text-align:center;" | '''20'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Milan Haverlag'''<br />
| style="text-align:center;" | '''Sjoerd Tunissen'''<br />
| style="text-align:center;" | '''Sjoerd Koopmans'''<br />
| style="text-align:center;" | '''Bas Büthker'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''m.a.haverlag@student.tue.nl'''<br />
| style="text-align:center;" | '''s.a.m.tunissen@student.tue.nl'''<br />
| style="text-align:center;" | '''s.j.m.koopmans@student.tue.nl'''<br />
| style="text-align:center;" | '''b.buthker@student.tue.nl''' <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''internship'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Integrating the eight-wheeled soccer robot in the current software'''<br />
| style="text-align:center;" | '''Heartbeat and breathing detection in in-eye OCT distance measurements'''<br />
| style="text-align:center;" | '''Tech United MSL'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''21'''<br />
| style="text-align:center;" | '''22'''<br />
| style="text-align:center;" | '''23'''<br />
| style="text-align:center;" | '''24'''<br />
| style="text-align:center;" | '''25'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Mathijs Schouten'''<br />
| style="text-align:center;" | '''Martin Cornelis'''<br />
| style="text-align:center;" | '''Martijn Bos'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Huijser'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | m dot c dot w dot schouten (at) student dot tue dot nl<br />
| style="text-align:center;" | '''m.cornelis@student.tue.nl''' <br />
| style="text-align:center;" | m dot p dot bos (at) student dot tue dot nl<br />
| style="text-align:center;" | m dot f dot m dot b dot v dot d dot burgh (at) student dot tue dot nl<br />
| style="text-align:center;" | '''f.c.a.huijser@student.tue.nl'''<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | ''''''<br />
| style="text-align:center;" | '''Semantic Localization'''<br />
| style="text-align:center;" | '''Geometric Linearization'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''Energy Efficient Motion Planning for Mobile Robots'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''26'''<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''28'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Teun Bosch'''<br />
| style="text-align:center;" | '''Sjouke de Zwart'''<br />
| style="text-align:center;" | '''Ilias Aouaj'''<br />
| style="text-align:center;" | '''Chiara Grammatico '''<br />
| style="text-align:center;" | '''Luc Schoonen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | t.j.bosch@student.tue.nl<br />
| style="text-align:center;" | s.w.d.zwart@student.tue.nl<br />
| style="text-align:center;" | i.aouaj@student.tue.nl<br />
| style="text-align:center;" | chiara.grammatico3@gmail.com<br />
| style="text-align:center;" | l.p.a.schoonen@student.tue.nl<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Dynamic Robot Collision Avoidance'''<br />
| style="text-align:center;" | '''Reference spreading and Machine Learning'''<br />
| style="text-align:center;" | '''-''' <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Optimal Irrigation Control'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''31'''<br />
| style="text-align:center;" | '''32'''<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''35'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 45%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Annelore Visker<br />
| style="text-align:center;" | Joeri Roelofs<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | a.j.j.visker@student.tue.nl<br />
| style="text-align:center;" | j.roelofs@student.tue.nl<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''MSc Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Crop Growth Model for Control'''<br />
| style="text-align:center;" | '''Farm Simulator'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''36'''<br />
| style="text-align:center;" | '''37'''<br />
| style="text-align:center;" | '''38'''<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''-'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | -<br />
<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | -<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | -<br />
<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''-'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | -<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''-'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | -<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | -<br />
|-<br />
|}<br />
</center><br />
<br />
== Robotics Research Lab - Wall of Fame ==<br />
In this Wall of Fame all the students that have achieved their Master's Thesis within the Robotics Research Lab will be remembered. <br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WHoutman.JPG|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''EureyeCase: Viscoelastic Modeling of Porcine Eyes for Membrane Peeling Purposes'''<br />
| style="text-align:center;" | ''' '''<br />
|-<br />
! scope="row"| Report<br />
| style="text-align:center;" | [[File:Report_Rozemarijn.pdf]]<br />
| style="text-align:center;" | [[File:Report_Wouter.pdf]] <br />
| style="text-align:center;" | [[File:Report_Freek.pdf]] <br />
|-<br />
! scope="row"| Presentation<br />
| style="text-align:center;" | [[File:Presentation_Rozemarijn.pdf]] <br />
| style="text-align:center;" | [[File:Presentation_Wouter.pdf]] <br />
| style="text-align:center;" | [[File:Presentation_Freek.pdf]] <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2018&diff=46300Embedded Motion Control 20182018-01-22T15:45:59Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
Lectures will be given on Wednesdays from 15.45h-17.45h from in Luna 1.050 or Fridays from 10.45h-12.45h from in Auditorium 11. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| May 2 / May 4<br />
| width="325" | Introduction by ''René van de Molengraft'' (see Canvas!)<br />
| width="325" | Tooling and Infrastructure by ''Wouter Kuijpers'' <br />
|-<br />
| May 16 / May 18<br />
| colspan="2" | Best Practices in System Design for Robot Control by ''Nico Huebel''<br />
|-<br />
| May 23 / May 25<br />
| colspan="2" | First presentation of the design by ''the groups''. 6-minute presentation, about the group's initial design. Afterwards 4 minutes for questions.<br />
|-<br />
| May 30 / June 1<br />
| '''Escape Room competition'''<br />
| Worldmodeling for Experts by ''Wouter Houtman''<br />
|-<br />
| June 6 / June 8<br />
| colspan="2" | Architecture by "Herman Bruyninckx"<br />
|-<br />
| June 13 / June 15<br />
| colspan="2" | Presentation of final design by the ''groups''.<br />
|-<br />
| June 20 / June 22<br />
| colspan="2" | '''Final Competition'''<br />
|-<br />
| June 21 / June 25<br />
| colspan="2" | '''Deadline Wiki Pages'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Check this page regularly to find out the new assignment for Embedded Motion Control in 2018!<br />
<!--<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2017}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2017}}<br />
--><br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. <!--Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
--><br />
= FAQ =<br />
[[Embedded_Motion_Control_2017/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2018 Group 1 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 2 - [[Embedded Motion Control 2018 Group 2 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 3 - [[Embedded Motion Control 2018 Group 3 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 4 - [[Embedded Motion Control 2018 Group 4 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 5 - [[Embedded Motion Control 2018 Group 5 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 6 - [[Embedded Motion Control 2018 Group 6 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 9 - [[Embedded Motion Control 2018 Group 9 | visit wiki ]] - '''Tutor''': <br />
<br />
Group 10 - [[Embedded Motion Control 2018 Group 10 | visit wiki ]] - '''Tutor''':<br />
<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2018/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Maze_competition_2017&diff=42100Embedded Motion Control/Maze competition 20172017-06-16T14:11:15Z<p>Ydouven: </p>
<hr />
<div>The final competition will be held (date to be determined) at the RoboCup soccer field. The goal of this competition is to let PICO autonomously drive through a maze and find the exit. Some facts:<br />
<br />
* Where and when:<br />
** When: to be determined<br />
** Location: RoboCup Soccer field, GEM-N<br />
* Set-up<br />
** Make sure your software is easy to set-up, ''i.e'':<br />
*** Your software can be updated with one easy command, ''e.g.'' 'git pull'<br />
*** Your software can be compiled using 'cmake' and 'make'<br />
*** To start your software, only one executable has to be called<br />
*** '''If your set-up deviates from this method, let us know as soon as possible!'''<br />
* Maze characteristics:<br />
** Exact location of the exit is unknown, but it will be on the boundaries of the maze (which means: PICO has to drive ''out'' of the maze).<br />
** Walls are approximately axis-aligned, meaning all angles are 90 degrees. Approximately means: built by hand, so slight differences may occur.<br />
** Open spaces '''may''' occur<br />
** There '''may''' be loops in the maze, which means that some walls may not be connected to other walls.<br />
* Start, goal and limits:<br />
** PICO will start '''inside''' the maze.<br />
** PICO will '''not''' start in a door area (see below for definition). So, for example, the door will not be directly behind PICO's starting location<br />
** You have finished the assignment if PICO did not drive into walls, found the exit and the whole robot is across the finish line.<br />
** Maximum speed (is limited in PICO): 0.5 m/s translational, 1.2 rad/s rotational. By the way, that's pretty fast (compared to last year's 0.2 m/s), so be careful! You don't ''have to'' drive that fast!<br />
* Doors:<br />
** There is exactly 1 door in the maze<br />
** The door will be situated at a dead end, a dead end being defined as a piece of wall with minimum length 0.5 and maximum length 1.5 with side-walls of at least 0.3 meter length. ('''Picture explaining this will follow shortly''')<br />
** There might be multiple dead ends in the maze, one of which is a door<br />
** You need to pass the door to solve the maze, ''i.e.'', if you cannot open the door, the maze is unsolvable<br />
** The door will open if and only if the following conditions are met:<br />
*** PICO is located within 1.3m distance from the door (''i.e.'', '''no''' part of PICO is located outside the 1.3m range). The 1.3m in front of the door is called the '''door area'''.<br />
*** PICO is '''not''' driving, ''i.e.'', the commanded velocity is 0 (both translational and rotational)<br />
*** PICO '''asks to open the door'''. This will become available from the '''io'''-layer, ''e.g.,:<pre>io.requestOpenDoor()</pre><br />
** '''If''' these conditions are met:<br />
*** The door will start sliding open within 2 seconds from PICO's request<br />
*** The door will slide open to the left '''or''' to the right<br />
*** The door slides open at approximately constant velocity<br />
*** The door is fully open within 5 seconds from PICO's request<br />
** Once the door is open, it will stay open<br />
* Scoring:<br />
** You have 2 attempts (= maximum one restart)<br />
** restart means:<br />
*** PICO restarts at beginning of maze<br />
*** MAZE time (= time used for scoring) is reset, BUT<br />
*** TOTAL time keeps running<br />
** You have a total of 7 minutes for both attempts<br />
** Hit wall = that attempt fails<br />
** PICO standing still for 30 seconds = that attempt fails<br />
** There will be no second attempt if first attempt was successful<br />
<br />
Next you can see an examples of an ''open space'' and a ''door'' and examples:<br />
[[File:emc_labirynth_scheme.png|thumb|center|640px|Scheme of an ''open space'' and a ''door template' and examples]]<br />
<br />
The maze of the final maze challenge is shown in the figure below. You can download this and try it in the simulator, to show that you are able to finish the maze in simulation.<br />
[[File:FinalMaze2017.png|500px|thumb|center|Maze of the final challenge]]</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=File:FinalMaze2017.png&diff=42099File:FinalMaze2017.png2017-06-16T14:08:44Z<p>Ydouven: The maze of the final challenge on June 14th 2017.</p>
<hr />
<div>The maze of the final challenge on June 14th 2017.</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=41592Robotics Lab Map2017-06-14T11:20:38Z<p>Ydouven: /* Students */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:YanickDouven.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtes'''<br />
| style="text-align:center;" | '''Roy Cobbenhagen'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | j dot scholtes (at) tue dot nl<br />
| style="text-align:center;" | a dot t dot j dot r dot cobbenhagen (at) tue dot nl<br />
| style="text-align:center;" | y dot g dot m dot douven (at) tue dot nl<br />
| style="text-align:center;" | W dot J dot P dot Kuijpers (at) tue dot nl<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''5'''<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:MDolatabadi.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WHoutman.JPG|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jos Elfring'''<br />
| style="text-align:center;" | '''Marzieh Dolatabadi'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
| style="text-align:center;" | '''Cesar A. Lopez M.'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | W dot Houtman (at) tue dot nl <br />
| style="text-align:center;" | c dot a dot lopez dot martinez dot (at) tue dot nl<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Part-Time Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''TNO'''<br />
| style="text-align:center;" | '''autopilot'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''RoPod'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''6'''<br />
| style="text-align:center;" | '''7'''<br />
| style="text-align:center;" | '''8'''<br />
| style="text-align:center;" | '''9'''<br />
| style="text-align:center;" | '''10'''<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Zhihao Wu<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Internship'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Tech United @Home'''<br />
| style="text-align:center;" | '''Tech United @Home'''<br />
| style="text-align:center;" | '''Tech United @Home'''<br />
| style="text-align:center;" | '''Tech United @Home'''<br />
| style="text-align:center;" | '''New Ballhandling system''' <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''11'''<br />
| style="text-align:center;" | '''12'''<br />
| style="text-align:center;" | '''13'''<br />
| style="text-align:center;" | '''14'''<br />
| style="text-align:center;" | '''15'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:Lotte_de_Koning.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | '''Chenyang Lu'''<br />
| style="text-align:center;" | '''Jerrel Unkel'''<br />
| style="text-align:center;" | '''Noud Paes'''<br />
| style="text-align:center;" | '''Andrea Macheda'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Erasmus's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''Image Processing and Visual Servoing'''<br />
| style="text-align:center;" | '''Compliant control of RoPod'''<br />
| style="text-align:center;" | '''RoPod Flock Control'''<br />
| style="text-align:center;" | '''RoPod Energy Efficient Motion Planing'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''17'''<br />
| style="text-align:center;" | '''18'''<br />
| style="text-align:center;" | '''19'''<br />
| style="text-align:center;" | '''20'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Mahmoud Al Abbassi'''<br />
| style="text-align:center;" | '''Alex Cabañeros'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Erasmus's Thesis'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Dynamical Wall-Following for an Autonomous Robot'''<br />
| style="text-align:center;" | '''RoPod Indoor Map Based Localization'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''21'''<br />
| style="text-align:center;" | '''22'''<br />
| style="text-align:center;" | '''23'''<br />
| style="text-align:center;" | '''24'''<br />
| style="text-align:center;" | '''25'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Martin Plantinga'''<br />
| style="text-align:center;" | '''Marjon van 't Klooster'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | m dot f dot b dot v dot d dot burgh (at) student dot tue dot nl<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''CNN'''<br />
| style="text-align:center;" | '''Deep Learning for Opponent Action Prediction in Robot Soccer MSL'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''Team leader Tech United @Home '''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''26'''<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''28'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 75%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Username: '''oct'''<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | 131.155.103.114<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''OCT Server'''<br />
| style="text-align:center;" | '''Master's Thesis''''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''EurEyeCase: retinal proximity measurements using an OCT probe''' <br />
| style="text-align:center;" | '''EurEyeCase: design and control of a fast-moving OCT reference stage'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''31'''<br />
| style="text-align:center;" | '''32'''<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''35'''<br />
|}<br />
</center><br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 45%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
| style="text-align:center;" | '''Tech United Flex Desk'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Tech United MSL'''<br />
| style="text-align:center;" | '''Tech United MSL'''<br />
| style="text-align:center;" | '''Tech United MSL'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''36'''<br />
| style="text-align:center;" | '''37'''<br />
| style="text-align:center;" | '''38'''<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 65%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | r dot koopmanschap (at) student dot tue dot nl<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Multi-sensor people tracking<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Cesar Martinez Lopez<br />
|-<br />
|}<br />
</center><br />
<br />
== Robotics Research Lab - Wall of Fame ==<br />
In this Wall of Fame all the students that have achieved their Master's Thesis within the Robotics Research Lab will be remembered. <br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WHoutman.JPG|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''EureyeCase: Viscoelastic Modeling of Porcine Eyes for Membrane Peeling Purposes'''<br />
| style="text-align:center;" | ''' '''<br />
|-<br />
! scope="row"| Report<br />
| style="text-align:center;" | [[File:Report_Rozemarijn.pdf]]<br />
| style="text-align:center;" | [[File:Report_Wouter.pdf]] <br />
| style="text-align:center;" | [[File:Report_Freek.pdf]] <br />
|-<br />
! scope="row"| Presentation<br />
| style="text-align:center;" | [[File:Presentation_Rozemarijn.pdf]] <br />
| style="text-align:center;" | [[File:Presentation_Wouter.pdf]] <br />
| style="text-align:center;" | [[File:Presentation_Freek.pdf]] <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control&diff=35473Embedded Motion Control2017-03-22T10:42:36Z<p>Ydouven: Redirected page to Embedded Motion Control 2017</p>
<hr />
<div>#REDIRECT [[Embedded Motion Control 2017]]</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2017&diff=35471Embedded Motion Control 20172017-03-22T10:40:24Z<p>Ydouven: /* Group Wiki Pages */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
To be determined. <!--<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by the ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| [[Media:20160518-EMC-IPC-nup.pdf | Communication patterns by ''Herman Bruyninckx'']]<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by the ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
--><br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2017}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2017}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2017/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2017 Group 1 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 2 - [[Embedded Motion Control 2017 Group 2 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 3 - [[Embedded Motion Control 2017 Group 3 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 4 - [[Embedded Motion Control 2017 Group 4 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 5 - [[Embedded Motion Control 2017 Group 5 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 6 - [[Embedded Motion Control 2017 Group 6 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 7 - [[Embedded Motion Control 2017 Group 7 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week #'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| date || time || group<br />
|-<br />
|}<br />
<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2017/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2017&diff=35470Embedded Motion Control 20172017-03-22T10:39:31Z<p>Ydouven: /* Pico test schedule */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
To be determined. <!--<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by the ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| [[Media:20160518-EMC-IPC-nup.pdf | Communication patterns by ''Herman Bruyninckx'']]<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by the ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
--><br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2017}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2017}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2017/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<!--<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
--><br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week #'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| date || time || group<br />
|-<br />
|}<br />
<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2017/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2017&diff=35469Embedded Motion Control 20172017-03-22T10:39:10Z<p>Ydouven: Created page with '<div align="center"> <font size="5">Guide towards the assignment</font><br /> <font size="4">'A-MAZE-ING PICO'</font> </div> 350px …'</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
To be determined. <!--<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by the ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| [[Media:20160518-EMC-IPC-nup.pdf | Communication patterns by ''Herman Bruyninckx'']]<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by the ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
--><br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2017}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2017}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2017/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<!--<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
--><br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| date || time || group<br />
|-<br />
|}<br />
<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2017/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2017/FAQ&diff=35468Embedded Motion Control 2017/FAQ2017-03-22T10:38:03Z<p>Ydouven: Created page with 'When you ran into a problem, try to find the solution here first. If it's not here, try to find an answer by googling your problem, asking fellow students, or, as a very last res…'</p>
<hr />
<div>When you ran into a problem, try to find the solution here first. If it's not here, try to find an answer by googling your problem, asking fellow students, or, as a very last resort, ask your tutor! If you found a solution, please put it here such that others can use it! Try to be as consise yet descriptive as possible, and try to file your Problem-Solution pair under the correct category (or add a new category if necessary).<br />
<br />
== Example ==<br />
<br />
Just as an example! Please remove this section if you're the first to add a Problem-Solution pair!<br />
<br />
=== My computer is on fire. Is this a bad thing? ===<br />
<br />
Nah, probably not, the fire will soon die out. Be sure though to commit all your changes to git! Just in case...<br />
<br />
== Ubuntu ==<br />
<br />
<br />
=== My laptop is stuck on maximum brightness ===<br />
<br />
Open your Terminal. Type<br />
<br />
sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf<br />
<br />
A text editor will open. Add the following content<br />
<br />
Section "Device"<br />
Identifier "card0"<br />
Driver "intel"<br />
Option "Backlight" "intel_backlight"<br />
BusID "PCI:0:2:0"<br />
EndSection<br />
<br />
Log out and back in. You can now use the brightness controls on your keyboard to change the brightness.<br />
<br />
== C++ ==<br />
<br />
Everything related to the programming language<br />
<br />
== Version control (git) ==<br />
<br />
Everything related to version control using git<br />
<br />
== PICO ==<br />
<br />
Everything related to PICO<br />
<br />
== Qt Creator ==<br />
<br />
=== My program is not building and running within Qt Creator ===<br />
<br />
When building the program does not work in Qt creator, but does work in the terminal, the following may fix the problem.<br />
<br />
When your project is open, click 'Projects' on the left task bar. Scroll down to 'Build Environment', and expand it (click Details). Now, all the way to the bottom right, click 'Batch Edit'.<br />
<br />
Next, open your terminal (ctrl+alt+t), and type<br />
<br />
printenv<br />
<br />
Select the entire output (you probably only need a few relevant variables, but copying everything works fine), and copy (ctrl+shift+c). Paste the entire output in your QT creator Batch Edit window, and click OK. Building with CTRL+B should work now!</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Tutorials/Setting_up_the_PICO_simulator_2017&diff=35466Embedded Motion Control/Tutorials/Setting up the PICO simulator 20172017-03-22T10:36:21Z<p>Ydouven: Created page with '= Introduction = During the course, we have 10 large groups and only one robot, so test time on the robot is scarce. Fortunately, we have a virtual (software) representation of …'</p>
<hr />
<div>= Introduction =<br />
<br />
During the course, we have 10 large groups and only one robot, so test time on the robot is scarce. Fortunately, we have a virtual (software) representation of the robot that can be used to simulate the robot. At the moment it:<br />
<br />
* Simulates the movement of the robot<br />
* The laser data of the robot, created by the virtual environment<br />
* Provide a simple visualization<br />
<br />
This should already be enough to get you started, and more will be added later (odometry, moving doors, better dynamics, etc).<br />
<br />
= Updating the simulator =<br />
<br />
Before you start working with the simulator, make sure you have our latest version by running<br />
<br />
<pre><br />
emc-update<br />
</pre><br />
<br />
This will download the latest changes and compile the updated software (framework and simulator). I will notify you when I made changes to the software such that you can run the updater, but feel free to run the command whenever you want.<br />
<br />
= Starting the simulator =<br />
<br />
As was already stated before, we will not be using ROS in this course, unless you really want to use it yourself. However, secretly the provided tools are build on top of that; the inter-process communication to be more specific. Don't worry about it too much. The only thing you need to know is that before running the simulator or your software, you need to create a ''roscore''. Simply open a terminal an run:<br />
<br />
<pre><br />
roscore<br />
</pre><br />
<br />
and keep it running. This allows processes to 'find' each other and communicate. For example, the software abstraction layer we provide 'talks' to the simulator through this roscore.<br />
<br />
Enough about ROS, let's start the simulator! Open a terminal and run<br />
<br />
<pre><br />
emc-sim<br />
</pre><br />
<br />
That's it! What you will see, is a visualization of the virtual environment (the white lines are walls) and a top-down view of the robot (the red lines).<br />
<br />
= Controlling the robot =<br />
<br />
Now, as you can see, not much is happening. The robot is standing still in a static environment. Let's change that! A first simple way to test the simulator is by controlling the robot using your keyboard. Just run:<br />
<br />
<pre><br />
pico-teleop<br />
</pre><br />
<br />
and you will be able to control the robot using the ''numpad'' keys. You can rotate the robot using '/' and '*'.<br />
<br />
= Visualization =<br />
<br />
As you already noticed, the simulator pops up a visualization windows showing the robot in the virtual world. This shows how the world ''is'' (at least in simulation...). It is also very interesting to know how to robot ''perceives'' the world through its sensors. Note that this is a big difference! We also created a visualization for that. Just run<br />
<br />
<pre><br />
emc-viz<br />
</pre><br />
<br />
You will again see the robot footprint displayed in red. However, the walls are gone and replaced by the actual (simulated) sensor data from the robot (the green dots). The laser data is actually represented in polar coordinates (remember, the LRF is a laser with a rotating mirror, so what it will return are angles and distances) but the visualization 'projects' them back to world coordinates. See how the laser data changes even if the robot is standing still: this is the simulated noise added to the data.<br />
<br />
Try driving the robot around using 'pico-teleop' and notice how the laser data changes, and how it differs from the actual virtual world.<br />
<br />
= Stopping the simulator and visualization =<br />
<br />
You can stop the simulator and visualization by pressing ''ctrl-C'' in the terminal.<br />
<br />
= Loading a custom heightmap =<br />
<br />
By default, the simulator loads a pretty ugly maze. Fortunately, you can change the simulation environment very easily! You just have to create a heightmap: an image that specifies for each pixel how 'high' the world has to be at that point. Since the laser only scans at one height, we can use two extremes here: flat (ground level) or high enough to be detected by the laser.<br />
<br />
To create an image, simply open your favourite image editor and create a black-and-white image. If you don't know how to create an image, have a look at the section below. White corresponds to the floor, black to the walls (i.e., which will be detected by the laser). You have to keep the following things in mind:<br />
<br />
* The simulator converts the pixels to world coordinates. Each pixel corresponds to a block of 2.5 by 2.5 cm, or in other words, 40 pixels correspond to 1 meter.<br />
* The robot always starts in the center of the image. So, if you want to robot to start at the edge of your maze / corridor, just create a bigger image and move the black pixels to the upper part of the image.<br />
* You'll get the best result if the lines drawn are at least 2 pixels wide<br />
* Store your image lossless, ''i.e.'' using the ''png'' format (which is recommended by the way!), instead of the ''jpg'' format.<br />
* Make sure your heightmap images always have a border of white pixels, ''i.e.'' there should '''not''' be any non-white pixels at the borders of your image<br />
<br />
Once you have created an image, simply run the simulator and provide the image file as argument:<br />
<br />
<pre><br />
emc-sim <YOUR_IMAGE_FILE>.png<br />
</pre><br />
<br />
That's it!<br />
<br />
== Create a heigthmap image ==<br />
<br />
There are many linux applications that you use to create images. We suggest using Gimp, an open-source alternative to Photoshop. Although it might be a bit overkill to use for our application, it has great support and the thing we want to do (draw black lines on a white background) isn't hard. To install Gimp, run:<br />
<br />
<pre><br />
sudo apt-get install gimp<br />
</pre><br />
<br />
And run it using:<br />
<pre><br />
gimp<br />
</pre><br />
<br />
Then to create a simple image:<br />
<br />
* Select ''File'' -> ''New'' (or ''ctrl-N'')<br />
* Specify the size of your image. Remember, 40 pixels = 1 meter, and the robot starts in the center<br />
* Select the ''Pencil Tool'' from the left pane.<br />
* Set the pencil size in the lower left pane to something sensible, ''e.g.'' 2 pixels<br />
<br />
Now, if you click left on the image, a dot is drawn, but we want lines! To draw a line:<br />
<br />
* left click, ''then'' hold ''shift'', ''then'' left click again.<br />
* While holding the ''shift'' button, you can click more times to create a sequence of lines<br />
* To create nice, axis-aligned lines, also hold ''ctrl''<br />
<br />
There is two types of saving in Gimp. The first one is the using ''File'' -> ''Save''. However, this will only generate an ''xcf''-file, something that can only be read by Gimp. Instead, you should use the ''File'' -> ''Export'' option:<br />
<br />
* ''File'' -> ''Export''<br />
* Provide a name for your file. If you put '.png' as extension, it will be saved as png<br />
* Use the default ''png'' export settings<br />
<br />
That's it!<br />
<br />
== Adding doors ==<br />
<br />
The real maze will contain a door that the robot needs to open. The simulator is capable of simulating these doors, such that you can test your software before it gets real! To add doors to the simulated world, simply edit your heightmap and add ''grey'' lines to it. To be specific:<br />
<br />
* The door should be a straight line (but not necessarily axis-aligned), with a minimum thickness of 2 pixels. To be more specific, all pixels in the door line should be connected<br />
* The average RGB value should be between 50 and 205 (on a scale of 0-255). So for example, the RGB value (100, 100, 100) is a door, while (20, 20, 20) is a wall (and (255, 255, 255) is open space).<br />
* You can have multiple doors in your world. However, make sure that they are always separated by at least one pixel. ''Remember that there will only be one door, i.e, one sliding block, in the final maze'', but the possibility of having multiple doors to test with in simulation might be nice.<br />
* You can experiment with the direction in which it slides open. Darker lines (RGB values below 128) will open in a different direction than lighter lines (RGB values above 128).<br />
<br />
An example: [[Media:Emc2015-heightmap-example.png | Height Map]]. Note that doors as skewed as the left one in the example will not occur in the final maze (but are allowed in the simulation, for you to test with).<br />
<br />
<br />
The doors should be visible as green blocks in the simulator. Now, you can use the ''emc::IO'' object from your code to open these doors (but only if you are standing in front):<br />
<br />
<pre><br />
// ... Make sure robot is in front of a possible door<br />
// ... Make sure robot is standing still<br />
<br />
io.sendRequestOpenDoor();<br />
</pre></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Tutorials&diff=35465Embedded Motion Control/Tutorials2017-03-22T10:35:47Z<p>Ydouven: Redirected page to Embedded Motion Control/Tutorials 2017</p>
<hr />
<div>#REDIRECT [[Embedded Motion Control/Tutorials 2017]]</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Tutorials_2017&diff=35464Embedded Motion Control/Tutorials 20172017-03-22T10:35:31Z<p>Ydouven: Created page with '# Introduction # Installing Ubuntu # [[ Embedded Motion Control…'</p>
<hr />
<div># [[ Embedded Motion Control/Tutorials/Introduction | Introduction ]]<br />
# [[ Embedded Motion Control/Tutorials/Installing Ubuntu | Installing Ubuntu ]]<br />
# [[ Embedded Motion Control/Tutorials/Customizing Ubuntu | Customizing Ubuntu ]]<br />
# Do the following C++ tutorials:<br />
## [http://www.cplusplus.com/doc/tutorial/ cplusplus.com]: up to and including '''Name visibility'''<br />
## [http://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-096-introduction-to-c-january-iap-2011/lecture-notes/ MIT's Introduction to C++]: up to and including '''Classes'''<br />
#* Remarks:<br />
#** For now, use a simple editor such as ''gedit'' (the ubuntu version of Notepad). We will install a more advanced editor (IDE - Integrated Development Environment) later.<br />
#** Once you have saved your C++ program (e.g. as ''example.cpp''), it can be compiled from a terminal using:<pre>g++ example.cpp -o example</pre>and run with<pre>./example</pre><br />
<br />
# [[ Embedded Motion Control/Tutorials/Installing the EMC environment | Installing the EMC environment ]]<br />
# [[ Embedded Motion Control/Tutorials/Setting up your project | Setting up your project ]]<br />
# [[ Embedded Motion Control/Tutorials/Setting up an IDE | Setting up an IDE ]]<br />
# [[ Embedded_Motion_Control/Tutorials/Setting_up_the_PICO_simulator_2017 | Setting up the PICO simulator ]]<br />
# [[ Embedded_Motion_Control/Tutorials/Towards an autonomous robot | Towards an autonomous robot ]]<br />
# [[ Embedded_Motion_Control/Tutorials/Obtaining laser and odometry data | Obtaining laser and odometry data ]]<br />
# [[ Embedded_Motion_Control/Tutorials/Sharing your project through git | Sharing your project through git ]]<br />
# [[ Embedded_Motion_Control/Using_Pico | Testing on the real robot and recording data]]<br />
<!--<br />
<br />
# .. More tutorials coming up ..!<br />
<br />
<br />
# [[ Embedded Motion Control/Tutorials/Using Subversion to share and manage your project | Using Subversion to share and manage your project ]]<br />
# [[ Embedded Motion Control/Tutorials/Building a ROS package | Building a ROS package ]]<br />
# On the [http://wiki.ros.org/ROS/Tutorials ROS tutorials page], do tutorials 5 ([http://wiki.ros.org/ROS/Tutorials/UnderstandingNodes Understanding ROS Nodes]) to 17 ([http://wiki.ros.org/ROS/Tutorials/Recording%20and%20playing%20back%20data Recording and playing back data]), but '''keep this in mind''':<br />
#* If you can choose between ''rosbuild'' and ''catkin'', select '''rosbuild'''<br />
#* If you can choose between ''C++'' and ''Python'', select '''C++'''<br />
#* Whenever the tutorial refers to the ''beginners_tutorial'' ROS package, use the name of the package you created above instead (that is, ''beginners_tutorial_<YOUR_NAME>''). Of course, you can use TAB completion when possible.<br />
#* The path to your ROS package differs from the path in the ROS tutorials<br />
# [[ Embedded Motion Control/Tutorials/Setting up an IDE | Setting up an IDE ]]<br />
# [[ Embedded Motion Control/Tutorials/Setting up the PICO simulator | Setting up the PICO simulator ]]<br />
<br />
# [[ Embedded Motion Control/Tutorials/Creating your first PICO-related ROS package | Creating your first PICO-related ROS package ]]<br />
<br />
Learn about ROS concepts on the ROS tutorial page. Start [http://wiki.ros.org/ROS/Tutorials/UnderstandingNodes here] and continue up until the tutorial '''Using RosEd'''<br />
# [[ Embedded Motion Control/Tutorials/Understanding ROS nodes | Understanding ROS nodes ]]<br />
# [[ Embedded Motion Control/Tutorials/Understanding ROS topics | Understanding ROS topics ]]<br />
# [[ Embedded Motion Control/Tutorials/Understanding ROS services and parameters | Understanding ROS services and parameters ]]<br />
# [[ Embedded Motion Control/Tutorials/Using rqt_console and roslaunch | Using rqt_console and roslaunch ]]<br />
# [[ Embedded Motion Control/Tutorials/Using rosed to edit files in ROS | Using rosed to edit files in ROS ]]<br />
# [[ Embedded Motion Control/Tutorials/Creating a ROS msg and srv | Creating a ROS msg and srv ]]<br />
# [[ Embedded Motion Control/Tutorials/Writing a simple publisher and subscriber | Writing a simple publisher and subscriber ]]<br />
# [[ Embedded Motion Control/Tutorials/Examining the simple publisher and subscriber | Examining the simple publisher and subscriber ]]<br />
# [[ Embedded Motion Control/Tutorials/Writing a simple service and client | Writing a simple service and client ]]<br />
# [[ Embedded Motion Control/Tutorials/Examining the simple service and client | Examining the simple service and client ]]<br />
# [[ Embedded Motion Control/Tutorials/Recording and playing back data | Recording and playing back data ]]<br />
--></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Maze_competition_2017&diff=35462Embedded Motion Control/Maze competition 20172017-03-22T10:34:28Z<p>Ydouven: Created page with 'The final competition will be held (date to be determined) at the RoboCup soccer field. The goal of this competition is to let PICO autonomously drive through a maze and find the…'</p>
<hr />
<div>The final competition will be held (date to be determined) at the RoboCup soccer field. The goal of this competition is to let PICO autonomously drive through a maze and find the exit. Some facts:<br />
<br />
* Where and when:<br />
** When: to be determined<br />
** Location: RoboCup Soccer field, GEM-N<br />
* Set-up<br />
** Make sure your software is easy to set-up, ''i.e'':<br />
*** Your software can be updated with one easy command, ''e.g.'' 'git pull'<br />
*** Your software can be compiled using 'cmake' and 'make'<br />
*** To start your software, only one executable has to be called<br />
*** '''If your set-up deviates from this method, let us know as soon as possible!'''<br />
* Maze characteristics:<br />
** Exact location of the exit is unknown, but it will be on the boundaries of the maze (which means: PICO has to drive ''out'' of the maze).<br />
** Walls are approximately axis-aligned, meaning all angles are 90 degrees. Approximately means: built by hand, so slight differences may occur.<br />
** Open spaces '''may''' occur<br />
** There '''may''' be loops in the maze, which means that some walls may not be connected to other walls.<br />
* Start, goal and limits:<br />
** PICO will start '''inside''' the maze.<br />
** PICO will '''not''' start in a door area (see below for definition). So, for example, the door will not be directly behind PICO's starting location<br />
** You have finished the assignment if PICO did not drive into walls, found the exit and the whole robot is across the finish line.<br />
** Maximum speed (is limited in PICO): 0.5 m/s translational, 1.2 rad/s rotational. By the way, that's pretty fast (compared to last year's 0.2 m/s), so be careful! You don't ''have to'' drive that fast!<br />
* Doors:<br />
** There is exactly 1 door in the maze<br />
** The door will be situated at a dead end, a dead end being defined as a piece of wall with minimum length 0.5 and maximum length 1.5 with side-walls of at least 0.3 meter length. ('''Picture explaining this will follow shortly''')<br />
** There might be multiple dead ends in the maze, one of which is a door<br />
** You need to pass the door to solve the maze, ''i.e.'', if you cannot open the door, the maze is unsolvable<br />
** The door will open if and only if the following conditions are met:<br />
*** PICO is located within 1.3m distance from the door (''i.e.'', '''no''' part of PICO is located outside the 1.3m range). The 1.3m in front of the door is called the '''door area'''.<br />
*** PICO is '''not''' driving, ''i.e.'', the commanded velocity is 0 (both translational and rotational)<br />
*** PICO '''asks to open the door'''. This will become available from the '''io'''-layer, ''e.g.,:<pre>io.requestOpenDoor()</pre><br />
** '''If''' these conditions are met:<br />
*** The door will start sliding open within 2 seconds from PICO's request<br />
*** The door will slide open to the left '''or''' to the right<br />
*** The door slides open at approximately constant velocity<br />
*** The door is fully open within 5 seconds from PICO's request<br />
** Once the door is open, it will stay open<br />
* Scoring:<br />
** You have 2 attempts (= maximum one restart)<br />
** restart means:<br />
*** PICO restarts at beginning of maze<br />
*** MAZE time (= time used for scoring) is reset, BUT<br />
*** TOTAL time keeps running<br />
** You have a total of 7 minutes for both attempts<br />
** Hit wall = that attempt fails<br />
** PICO standing still for 30 seconds = that attempt fails<br />
** There will be no second attempt if first attempt was successful<br />
<br />
Next you can see an examples of an ''open space'' and a ''door'' and examples:<br />
[[File:emc_labirynth_scheme.png|thumb|center|640px|Scheme of an ''open space'' and a ''door template' and examples]]</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Corridor_competition_2017&diff=35461Embedded Motion Control/Corridor competition 20172017-03-22T10:33:38Z<p>Ydouven: Created page with 'An intermediate review will be held (date to be determined) at the RoboCup soccer field. During this challenge, called the ''corridor competition'' the students have to let the r…'</p>
<hr />
<div>An intermediate review will be held (date to be determined) at the RoboCup soccer field. During this challenge, called the ''corridor competition'' the students have to let the robot drive through a corridor and then take the first exit. The precise location of this exit will not be given in advance. Some facts:<br />
<br />
* Set-up<br />
** Make sure your software is easy to set-up, ''i.e'':<br />
*** Your software can be updated with one easy command, ''e.g.'' 'git pull'<br />
*** Your software can be compiled using 'cmake' and 'make'<br />
*** To start your software, only one executable has to be called<br />
*** '''If your set-up deviates from this method, let us know as soon as possible!'''<br />
** The software of all groups will be updated on the robot '''before''' the challenge starts<br />
*** This way, teams starting the challenge have as much time as teams that do the challenge at the end<br />
* The corridor:<br />
** The exit can be either left or right<br />
** It is not known beforehand how far the exit is located from the start (somewhere between 1 and 10 meters)<br />
** The opposing end wall (on the far end) will be open<br />
** The walls are approximately parallel to each other<br />
*** '''Note:''' the walls might not be perfectly straight<br />
** The distance between the walls is not known in advance, but will be reasonable (somewhere between 0.5 and 1.5 meters).<br />
** The distance between the walls will be fairly constant throughout the corridor, 'fairly' meaning that we build the corridor by hand, and the distance may change a little along the corridor.<br />
** At the exit, the finish line is located '''approximately''' 30 cm from the side of the corridor (Notice: '''approximately''', so don't just drive forward for ''30'' cm!). The walls that can be used to align PICO will be a little bit longer.<br />
* Start, goal and limits:<br />
** PICO will start with its laser range finder between the walls<br />
** PICO will be '''approximately''' facing the end of the corridor. (Notice: '''approximately''', so don't just drive forward for ''n'' seconds!)<br />
** You have finished the assignment if PICO did not drive into walls, took the correct turn and the entire rear wheel is across the finish line.<br />
** Maximum speed (is limited in PICO): 0.5 m/s translational, 1.2 rad/s rotational. By the way, that's pretty fast (compared to last year's 0.2 m/s), so be careful! You don't ''have to'' drive that fast!<br />
* Scoring:<br />
** Try not to touch the wall! Slightly touching is OK, however, bumping (''i.e.'', driving head-on into a wall) '''is not allowed'''! If PICO hits the wall, '''we''' decide whether it counts as ''bumping''. '''If''' PICO ''bumps'' into the wall, that trial ends immediately.<br />
** Every team has two trials (= max one restart). A trial ends if:<br />
*** PICO ''bumps'' into the wall<br />
*** PICO has not moved or has not made sensible movements (as judged by the tutors) for 30 seconds<br />
*** The total time limit of 5 minutes per group is reached<br />
*** The group requests a restart (on the first trial)<br />
** restart means:<br />
*** PICO restarts at the beginning of the corridor<br />
*** CORRIDOR time (= time used for scoring) is reset, BUT<br />
*** TOTAL time keeps running<br />
** Every team has a total of 5 minutes<br />
** There will be no second attempt if first attempt was successful<br />
<br />
Next you can see an example of a corridor:<br />
[[File:Emc_corridor_scheme.png|thumb|center|640px|Scheme of a possible corridor composition, with measurements]]</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2017/Contact_Details&diff=35460Embedded Motion Control 2017/Contact Details2017-03-22T10:32:43Z<p>Ydouven: Created page with '==Tutors== '''Yanick Douven''' - <tt>y dot g dot m dot douven at tue dot nl</tt> '''Wouter Kuijpers''' - <tt>w dot j dot p dot kuijpers at tue dot nl</tt> '''Wouter Houtman'''…'</p>
<hr />
<div>==Tutors==<br />
<br />
'''Yanick Douven''' - <tt>y dot g dot m dot douven at tue dot nl</tt><br />
<br />
'''Wouter Kuijpers''' - <tt>w dot j dot p dot kuijpers at tue dot nl</tt><br />
<br />
'''Wouter Houtman''' - <tt>w dot houtman at tue dot nl</tt></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=32344Robotics Lab Map2017-02-10T12:14:46Z<p>Ydouven: /* Employees */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 80%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:YanickDouven.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtens'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | '''Cesar Martinez Lopez'''<br />
| style="text-align:center;" | '''Herman Bruyninckx'''<br />
<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | j dot scholtes (at) tue dot nl<br />
| style="text-align:center;" | y dot g dot m dot douven (at) tue dot nl<br />
| style="text-align:center;" | W dot J dot P dot Kuijpers (at) tue dot nl<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Herman dot Bruyninckx (at) mech dot kuleuven dot be<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
| style="text-align:center;" | '''Professor'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''Various'''<br />
<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''???'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 65%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:R.A.M.weijers@student.tue.nl r.a.m.weijers@student.tue.nl]<br />
| style="text-align:center;" | [mailto:M.F.B.v.d.Burgh@student.tue.nl M.F.B.v.d.Burgh@student.tue.nl]<br />
| style="text-align:center;" | [mailto:f.j.ramp@student.tue.nl f.j.ramp@student.tue.nl]<br />
| style="text-align:center;" | [mailto:w.houtman@student.tue.nl w.houtman@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''''<br />
| style="text-align:center;" | '''EureyeCase: retinal tissue modeling for use in semi-automated robot-assisted membrane peeling'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
| style="text-align:center;" | '''31'''<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:Lotte_de_Koning.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | '''Chenyang Lu'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.j.samplonius@student.tue.nl r.j.samplonius@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:c.k.m.d.koning@student.tue.nl c.k.m.d.koning@student.tue.nl]<br />
| style="text-align:center;" | [mailto:c.lu.2@student.tue.nl c.lu.2@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis''' <br />
| style="text-align:center;" | '''Internship'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EurEyeCase: retinal proximity measurements using an OCT probe'''<br />
| style="text-align:center;" | '''EurEyeCase: design and control of a fast-moving OCT reference stage'''<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''Image Processing and Visual Servoing'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''20'''<br />
|-<br />
!<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Mahmoud Al Abbassi'''<br />
| style="text-align:center;" | '''Jerrel Unkel'''<br />
| style="text-align:center;" | '''Noud Paes'''<br />
| style="text-align:center;" | '''Martin Plantinga'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:m.alabbassi@student.tue.nl m.alabbassi@student.tue.nl]<br />
| style="text-align:center;" | [mailto:j.j.e.unkel@student.tue.nl j.j.e.unkel@student.tue.nl]<br />
| style="text-align:center;" | [mailto:n.g.paes@student.tue.nl n.g.paes@student.tue.nl]<br />
| style="text-align:center;" | [mailto:m.plantinga@student.tue.nl m.plantinga@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Dynamical Wall-Following for an Autonomous Robot'''<br />
| style="text-align:center;" | '''Compliant control of RoPod'''<br />
| style="text-align:center;" | '''RoPod flock control'''<br />
| style="text-align:center;" | '''CNN'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''22'''<br />
| style="text-align:center;" | '''18'''<br />
| style="text-align:center;" | '''19'''<br />
| style="text-align:center;" | '''26'''<br />
|-<br />
!<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Marjon van 't Klooster'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:m.e.v.t.klooster@student.tue.nl m.e.v.t.klooster@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Deep Learning for Opponent Action Prediction in Robot Soccer MSL'''<br />
| style="text-align:center;" | '''--'''<br />
| style="text-align:center;" | '''--'''<br />
| style="text-align:center;" | '''--'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''--'''<br />
| style="text-align:center;" | '''--'''<br />
| style="text-align:center;" | '''--'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 65%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center; width: 15%" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Sam Lousberg'''<br />
| style="text-align:center;" | '''Johan Baeten'''<br />
| style="text-align:center;" | '''Job van der Velde'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''PreMaster End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Wouter Kuijpers<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:emptyTURTLE.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" |<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; width: 20%; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center; width: 15%" | [[File:emptyAMIGO.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.koopmanschap@student.tue.nl r.koopmanschap@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Multi-sensor people tracking<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | ???<br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=31874Robotics Lab Map2017-01-10T15:28:26Z<p>Ydouven: /* Students */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtens'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | '''Cesar Martinez Lopez'''<br />
| style="text-align:center;" | '''Herman Bruyninckx'''<br />
<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:j.scholtes@tue.nl j.scholtes@tue.nl] <br />
| style="text-align:center;" | [mailto:y.g.m.douven@tue.nl y.g.m.douven@tue.nl]<br />
| style="text-align:center;" | [mailto:W.J.P.Kuijpers@tue.nl W.J.P.Kuijpers@tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:Herman.Bruyninckx@mech.kuleuven.be Herman.Bruyninckx@mech.kuleuven.be]<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
| style="text-align:center;" | '''Professor'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''Various'''<br />
<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''???'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center;" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:R.A.M.weijers@student.tue.nl r.a.m.weijers@student.tue.nl]<br />
| style="text-align:center;" | [mailto:M.F.B.v.d.Burgh@student.tue.nl M.F.B.v.d.Burgh@student.tue.nl]<br />
| style="text-align:center;" | [mailto:f.j.ramp@student.tue.nl f.j.ramp@student.tue.nl]<br />
| style="text-align:center;" | [mailto:w.houtman@student.tue.nl w.houtman@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''''<br />
| style="text-align:center;" | '''EureyeCase: retinal tissue modeling for use in semi-automated robot-assisted membrane peeling'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
| style="text-align:center;" | '''31'''<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.j.samplonius@student.tue.nl r.j.samplonius@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:c.k.m.d.koning@student.tue.nl c.k.m.d.koning@student.tue.nl]<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis''' <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EurEyeCase: retinal proximity measurements using an OCT probe'''<br />
| style="text-align:center;" | '''EurEyeCase: design and control of a fast-moving OCT reference stage'''<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Sam Lousberg'''<br />
| style="text-align:center;" | '''Johan Baeten'''<br />
| style="text-align:center;" | '''Job van der Velde'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''PreMaster End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Wouter Kuijpers<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" |<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Adam Siemieniuk'''<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Sound Source Localization<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Matthijs van der Burgh<br />
| style="text-align:center;" | ???<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=31873Robotics Lab Map2017-01-10T15:27:38Z<p>Ydouven: /* Employees */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtens'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | '''Cesar Martinez Lopez'''<br />
| style="text-align:center;" | '''Herman Bruyninckx'''<br />
<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:j.scholtes@tue.nl j.scholtes@tue.nl] <br />
| style="text-align:center;" | [mailto:y.g.m.douven@tue.nl y.g.m.douven@tue.nl]<br />
| style="text-align:center;" | [mailto:W.J.P.Kuijpers@tue.nl W.J.P.Kuijpers@tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:Herman.Bruyninckx@mech.kuleuven.be Herman.Bruyninckx@mech.kuleuven.be]<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
| style="text-align:center;" | '''Professor'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | '''EurEyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''Various'''<br />
<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''???'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center;" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:R.A.M.weijers@student.tue.nl r.a.m..weijers@student.tue.nl]<br />
| style="text-align:center;" | [mailto:M.F.B.v.d.Burgh@student.tue.nl M.F.B.v.d.Burgh@student.tue.nl]<br />
| style="text-align:center;" | [mailto:f.j.ramp@student.tue.nl f.j.ramp@student.tue.nl]<br />
| style="text-align:center;" | [mailto:w.houtman@student.tue.nl w.houtman@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''''<br />
| style="text-align:center;" | '''EureyeCase: retinal modeling'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
| style="text-align:center;" | '''31'''<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.j.samplonius@student.tue.nl r.j.samplonius@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:c.k.m.d.koning@student.tue.nl c.k.m.d.koning@student.tue.nl]<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis''' <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EurEyeCase: retinal proximity measurements using an OCT probe'''<br />
| style="text-align:center;" | '''EurEyeCase: design and control of a fast-moving OCT reference stage'''<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Sam Lousberg'''<br />
| style="text-align:center;" | '''Johan Baeten'''<br />
| style="text-align:center;" | '''Job van der Velde'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''PreMaster End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Wouter Kuijpers<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" |<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Adam Siemieniuk'''<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Sound Source Localization<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Matthijs van der Burgh<br />
| style="text-align:center;" | ???<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=31872Robotics Lab Map2017-01-10T15:26:35Z<p>Ydouven: /* Students */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtens'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | '''Cesar Martinez Lopez'''<br />
| style="text-align:center;" | '''Herman Bruyninckx'''<br />
<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:j.scholtes@tue.nl j.scholtes@tue.nl] <br />
| style="text-align:center;" | [mailto:y.g.m.douven@tue.nl y.g.m.douven@tue.nl]<br />
| style="text-align:center;" | [mailto:W.J.P.Kuijpers@tue.nl W.J.P.Kuijpers@tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:Herman.Bruyninckx@mech.kuleuven.be Herman.Bruyninckx@mech.kuleuven.be]<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
| style="text-align:center;" | '''Professor'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | '''EureyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''Various'''<br />
<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''???'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center;" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:R.A.M.weijers@student.tue.nl r.a.m..weijers@student.tue.nl]<br />
| style="text-align:center;" | [mailto:M.F.B.v.d.Burgh@student.tue.nl M.F.B.v.d.Burgh@student.tue.nl]<br />
| style="text-align:center;" | [mailto:f.j.ramp@student.tue.nl f.j.ramp@student.tue.nl]<br />
| style="text-align:center;" | [mailto:w.houtman@student.tue.nl w.houtman@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''''<br />
| style="text-align:center;" | '''EureyeCase: retinal modeling'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
| style="text-align:center;" | '''31'''<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.j.samplonius@student.tue.nl r.j.samplonius@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:c.k.m.d.koning@student.tue.nl c.k.m.d.koning@student.tue.nl]<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis''' <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EurEyeCase: retinal proximity measurements using an OCT probe'''<br />
| style="text-align:center;" | '''EurEyeCase: design and control of a fast-moving OCT reference stage'''<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Sam Lousberg'''<br />
| style="text-align:center;" | '''Johan Baeten'''<br />
| style="text-align:center;" | '''Job van der Velde'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''PreMaster End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Wouter Kuijpers<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" |<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Adam Siemieniuk'''<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Sound Source Localization<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Matthijs van der Burgh<br />
| style="text-align:center;" | ???<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Robotics_Lab_Map&diff=31871Robotics Lab Map2017-01-10T15:25:34Z<p>Ydouven: /* Students */</p>
<hr />
<div>[[File:Floorplan_robotics_lab_new.png]]<br />
<br />
== Tech United FlexDesks ==<br />
For the Bachelor End Project-students we have reserved four desks for the MSL-team (''Tech United MSL FlexDesks'') and four desks for the @Home-team (''Tech United @Home FlexDesks''). As these are flexdesks you ''do not'' own a desk, just find a Flexdesk when you enter. Because of this, these desks have to be empty and clean when you are done working!<br />
<br />
'''Tech United MSL FlexDesks:''' ''35-38''<br />
<br />
'''Tech United @Home FlexDesks:''' ''11-14''<br />
<br />
== Employees ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:JesseScholtes.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:WouterKuijpersWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Jesse Scholtens'''<br />
| style="text-align:center;" | '''Yanick Douven'''<br />
| style="text-align:center;" | '''Wouter Kuijpers'''<br />
| style="text-align:center;" | '''Cesar Martinez Lopez'''<br />
| style="text-align:center;" | '''Herman Bruyninckx'''<br />
<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:j.scholtes@tue.nl j.scholtes@tue.nl] <br />
| style="text-align:center;" | [mailto:y.g.m.douven@tue.nl y.g.m.douven@tue.nl]<br />
| style="text-align:center;" | [mailto:W.J.P.Kuijpers@tue.nl W.J.P.Kuijpers@tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:Herman.Bruyninckx@mech.kuleuven.be Herman.Bruyninckx@mech.kuleuven.be]<br />
|-<br />
! scope="row"| Function<br />
| style="text-align:center;" | '''Project Management'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''PhD Researcher'''<br />
| style="text-align:center;" | '''Postdoctoral Researcher'''<br />
| style="text-align:center;" | '''Professor'''<br />
<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''Various'''<br />
| style="text-align:center;" | '''EureyeCase'''<br />
| style="text-align:center;" | '''LED it Be 50%'''<br />
| style="text-align:center;" | '''RoPod'''<br />
| style="text-align:center;" | '''Various'''<br />
<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''1'''<br />
| style="text-align:center;" | '''3'''<br />
| style="text-align:center;" | '''4'''<br />
| style="text-align:center;" | '''2'''<br />
| style="text-align:center;" | '''???'''<br />
|-<br />
|}<br />
</center><br />
<br />
== Students ==<br />
<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:roos.png|250x250px|]]<br />
| style="text-align:center;" | [[File:MatthijsvdBurgh.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rozemarijn Weijers'''<br />
| style="text-align:center;" | '''Matthijs van der Burgh'''<br />
| style="text-align:center;" | '''Freek Ramp'''<br />
| style="text-align:center;" | '''Wouter Houtman'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:R.A.M.weijers@student.tue.nl r.a.m..weijers@student.tue.nl]<br />
| style="text-align:center;" | [mailto:M.F.B.v.d.Burgh@student.tue.nl M.F.B.v.d.Burgh@student.tue.nl]<br />
| style="text-align:center;" | [mailto:f.j.ramp@student.tue.nl f.j.ramp@student.tue.nl]<br />
| style="text-align:center;" | [mailto:w.houtman@student.tue.nl w.houtman@student.tue.nl]<br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Tech United'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EureyeCase: retinal structure recognition in images reconstructed from OCT A-scans'''<br />
| style="text-align:center;" | '''Team leader Tech United @Home'''<br />
| style="text-align:center;" | '''''<br />
| style="text-align:center;" | '''EureyeCase: retinal modeling'''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''27'''<br />
| style="text-align:center;" | '''29'''<br />
| style="text-align:center;" | '''30'''<br />
| style="text-align:center;" | '''31'''<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:RensWiki.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Rens Samplonius'''<br />
| style="text-align:center;" | '''Alexis Siagkris-Lekkos'''<br />
| style="text-align:center;" | '''Lotte de Koning'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | [mailto:r.j.samplonius@student.tue.nl r.j.samplonius@student.tue.nl]<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | [mailto:c.k.m.d.koning@student.tue.nl c.k.m.d.koning@student.tue.nl]<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Master's Thesis'''<br />
| style="text-align:center;" | '''Internship'''<br />
| style="text-align:center;" | '''Master's Thesis''' <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | '''EurEyeCase: measuring the distance to the retina using an OCT probe'''<br />
| style="text-align:center;" | '''EurEyeCase: fast-moving OCT reference stage'''<br />
| style="text-align:center;" | '''Improving the Applicability of Non-Destructive Measurement Methods'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''33'''<br />
| style="text-align:center;" | '''34'''<br />
| style="text-align:center;" | '''16'''<br />
| style="text-align:center;" | '''''<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United MSL BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Sam Lousberg'''<br />
| style="text-align:center;" | '''Johan Baeten'''<br />
| style="text-align:center;" | '''Job van der Velde'''<br />
| style="text-align:center;" | '''Jeroen van Willigen'''<br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''PreMaster End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | Calibration of Kinect Sensor based on Omni-vision<br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Wouter Kuijpers<br />
| style="text-align:center;" | Yanick Douven<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Luuk Poort'''<br />
| style="text-align:center;" | '''Peter van Dooren'''<br />
| style="text-align:center;" | '''Josja Geijsberts'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Improving the lever setting mechanism<br />
| style="text-align:center;" | Improving the reproducibility of shots<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" | '''Tech United MSL FlexDesk'''<br />
| style="text-align:center;" |<br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Marjon van 't Klooster<br />
| style="text-align:center;" | Jordy Senden<br />
| style="text-align:center;" | Lotte de Koning<br />
| style="text-align:center;" |<br />
|-<br />
|}<br />
</center><br />
<br />
== Tech United @Home BEP Projects ==<br />
<center><br />
{| border="1" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse"<br />
|-<br />
! <br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
| style="text-align:center;" | [[File:example.jpg|250x250px|]]<br />
|-<br />
! scope="row"| Name<br />
| style="text-align:center;" | '''Adam Siemieniuk'''<br />
| style="text-align:center;" | '''Raymond Koopmanschap'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| E-mail<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project Level<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | '''Bachelor End Project'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Project<br />
| style="text-align:center;" | Sound Source Localization<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Desk<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | '''Tech United @Home FlexDesk'''<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
! scope="row"| Supervisor<br />
| style="text-align:center;" | Matthijs van der Burgh<br />
| style="text-align:center;" | ???<br />
| style="text-align:center;" | <br />
| style="text-align:center;" | <br />
|-<br />
|}<br />
</center></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27448Embedded Motion Control 20162016-05-25T08:42:03Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by the ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| [[Media:20160518-EMC-IPC-nup.pdf | Communication patterns by ''Herman Bruyninckx'']]<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by the ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* ||<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || Group 6 <br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 21'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 24-05-2016 || 14:45-16:45 || <br />
|-<br />
| 24-05-2016 || 16:45-18:45 || <br />
|-<br />
| 24-05-2016 || 18:45-20:45 || <br />
|-<br />
| 26-05-2016 || 8:45-10:45 || Group 5<br />
|-<br />
| 26-05-2016 || 10:45-12:45 || Group 7<br />
|-<br />
| 26-05-2016 || 12:45-14:45 || Group 6<br />
|-<br />
| 26-05-2016 || 14:45-16:45 || Group 3<br />
|-<br />
| 26-05-2016 || 16:45-18:45 || Group 1<br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=File:20160518-EMC-IPC-nup.pdf&diff=27447File:20160518-EMC-IPC-nup.pdf2016-05-25T08:40:58Z<p>Ydouven: </p>
<hr />
<div></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27446Embedded Motion Control 20162016-05-25T08:40:43Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| [[Media:20160518-EMC-IPC-nup.pdf | Communication patterns by ''Herman Bruyninckx'']]<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* ||<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || Group 6 <br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 21'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 24-05-2016 || 14:45-16:45 || <br />
|-<br />
| 24-05-2016 || 16:45-18:45 || <br />
|-<br />
| 24-05-2016 || 18:45-20:45 || <br />
|-<br />
| 26-05-2016 || 8:45-10:45 || Group 5<br />
|-<br />
| 26-05-2016 || 10:45-12:45 || Group 7<br />
|-<br />
| 26-05-2016 || 12:45-14:45 || Group 6<br />
|-<br />
| 26-05-2016 || 14:45-16:45 || Group 3<br />
|-<br />
| 26-05-2016 || 16:45-18:45 || Group 1<br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27445Embedded Motion Control 20162016-05-25T08:30:57Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation (excluding 6 minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Communication patterns by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| colspan="2" | Presentation of final design by ''groups'': 9-minute presentation (excluding 4 minutes for questions, so 13 minutes in total)<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* ||<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || Group 6 <br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 21'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 24-05-2016 || 14:45-16:45 || <br />
|-<br />
| 24-05-2016 || 16:45-18:45 || <br />
|-<br />
| 24-05-2016 || 18:45-20:45 || <br />
|-<br />
| 26-05-2016 || 8:45-10:45 || Group 5<br />
|-<br />
| 26-05-2016 || 10:45-12:45 || Group 7<br />
|-<br />
| 26-05-2016 || 12:45-14:45 || Group 6<br />
|-<br />
| 26-05-2016 || 14:45-16:45 || Group 3<br />
|-<br />
| 26-05-2016 || 16:45-18:45 || Group 1<br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27444Embedded Motion Control 20162016-05-25T08:24:49Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation (6-minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Communication patterns by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
| June 17<br />
| colspan="2" | '''Deadline wiki pages'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* ||<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || Group 6 <br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 21'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 24-05-2016 || 14:45-16:45 || <br />
|-<br />
| 24-05-2016 || 16:45-18:45 || <br />
|-<br />
| 24-05-2016 || 18:45-20:45 || <br />
|-<br />
| 26-05-2016 || 8:45-10:45 || Group 5<br />
|-<br />
| 26-05-2016 || 10:45-12:45 || Group 7<br />
|-<br />
| 26-05-2016 || 12:45-14:45 || Group 6<br />
|-<br />
| 26-05-2016 || 14:45-16:45 || Group 3<br />
|-<br />
| 26-05-2016 || 16:45-18:45 || Group 1<br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27443Embedded Motion Control 20162016-05-25T08:23:38Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation (6-minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Communication patterns by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| colspan="2" | '''No lecture'''<br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<br />
It is possible to test on the robot outside of the scheduled time, but know that this is unsupported. Make sure that when you want to test on the robot outside the schedule you add your time to the schedule and put an asterix after the time. Know that other people need to use the field as well (Tech United etc.) and outside the scheduled time these parties have precedence over you. Also know that you can only test once a week, so scheduling twice in a week is not allowed.<br />
<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* ||<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || Group 6 <br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 21'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 24-05-2016 || 14:45-16:45 || <br />
|-<br />
| 24-05-2016 || 16:45-18:45 || <br />
|-<br />
| 24-05-2016 || 18:45-20:45 || <br />
|-<br />
| 26-05-2016 || 8:45-10:45 || Group 5<br />
|-<br />
| 26-05-2016 || 10:45-12:45 || Group 7<br />
|-<br />
| 26-05-2016 || 12:45-14:45 || Group 6<br />
|-<br />
| 26-05-2016 || 14:45-16:45 || Group 3<br />
|-<br />
| 26-05-2016 || 16:45-18:45 || Group 1<br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Using_Pico&diff=27228MRC/Using Pico2016-05-18T09:47:47Z<p>Ydouven: /* Recording data */</p>
<hr />
<div>== Starting Pico ==<br />
To start Pico please follow the following steps:<br />
# Power on the robot<br />
#* For Pico, the on-off switch is on the bottom, next to the emergency button. This also starts the on-board computer<br />
<!--<br />
#* For Taco, the on-off switch is on the outer edge of the base. Also start the laptop, if it is not already on (you don't need to log in).<br />
--><br />
# Now plug in the laptop you want to use (one of your group members' laptops) to the given UTP cable and make sure it is connected using this wired network connection.<br />
# '''From here on, you should work on your laptop.''' Open a terminal and type <pre>sshpico</pre> The password is '''emc'''.<br />
<!-- where <robot name> is either pico or taco, depending on which robot you want to use. Using this command, you login on the robot's computer; the password is again '''emc'''. --><br />
# Now that you are in, you can start all the necessary nodes on the robot. These controllers and drivers let your software communicate with the hardware. On the robot (so in the terminal you opened in the previous step) enter <br />
#* For Pico: <pre>pstart</pre><br />
<!--<br />
#* For Taco: <pre>tstart</pre><br />
--><br />
# '''N.B. leave this terminal open! '''<br />
<br />
== Running your software ==<br />
Pico is now up and running. To run your own software follow these steps:<br />
# Open a '''new''' terminal and login to your robot again: <pre>sshpico</pre> with password '''emc'''.<br />
# Go to your group's folder: <pre>cd ~/emc/emc<group number></pre><br />
# The rest works the same as on your own PC. <br />
#* The first time, you will have to clone your git project on the robot's computer: <pre>git clone https://gitlab.com/emc2016/group<group number>.git</pre> Of course with your own group number, project name etc. Just like you did on the PCs of the group members.<br />
#* Any next time you can just navigate to your project folder within your group's folder and <pre>git pull</pre><br />
#* Now that your own software is up to date, you can compile it and run it, again just like you would on your own laptop.<br />
<br />
== Develop while testing ==<br />
<br />
You should avoid having to do hard-core debugging and developing while testing, since you only have limited testing time. However, there may be times when you have to change some things in your code and retry. There are roughly two ways to do this:<br />
<br />
# Edit the files on your pc:<br />
## Simply use Qt Creator or any other editor to change the files<br />
## Push your changes to the git server<br />
## Pull the changes on the robot, recompile, and try<br />
# Edit the files on the robot:<br />
## Use programs such as 'nano' or 'vim' to edit the files<br />
## recompile and test<br />
## Commit and push your changes once you're happy<br />
##* Be sure to set your name and email address before committing!<pre>git config user.email "bla@student.tue.nl"</pre><pre>git config user.name "Your name"</pre>'''Note: don't use the '--global' option as other people are also using the robot. Not having the '--global' option will limit the config change to the current repository.'''<br />
<br />
== Visualization ==<br />
When you want to visualize the robot while testing, you can do the following<br />
# Open a new terminal and type <pre>pico-core</pre> This makes sure that any software you run in this terminal listens to the ros-master on your robot.<br />
# So if you now run our visualization software by entering <pre>emc-viz</pre> it will subscribe to the topics published on the robot.<br />
<br />
== Recording data ==<br />
A simulator simulates a perfect world, so if your software works in the simulator, it is not (at all) guaranteed to work in the real world. But because you only have limited testing time on the robots, it would be nice if you could somehow simulate being in the real world. Luckily, the developers of ROS also ran into this, so they created rosbag. Using rosbag you can record data published by the robot and play it later when you want to test an awesome new feature of your software using real sensor data, or if you just want to inspect the quality of the sensor data, etc.<br />
# The first step is again to open a terminal and log in to the robot <pre>sshpico</pre><br />
# Find the topics you would like to record (usually those will be the ones containing data from the LRF and the odometry: /pico/laser and /pico/odom) by using <pre>rostopic list</pre><br />
# You can now use the rosbag tool to record the topics you like: <pre>rosbag record topic_1 topic_2</pre>Topic_1 and topic_2 should of course be changed to the correct topic names, but you can also add more topics to this command. While recording, you should leave this terminal open, and if you think you have enough data, you can stop recording by pressing ctrl+C. If you would like to record all topics (not recommended, as this means recording '''a lot''' of unnecessary data), you could use the option -a instead of typing in all of the topic names.<br />
# The bag file you just recorded is now in the current directory, so if you enter <pre>ls</pre> you can see it among the other files in the current directory. This should be the home directory (if you did not cd to somewhere else). You can now copy this file over the network to your own laptop by opening a '''new terminal''' (or just log out of the robot by pressing ctrl+D), navigating to the directory where you want to place your new bag file, and entering<pre>scp emc@192.168.2.81:~/<filename> <filename></pre> What this command does is the following: it securely copies (scp) from the emc account at the robot's computer the file given by the path after the colon and it places it in your current directory with the second file name. If you gathered multiple bag files on the robot's PC, you can easily copy all of them in one go by doing <pre>scp emc@192.168.2.81:~/*.bag .</pre> This will copy all files wit the .bag extention from the home folder of Pico to your current directory.<br />
# After you have copied your bag files to your own PC, clean up the robot's PC by removing your bag file(s): <pre>rm <filename></pre> This '''permanently''' removes the file from the robot's file system, so if you want to keep it, make sure you only do this after copying it to your own PC!<br />
<br />
== Playing back bag files ==<br />
Now you can play this bag file as often as you like and have your software analyse the sensor data. To do that, take the following steps:<br />
# First start a roscore, like you always do<br />
# Now, because you want your node(s) to use the time that was recorded in the bag file instead of the current system time, you will have to tell it to do that. You can do that by setting the ROS parameter use_sim_time to ''true'': <pre>rosparam set use_sim_time true</pre><br />
# If all is well, you should now be able to play the bag file by entering <pre>rosbag play --clock <filename></pre><br />
For more advanced use and other information on the command line use of rosbag, go to the official [http://wiki.ros.org/rosbag/Commandline documentation of the tool].</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27225Embedded Motion Control 20162016-05-18T09:04:21Z<p>Ydouven: /* Pico test schedule */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation (6-minutes for questions) about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00.<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 19'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 20'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 17-05-2016 || 8:45-10:45 || Group 3<br />
|-<br />
| 17-05-2016 || 10:45-12:45 || Group 1<br />
|-<br />
| 17-05-2016 || 12:45-14:45 || Group 5<br />
|-<br />
| 17-05-2016 || 14:45-16:45 || Group 7<br />
|-<br />
| 17-05-2016 || 16:45-18:45 || Group 4<br />
|-<br />
| 17-05-2016 || 18:45-20:45* || Group 6<br />
|-<br />
| 18-05-2016 || 8:45-10:45* || Group 2<br />
|-<br />
| 18-05-2016 || 10:45-12:45* || <br />
|-<br />
| 19-05-2016 || 8:45-10:45 || <br />
|-<br />
| 19-05-2016 || 10:45-12:45 || <br />
|-<br />
| 19-05-2016 || 12:45-14:45 || <br />
|}<br />
<div style="clear:both"></div><br />
<br />
<br />
\*no support available<br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=File:20160504-EMC-Skills-nup.pdf&diff=27110File:20160504-EMC-Skills-nup.pdf2016-05-09T09:38:23Z<p>Ydouven: </p>
<hr />
<div></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=27109Embedded Motion Control 20162016-05-09T09:38:02Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| colspan="2" | [[Media:20160504-EMC-Skills-nup.pdf | Best Practices in System Design for Robot Control by ''Herman Bruyninckx'']]<br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
Submissions are last checked the day before at 22:00, except this week for monday since the schedule was online late.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 16'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 26-04-2016 || 10:45 - 11:45 || INTRO SESSION<br />
|-<br />
| 26-04-2016 || 11:45 - 13:45 || <br />
|-<br />
| 26-04-2016 || 13:45 - 15:45 || <br />
|-<br />
| 26-04-2016 || 15:45 - 17:45 ||<br />
|-<br />
| 29-04-2016 || 8:45 - 10:45 || Intro Session- Group 3+5<br />
|-<br />
| 29-04-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 29-04-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 29-04-2016 || 14:45 - 16:45 ||<br />
|}<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 17'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 03-05-2016 || 8:45 - 10:45 ||<br />
|-<br />
| 03-05-2016 || 10:45 - 12:45 || <br />
|-<br />
| 03-05-2016 || 12:45 - 14:45 || <br />
|-<br />
| 03-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 04-05-2016 || 8:45 - 10:45 || Group 5<br />
|-<br />
| 04-05-2016 || 10:45 - 12:45 || Group 1<br />
|-<br />
| 04-05-2016 || 12:45 - 14:45 || Group 7<br />
|-<br />
| 04-05-2016 || 14:45 - 16:45 || Group 6<br />
|}<br />
<div style="clear:both"></div><br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 17'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 09-05-2016 || 14:45 - 16:45 ||<br />
|-<br />
| 09-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 10-05-2016 || 8:45 - 10:45 || <br />
|-<br />
| 10-05-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 10-05-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 10-05-2016 || 14:45 - 16:45 || <br />
|- <br />
| 10-05-2016 || 16:45 - 18:45 || <br />
|-<br />
| 13-05-2016 || 8:45 - 10:45 || Group 1<br />
|-<br />
| 13-05-2016 || 10:45 - 12:45 || Group 3<br />
|}<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=26836Embedded Motion Control 20162016-04-28T14:57:24Z<p>Ydouven: /* Group Wiki Pages */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| Composition Pattern part I by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': Roel Smallegoor<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': Yanick Douven<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': Wouter Kuijpers<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': René van de Molengraft<br />
<br />
= Pico test schedule =<br />
A timetable for testing is now available. During this first week most of the groups will not have any software to test. Therefore, a session will be held to introduce the robot to the groups on '''tuesday 10:45 ''', multiple groups can come to this session. If tuesday is a bad time, because a lecture is being held at that time, please let me now (j.smit@student.tue.nl). It is still possible to reserve a slot to test your software at another moment.<br />
<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 16'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 26-04-2016 || 10:45 - 11:45 || INTRO SESSION<br />
|-<br />
| 26-04-2016 || 11:45 - 13:45 || <br />
|-<br />
| 26-04-2016 || 13:45 - 15:45 || <br />
|-<br />
| 26-04-2016 || 15:45 - 17:45 ||<br />
|-<br />
| 29-04-2016 || 8:45 - 10:45 || Intro Session- Group 3+5<br />
|-<br />
| 29-04-2016 || 10:45 - 12:45 ||<br />
|-<br />
| 29-04-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 29-04-2016 || 14:45 - 16:45 ||<br />
|}<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Tutorials/Sharing_your_project_through_git&diff=26811MRC/Tutorials/Sharing your project through git2016-04-28T13:18:51Z<p>Ydouven: /* Share a project */</p>
<hr />
<div>= Introduction =<br />
<br />
Creating a software solution together means sharing a project, which in our case means sharing code. We will be using [http://git-scm.com/ ''git''] for this. Git is "a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency":<br />
<br />
* ''version control'' means that the files and changes you make to them are 'tracked' over time, ''i.e.'', their 'history' is stored. You can always go back to previous version, show the difference since a certain point in time, etc.<br />
* ''distributed'' means that you don't necessarily need a central server to store your changes. Every team member has the full history available, and can always stored his changes and go back to previous versions, even if he or she is off-line. However, note that we will use a central server every team member stores his or her changes to, and loads the changes others made from.<br />
<br />
<br />
The first part of the tutorial shows how to initialize a git repository and how to store your local changes to the server. However, imagine that this may soon become a mess if every team member will do so. Therefore, it is advised that only one team member actually runs all the commands in this tutorial, but it is strongly recommended for the others to ''also'' take a good look and understand the different steps and commands.<br />
<br />
= Telling git who you are =<br />
<br />
Before you start using git, you have to tell git who you are. That way, git can 'stamp' all the changes you make with your name and email address. That way it is easy to keep track of who did what, and when. Just run the following (with your real name and email address):<br />
<br />
<pre>git config --global user.name "Put your name here"</pre><br />
<br />
<pre>git config --global user.email "Put your email address here"</pre><br />
<br />
= Intializing a git repository =<br />
<br />
Navigate to your project directory. For this tutorial, we will use '~/emc/my_project', but if you renamed your project in the meantime (which is actually advisable), use that name instead.<br />
<br />
<pre>cd ~/emc/my_project</pre><br />
<br />
Turn the directory into a git repository:<br />
<pre>git init</pre><br />
<br />
It's that easy! Now let's have a look at the current status of the git repository. Run:<br />
<pre>git status</pre><br />
<br />
You will see a list of untracked files, e.g., something like this:<br />
<pre><br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
CMakeLists.txt<br />
bin/<br />
build/<br />
src/<br />
</pre><br />
<br />
''Untracked'' means that these files are not under git version control. Note that we only want some of the files to be ''tracked'' by git. For example, the ''bin'' and ''build'' folder are automatically generated by CMake and compilation. We should therefore only add the ''source'' files, and the ''CMakeLists.txt'' (and possibly other files that you want to share). To make sure git will keep track of these files, use ''git add'':<br />
<br />
<pre>git add src CMakeLists.txt</pre><br />
<br />
Now, run ''git status'' again. You should see something like this:<br />
<br />
<pre><br />
Changes to be committed:<br />
(use "git rm --cached <file>..." to unstage)<br />
<br />
new file: CMakeLists.txt<br />
new file: src/example.cpp<br />
<br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
bin/<br />
build/<br />
</pre><br />
<br />
As you can see, you now have some 'changes to be committed'. Committing means we store the added files as they are now. From that point on we can make new modifications, and we can always roll back to this version, see the changes since this version, ''and'', we can share the changes with others. To commit the changes:<br />
<br />
<pre>git commit -m 'Type a meaningful sentence here'</pre><br />
<br />
The part after '-m' is the ''commit message''. It is important that this message is a meaningful message that describes what the added changes are, for example 'fixed this-and-this bug' or 'added this-and-this feature'. That way, you can look in the 'git log' and easily see what was added when, and to which version you need to roll back if you have to.<br />
<br />
So, we have commited our changes. Let's see the status using ''git status''. It no longer indicates any changes. That is correct, we just committed them! Now, have a look at the git log:<br />
<br />
<pre>git log</pre><br />
<br />
It outputs an overview of who committed what and when. You should see your name and commit message, and some long code with letters and numbers. This is a ''commit hash'', and can be thought of as a unique id for this commit.<br />
<br />
= Storing your changes on the server =<br />
<br />
Alright, your work is now safely stored on your computer. You can make changes, and commit these as well (remember, first use 'git add', then 'git commit'). But you also want to share these changes with your team mates!<br />
<br />
For this purpose, we will use [https://gitlab.com GitLab]. GitLab is open source software to collaborate on code. <br />
<br />
Well, we have put up a git server such that you can store your projects in a safe place. You should have received an email with a username and password. Now:<br />
<br />
* Browse to [https://gitlab.com/users/sign_in gitlab.com/users/sign_in] and create an account (it's free and you won't receive any spam, don't worry)<br />
* E-mail your username to (one of) the tutors (only one group member has to send his username)<br />
* Once we have added you to your group's project, you will receive an e-mail with the link to your repository<br />
* You can then add your colleagues to your project and start collaborating!<br />
<br />
That's it! We can now push the local commits you made so far to this project. Once we've done that, the commits are also safely stored on the server. So, let's do this!<br />
<br />
First, we need to tell git where it has to store the commits. The online git project has unique URL. This URL depends on your group number. If your group number is 1, you can set the URL of your local git repository as follows:<br />
<br />
<pre>git remote add origin https://gitlab.com/emc2016/group1.git</pre><br />
<br />
So, we've told the git repository where it should send the commits to (and where it can pull them from later). But we still have to tell git to actually send them there. This is called 'pushing'. The first time you push commits to the server, you have to use this command:<br />
<br />
<pre>git push -u origin master</pre><br />
<br />
and enter your username and password.<br />
<br />
We won't go into details here, but the command basically states that the current commits should be send to the origin (of which we set the URL above) and that the git repository should 'keep an eye' on what happens on the server. This means that if one of your team mates also pushes commits to this address, we can 'pull' them to your local repository. This is exactly how the synchronization works. You push your changes, and pull changes that others made.<br />
<br />
Now, make a small change to one of the files. Then if you run 'git status', you will see which file was modified. If you type 'git diff' you can see the actual changes. Quite useful, isn't it!<br />
<br />
Again, you can commit the change once you've done something useful, but first you need to tell git again which files you want to commit by using 'git add'. Then once you've created the commit, you can push it to the server, this time simply using 'git push'. So, to sum up:<br />
<br />
# Make your changes<br />
# Add the files of which you want to commit the changes:<pre>git add ...</pre><br />
# Commit your changes:<pre>git commit -m '... message ...'</pre><br />
# Push your changes to the server: <pre>git push</pre>(the '-u' stuff is no longer necessary)<br />
<br />
= Share a project =<br />
<br />
Up until now, you have seen how you can commit your changes to the server, but it is not very useful if you cannot share your changes with your teammates. Well, sharing is easy in git! Your teammates can get a local copy of the repository. This is called 'cloning', and works as follows (change the URL to the correct project url)<br />
<br />
<pre>cd ~/emc<br />
git clone https://gitlab.com/emc2016/group1.git shared_project<br />
</pre><br />
<br />
This will create a directory called 'shared_project' in which you will find the files that someone else committed. Have a look at the git log, and you see who committed what.<br />
<br />
Now, this is just a normal git repository to which you can make changes, commit and from which you can push your commits to the server. It is advised that ''one'' person in the group pushes the origin branch ('-u' stuff), and that the others clone it.<br />
<br />
One thing is not yet explained, and that is how you can get the changes that others pushed to the server since you cloned it. Well, it's easy:<br />
<br />
<pre>git pull</pre><br />
<br />
This will 'pull in' the latest commits and your files will be updated accordingly. Note that this won't work if you have modified files, ''i.e.'' file changes that you have not yet committed. You don't want these changes to be overwritten by a 'pull', so git doesn't allow it. To get the latest changes, you have to commit your changes and try pulling again.<br />
<br />
= Recap =<br />
<br />
The tutorial above showed how to create a repository in Gitlab, how to push changes to it, and how to pull changes from it. From now on, keep working in this directory and commit all your changes, and pull the changes from your team members.</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Tutorials/Sharing_your_project_through_git&diff=26810MRC/Tutorials/Sharing your project through git2016-04-28T13:17:10Z<p>Ydouven: /* Share a project */</p>
<hr />
<div>= Introduction =<br />
<br />
Creating a software solution together means sharing a project, which in our case means sharing code. We will be using [http://git-scm.com/ ''git''] for this. Git is "a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency":<br />
<br />
* ''version control'' means that the files and changes you make to them are 'tracked' over time, ''i.e.'', their 'history' is stored. You can always go back to previous version, show the difference since a certain point in time, etc.<br />
* ''distributed'' means that you don't necessarily need a central server to store your changes. Every team member has the full history available, and can always stored his changes and go back to previous versions, even if he or she is off-line. However, note that we will use a central server every team member stores his or her changes to, and loads the changes others made from.<br />
<br />
<br />
The first part of the tutorial shows how to initialize a git repository and how to store your local changes to the server. However, imagine that this may soon become a mess if every team member will do so. Therefore, it is advised that only one team member actually runs all the commands in this tutorial, but it is strongly recommended for the others to ''also'' take a good look and understand the different steps and commands.<br />
<br />
= Telling git who you are =<br />
<br />
Before you start using git, you have to tell git who you are. That way, git can 'stamp' all the changes you make with your name and email address. That way it is easy to keep track of who did what, and when. Just run the following (with your real name and email address):<br />
<br />
<pre>git config --global user.name "Put your name here"</pre><br />
<br />
<pre>git config --global user.email "Put your email address here"</pre><br />
<br />
= Intializing a git repository =<br />
<br />
Navigate to your project directory. For this tutorial, we will use '~/emc/my_project', but if you renamed your project in the meantime (which is actually advisable), use that name instead.<br />
<br />
<pre>cd ~/emc/my_project</pre><br />
<br />
Turn the directory into a git repository:<br />
<pre>git init</pre><br />
<br />
It's that easy! Now let's have a look at the current status of the git repository. Run:<br />
<pre>git status</pre><br />
<br />
You will see a list of untracked files, e.g., something like this:<br />
<pre><br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
CMakeLists.txt<br />
bin/<br />
build/<br />
src/<br />
</pre><br />
<br />
''Untracked'' means that these files are not under git version control. Note that we only want some of the files to be ''tracked'' by git. For example, the ''bin'' and ''build'' folder are automatically generated by CMake and compilation. We should therefore only add the ''source'' files, and the ''CMakeLists.txt'' (and possibly other files that you want to share). To make sure git will keep track of these files, use ''git add'':<br />
<br />
<pre>git add src CMakeLists.txt</pre><br />
<br />
Now, run ''git status'' again. You should see something like this:<br />
<br />
<pre><br />
Changes to be committed:<br />
(use "git rm --cached <file>..." to unstage)<br />
<br />
new file: CMakeLists.txt<br />
new file: src/example.cpp<br />
<br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
bin/<br />
build/<br />
</pre><br />
<br />
As you can see, you now have some 'changes to be committed'. Committing means we store the added files as they are now. From that point on we can make new modifications, and we can always roll back to this version, see the changes since this version, ''and'', we can share the changes with others. To commit the changes:<br />
<br />
<pre>git commit -m 'Type a meaningful sentence here'</pre><br />
<br />
The part after '-m' is the ''commit message''. It is important that this message is a meaningful message that describes what the added changes are, for example 'fixed this-and-this bug' or 'added this-and-this feature'. That way, you can look in the 'git log' and easily see what was added when, and to which version you need to roll back if you have to.<br />
<br />
So, we have commited our changes. Let's see the status using ''git status''. It no longer indicates any changes. That is correct, we just committed them! Now, have a look at the git log:<br />
<br />
<pre>git log</pre><br />
<br />
It outputs an overview of who committed what and when. You should see your name and commit message, and some long code with letters and numbers. This is a ''commit hash'', and can be thought of as a unique id for this commit.<br />
<br />
= Storing your changes on the server =<br />
<br />
Alright, your work is now safely stored on your computer. You can make changes, and commit these as well (remember, first use 'git add', then 'git commit'). But you also want to share these changes with your team mates!<br />
<br />
For this purpose, we will use [https://gitlab.com GitLab]. GitLab is open source software to collaborate on code. <br />
<br />
Well, we have put up a git server such that you can store your projects in a safe place. You should have received an email with a username and password. Now:<br />
<br />
* Browse to [https://gitlab.com/users/sign_in gitlab.com/users/sign_in] and create an account (it's free and you won't receive any spam, don't worry)<br />
* E-mail your username to (one of) the tutors (only one group member has to send his username)<br />
* Once we have added you to your group's project, you will receive an e-mail with the link to your repository<br />
* You can then add your colleagues to your project and start collaborating!<br />
<br />
That's it! We can now push the local commits you made so far to this project. Once we've done that, the commits are also safely stored on the server. So, let's do this!<br />
<br />
First, we need to tell git where it has to store the commits. The online git project has unique URL. This URL depends on your group number. If your group number is 1, you can set the URL of your local git repository as follows:<br />
<br />
<pre>git remote add origin https://gitlab.com/emc2016/group1.git</pre><br />
<br />
So, we've told the git repository where it should send the commits to (and where it can pull them from later). But we still have to tell git to actually send them there. This is called 'pushing'. The first time you push commits to the server, you have to use this command:<br />
<br />
<pre>git push -u origin master</pre><br />
<br />
and enter your username and password.<br />
<br />
We won't go into details here, but the command basically states that the current commits should be send to the origin (of which we set the URL above) and that the git repository should 'keep an eye' on what happens on the server. This means that if one of your team mates also pushes commits to this address, we can 'pull' them to your local repository. This is exactly how the synchronization works. You push your changes, and pull changes that others made.<br />
<br />
Now, make a small change to one of the files. Then if you run 'git status', you will see which file was modified. If you type 'git diff' you can see the actual changes. Quite useful, isn't it!<br />
<br />
Again, you can commit the change once you've done something useful, but first you need to tell git again which files you want to commit by using 'git add'. Then once you've created the commit, you can push it to the server, this time simply using 'git push'. So, to sum up:<br />
<br />
# Make your changes<br />
# Add the files of which you want to commit the changes:<pre>git add ...</pre><br />
# Commit your changes:<pre>git commit -m '... message ...'</pre><br />
# Push your changes to the server: <pre>git push</pre>(the '-u' stuff is no longer necessary)<br />
<br />
= Share a project =<br />
<br />
Up until now, you have seen how you can commit your changes to the server, but it is not very useful if you cannot share your changes with your teammates. Well, sharing is easy in git! Your teammates can get a local copy of the repository. This is called 'cloning', and works as follows (change the URL to the correct project url)<br />
<br />
<pre>cd ~/emc<br />
git clone https://gitlab.com/emc2016/group1.git shared_project<br />
</pre><br />
<br />
This will create a directory called 'shared_project' in which you will find the files that someone else committed. Have a look at the git log, and you see who committed what.<br />
<br />
Now, this is just a normal git repository to which you can make changes, commit and from which you can push your commits to the server. It is advised that ''one'' person in the group creates a project and corresponding git repository, and that the others clone it.<br />
<br />
One thing is not yet explained, and that is how you can get the changes that others pushed to the server since you cloned it. Well, it's easy:<br />
<br />
<pre>git pull</pre><br />
<br />
This will 'pull in' the latest commits and your files will be updated accordingly. Note that this won't work if you have modified files, ''i.e.'' file changes that you have not yet committed. You don't want these changes to be overwritten by a 'pull', so git doesn't allow it. To get the latest changes, you have to commit your changes and try pulling again.<br />
<br />
= Recap =<br />
<br />
The tutorial above showed how to create a repository in Gitlab, how to push changes to it, and how to pull changes from it. From now on, keep working in this directory and commit all your changes, and pull the changes from your team members.</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Tutorials/Sharing_your_project_through_git&diff=26809MRC/Tutorials/Sharing your project through git2016-04-28T13:13:30Z<p>Ydouven: /* Storing your changes on the server */</p>
<hr />
<div>= Introduction =<br />
<br />
Creating a software solution together means sharing a project, which in our case means sharing code. We will be using [http://git-scm.com/ ''git''] for this. Git is "a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency":<br />
<br />
* ''version control'' means that the files and changes you make to them are 'tracked' over time, ''i.e.'', their 'history' is stored. You can always go back to previous version, show the difference since a certain point in time, etc.<br />
* ''distributed'' means that you don't necessarily need a central server to store your changes. Every team member has the full history available, and can always stored his changes and go back to previous versions, even if he or she is off-line. However, note that we will use a central server every team member stores his or her changes to, and loads the changes others made from.<br />
<br />
<br />
The first part of the tutorial shows how to initialize a git repository and how to store your local changes to the server. However, imagine that this may soon become a mess if every team member will do so. Therefore, it is advised that only one team member actually runs all the commands in this tutorial, but it is strongly recommended for the others to ''also'' take a good look and understand the different steps and commands.<br />
<br />
= Telling git who you are =<br />
<br />
Before you start using git, you have to tell git who you are. That way, git can 'stamp' all the changes you make with your name and email address. That way it is easy to keep track of who did what, and when. Just run the following (with your real name and email address):<br />
<br />
<pre>git config --global user.name "Put your name here"</pre><br />
<br />
<pre>git config --global user.email "Put your email address here"</pre><br />
<br />
= Intializing a git repository =<br />
<br />
Navigate to your project directory. For this tutorial, we will use '~/emc/my_project', but if you renamed your project in the meantime (which is actually advisable), use that name instead.<br />
<br />
<pre>cd ~/emc/my_project</pre><br />
<br />
Turn the directory into a git repository:<br />
<pre>git init</pre><br />
<br />
It's that easy! Now let's have a look at the current status of the git repository. Run:<br />
<pre>git status</pre><br />
<br />
You will see a list of untracked files, e.g., something like this:<br />
<pre><br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
CMakeLists.txt<br />
bin/<br />
build/<br />
src/<br />
</pre><br />
<br />
''Untracked'' means that these files are not under git version control. Note that we only want some of the files to be ''tracked'' by git. For example, the ''bin'' and ''build'' folder are automatically generated by CMake and compilation. We should therefore only add the ''source'' files, and the ''CMakeLists.txt'' (and possibly other files that you want to share). To make sure git will keep track of these files, use ''git add'':<br />
<br />
<pre>git add src CMakeLists.txt</pre><br />
<br />
Now, run ''git status'' again. You should see something like this:<br />
<br />
<pre><br />
Changes to be committed:<br />
(use "git rm --cached <file>..." to unstage)<br />
<br />
new file: CMakeLists.txt<br />
new file: src/example.cpp<br />
<br />
Untracked files:<br />
(use "git add <file>..." to include in what will be committed)<br />
<br />
bin/<br />
build/<br />
</pre><br />
<br />
As you can see, you now have some 'changes to be committed'. Committing means we store the added files as they are now. From that point on we can make new modifications, and we can always roll back to this version, see the changes since this version, ''and'', we can share the changes with others. To commit the changes:<br />
<br />
<pre>git commit -m 'Type a meaningful sentence here'</pre><br />
<br />
The part after '-m' is the ''commit message''. It is important that this message is a meaningful message that describes what the added changes are, for example 'fixed this-and-this bug' or 'added this-and-this feature'. That way, you can look in the 'git log' and easily see what was added when, and to which version you need to roll back if you have to.<br />
<br />
So, we have commited our changes. Let's see the status using ''git status''. It no longer indicates any changes. That is correct, we just committed them! Now, have a look at the git log:<br />
<br />
<pre>git log</pre><br />
<br />
It outputs an overview of who committed what and when. You should see your name and commit message, and some long code with letters and numbers. This is a ''commit hash'', and can be thought of as a unique id for this commit.<br />
<br />
= Storing your changes on the server =<br />
<br />
Alright, your work is now safely stored on your computer. You can make changes, and commit these as well (remember, first use 'git add', then 'git commit'). But you also want to share these changes with your team mates!<br />
<br />
For this purpose, we will use [https://gitlab.com GitLab]. GitLab is open source software to collaborate on code. <br />
<br />
Well, we have put up a git server such that you can store your projects in a safe place. You should have received an email with a username and password. Now:<br />
<br />
* Browse to [https://gitlab.com/users/sign_in gitlab.com/users/sign_in] and create an account (it's free and you won't receive any spam, don't worry)<br />
* E-mail your username to (one of) the tutors (only one group member has to send his username)<br />
* Once we have added you to your group's project, you will receive an e-mail with the link to your repository<br />
* You can then add your colleagues to your project and start collaborating!<br />
<br />
That's it! We can now push the local commits you made so far to this project. Once we've done that, the commits are also safely stored on the server. So, let's do this!<br />
<br />
First, we need to tell git where it has to store the commits. The online git project has unique URL. This URL depends on your group number. If your group number is 1, you can set the URL of your local git repository as follows:<br />
<br />
<pre>git remote add origin https://gitlab.com/emc2016/group1.git</pre><br />
<br />
So, we've told the git repository where it should send the commits to (and where it can pull them from later). But we still have to tell git to actually send them there. This is called 'pushing'. The first time you push commits to the server, you have to use this command:<br />
<br />
<pre>git push -u origin master</pre><br />
<br />
and enter your username and password.<br />
<br />
We won't go into details here, but the command basically states that the current commits should be send to the origin (of which we set the URL above) and that the git repository should 'keep an eye' on what happens on the server. This means that if one of your team mates also pushes commits to this address, we can 'pull' them to your local repository. This is exactly how the synchronization works. You push your changes, and pull changes that others made.<br />
<br />
Now, make a small change to one of the files. Then if you run 'git status', you will see which file was modified. If you type 'git diff' you can see the actual changes. Quite useful, isn't it!<br />
<br />
Again, you can commit the change once you've done something useful, but first you need to tell git again which files you want to commit by using 'git add'. Then once you've created the commit, you can push it to the server, this time simply using 'git push'. So, to sum up:<br />
<br />
# Make your changes<br />
# Add the files of which you want to commit the changes:<pre>git add ...</pre><br />
# Commit your changes:<pre>git commit -m '... message ...'</pre><br />
# Push your changes to the server: <pre>git push</pre>(the '-u' stuff is no longer necessary)<br />
<br />
= Share a project =<br />
<br />
Up until now, you have seen how you can commit your changes to the server, but it is not very useful if you cannot share your changes with your teammates. Well, sharing is easy in git! Instead of creating their own project, they can get a local copy of the repository you created in GitLab (and to which you pushed your local commits). This is called 'cloning', and works as follows (change the URL to the correct project url)<br />
<br />
<pre>cd ~/emc<br />
git clone http://roboticssrv.wtb.tue.nl:8800/emc01/my_project.git shared_project<br />
</pre><br />
<br />
This will create a directory called 'shared_project' in which you will find the files that someone else committed. Have a look at the git log, and you see who committed what.<br />
<br />
Now, this is just a normal git repository to which you can make changes, commit and from which you can push your commits to the server. It is advised that ''one'' person in the group creates a project and corresponding git repository, and that the others clone it.<br />
<br />
One thing is not yet explained, and that is how you can get the changes that others pushed to the server since you cloned it. Well, it's easy:<br />
<br />
<pre>git pull</pre><br />
<br />
This will 'pull in' the latest commits and your files will be updated accordingly. Note that this won't work if you have modified files, ''i.e.'' file changes that you have not yet committed. You don't want these changes to be overwritten by a 'pull', so git doesn't allow it. To get the latest changes, you have to commit your changes and try pulling again.<br />
<br />
= Recap =<br />
<br />
The tutorial above showed how to create a repository in Gitlab, how to push changes to it, and how to pull changes from it. From now on, keep working in this directory and commit all your changes, and pull the changes from your team members.</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=26701Embedded Motion Control 20162016-04-26T11:41:44Z<p>Ydouven: /* Group Wiki Pages */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction (see Oase) by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| Composition Pattern part I by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 5 - [[Embedded Motion Control 2016 Group 5 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 6 - [[Embedded Motion Control 2016 Group 6 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 7 - [[Embedded Motion Control 2016 Group 7 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
= Pico test schedule =<br />
A timetable for testing is now available. During this first week most of the groups will not have any software to test. Therefore, a session will be held to introduce the robot to the groups on '''tuesday 10:45 ''', multiple groups can come to this session. If tuesday is a bad time, because a lecture is being held at that time, please let me now (j.smit@student.tue.nl). It is still possible to reserve a slot to test your software at another moment.<br />
<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
<br />
{| class="TablePager" style="width: 300px; min-width: 240px; margin-left: 2em; float:left; color: black;"<br />
|+ '''Week 16'''<br />
|-<br />
! scope="col" | '''Date'''<br />
! scope="col" | '''Time'''<br />
! scope="col" | '''Group'''<br />
|-<br />
| 26-04-2016 || 10:45 - 11:45 || INTRO SESSION<br />
|-<br />
| 26-04-2016 || 11:45 - 13:45 || <br />
|-<br />
| 26-04-2016 || 13:45 - 15:45 || <br />
|-<br />
| 26-04-2016 || 15:45 - 17:45 ||<br />
|-<br />
| 29-04-2016 || 8:45 - 10:45 ||<br />
|-<br />
| 29-04-2016 || 10:45 - 12:45 || Intro Session- lakhotia, sharma, chaudhuri, wang<br />
|-<br />
| 29-04-2016 || 12:45 - 14:45 ||<br />
|-<br />
| 29-04-2016 || 14:45 - 16:45 ||<br />
|}<br />
<div style="clear:both"></div><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016_Group_7&diff=26700Embedded Motion Control 2016 Group 72016-04-26T11:00:11Z<p>Ydouven: Created page with '= '''Group Members''' = {| border="1" cellpadding="5" cellspacing="0" align="left" |- | 0816253 | Emile van Halsema |- | 0805999 | Nard Strijbosch |- | 0816608 | Raymond Kerste…'</p>
<hr />
<div>= '''Group Members''' =<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" <br />
|- <br />
| 0816253<br />
| Emile van Halsema<br />
|-<br />
| 0805999<br />
| Nard Strijbosch<br />
|-<br />
| 0816608<br />
| Raymond Kerstens<br />
|-<br />
| 0814199<br />
| Frank Heck<br />
|-<br />
| 0816361<br />
| Ids van den Meijdenberg<br />
|-<br />
|}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016_Group_6&diff=26699Embedded Motion Control 2016 Group 62016-04-26T10:58:46Z<p>Ydouven: /* Group Members */</p>
<hr />
<div>= '''Group Members''' =<br />
'''Please enter your studentnumber in the first column.'''<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" <br />
|- <br />
| <br />
| R. Beenders<br />
|-<br />
| <br />
| M.P. Bos<br />
|-<br />
| <br />
| M. Cornelis<br />
|-<br />
| <br />
| S.J.M. Koopmans<br />
|-<br />
|}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016_Group_6&diff=26698Embedded Motion Control 2016 Group 62016-04-26T10:57:02Z<p>Ydouven: Created page with '= '''Group Members''' = {| border="1" cellpadding="5" cellspacing="0" align="left" |- | | R. Beenders |- | | M.P. Bos |- | | M. Cornelis |- | | S.J.M. Koopmans |- |}'</p>
<hr />
<div>= '''Group Members''' =<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" <br />
|- <br />
| <br />
| R. Beenders<br />
|-<br />
| <br />
| M.P. Bos<br />
|-<br />
| <br />
| M. Cornelis<br />
|-<br />
| <br />
| S.J.M. Koopmans<br />
|-<br />
|}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016_Group_5&diff=26697Embedded Motion Control 2016 Group 52016-04-26T10:56:02Z<p>Ydouven: Created page with '= '''Group Members''' = {| border="1" cellpadding="5" cellspacing="0" align="left" |- | 0976517 | Rohan Lakhotia |- | 0976553 | Parth Sharma |- | 0977462 | Xixiao Wang |- | 097…'</p>
<hr />
<div>= '''Group Members''' =<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" <br />
|- <br />
| 0976517<br />
| Rohan Lakhotia<br />
|-<br />
| 0976553<br />
| Parth Sharma<br />
|-<br />
| 0977462<br />
| Xixiao Wang<br />
|-<br />
| 0977242<br />
| Satyaki Chaudhuri<br />
|-<br />
|}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016_Group_1&diff=26575Embedded Motion Control 2016 Group 12016-04-22T15:29:33Z<p>Ydouven: Created page with '= '''Group Members''' = {| border="1" cellpadding="5" cellspacing="0" align="left" |- |0878154 | Wouter Scholte |- | 0979324 | Goksan Isil |- | 0976279 | Muhammed Erşat Emek |…'</p>
<hr />
<div>= '''Group Members''' =<br />
{| border="1" cellpadding="5" cellspacing="0" align="left" <br />
|- <br />
|0878154<br />
| Wouter Scholte<br />
|-<br />
| 0979324<br />
| Goksan Isil<br />
|-<br />
| 0976279<br />
| Muhammed Erşat Emek<br />
|-<br />
| 0979770<br />
| Stefan Kojchev<br />
|-<br />
|}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=26574Embedded Motion Control 20162016-04-22T15:17:48Z<p>Ydouven: /* Group Wiki Pages */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| Composition Pattern part I by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
Group 1 - [[Embedded Motion Control 2016 Group 1 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 2 - [[Embedded Motion Control 2016 Group 2 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 3 - [[Embedded Motion Control 2016 Group 3 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
Group 4 - [[Embedded Motion Control 2016 Group 4 | visit wiki ]] - '''Tutor''': tbd<br />
<br />
= Pico test schedule =<br />
A timetable for testing will soon be available.<br />
<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016/Contact_Details&diff=26539Embedded Motion Control 2016/Contact Details2016-04-22T09:55:13Z<p>Ydouven: /* Tutors */</p>
<hr />
<div>In case of questions related to working with the real PICO robot, please contact Jorrit. For questions regarding the simulator or Git, please contact Yanick.<br />
<br />
==Tutors==<br />
<br />
'''Yanick Douven''' - <tt>y dot g dot m dot douven at tue dot nl</tt><br />
<br />
'''Roel Smallegoor''' - <tt>r dot smallegoor at student dot tue dot nl</tt><br />
<br />
'''Wouter Kuijpers''' - <tt>w dot j dot p dot kuijpers at student dot tue dot nl</tt><br />
<br />
'''Jorrit Smit''' - <tt>j dot smit at student dot tue dot nl</tt></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Tutorials/Installing_Ubuntu&diff=26250MRC/Tutorials/Installing Ubuntu2016-04-20T21:01:52Z<p>Ydouven: </p>
<hr />
<div>= Installing Ubuntu =<br />
<br />
Download Ubuntu 14.04:<br />
<br />
* [http://releases.ubuntu.com/trusty/ubuntu-14.04.4-desktop-i386.iso 32-bit]<br />
* [http://releases.ubuntu.com/trusty/ubuntu-14.04.4-desktop-amd64.iso 64-bit]<br />
<br />
Then, assuming you are currently running Windows, go to [http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows this page] and follow the instructions to create a bootable USB stick. Reboot your computer with the newly created USB stick, and install Ubuntu. If you want to keep using Windows next to Ubuntu the most easy way is to have a dual-boot system, i.e., during startup you can choose to boot either Ubuntu or Windows. Of course you can also bring your notebook to the ICT servicedesk and ask them to install Ubuntu (but mention that you need version '''14.04''').<br />
<br />
=== Troubleshoot ===<br />
<br />
'''Nothing happens when I reboot with the USB drive'''<br />
<br />
When rebooting your computer with the USB stick it may be the case that booting from your hard drive or SSD is preferred over booting from the USB drive, and the Ubuntu installation doesn't start. In that case, try rebooting again, and now try to enter the ''BIOS'' or watch out for a ''Boot order'' menu. Often, you have to press keys during start-up such as F12 or DEL. Once you found the boot order menu, make sure the USB drive has priority over your normal drive, and restart.<br />
<br />
= The Ubuntu Terminal =<br />
<br />
Most of your interaction with Ubuntu will be done through the terminal, the number-one way of interacting with Ubuntu using your keyboard. A terminal can be started by pressing ''ctrl-alt-t''. <!-- It might be a good idea to drag the terminal icon in the menu to the Ubuntu panel, as you will be using it a lot. --><br />
<br />
Although the terminal commands may seem somewhat puzzling at first, you'll soon find out that the terminal is a nifty tool and allows for faster and more powerful access to all of Ubuntu's possibilities than the graphical interface and mouse. If you don't know your way around the terminal, have a look at [https://help.ubuntu.com/community/UsingTheTerminal this page].<br />
<br />
<br />
Ubuntu is already pretty great out-of-the-box, but some [[Embedded Motion Control/Tutorials/Customizing Ubuntu | customizations will make your Ubuntu experience even better]].</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=MRC/Tutorials/Introduction&diff=26249MRC/Tutorials/Introduction2016-04-20T21:00:21Z<p>Ydouven: </p>
<hr />
<div>During the Embedded Motion Control course you will encounter many tools, systems and concepts that you are currently unfamiliar with. This may be daunting at first, but soon you will notice the strengths of each of the tools and find out how they work together to allow you to program a real, physical robot. The following tutorials are aimed at getting you up speed with these tools as fast as possible.<br />
<br />
<br />
Let's start with an overview of the tools we will be using and the roles they play within your project:<br />
<br />
* '''Ubuntu''': the Operating System we will be using. Ubuntu is a popular Linux distribution. The latest long term support release is 14.04, which we will be using.<br />
<!-- * '''ROS''': (Robot Operating System) is the robot software framework we will be using for managing your software and dealing with the communication between different software modules. ROS comes with a large amount of robot software that can be used out of the box, including device drivers, libraries, low- and high-level software, visualizers and more. --><br />
* '''C++''': is the programming language we will be using. This means that your program, or code, will be written in C++.<br />
* '''git''': is a software versioning and revision control system. You will use it to share your project code between different group members, while maintaining a file version history. Think of it as Dropbox.<br />
* '''Qt Creator''': an Integrated Development Environment (IDE) for C++. All you need to create a C++ program is a simple text editor and a C++ compiler. However, it can become difficult to manage large projects, trace back where compile errors are coming from, etc. Think of Qt Creator as a very advanced text editor that understands C++ and makes programming C++ a lot nicer.<br />
<!-- * '''Gazebo''': the robot simulator we will be using to simulate the PICO robot. You will have limited testing time on the real robot, but this simulator will allow you to test your PICO program on your computer. --><br />
<br />
<br />
Alright, let's get our hands dirty. Time to [[Embedded Motion Control/Tutorials/Installing Ubuntu | install Ubuntu on your computer]].</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=26203Embedded Motion Control 20162016-04-20T13:29:51Z<p>Ydouven: /* Course Schedule and Lecture Slides */</p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Helix-Oost, room 4.91. The preliminary course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| Composition Pattern part I by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
To be added...<br />
<br />
= Pico test schedule =<br />
A timetable for testing will soon be available.<br />
<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=File:Emc-2016-04-20-tools-and-infrastructure.pdf&diff=26200File:Emc-2016-04-20-tools-and-infrastructure.pdf2016-04-20T13:21:39Z<p>Ydouven: </p>
<hr />
<div></div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016&diff=26197Embedded Motion Control 20162016-04-20T13:18:40Z<p>Ydouven: </p>
<hr />
<div><div align="center"><br />
<font size="5">Guide towards the assignment</font><br /><br />
<font size="4">'A-MAZE-ING PICO'</font><br />
</div><br />
[[File:Gostai-Jazz-500x500.jpg|center|thumb|350px]]<br />
<br />
----<br />
<br />
= Introduction =<br />
This course is about software design and how to apply this in the context of autonomous robots. The accompanying assignment is about applying this knowledge to a real-life robotics task.<br />
<br />
= Course Schedule and Lecture Slides =<br />
<br />
Lectures will be given on Wednesdays from 15.45 - 16.30 in Gem-Z 3A-12. The course schedule is as follows:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0" align="center" style="margin-left: 3em;"<br />
|-<br />
| width="150" | April 20<br />
| width="325" | Introduction by ''René van de Molengraft''<br />
| width="325" | [[Media:Emc-2016-04-20-tools-and-infrastructure.pdf | Tooling and Infrastructure by ''Yanick Douven'']]<br />
|-<br />
| April 27<br />
| Kings day: no lecture<br />
| <br />
|-<br />
| May 4<br />
| Composition Pattern part I by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| May 11<br />
| First presentation of the design by ''groups'': 6-minute presentation about the group's design in the context of the task-skill-motion system architecture and the composition pattern.<br />
| <br />
|-<br />
| May 18<br />
| '''Corridor competition'''<br />
| Composition Pattern part II by ''Herman Bruyninckx''<br />
|-<br />
| May 25<br />
| Communication patterns by ''Herman Bruyninckx''<br />
| <br />
|-<br />
| June 1<br />
| Presentation of final design by ''groups''<br />
|<br />
|-<br />
| June 8<br />
| colspan="2" | '''Final competition'''<br />
|-<br />
|}<br />
<br />
= Assignment =<br />
Design and implement a robotic software system that will let robots Pico/Taco solve a maze in the robotics lab. The maze can contain doors that automatically open and close.<br />
<br />
= Corridor Competition =<br />
{{:Embedded_Motion_Control/Corridor_competition_2016}}<br />
<br />
= Maze Competition =<br />
{{:Embedded_Motion_Control/Maze_competition_2016}}<br />
<br />
= Getting Started =<br />
<br />
To get started, please do the tutorials on the [[Embedded Motion Control/Tutorials | Tutorial Page]]. Please note:<br />
<br />
* '''Do all tutorials, and all steps. Missing one step may cause a different behavior or incorrect working system later'''. If something is not working as expected, make sure you correctly did all previous steps.<br />
* Of course, things may still go wrong. If so, do not hesitate to contact us.<br />
<br />
* See [[Embedded_Motion_Control/Using_Pico | Using Pico]] for a quick overview of how to use Pico.<br />
<br />
= FAQ =<br />
[[Embedded_Motion_Control_2016/FAQ | Here]] you can find a collection of Frequently Asked Questions. Please check this page before contacting the student assistants or the tutors! If you find any issues or questions you had to deal with, please add them as well so your colleagues don't run into the same problems.<br />
<br />
=Group Wiki Pages=<br />
<br />
To be added...<br />
<br />
= Pico test schedule =<br />
A timetable for testing will soon be available.<br />
<br />
Be sure you have your software on git before coming to the test session so that you only have to git clone/git pull to get your code on the robot!<br />
<br />
Please charge the robot whenever possible so there is no down time due to empty batteries.<br />
<br />
<!--<br />
In order to test your software on the real robot, each group has a number of available time slots. During the second stage test sessions, two robots will be available: Pico and Taco. Taco is a slightly different robot, but if your software works well on Taco, it will also work on Pico. The difference is that Taco's base is non-holonomic. This means that you cannot give it a velocity command in the y-direction (sideways), only in x and theta. So if your software relies on giving velocity commands in y-direction, you might just want to choose for testing on Pico (or change your software); if you only give x and theta commands, you can also test on Taco, doubling the available time slots!<br />
--><br />
<br />
= Group Final Presentations =<br />
<br />
To be added...<br />
<br />
=Contact Details=<br />
{{:Embedded_Motion_Control_2016/Contact_Details}}</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control_2016/FAQ&diff=26195Embedded Motion Control 2016/FAQ2016-04-20T13:18:13Z<p>Ydouven: Created page with 'When you ran into a problem, try to find the solution here first. If it's not here, try to find an answer by googling your problem, asking fellow students, or, as a very last res…'</p>
<hr />
<div>When you ran into a problem, try to find the solution here first. If it's not here, try to find an answer by googling your problem, asking fellow students, or, as a very last resort, ask your tutor! If you found a solution, please put it here such that others can use it! Try to be as consise yet descriptive as possible, and try to file your Problem-Solution pair under the correct category (or add a new category if necessary).<br />
<br />
== Example ==<br />
<br />
Just as an example! Please remove this section if you're the first to add a Problem-Solution pair!<br />
<br />
=== My computer is on fire. Is this a bad thing? ===<br />
<br />
Nah, probably not, the fire will soon die out. Be sure though to commit all your changes to git! Just in case...<br />
<br />
== Ubuntu ==<br />
<br />
<br />
=== My laptop is stuck on maximum brightness ===<br />
<br />
Open your Terminal. Type<br />
<br />
sudo gedit /usr/share/X11/xorg.conf.d/20-intel.conf<br />
<br />
A text editor will open. Add the following content<br />
<br />
Section "Device"<br />
Identifier "card0"<br />
Driver "intel"<br />
Option "Backlight" "intel_backlight"<br />
BusID "PCI:0:2:0"<br />
EndSection<br />
<br />
Log out and back in. You can now use the brightness controls on your keyboard to change the brightness.<br />
<br />
== C++ ==<br />
<br />
Everything related to the programming language<br />
<br />
== Version control (git) ==<br />
<br />
Everything related to version control using git<br />
<br />
== PICO ==<br />
<br />
Everything related to PICO<br />
<br />
== Qt Creator ==<br />
<br />
=== My program is not building and running within Qt Creator ===<br />
<br />
When building the program does not work in Qt creator, but does work in the terminal, the following may fix the problem.<br />
<br />
When your project is open, click 'Projects' on the left task bar. Scroll down to 'Build Environment', and expand it (click Details). Now, all the way to the bottom right, click 'Batch Edit'.<br />
<br />
Next, open your terminal (ctrl+alt+t), and type<br />
<br />
printenv<br />
<br />
Select the entire output (you probably only need a few relevant variables, but I can be bothered to check which), and copy (ctrl+shift+c). Paste the entire output in your QT creator Batch Edit window, and click OK. Building with CTRL+B should work now!</div>Ydouvenhttps://cstwiki.wtb.tue.nl/index.php?title=Embedded_Motion_Control/Tutorials&diff=26188Embedded Motion Control/Tutorials2016-04-20T13:14:10Z<p>Ydouven: Redirected page to Embedded Motion Control/Tutorials 2016</p>
<hr />
<div>#REDIRECT [[Embedded Motion Control/Tutorials 2016]]</div>Ydouven