Question:
- Using the map you just created the aim of this task is to set the robots position anywhere In the bounding box, the robot should next wander randomly in the environment, if the robot sees a wall then it should follow the wall in a determined direction.
- From the statement above you will see two sub-tasks, so you could break up your code into two sections. You’ll need to make a way for the robot to transition from one task to the other.
- Breaking up the tasks:
o Random wander:
▪ Consider the random distance to travel in a straight line,
▪ Consider the random angle to turn to, and which random direction
▪ In V-REP you cannot tell the robot how far to travel or how much to turn by so you will need to devise a way to allow the robot to travel randomly
o Transitioning to a task
o Wall following:
▪ You could move forward at a constant rate
▪ Measure the distance between the robot and the wall using one of the sensors to the side.
▪ Set a threshold – or distance – away from the wall that the robot has to follow
▪ If the robot travels away from the line, adjust its speed of the wheels accordingly (robot travels too far to the left, adjust the speed to rotate right)
- Remember, plotting the position data will be useful in your reports.
- Test different parameters or your own programming experiments to enhance:
o Making the path smoother and avoiding near misses
o Wasting less time in overshooting correction actions (e.g observe what happens at the turnings in the top tips of the vertical walls)
o Is there any better methods of randomly wandering?
REPORT:
- There is no limit on the number of pages, however, 2 sides should be adequent to introduce the task, what you did and the results and conclusions.
- You must submit your code and the end of the report as a appendix. Failure to do so may mean losing marks from the Design and Implementation criteria of the marking sheet.
- Each Lab handout will have specific instructions on what is the main purpose, which is what should guide your report content.
- You need to submit your own code your own reflections, so that is why we ask not to share code via the Discussion Board.
- You need to present your own experience and analysis of your experiments and results.
- The most important part is that you need to write what you HAVE LEARNED by doing this lab (I already know what you are supposed to do!)
- It is very important to draw and present your own conclusions.
- Take into account that the mark for your work will be given through the report, which should present appropriately your work, therefore it is not enough to just do the exercises (or in the case of the second assignment, develop your solution) and dump some results. You need to present your work appropriately.
- You have a few sources of information to base how your reports should be structured. The first one should be your generic knowledge on how to write reports, this is included here:
o Every report has to have an introduction and present your own interpretation of the problem. So do not just paste the brief’s text, you need to write the interpretation of the problem in your own words.
o For larger projects, you need to provide support for your decisions, previous knowledge and statements, which is achieved through a literature review or suitable background section.
o Then you need to present your methodology which includes detailing your chosen alternative(s) approach to solve the problem (if available/applicable) and your experimental setup, development, etc.
o Once you have developed and tested your solution you need to present your results and analyse/discuss them. Depending on the size of the project and report this can
involve a section on results and a section on discussion. For a small lab report and coursework report, a single section on analysis of results should do.
o Finally, no report will be complete without an explicit conclusion. The conclusions are NOT a summary of results or objectives achieved (that goes in the section above, analysis of results). The conclusion should be your own reflection on what you have learned by developing the whole project, including lessons on what could have been done better, differently and in the future.
- Some additional recommendations:
o Even if you have limited results (not as good as what you expected or were required to achieve) the conclusions/reflection that you present in the report can still can still be good and this can allow you to achieve a higher mark than good results alone. Particularly for academic reports, in which the most important issue is what you learned, rather than what you achieved.
o So you can demonstrate this through an excellent reflection on the work carried out during the attempt (note: this is NOT an explanation of why you could not dosomething, such as running out of time). If you did achieve something but it did not work as expected, if you can explain why it did not work and how could it be done better if attempted again, then again you can get good credit for this.
