Merge branch '2024-setup' into 'main'

more

See merge request !7

assignments.md

----
-layout: page
-title: Assignments
-description: Types of assignments, graded and not graded.
-nav_order: 5
-nav_exclude: false
----
-
-# Assignments
-
-**Assignments** is a generic term for the set of regularly-schedule activities that we provide each week. There are two types of assignments that you are must submit for feedback, and contribute to your Project Portfolio grade:
-- Programming Assignments (PA)
-- Projects (P): described on [this page](../projects)
-
-Both types of assignments will be submitted using GitLab; feedback will also be provided using GitLab. More instructions on the procedure for doing this will be provided in week 3. The assignment instructions and solutions will be provided via this course website, but any data or specialty code that is required for the assignments, will be provided via GitLab.
-
-In addition to Programming Assignments and Projects, other types of non-graded assignments may be provided each week to help you study the material: **Workshops** (WS) are for the in-class activities on Wednesday, whereas any other assignments for doing outside of class time will be called **homework** (HW). These are all optional (but encouraged!).
-
-## Programming Assignments (PA)
-
-A Programming Assignment is provided each week to introduce a few relevant concepts that are expected to be applied directly in the project for that week. For the first two weeks these are not submitted for feedback, however, starting in week 3 the programming assignments will begin and collectively make up 20% of the project portfolio (i.e., 10% of the total MUDE grade). Programming Assignments are automatically graded after submitting them to GitLab and are assessed on a pass/no pass basis. You may resubmit as many times as needed to pass the assignment before the deadline at the end of each quarter.
-
-We will use a _static check_ to evaluate your work on a regular basis. This involves the teaching team making a clone of your repository and checking to see if you have met a few basic requirements. For example, did you use the right file name, and does your notebook run without error? These criteria will be specified for each assignment, and if you did not meet the criteria, you will get a report in a `static_check.md` file notifying you of any issues. We will make every attempt to run the static checks for the Programming Assignments every Monday, Wednesday and Friday at 8:45; however, depending on personnel, the times will be somewhat irregular. For practical purposes, you can assume that if your assignment is ready by 8:45 on Monday, Wednesday or Friday it will be checked by the end of the day.
-
-All Programming Assignments for a given quarter will be checked on Monday, Wednesday and Friday, until the last check of the quarter, which will be the **Monday of week 9**. At this point, you will get full credit (2.5 pts) for all Programming Assignments that have passed the static check. See the point breakdown on the [Project page](../projects) for how the Programming Assignments are included in the Project Portfolio.
-
-**Note about deadlines:** the times specified for the static are the _earliest_ time at which we will collect your work; it is your responsibility to make sure that your work is pushed to GitLab by this time, or you risk the chance of it not being checked until the next run. If you have made changes to your repository and the feedback in the static check file does not make sense, make sure you look at the time and day when it was run last, to see if your updates were actually taken into account.
-
-## Projects (P)
-
-Described on the [Project page](../projects).
\ No newline at end of file

multiyear.md

@@ -7,7 +7,11 @@ nav_exclude: false
 # math: mathjax
 ---
 
-# Students from Previous Years
+# Multiyear Students (Students from Previous Years)
+
+This page gives advice on how to pass the Exam or Portfolio assessment for MUDE for students that have not completed all assessments for the entire module. For an overview of changes to the technical content in previous years, see the [Exams page](../exams).
+
+If you are a student from a previous year, please inform MUDE staff of your situation and plan for completing the module by the start of each quarter. We will do our best to find ways to help you study the material and pass the exam and/or portfolio.
 
 ## Exams
 
@@ -15,4 +19,14 @@ Students resitting the exam from previous years of MUDE are expected to write th
 
 It is also recommended that you follow activities, such as the workshops (WS) on Wednesday's, the Group Assignments (GA) on Friday's, and the weekly Programming Assignments (PA) as these are meant to help learn topics covered for the exam.
 
-Please talk to an instructor if you would like to find other students from previous years to work with. Unless you can commit to following the entire module as a "normal" student from this year, it is not possible to put you in a group with current students.
\ No newline at end of file
+Please talk to an instructor if you would like to find other students from previous years to work with. Unless you can commit to following the entire module as a "normal" student from this year, it is not possible to put you in a group with current students.
+
+## Portfolio
+
+The _Project Portfolio_ from the 2022-2023 and 2023-2024 academic years is now called the _Assignment Portfolio_, due to the transition to a weekly assignment that is turned in every Friday (now called the _Group Assignment_).
+
+If you completed the projects from previous years and recieved passing grades for the projects in an entire quarter, you do not need to repeat that quarter. Once you complete the remaining quarter, a composite grade will be computed using the grading rules for each year where the assignments were completed.
+
+If you only completed (or passed) part of the project assignments from a previous year, you must repeat the present year portfolio assignments for that quarter.
+
+Students from previous years that must finish the portfolio assignments from this year must also complete the programming assignments. BuddyChecks are not required if you complete the assignments individually (but we recommend you work with a group, if possible!). Please consult MUDE staff to arrange this. 
\ No newline at end of file

assignments_group.md → portfolio.md

 ---
 layout: page
-title: Group Assignments
-description: Overview of Group Assignments and policies for report writing, directory structure and code documentation.
+title: Assignment Portfolio
+description: Overview of Assignment Portfolio (particularly the Group Assignments) and policies for report writing, directory structure and code documentation.
 nav_order: 6
 nav_exclude: false
