ASSIGNMENTS:The assignments will be based on the homeworks assigned for each lecture and posted in the coverage. Make sure to do these when they are posted, otherwise there will not be enough time for you to get any potential questions answered!
- Due Tuesday, February 24th.
- Please bring your code/assignments to class. Assignments will be collected first thing and code will be checked by TA throughout the class. You may also be asked specific questions etc about the code, and to run all/parts of the code as well.
- OFFICE HOURS: I will have office hours on Tuesday, February 17th in case you have any questions (from 10-11 am).
- SOLUTIONS: [PDF][R script 1][R script 2]
- April 7th (by vote and no descending opinions)
- The test will cover everything we have done in the class up until roughly a week before the date of the test. You will not be asked about R code, but you may be asked about various algorithms, or to describe routines via pseudo-code. Please note that "theoretical" practice problems have also been posted throughout the term.
- Coverage for the test will go up to and including the March 26th lecture where the bootstrap was introduced.
- We will write the test in the Gauss Lab.
Overview:More details will be posted as we go along.
- IMPORTANT: for those of you that are taking MATH4090 concurrently, make sure that your projects are different for the two courses! We will check!
- Groups and topics are due on Thursday, February 12th.
- A 3-5 page proposal is due on Tuesday, March 3rd. This proposal should provide a well-researched problem and solution, along with a detailed plan of the simulations you plan on carrying out.
- A revised version of the proposal is due on Thursday, March 26th. The reason that I am doing this is that I felt you needed more guidance from your first proposal before proceeding with the project. Please provide more information on your models, simulations, parameters of your simulations - etc. See the specific comments I made, or visit me during office hours, for additional information.
- The final project will be due on Thursday, April 30th. On this day
we will hold the presentations (each should be about 20 minutes in
length). The presentations will be held in Ross N638 starting
at 9:45am. There will be 7 presentations, so we should be done
before 1pm (allowing for breaks and changes between presentations). The
order of the presentations will be revealed the day
of. Please note that you are
expected to be present for the entire duration of the presentations.
Bring your presentation on a USB stick, please. PDF format would work
best. You should
also provide me with (via email prior to the start of the presentations):
- project write-up in pdf format (15-20 pages, inclusive)
- your annotated code for grading
- a brief statement from all members of the group about the split of the workload among the group members
- Proposal - 5%
- Presentation - 25%. Part of the presentation grade will come from averaging peer-evaluations. A rubric will be provided for you the day of.
- Project - 70% [grading rubric]. The write-up should be about 15-20 pages in length (inclusive of figures and references). The write-up will be graded based on the rubric. In terms of the quality of presentation, imagine explaining your work to a non-expert - I should be able to write your simulation code with only the information provided in your write up!