# Assessment

The course is designed to include two types of assessments:

1. Formative : These are ungraded and are intended to a) fill gaps in knowledge for those who have not had any programming experience before and b) to serve as a refresher to those who wish to update their skills. The formative components of the course are:

• 8 In-Class Labs: During the scheduled lab-hours on Wednesday, you can work through the interactive Jupyter Notebooks with TAs available to help you and answer your questions. I advise you to go through these notebooks before and prepare a set of questions you want to discuss with your TA in class.
• 8 Peer-Reviewed Homework Questions: A set of homework questions will follow the In-Class Lab sessions to further consolidate your understanding. To enable peer-learning, you have the option to give and receive Peer-Feedback for these questions through the Peer system on developed by TU Delft scientists at EWI. This is neither graded nor obligatory. However, written peer feedback enhances student learning.
• Discussion Sessions: Every Friday you will participate in an online discussion session with your peers to discuss assigned readings. This session will be moderated by a TA in a group of 10-20 students each. The papers that you will read for each week will come along with a set of questions that will guide your reading and subsequent discussions. These papers complement the topic discussed that week in lectures and tested in assignments, therefore you are strongly encouraged to participate. The concepts covered in these sessions will also shape your ideas for the Final Group Project.
2. Summative : These are graded components and contribute to the final mark for the course as follows:

• Assignment 01 (15%)
• Assignment 02 (15%)
• Assignment 03 (10%)
• Final Project (60%)

### Marking Criteria for assignments

The following specific criteria relating to the code provided will be used:

CriteriaIndicative weight(0-0.5)(1-1.5)(2)
Output0.5the code does not run/seem to be runnable* (in case of html files) * if your syntax is wrong or data paths are messy / not reproducible (e.g. not using os.getcwd())the code runs but does not produce the expected outputthe code runs and produces the expected output
Formatting0.5code is not formatted at all or messy* * variables are used before they are defined, functions are used unnecessarily.code is properly formatted* * each section describes one aspect in a logical order and the code structure is readable (for reference see how labs are formatted with markdown and code sections)- code is properly formatted.. + - variables and functions are named well.
Methods (e.g. Tidy Data, EDA, Graphical Excellence, Spatial Autocorrelation, Network Weights, Regression, etc.)2code/output shows no evidence of methods presented in class and homework exercisescode/output shows some evidence of methods presented in class and homework exercisescode/output illustrates clear evidence of methods presented in class and homework exercises
Documentation (Markdown/Comments)2there is no documentation to follow your code. there is no documentation to follow your code. (e.g. why did you drop a certain variable or why did you choose one over another?)there is some documentation explaining your code’s logic and your choices in the analysis but these choices or logic is not clear.there is extensive documentation explaining your code’s logic and your choices in the analysis. - no hypothesis present, if one was explicitly asked for

### Submission

Deadlines for everything will be Friday at 2330 for the week’s homework or assignments. The first week’s homework deadline is Monday 7th Sep at 2330.

• In-Class Labs: labs are not for submission. They help you practice and understand python programming in this course.
• Peer-Reviewed Homework Questions: Submit weekly homework exercises called hw-0x.ipynb as follows,
• find the course Introduction to Urban Data Science