home > undergraduate > Robotics  > Robotics Homepage

Robotics (231.315) 6 points / Semester 2 Handbook Description The official handbook entry for Robotics 315 from the Faculty of Engineering, Computing and Mathematics Unit Aims The aim of this course is to provide knowledge in the basic science and engineering and robotics, particularly from the perspective of the programmer. Students will gain in-depth technical competence in robot manipulators in particular, with knowledge of kinematics, simulation and animation. They will develop the generic attributes to undertake problem identification, formulation, and solution within this domain, as well as their ability to communicate effectively through technical documentation. Teaching Staff Lecturer Angeline Loh and Nick Lowe Teaching Assistants N/A Email help315@csse.uwa.edu.au Textbook There is no prescribed text as all the books are either very expensive or inappropriate. The lectures will follow a traditional method of delivery, namely a verbal presentation and hand written "overhead" notes. A copy of the text used for the overheads s available from the departmental secretary for a short loan, long enough for you to photocopy the contents. However students are strongly encouraged to attend lectures as the presentation will occasionally take additional paths and involve deeper discussion to that defined in the notes. Recommended Reading To provide some reference material the following books will be kept in the MPSL closed reserve: "Introduction to Robotics" by Phillip McKerrow "Robot Manipulators: Mathematics, Programming and Control" by Richard Paul. "Introduction to Robotics: Mechanics and Control" by John Craig. Contact Hours With regards to formal contact hours, you will be required to attend 26 hours of lectures and 39 hours of laboratory work. To complete the work in this unit you are expected to work out of hours. A total of 10 hours of effort per week on average (including formal contact time) would be usual. Type Time Day Location Lecture 3-4.45 Tue Geography Lecture Theatre 1 Lab1 2-5 Wed CS-Lab 2.01 Lab2 10-1 Fri CS-Lab 2.01 Assessment The assessment for Robotics 315 comprises a portfolio of laboratory assignments (worth 40%), and a final 2hr examination held in November (60%). The laboratory work tests technical competence in robotics, simulation, animation and programming skills. Students must demonstrate their capacity to identify problems and formulate solutions to specified standards. The project component must also demonstrate an ability to communicate effectively in the area of Web-based technical documentation. You will be required to progressively submit various examples of your laboratory exercises. These will not be marked but kept as a record of your developing portfolio. Only the final and completed portfolio will be assessed. The dates of these submissions will be fixed later in the semester. Assessment % of final mark Assessment Dates Final Portfolio: 40 Wednesday (week 11) Examination 60 November Exam Period Unsatisfactory Progress Any student who does not demonstrate satisfactory progress in this unit, as defined in the FECM Policy on Assessment Practices and Procedures, may be refused admission to the final examinations. The final deadline for notification of unsatisfactory progress is the last day of Week 10. Penalties The School of Computer Science and Software Engineering has adopted a policy on minimum penalties for late items of assessment. This is the default policy of all units unless indicated otherwise, in writing, by the specific unit coordinator. This policy shall apply to all items of continuous assessment, whether submitted either physically or electronically. Immediately after the submission deadline for an item of continuous assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF. The minimum mark possible for late submission is zero. The percentage is based on the item´s total contribution to the unit´s assessment. For example, a project contributing 40% to the unit´s assessment will incur a penalty of 8 marks for each day late until it is submitted or a mark of zero results. A more detailed description is given in this School´s Policy on Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals. Plagiarism Plagiarism is broadly defined to be when any portion of the work presented for assessment, can be attributed to another party. The student making the submission should acknowledge what aspects of the presented work is not directly derived by them. For the purposes of plagiarism it is irrelevant that you have been given permission by someone to copy their work and present it as your own. You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism. Faculty Scaling Final assessment is subject to the Faculty Scaling Policy.     home > undergraduate > Robotics  > Robotics Homepage    This information is correct as at 20-Jul-2004, but is subject to change from time to time. In particular, The University reserves the right to change the content and/or method of presentation and/or the method of assessment of any unit of study, to withdraw any unit of study or programme, and/or to vary arrangements for any programme. Copyright© 2004 School of Computer Science, & Software Engineering The University of Western Australia CRICOS Provider Code: 00126G Last updated: 20-Jul-2004