Computer, Engineering and Media – Coursework Brief 2018/19

Module name: Introduction to CI and Control Systems

Module code: IMAT2801
Title of the Assignment: Vehicle scheduling and control
This coursework item is: (delete as appropriate) Summative Formative
This summative coursework will be marked Yes No
anonymously:
The learning outcomes that are assessed by this coursework are:
1. Know the principal areas of Computation Intelligence and how they are related
2. Be able to implement a simple control system and tune it using CI techniques.
This coursework is: (delete as appropriate) Individual Group
This coursework constitutes 100% of the overall module mark.
Date Set: 05 March 2019
Date & Time Due: Friday 26 April at 12.00 NOON (MIDDAY)
Your marked coursework and feedback will be available to you on: Wednesday
If for any reason this is not forthcoming by the due date your module leader will let you 29 May
know why and when it can be expected. The Associate Professor Student Experience (University is
(sCEMstudentexperience@dmu.ac.uk) should be informed of any issues relating closed on 6, 27
to the return of marked coursework and feedback. and 28 May)
Note that you should normally receive feedback on your coursework by no later than
20 University working days after the formal hand-in date, provided that you have
met the submission deadline.
When completed you are required to submit your coursework via:
Submission via Blackboard  Turnitin. See detailed description on next pages.
If you need any support or advice on completing this coursework please visit the Student
Matters tab on the Computing, Engineering and Media Blackboard page.
Late submission of coursework policy: Late submissions will be processed in accordance
with current University regulations which state:“the time period during which a student may submit a
piece of work late without authorisation and have the work capped at 40% [50% at PG level] if passed is
14 calendar days. Work submitted unauthorised more than 14 calendar days after the original
submission date will receive a mark of 0%. These regulations apply to a student’s first attempt at
coursework. Work submitted late without authorisation which constitutes reassessment of a previously
failed piece of coursework will always receive a mark of 0%.”
Academic Offences and Bad Academic Practices:
These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor
referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about what
constitutes an academic offence or bad academic practice you must check with your tutor. Further
information and details of how DSU can support you, if needed, is available at:
http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academic-offences.aspx and
http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/bad-academic-practice.aspx

Tasks to be undertaken: See detailed description on next pages.

Deliverables to be submitted for assessment:
See detailed description on next pages.
How the work will be marked: See marking scheme on next pages.
Module leader/tutor name: Liang Hu
Contact details: Liang.hu@dmu.ac.uk
 Specification
Tasks to be undertaken:
This is an individual assignment. The main CI application that you will consider is
optimisation, and therefore you will need also to apply your skills in modelling and cost
calculations. You will need to design the solution to the problems, implement it and test it
in a program using Matlab.

Instructions:

Download the coursework handout documents and Matlab M files from Blackboard and
extract to the same folder where your lab work is saved. Create you program in M files in
Matlab 2017.

Explanation of the Coursework:

You will consider two tasks in the coursework: 1). the macroscopic logistics schedule of
a number of vehicles among different places; 2). the microscopic vehicle speed control
problem from an optimisation perspective using the CI techniques. A detailed description
of the coursework is provided in the coursework-brief document.

Your Task:
You need to complete two tasks.
1. Given the environmental and vehicle information (see the handout .xslx file), use a
vehicle (unique) per job and find the speed at which each one should travel to
minimise the total amount of fuel used to achieve all tasks. You need to develop a
CI-based program to find: the optimal velocity of each vehicle, the time of
arrival/completion for every job, the amount of fuel used per job, the total amount
of fuel used.
2. Each vehicle is expected to maintain the the optimal speed obtained in task 1.
Given the vehicle model and the PID controller structures codified in Matlab .m
files, you need to tune the PID controller, i.e., tune the three parameters in PID
controllers using GA algorithms such that a good system performance is achieved.

Higher marks will be available for individuals that develop several different solutions using
CI strategies and test them against one another. In task 2, you may add additional codes
in the provided Matlab codes but you may not alter any of the existing functionality that is
NOT ALLOWED TO BE CHANGED AS COMMENTED in the codes. You will be graded
on your report and codes in addition to your technical abilities. These skills will be
invaluable to your future career.
 Deliverables
There are two deliverables for this coursework. A report on your project and the project
codes of the functionality of the program.

REPORT

Your report should be no more than SIX sides of A4 and no more than 2,000 words
(EXCLUDING the title page and appendices) and should explaining how did you tackle
the problem and presenting the design and solution developed by you. It should include
the following for both tasks of the coursework:
• The cost functions
• The approach and configuration of the CI tools used
• A thorough analysis of results
• Your reflection on the work and your own conclusions
• Full code listing in appendix in TEXT FORMAT – NOT PICTURES.

SUBMISSION

For the final submission of your coursework you will need to upload a zipped folder
through TURNITIN. The folder should contain the following:

o A report detailing and explaining the design decisions of your software, level
of functionality achieved and the testing regime used.
o All Matlab codes (in M files) for the projects.
 MARKING SCHEME
0-39% [Fail] 40-49% [Marginal pass] 50-59% [2nd honours] 60-69% [1st honours] 70-100% [First class]

Final Project Submission

Effective use of CI No CI Techniques. Some attempt to include Overall decent CI, but a Good CI, however, a lack of Excellent use of CI. Excellent
Techniques CI Techniques, but lack of originality, or innovation, or integration with integration with the problem
Weight: 15% incomplete generic implementation. the specific problem of each in each task.
implementation. task, prevented obtaining a
higher mark.
Modelling of the cost No use of cost function. Cost function designed for Overall decent modelling Good use of cost functions for Excellent use of cost
functions only one task. of cost functions (one for both task, but limited functions, including effective
each task, implemented justifications and tests of synthesis and reasonable
Weight: 15% effectively) different options of the cost justifications, with discussion
functions. outlined in report.

PID Tuning No tuning or PID controller. Limited tune of PID Overall decent use of CI Good overall use of CI Excellent use of CI
controller, or very techniques to tune PID techniques to fine tune PID techniques to tune PID
Weight: 15% rudimentary use CI controller, but poor overall controller, with some system controller, with immerse
techniques. sense of system performance improvement. discussion on parameters
performance. selections that improve
system performance.

No use of Matlab, or did not Some attempt was made A reasonable use of Overall, a good use of Matlab Excellent use of Matlab Code,
Matlab Code work. to follow the Code Matlab Code, but not Code, attempts at innovation, with an effective use of
examples in Labs, no much understanding but minor consistency issues. comments and high-level of
Weight: 15% comments, or partially outside what was done in innovation.
incomplete code. Labs, or limited
commenting.
Written Report No clear vision or A minor attempt was A reasonable strategy and Overall, a good attempt was Excellent report with good
incorporation with the key made by the student at vision in terms of made, in terms of integrating integration of the key themes
themes of the Lectures. streamlining their work incorporating the key the key themes with the of the Lectures and excellent
Weight: 40% with the objectives set, themes of the Lectures, student’s work and the use of grammar, formatting
but not substantive but lacking cohesion and Lectures, but minor grammar and clarity of expression.
enough. clarity of expression. and/or expression problems.