Skip to content
Snippets Groups Projects
Commit 6f2644f9 authored by Robert Lanzafame's avatar Robert Lanzafame
Browse files

Merge branch '2024-setup' into 'main' 

more

See merge request !7
parents 36debeb4 ebcaeda1
No related branches found
No related tags found
2 merge requests!10merge for publish,!7more
Pipeline #245734 passed
Stage: build
Stage: deploy
Hide whitespace changes
Inline Side-by-side
assets/figures/week.png
+ 0
− 0
View replaced file @ 36debeb4 View file @ 6f2644f9
assets/figures/week.png

46.2 KiB | W: | H:

assets/figures/week.png

101 KiB | W: | H:

assets/figures/week.png
assets/figures/week.png
assets/figures/week.png
assets/figures/week.png
  • 2-up
  • Swipe
  • Onion skin
assignments.md deleted 100644 → 0
+ 0
− 31
View file @ 36debeb4
---
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
info.md
+ 73
− 39
View file @ 6f2644f9
......@@ -13,84 +13,118 @@ nav_exclude: false
An overview of the module and some key policies are described on this page, adding to the description provided in the <a href="https://studiegids.tudelft.nl/a101_displayCourse.do?course_id=69347" target="_blank">Study Guide</a>.
_Updates to the material on this page will be accompanied by announcements in class during the Monday lectures and and via the [Announcements](..announcements/) page on this website._
_Updates to the material on this page will be accompanied by announcements in class during the Monday lectures and and via the [Announcements](../announcements/) page on this website._
MUDE is built on a repetetive and consistent weekly schedule, which is illustrated on the [Schedule page](./schedule), along with a list of topics, by week.
MUDE is built on a repetetive and consistent weekly schedule, which is illustrated on the [Schedule page](../schedule), along with a list of topics, by week.
If the information below does not answer your question, firt check the [Answers Platform](https://answers.citg.tudelft.nl/){:target="_blank"} (described [below](#answers-platform)). If that doesn't help, you can contact MUDE staff at MUDE-CEG@tudelft.nl.
This page contains the following sections:
- [Module Information](#module-information)
- [Assessment](#assessment)
- [Assignments](#assignments)
- [Weekly Schedule](#weekly-schedule)
- [In-Class Sessions](#in-class-sessions)
- [Question Hours](#question-hours)
- [Online Resources](#online-resources)
- [Answers Platform](#answers-platform)
- [Attendance](#attendance)
- [Conduct](#conduct)
## Assessment
Your total MUDE grade consists of 3 assessments:
Your total MUDE grade consists of three assessments:
- Exam at end of Q1 (resit in Q2) (25%)
- Exam at end of Q2 (resit in Q3) (25%)
- Assignment Portfolio (50%)
You will pass the module if you obtained at least a 5.8 for the three individual components. There will be a resit opportunity for the exams. If the grade for your Assignment Portfolio is below 5.8, you will get the opportunity to submit a revised version for which you will get a 6.0 if judged sufficient.
The exams are described further on the [Exam page of this website](./exams).
This website has separate pages to describe the [Exams](../exams) and the [Assignment Portfolio](../portfolio).
The Assignment Portfolio consists of three components:
Note that the first part of Q1 is used to get used to the weekly MUDE activities and workflow; therefore, **none of the work during the first two weeks of Q1 is part of the Assignment Portfolio grade** (but the content is still part of the exam!).
**FILL ME IN**
## Assignments
There are three types of assignments every week, each of which is described below:
- **Programming Assignments (PA)**: individual, part of Assignment Portfolio grade.
- **Workshops (WS)**: assigned and completed during Wednesday sessions. _Not_ part of Assignment Portfolio grade.
- **Group Assignments (GA)**: completed in groups during Friday sessions. Part of Assignment Portfolio grade.
Assignments (and weeks) are numbered to indicate the quarter and week in which they occur. For example, PA 1.4 is the Programming Assignment for week 4 in quarter 2. Files and folders will use an underscore, for example `PA_1_4_*.ipynb` will be stored in folder `Week_1_4`.
### Assignment Portfolio
GitLab will be used to submit PA's and GA's and to recieve feedback from instructors. Instructions for how to access and use GitLab will be provided over the first two weeks of Q1.
Assignment Portfolio includes weekly 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.
## Weekly Schedule
### Assignment Portfolio
Each week begins with a lecture on Monday and ends with a Group Assignment completed in-class on a Friday; question hours, Programming Assignments and Wednesday Workshops are designed to help you learn the topic for each week in a structured and way that is repeated each week. See the [weekly schedule page](../shedule) for an illustration.
PA and GA.
### In-Class Sessions
The in-class sessions on Wednesday and Friday are designed for you to work collaboratively with classmates and be able to easily ask questions to teachers. We will be distributed over multiple locations, with instructors in each room. Room assignments will be posted to this website each week, by group number. You are not required to work with your group during the Wednesday sessions, although it is a useful moment to reflect on the Group Assignment from the previous week and plan for the upcoming Friday. Attendance is required for the Friday sessions (see [Attendance section below](#attendance)).
### Question Hours
The best chance for you to ask in-person questions about MUDE is during the Tuesday question hour, when we will have multiple teachers present to help with the theoretical topics, as well as issues related to programming.
## MUDE Resources
Thursday is planned during the lunch period due to the fact that all three MSc programs have full schedules on that day; it is provided in case you need a question answered before the Friday session (for example, perhaps you are trying to finish the programming assignment). There will be only 1 or 2 teachers present on Thursday.
There are several primary resources for this module, each of which is also available with a quick-link in the top right corner of this website:
- **MUDE Textbook**: this is where assigned reading is located, along with interactive exercises to practice and study the material.
- **Answers Platform** ([answers.citg.tudelft.nl](https://answers.citg.tudelft.nl/)) a [stack-exchange](https://stackexchange.com/){:target="_blank"} style question and answer platform; a place to collaborate with your teachers and fellow students. Everyone is encouraged to post questions _and_ answers!
- **Course Files** ([mude.citg.tudelft.nl/2023/files/](https://mude.citg.tudelft.nl/2023/files/)): key files for the module are available at this URL for easy access, for example, weekly instructions, solutions or Group Assignments instructions. Often notebook files (`*.ipynb`) will be converted to HTML for easy online viewing; however the complete set of files required for an assignment (e.g., `*.py` or data files) will only be available via GitLab.
- **GitLab**: starting in week 3 this will be our primary platform for sharing and submitting assignments, as well as receiving feedback. In Weeks 1 and 2 you will download your assignments from GitLab, but not submit them.
- **Collegerama**: Our Monday lectures are available to stream online [here](https://collegeramavideoportal.tudelft.nl/catalogue/cegm1000/?academicYear=2023-2024-cegm1000).
- **Brightspace:** this platform is used to ensure students receive important annoucements about the module contents and activities in a timely manner; however, they will typically be links to announcements made on this website. General announcements such as exam registration reminders will be posted to Brightpsace only. To make sure you never miss an announcement, get the Pulse app! An overview with instructions can be found [here](https://teaching-support.tudelft.nl/how-to-use-pulse/).
Monday question hours are held in 3.80.6 with Robert Lanzafame and are meant for quick questions or personal issues. As the room is small, please line up outside the door if there is a student ahead of you. Note that these sessions are _not_ visible in MyTimeTable.
Please note that content in the online textbook will be added throughout the module, and changes will be announced and documented as needed. When new content is added, it will be done in large chunks. Changes will not be made retroactively that impact the scope of the exams (in other words, you will never need to re-study material because it changed prior to the exam). Notifications of errors, corrections and suggestions for improvement are glady welcomed via the Answers platform and/or via the MUDE email address.
Tuesday Question Hours are additionally scheduled during Weeks 1.9, 2.9, 2.10 and 3.9 for exam review.
## Questions and Answers
## Online Resources
There are a variety of ways to obtain answers to your MUDE-y questions, described in the sections below. Please try to be considerate when asking questions and provide enough detail and context to make it easier to understand what it is you need help with. In addition, don't forget to check the Answers platform to see if someone has already asked the same question, and to use the search function in the online textbook to look for relevant key words. do your best to Jupyter Book search function. If you find a good resource online (i.e., outside the textbook), you can also share that via the Answers platform.
There are several online resources for this module, most of which are available with a quick-link in the top right corner of this website:
- **MUDE Online Textbook**: weekly reading, along with interactive exercises to practice and study the material.
- **Answers Platform** ([answers.citg.tudelft.nl](https://answers.citg.tudelft.nl/)) a stack-exchange-style platform; you are encouraged to post questions _and_ answers!
- **Files Page** ([mude.citg.tudelft.nl/2024/files/](https://mude.citg.tudelft.nl/2024/files/)): key files for easy access. Notebook files (`*.ipynb`) will be converted to HTML for easy online viewing; however the complete set of files required for an assignment (e.g., `*.py` or data files) will only be available via GitLab.
- **GitLab**: starting in week 3 this will be our primary platform for sharing and submitting assignments, as well as receiving feedback. In Weeks 1 and 2 you will download your assignments from GitLab, but not submit them.
- **Collegerama**: Our Monday lectures are available to stream online [here](https://collegeramavideoportal.tudelft.nl/catalogue/cegm1000/?academicYear=2024-2025-cegm1000).
- **Brightspace:** annoucements and BuddyCheck. To make sure you never miss an announcement, get the Pulse app! An overview with instructions can be found [here](https://teaching-support.tudelft.nl/how-to-use-pulse/).
Please note that content in the online textbook will be added on a weekly basis throughout the module, and changes will be announced and documented as needed. When new content is added, it will be done in large chunks. Changes will not be made retroactively that impact the scope of the exams (in other words, you will never need to re-study material because it changed prior to the exam). Notifications of errors, corrections and suggestions for improvement are glady welcomed via the Answers platform and/or via the MUDE email address.
### Answers Platform
This is your go-to place to ask a question about technical content in the course, as well as other non-technical quesions, for example, exam or absence policies. We strongly encourage you to use the platform to both ask and answer questions. The platform works by providing (and discussing) answers to questions, then voting whether or not you find the answer to be useful. You can also track statistics as you participate in the platform, giving it a bit of a competitive side: we will be periodically awarding prizes to students who make exceptional contributions to the Answers platform throughout the semester! In addition, this is also a useful metric we have for selecting future MUDE TA's.
Use the [Meta tab](https://answers.citg.tudelft.nl/categories/15){:target="_blank"} if you have questions for how the platform works (this is especially well-developed on the [page for the math department](https://answers.ewi.tudelft.nl/categories/2){:target="_blank"}).
The [Answers Platform](https://answers.citg.tudelft.nl/){:target="_blank"} is a website where you can find Answers to questions asked by yourself, other students and course staff. Ask anything you want related to MUDE!
### Open Question Hours (Tuesday)
The platform works by providing (and discussing) answers to questions, then voting whether or not you find the answer to be useful. You can also track statistics as you participate in the platform, giving it a bit of a competitive side: we will be periodically awarding prizes to students who make exceptional contributions to the Answers platform throughout the semester! In addition, this is also a useful metric we have for selecting future MUDE TA's.
Beginning in week 2, every Tuesday there is an optional question hour. Teachers and teaching assistants will be present to help you with any of your MUDE or programming questions. There are no teacher-led activities here, so you must come prepared with questions. Although we will do our best to answer them, it is recommended to post tto the Answers platform first. We will monitor the questions and be able to come to the session better prepared. Who knows---perhaps a fellow classmate or teacher will answer your question first!
There are numerous benefits for sharing our questions and answers on this platform. To ensure it becomes a useful resource, please consdier the following guidelines:
1. Questions and answers should be written as if they were a standalone document. You should not use it as if it were a WhatsApp or email conversation.
2. Add a vote if something is useful or not. If you like a question or answer, give it an upvote! Downvotes are also informative (try to use the comment thread to indicate why).
3. Edit your posts instead of adding a second post with a correction. Use the comment thread to discuss or explain confusion.
4. Ask questions and post answers that are clear enough to be answered without searching for additional material. For example, write the equation in question or include a screenshot; include a snippet of code if it is programming related.
5. Do not include personal information in your post.
6. Do not ask questions to course staff individually or to the MUDE email address; instead, use the MUDE email to request an answer to a question that has remained unanswered for a few days; include the link so it is easy for course staff to find.
### Contacting MUDE Teachers
Please avoid sending general questions about the module contents to the MUDE email address or individual teachers. You will be asked to post to the Answers platform. Worse, you deprive your fellow classmates the opportunity to learn from your question and answers, and to help each other learn the material.
### Personal Situations
For relatively common situations such as missing an occasional lecture or in-class session, check the Answers platform and policy information on this website. If you still have a question about your personal situation, use the email address MUDE-CEG@tudelft.nl. This is monitored by multiple instructors and is your best chance to get a quick reply.
<!-- Use the [Meta tab](https://answers.citg.tudelft.nl/categories/15){:target="_blank"} if you have questions for how the platform works (this is especially well-developed on the [page for the math department](https://answers.ewi.tudelft.nl/categories/2){:target="_blank"}). -->
## Attendance
Attendance in class is highly encouraged for the Monday and Wednesday sessions to stay on top of the material. However, attendance is mandatory only for the Group Assignment sessions on Friday. You are allowed to miss one session without obtaining prior permission (and we don't need to know the reason), but you should inform MUDE staff by sending an email to MUDE-CEG@tudelft.nl. Perhaps more importantly, you should also inform your group members in advance! You are free to arrange with each other to share the workload and catch up if a group member misses a Friday session. If you expect to miss more than one Friday session, you should inform MUDE staff immediately.
Attendance in class is highly encouraged for the Monday and Wednesday sessions to stay on top of the material. However, attendance is mandatory only for the Group Assignment sessions on Friday. Most importantly, you should inform your group members in advance if you will not be present! You are free to arrange with each other to share the workload and catch up if a group member misses a Friday session (see also the [Conduct Section below](#conduct)).
You are allowed to miss one session without obtaining prior permission. If you expect to miss more than one Friday session during a quarter, you should inform MUDE staff immediately, as repeated absences can impact your Group Assignments and cause a reduced Assignment Portfolio grade.
## Conduct
We expect all students and staff to adhere to the TU Delft [Code of Conduct](https://www.tudelft.nl/en/about-tu-delft/strategy/integrity-policy/tu-delft-code-of-conduct).
As MUDE Staff, we do our best to accomodate all students and answer your questions as quickly as possible. However, this is a challenge with a large module of around 300 students. To help us in this regard, we kindly ask for your patience and understanding; we also appreciate you checking the [Answers Platform](https://answers.citg.tudelft.nl/){:target="_blank"} and coming to our in-class sessions and question hours rather than asking questions about the course content via email. That said, do not hesitate to email us at MUDE-CEG@tudelft.nl if you have a challenging personal situation.
We expect all students and staff to adhere to the TU Delft [Code of Conduct](https://www.tudelft.nl/en/about-tu-delft/strategy/integrity-policy/tu-delft-code-of-conduct). In addition, there are several important points to consider for MUDE specifically.
In terms of student work, we also expect an honest effort and integrity for all assignments. We will run plagiarism checks throughout the semester on your work, and incidents will be reported directly to the Board of Examiners (you can learn more about the policy <a href="https://www.tudelft.nl/en/student/ceg-student-portal/education/education-information/academic-attitude" target="_blank">here</a>). In order to avoid this, please follow the following guidelines when working on and submitting your MUDE assignments:
- Reading and looking at each others work is OK, but avoid copy and paste of a) entire files, and b) small pieces of text or code
- Using material from fellow students or the internet is OK to get inspiration and ideas, but if this is more than a small number of sentences or lines you should be clear and honest. For example, write down the names of students with whom you worked or note whether or not you developed a piece of the code from a ChatGPT answer.
- Re-use material with a suitable license (for example, <a href="https://creativecommons.org/licenses/by/2.0/" target="_blank">Creative Commons CC-BY</a> allows re-use with proper acknowledgement).
In terms of your assignments, we expect an honest effort and integrity: if you submit work that is not your own you should explicitly explain this in your submission. Failure to do so will result in grade reduction. We will run plagiarism checks throughout the semester on your work, and incidents will be reported directly to the Board of Examiners (you can learn more about the policy <a href="https://www.tudelft.nl/en/student/ceg-student-portal/education/education-information/academic-attitude" target="_blank">here</a>). In order to avoid this, please follow the following guidelines when working on and submitting your MUDE assignments:
- You are free to use an AI tool, but we strongly recommend you try to ask small questions, rather than pasting the entire question prompt from an assignment. Never copy and paste the entire answer from an AI tool into your assignment submission. Our advice is to use AI tools to generate ideas, not answer questions.
- Always: a) write code yourself as much as possible, and 2) understand what it is you are writing: this is a much better strategy for learning, and, while it may be slow at first, you will find that in the long run you will need to copy/paste less often!
- Reading and looking at the work of classmates is OK, but avoid copy and paste of a) entire files, and b) large pieces of text or code. If you re-use more than a small number of sentences or lines you should clearly state that you have done so in your assignments. For example, write down the names of students with whom you worked or add a note that you developed a piece of the code from a ChatGPT answer. Note that answers in your Group Assignments which appears to come from another source, such as an AI tool, without citation, will result in points being deducted.
With regards to **group work**, the items above apply; in addition, you are expected to:
- Share the workload in an equitable way.
- Consider each members strengths and weaknesses and support each other to improve over the quarter.
- Inform your group members if your contribution to an assignment is not your own work (for example, from an AI tool or another classmate)
- Communicate in advance if you will be absence and coordinate with each other to make sure the Group Assignments are completed equitably. You are free to do this for a single week, or over the entire quarter, as long as all members consent.
- Use BuddyCheck to honestly evaluate the contributions of yourself and your group members individually.
- If there are problems with your group, use the weekly BuddyChecks to inform course staff. If you think the BuddyCheck is not sufficient, do not hesitate to contact course staff directly at MUDE-CEG@tudelft.nl (all communication will remain confidential).
- Don't wait until the end of the quarter to report issues with your group: the earler the better!
<!-- - Re-use material with a suitable license (for example, <a href="https://creativecommons.org/licenses/by/2.0/" target="_blank">Creative Commons CC-BY</a> allows re-use with proper acknowledgement). -->
multiyear.md
+ 16
− 2
View file @ 6f2644f9
......@@ -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
+ 36
− 3
View file @ 6f2644f9
---
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
+ 32
− 3
View file @ 6f2644f9
......@@ -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
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment