This page includes information about aim and learning outcomes, teachers, literature, examination and course evaluation. The program for all teaching sessions can be found on a separate page (Course syllabus).

Aim and learning outcomes

The aim and learning outcomes of the course can be found in the course plan.

Changes compared to the last occasion

Major changes from last year are: (i) we now have three written reports to hand in instead of four; (ii) some activities use the Python programming language, this one replacing C.

Teachers

Examiner: Umberto Picchini, picchini@chalmers.se (office H3030)

Lecturers: Annika Lang, annika.lang@chalmers.se (office L2086)

Petter Mostad, mostad@chalmers.se (office H3017)

Umberto Picchini, picchini@chalmers.se (office H3030)

Teaching assistants:

Oskar Allerbo (allerbo@chalmers.se), office L3076

Henrik Imberg (imbergh@chalmers.se), office L3070

Erik Jansson (erikjans@student.chalmers.se)

Filip Wikman (filipwi@chalmers.se), office L2088

Office hours

Students can visit Umberto Picchini's office H3030 on Tuesdays 16.00-17.00 during weeks 37, 38 and 39.

Students can visit Petter Mostad's office H3017 on Tuesdays 15:15 - 17:00 during weeks 40 and 41.

Students can visit Annika Lang's office L2086 on Wednesday, Oct 16, 13.00 - 14.00 and Wednesday, Oct 23, 11.00 - 12.00.

Notice: while you are welcome to visit teachers during office hour, please consider that teaching assistants are available 8 hours each week during computer labs. It is expected that you make use of this opportunity to solve the majority of your doubts concerning course work.

Back to the top

Course literature

Extensive lab introductions are available on the course syllabus page (posted there once the course has started, not before). No additional course literature. A reference book in basic mathematical statistics may be useful, for example Mathematical Statistics and Data Analysis by John A. Rice. References and tutorials for the programming languages can be found on the internet or at a library, but we expect that the provided examples, notes and slides should be enough to get started.

Since this course requires you to experiment with several programming languages, googling for "cheat sheets" can be a good idea to easily find the right commands: for example

a MATLAB/R cheat sheet is at http://mathesaurus.sourceforge.net/octave-r.html
a MATLAB/Python/R cheat sheet: http://mathesaurus.sourceforge.net/matlab-python-xref.pdf
R: there are lots (too many!) resources online to learn about R: here is just a possible one to get started, from Uni. Copenhagen http://r.sund.ku.dk/index.html

Back to the top

Examination

The course is examined by completing the mandatory assignments. There is no written exam.

Deadlines and instructions for handing in

Assignment	Language	Type of examination	Recommended deadline	Final deadline for all assignments: 4 November 23.59
A1	R	answers only	Thur 12 Sep 11.45	4 November 23.59
A2	R + Matlab	LaTeX report	Fri 27 Sep, 23:59	4 November 23.59
A3	R	answers only	Thur 3 Oct 11.45	4 November 23.59
A4	R	LaTeX report	Fri 11 Oct, 23:59	4 November 23.59
A5	Python	answers only	Thur 17 Oct 11.45	4 November 23.59
A6	Python	LaTeX report	Fri 25 Oct, 23:59	4 November 23.59

Assignments 1, 3 and 5:
Only results and answers to the questions are needed. You can pass the exercise either by showing your results and answering the questions to a teacher at the exercise session in the computer room, or (but this is discouraged) by submitting the answers as a short pdf report to Canvas. If you submit a short report, this one should contain your figures and/or tables, brief texts answering the questions and the code you wrote to solve the lab.

Assignments 2, 4 and 6:
Complete, detailed reports written in LaTeX are required. Each student writes his/her individual report. The report should not exceed 10 pages including figures and tables, but excluding the appendix. Important: the report has to be written individually and the same for the computer code. However since you probably collaborate with some other student when attempting the solution of the tasks (e.g. during the labs), you must write the name of the person you have collaborated with on the report cover page. More info will be given during the course.

Submit the report in pdf format to Canvas. The reports will be checked for plagiarism. If you hand in the report before the recommended deadline stated above, you will get the corrections back before the final deadline. In this way you will be able to hand in a return with corrections if you want. You can hand in each report maximum two times (original + return).
Instructions for hand-in of returns: Add a new section in the beginning of your report that informs the reader exactly where the report has been improved. (If your report becomes longer than 10 pages just because of this new section, it is OK). Submit the return via Canvas.

Rules for examination

