CS486/CS686 Course Project
- Required for graduate students
enrolled in CS686 and optional for undergraduate students enrolled in
CS486
- Pick an application domain that interests you
- Identify a problem in that application domain
- Analyze or develop artificial intelligence techniques to
tackle this problem
- (optional for CS486) Implement and evaluate empirically some of those
techniques
- Undergraduate students can form teams of up to 3 people, but
graduate students must do the project by themselves.
- Special notes for team projects (CS486 only):
- must be substantially more involved than individual projects,
- each team members contributions to the reserach project must be clearly and specifically described in both the proposal and report!
- there must be more papers referenced and discussed for team projects (see below)
Proposal (no mark)
Only students who have submitted a proposal following the stipulations below will be allowed to submit a final project.
- Submit before the Midterm
- One page of text + references
- Any format is acceptable (must be readable!)
- Name of student (or team members if undergraduate group project)
- Group projects (CS486 only) MUST specify what each team member is going to do for the full project (not what they did on the proposal)
- What is the application domain? Why is it interesting? Why is it hard? What are the challenges?
- What is the problem you plan to tackle? Has this been tried before? What are the challenges? What data will you use?
- What artificial intelligence techniques do you plan to develop
or analyze? Explain why these techniques are appropriate for the problem you are tackling.
- Reference and describe in the text (CS686: at least 10, CS486: at least 5, add 3 for each additional group member) papers that you plan to survey concerning this problem.
- Hand in on LEARN (in the project proposal dropbox) in PDF only prior to the midterm exam
Report (30% of final mark for CS686 and 5% bonus for CS486)
For CS486:
- 2 pages (add 2 pages for each additional group member from groups - i.e. a group of 3 people would be expected to deliver a 6-page report)
- any pages beyond first 2 will not be read/considered
- At least 5 references (add 3 references for each additional group member)
- Projects must be formatted according to the IEEE Templates for conference proceedings.
- Group projects (CS486 only) MUST specify what each team member's contributions are.
- Hand in on LEARN (in the project report dropbox) in PDF only prior to the final exam
For CS686:
- 7 pages not including all figures, tables and references. No appendices.
- Any pages beyond first 7 will not be read/considered
- At least 15 references
- Literature reviews will not be accepted. The project must be an implemented working system, a user study, a data analysis or replication of a previous result, or a new model or theory.
- Projects must be formatted according to the IEEE Templates for conference proceedings.
- Materials submitted in anything other than PDF, or with any incorrect formatting, will be rejected without evaluation.
- Hand in on LEARN (in the project report dropbox) in PDF only prior to the final exam
Ethical Approval
Important: If your plan to involve human participants in your project (e.g. do a survey, test an instrument), you must get ethical approval, and you must start this process immediately as it can take six weeks or more. See Office of Research Ethics and in particular this page for details. I don't have a blanket ethics procedure for the course, as projects are too varied to allow for that, so each student or group is responsible for their own ethics applications if needed.
Evaluation (CS486 students)
The project reports will be evaluated on three main criteria, with weights as shown.
These are used as guidelines for the instructor when evaluating the work. To get full marks, undergraduate student projects should be clearly written, easily understandable, and demonstrate the students have closely examined and analyzed the problem. Group projects will be expected to be proportionally more involved. A group must indicate in their final report who is reponsible for which parts.
- Completeness (50%): does the report state contributions, claims, assumptions, strengths and weaknesses? Does the report have an abstract that clearly defines the work and results? Does the report give a complete overview of the methods used? Does the report provide a discussion that appropriately summarises the work? Is there a conclusion that adequately summarises the work, including the main claims and results? Are there sufficient references?
- Clarity (40%): is the report clear, readable, and free of spelling and grammar errors, and presented using the required format? Does the report respect the integrity guidelines? If a group project, are the contributions of all group members clearly indicated?
- References (10%): are the references correctly formatted, complete (e.g. including page numbers, book titles, years, etc), and are the guidelines for citing wikipedia and other online content respected (see below)?
Evaluation (CS686 students)
The project reports will be evaluated on four main criteria, with weights as shown.
These are used as guidelines for the instructor when evaluating the work. To get full marks, graduate student projects to be of sufficient quality that they could be submitted for publication (at least at a AAAI Workshop or Symposium) with only a small amount of additional work.
- Completeness (50%): does the report state contributions, claims, assumptions, strengths and weaknesses? Does the report have an abstract that clearly defines the work and results? Does the report give a complete overview of the methods and data used? Does the report provide a discussion that appropriately summarises the work? Are there experimental or theoretical results to back up the claims? Is there a conclusion that adequately summarises the work, including the main claims and results? Are there sufficient references?
- Clarity (30%): is the report clear, readable, and free of spelling and grammar errors, and presented using the required format? Are figures properly captioned with sufficient information to explain the figure? Are all figures properly referenced and discussed in the text? Does the report respect the integrity guidelines?
- References (10%): are the references correctly formatted, complete (e.g. including page numbers, book titles, years, etc), and are the guidelines for citing wikipedia and other online content respected (see below)?
- Originality (10%): does the report uncover something novel? You do not need to invent time-travel to get this extra 10%! An original take on an old problem, or an original problem statement can be sufficient. Clearly state in your report what is novel about your work!
Suggested Structure for the Report
- Introduction
- What is the application domain?
- What is the problem?
- Techniques to tackle the problem
- brief survey of previous work concerning this problem (i.e.,
the 6-10 papers that you read)
- brief description of any other relevant technique
- Analysis of techniques
- Comparison: advantages/disadvantages, scalability, ease of
use,
etc.
- (Optional for cs486) report on your empirical evaluation
- Conclusion:
- What is the best technique?
- Can we solve the problem today?
- What future research do you recommend?
Academic Integrity
All submitted work (assignments and project reports) should be the submitting student's own work, and should bear his/her name as author.
Any evidence of writing from a different person or source will be considered plagiarism and will be dealt with as such (see University policy below). A few simple rules may help you here:
- ALWAYS write your own submitted work.
- CLEARLY indicate contributions from anyone else: enclose the text in "quotations" and CLEARLY indicate the source right next to the text. Just citing the work that you are quoting from at the end in the bibliography is NOT sufficient. Rule 2 must be applied IMMEDIATELY upon putting any text or image that is not your own into your document. Don't wait, you'll regret it later when you submit your work but have forgotten to go back and put in the citation.
- DON'T cut and paste.
- If you do cut and paste (remember: don't cut and paste - see rule 3), then apply rule 2 IMMEDIATELY.
- DON'T cite Wikipedia or other publicly generated web content. Read about citing Wikipedia or other web content.
Citations
Citations are an important part of any scientific writing. They put your work in context, and show its relationship to other work. A big part of the power of a citation comes from its trustworthiness: the source is such that you have good reason to believe that a group of professional scientists has read and evaluated the paper, and so it contains mostly valid scientific results (although they may have made a mistake, but then it is up to you to find it!).
If you are talking about someone else's work, then you put a reference (properly formatted) to the work in a bibliographic section at the end of your paper, and cite the reference after you have discussed the work:
Carroll's use of poetry is an important part of his work, as it contextualizes and motivates the compositional aspects of the work (Carroll, 1871).
However, if you are directly quoting someone else's work (do this very sparingly), then you need to enclose the text you are quoting in quotation marks, and put the reference, with a page number, immediately after the text you are quoting.
The poem opens with the line: "The sun was shining on the sea" (Carroll, 1871, p.72).
And, then, at the end of the document, you list the full reference.
Carroll, Lewis. Through the Looking Glass and What Alice Found There. MacMillan, 1871.
The actual format of the references will change depending on the journal or conference you are writing for. If you are using LaTeX, then you can simply change the bibliography style, see here for a guide to LaTeX sytles. If you're using Word™, then I question your sanity but nevertheless wish you the best of luck.
Wikipedia (or other publicly generated web content) is not a trustworthy source of information. Wikipedia entries can be generated by anyone, and may be left un-checked for months or years. Any references to Wikipedia in your submitted coursework for CS886 will not be considered valid, and significant marks will be deducted. However, you may use Wikipedia to seek the original references, and cite those instead.
The only exception to the "don't cite Wikipedia" rule is if the content you are citing is specifically about Wikipedia itself. e.g. "In my research on the trustworthiness of Wikipedia, I found that there was a significant error on the page about affective computing (reference to webpage and date of access)". In such cases, you must include the date that you accessed the content on and the exact URL.
Citations to works that are online only (not in print) are perfectly fine, but must include a journal name, volume number, and other relevant citation material, and/or a digital object identifier (DOI). You can also cite a web page from a well-established organisation, but you should include as much reference material as possible, e.g. an ISBN number or DOI.
Wikipedia itself has a good page about citing Wikipedia.