General info

  • 2 projects. Count for 40% of the final grade.

    • Each project report will be graded (0-100 score), and the two scores combined (with equal weight) into one grade.
  • 1 compulsory exercises. (Approved if score > 60%)
  • More non-compulsory exercises (not to be handed in), but we assume that you do them, and similar problems can be given on the exam.
  • Some hints/partial solutions will be posted afterwards depending on the capacity of the course team (theory part).
  • OBS: To take the exam, you need one approved compulsory exercises and at least one approved project (passing grade needed).

Groups for projects and compulsory exercise

  • You work in groups of up to 3 students.

    • Send an email to Alessandro with the group members in your group (in English please).
    • If you don't have a group, send an email, and you will be assigned to a group.

Submissions and requirements

  • Submit (i) reports/solutions in PDF format, and (ii) your Python code in a Jupyther notebook in ovsys. Use a zip-file to submit the two files.

  • Compulsory exercises: Handwritten solutions are sufficient, no report format required. Must be readable and in English. Plots can be given in the jupyther notebook.

  • Project reports: Write as scientific reports. Describe the problem and the methods you are using, write theoretical results as mathematical statements, use (readable!!) plots and tables of errors when appropriate, explain your observations, and if they are expected. Theoretical and numerical results should be consistent.

    • Max length: 7 pages without appendices, text-size 11pt.
       
    • If you need more pages, you can put some plots/figures an appendix.
      (You may include other appendices, but me may not read them.)

  • The code: The Jupyter notebook should run/compile without errors.

  • Grading of projects: Based on the report only. The notebook is to verify that you did actually code what you claim you did.

Tentative Plan:

Deadlines may be changed. Input is welcome!

Week Exercises/project Deadline Comments
3 Exercise 1 - (Partial) solutions: Exercise 1 sol
4-5 Exercise 2 - (Partial) solutions:
forward_euler_code
backward_euler_code
crank_nicholson_code
5-6 Exercise 3 Sunday 12.02. 23:59 Updated version (10.02) with clarifications
6-8 Project 1 Sunday 26.02. 23:59 Small update 14/02. The right hand side is now called \(f\) instead of \(h\) to avoid confusion with the space-step.
8-9 Exercise 4 - (Theoretical) solutions: Exercise 4 theory
10-12 Project 2 Sunday 26.03. 23:59
13-15 Exercise 5 - Additional jupyter notebook: Poisson2D_FEM.
Partial solutions (Exercise 2): SOR_Poisson

Supervision:

Dates Times/Rooms Assistants
Exercise 3 30.01 - 12.02. Friday 03.02.
Thursday 09.02.
Friday 10.02.
08:15-10:00 in R4
14:15-18:00 in KJL4
08:15-10:00 in R4

A+B+C
A(14-16)+B+C
A+C
Project 1 06.02 - 26.02. Friday 17.02.
Monday 20.02.
Wednesday 22.02.
Thursday 23.02.
Friday 24.02.
08:15-10:00 in R4
322F, sentralbygg 1
14:15-18:00 in 265 SB1
14:15-18:00 in EL4
08:15-10:00 in R4

A+B+C
C
A(14-16)+C
B
A(zoom)+B
Project 2 27.02 - 26.03. Friday 17.03.
Monday 20.03.
Wednesday 22.03.
Thursday 23.03.
Friday 24.03.
08:15-10:00 in R4
14:15-16:00 in KJL22
16:15-18:00 in Smia SB2
14:15-18:00 in H2
08:15-10:00 in R4

B+C
A
B
A(14-16)+B+C
A+C
2024-04-04, Espen Robstad Jakobsen