All solutions and reports are required to be written in English.
Examination is handled by means of 6 mandatory assignments. You may work in pairs during computer labs, however, it is required that each student writes his/her own report and code.
Each project consists of a number of exercises, the completion of which will give you points. The exception is the first, third and fifth assignment, where you will only get the grade "pass" or "not pass", and only answers are needed. The overall grading for the course will be based on the sum of points over all the projects. However, observe that in order to pass you have to complete at least some part of each of the projects (see below).
Written reports are to be handed in on assignments 2, 4 and 6. We strongly recommend you to hand in each report before its recommended deadline (see above), but there is only one "real" deadline: Monday 4 November at 23.59. We will give priority in the correction procedure to the reports that are handed in before the recommended deadlines.
You can hand in each project twice during the course. You can hand in a project partly (e.g. first two questions but not the third) and complete it later (in your return). When we correct the reports, we will give points for things you have done correctly and give comments on what you need to improve/do for getting additional points.
The reports for assignments 2, 4 and 6 are required to be written in LaTeX. See information in the Lectures section at the syllabus page and the Computer labs section below for advice on how to write the report, what to include and how to hand in.
The report for each lab should not be longer than 10 pages including figures, but excluding appendix. Figures and axes labels should be big enough to be readable if printed. It is OK to use colors.
It is also possible to hand in reports after the final deadline, but then they will not be graded until we open up the course for "reexamination period" in January. For students enrolled in TMS150 only: if these hand-ins result in a higher grade, your grade will be changed accordingly in Ladok.

Cheating

You are allow to work in pairs to solve the assignments, but reports and codes should be written individually. How to do this if you work together? Well, avoid situations where one code/write and other just watch. Learn from eachother, but write yourself the code and the report by avoiding copy/pasting. All hand-ins will be checked for plagiarism. It is, for example, not accepted to write the report together and then change words or sentences to make them different. Cheating will be reported to the disciplinary committee of Chalmers/GU.

Number of points given for reports

Assignment	Maximum	Pass
A2	11	6
A4	11	6
A6	8	4

For a given project report, 0.5 points will be deducted if the report is not clearly structured or is otherwise hard to understand. Likewise, 0.5 points will be deducted if the code attached to the report is not properly structured and commented.

Grading

For passing the course you need to have a pass on each of the six assignments, then the grading scheme below applies:

Chalmers:

Grade	Requirement
3	Pass all 6 assignments and have < 21 points in total
4	Pass all 6 assignments and have >= 21 points in total
5	Pass all 6 assignments and have >= 26 points in total

GU:

Grade	Requirement
G	Pass all 6 assignments and have <25 points in total
VG	Pass all 6 assignments and have >= 25 points in total

Back to the top

Computer Labs

Computer labs are in rooms MVF22, MVF24 and MVF25 in the physics building at campus Johanneberg. To use the computers, you will need a Chalmers computer account. Visit the IT helpdesk if you don't have one already link.

The lecture room MVF23 is also booked for computer labs (except Mondays 10-12). Sit there if you work on your own laptop.

If the teachers are busy, write your name on the blackboard in the big room with linux computers and they will come to you. If you are in another room, also write which room. 10-12 the rooms will be more crowded and the wait for help will be longer. Be there at 8 for less waiting time and more space!

To open Rstudio on the linux computers, open a terminal and type rstudio. To open Matlab on the linux computers, open a terminal and type matlab.

Writing: A big part of your work in this course will be spent on writing reports. Being able to express yourself, the methodology and results clearly and concisely is an important skill for all scientists and engineers. This skill is one of the learning goals of this course. Advice on LaTeX and report writing is given here. Examples of report outline can be found under Program at the syllabus page. This will help you in report writing, but it is not necessary to use the provided example structure.

Working on your own computer: You can, of course, work on your own computer. You should be able to download Matlab via Chalmers IT when you have a Chalmers computer account. R is free and can be downloaded from this site, and you can download RStudio from here. Python is easiest installed via Anaconda, where also editors such as Jupyter and Spyder are included. A popular, cloud-based solution for writing with LaTeX is Overleaf. You can register on Overleaf with any email account to get the basic free version. However we recommend that you register with your Chalmers email at Overleaf, to get a free premium account. Alternatively, there are standalone free LaTeX compilers out there, for example MikTeX for Windows and TeX Live for Linux. However, provided you have internet access, Overleaf is recommended.

Back to the top

Course evaluation

At the beginning of the course, at least two student representatives should have been appointed to carry out the course evaluation together with the teachers. The evaluation takes place through conversations between teachers and student representatives during the course and at a meeting after the end of the course when the survey result is discussed and a report is written.

Guidelines for Course evaluation in Chalmers student portal.

Student representatives

The following students have been appointed:

MPPDE	hedvin@student.chalmers.se	Edvin Hansson

TKTEM	viklofg@student.chalmers.se	Viktoria Löfgren

Back to the top

Program

The program can be found on the Course syllabus.

Back to the top