-permalink: /group_assignments/
+permalink: /portfolio/
 # math: mathjax
 ---
 # Group Assignments
@@ -16,6 +16,39 @@ Group Assignments consist of the following elements:
 2. BuddyCheck, a weekly questionnaire administered via Brightspace to evaluate yourself and your group members.
 3. Weekly reflections to improve the performance of your group and keep issues from becoming serious; recommended to occur at the beginning of the Wednesday in-class sessions, but this can be flexible.  
 
+
+
+
+
+
+## Programming Assignments (PA)
+
+A Programming Assignment is provided each week to introduce a few relevant concepts that are expected to be applied directly in the Group Assignment for that week. Programming Assignments are automatically graded after submitting them to GitLab and are assessed on a pass/no pass basis. You may resubmit as many times as needed to pass the assignment before the deadline at the end of each quarter (see the [Assignment Portfolio page](../portfolio) for deadlines).
+
+You do not have to submit PA 1.1 and 1.2.
+
+<!-- We will use a _static check_ to evaluate your work on a regular basis. This involves the teaching team making a clone of your repository and checking to see if you have met a few basic requirements. For example, did you use the right file name, and does your notebook run without error? These criteria will be specified for each assignment, and if you did not meet the criteria, you will get a report in a `static_check.md` file notifying you of any issues. We will make every attempt to run the static checks for the Programming Assignments every Monday, Wednesday and Friday at 8:45; however, depending on personnel, the times will be somewhat irregular. For practical purposes, you can assume that if your assignment is ready by 8:45 on Monday, Wednesday or Friday it will be checked by the end of the day. -->
+
+<!-- All Programming Assignments for a given quarter will be checked on Monday, Wednesday and Friday, until the last check of the quarter, which will be the **Monday of week 9**. At this point, you will get full credit (2.5 pts) for all Programming Assignments that have passed the static check. See the point breakdown on the [Project page](../projects) for how the Programming Assignments are included in the Project Portfolio. -->
+
+<!-- **Note about deadlines:** the times specified for the static are the _earliest_ time at which we will collect your work; it is your responsibility to make sure that your work is pushed to GitLab by this time, or you risk the chance of it not being checked until the next run. If you have made changes to your repository and the feedback in the static check file does not make sense, make sure you look at the time and day when it was run last, to see if your updates were actually taken into account. -->
+
+## Projects (P)
+
+Described on the [Project page](../projects).
+
+
+### Assignment Portfolio
+
+The Assignment Portfolio consists of three parts:
+- Group Assignments (80%) and Programming Assignments (20%). Note that the BuddyChecks are also required and make up 10% of the Group Assignments (10% overall MUDE grade). The ultimate deadline to submit all of the components of the Assignment Portfolio is the last Friday of instruction for the quarter (week 8) at 12:30 (the end of the last Friday classroom session). Please note, however, that a consistent weekly schedule has been incorporated into the course activities, in particular: bi-weekly feedback on the Group Assignment reports and weekly grading of the Programming Assignments. In addition, failure to cooperate with your group members may result in the requirement that you submit the Group Assignments individually. Please see the relevant pages on this website for further details.
+
+
+
+
+
+
+
 ## Assessment
 
 Each project is assessed on four categories using a discrete set of numeric criteria (4) for each, described in the sections below, with the total grade computed as a weighted sum. Every project receives equal weight, except Project 1, which is not included in the grade. 

shedule.md

@@ -13,8 +13,37 @@ It is relatively easy to update the events, their timings, or their locations, b
 
 ## Weekly Schedule
 
-Below you can find an example outline of the typical weekly course schedule. One exception is Week 1 of Q1, which starts on a Tuesday.
+Below you can find an outline of the weekly schedule for Weeks 1.1-1.8 and 2.1-2.8. In addition, the first lecture (Week 1 of Q1), on a Tuesday, is an exception.
 
-**INSERT IMAGE HERE**
+![weekly schedule](../assets/figures/week.png){:width="800px"}
 
-## Overview of Topics
\ No newline at end of file
+## Overview of Topics
+
+Quarter 1: 
+- **Week 1.1**: Landing zone / Introduction to modelling
+- **Week 1.2**: Uncertainty Propagation
+- **Week 1.3**: Observation Theory, Part 1
+- **Week 1.4**: Observation Theory, Part 2
+- **Week 1.5**: Numerical Analysis, Part 1, Numerical Analysis Techniques
+- **Week 1.6**: Numerical Analysis, Part 2, Finite Difference Method
+- **Week 1.7**: Continuous (univariate) Distributions
+- **Week 1.8**: Multivariate Distributions
+
+Quarter 2:
+- **Week 2.1**: Finite Volume Method
+- **Week 2.2**: Finite Element Method
+- **Week 2.3**: Signal Processing
+- **Week 2.4**: Time Series Analysis
+- **Week 2.5**: Optimization
+- **Week 2.6**: Machine Learning
+- Holiday Break (2 weeks)
+- **Week 2.7**: Extreme Value Analysis
+- **Week 2.8**: Risk and Reliability
+
+**Exams** are typically scheduled as follows:
+- Q1 Exam: Monday of Week 1.10
+- Q2 Exam: Thursday of Week 2.9
+- Q1 Resit: Wednesday of Week 2.10
+- Q2 Resit: Monday of Week 3.10
+
+Tuesday Question Hours (10:45-12:30) are additionally scheduled during Weeks 1.9, 2.9, 2.10 and 3.9 for exam review.
\ No newline at end of file