Project Period

Project Period#

In semester week 10, the project period of Spring 2025 will begin, replacing the usual teaching with your own independent work in groups on a mathematically focused project.

Intro#

Groups of 6 students will be formed. To register, each group fills out one joint registration form. A link to the registration form, along with project topic appetizers will be released in semester week 7 on DTU Learn. Registration deadline is March 26 at 18:00.

All project topics will include significant elements from the curriculum in the courses 01003 Mathematics 1a and/or 01004 Mathematics 1b, as well as the use of Python/SymPy. In some project topics, supplementary, project-specific methods will be introduced, building upon the curriculum.

The project period will finalize in a project report, where you document and present your work, results and conclusions, as well as a final project exam day.

Rules for Group Formation and Registration#

  • Students form their own project groups of 6 people.

  • Partial groups with fewer than 6 members can register with the group members they have.

  • If you have not found a group, you may fill out a registration form with only your name on it.

  • The course responsibles will combine partial groups to form 6-person groups. If you register with a partial group, you should expect to have more group members added - worst case, you risk being split up in order for the puzzle to fit.

  • On the registration form, the group must place all offered project topics in prioritized order.

Supervisors and Work Load#

During the project period, your group will be assigned one or more supervisors who will be available for supervision in the usual Long Day and Short Day timeslots. We expect you to put in the usual amount of work, i.e., at least 18 hours per week.

Structure and Submission of the Report#

This guide outlines the requirements for how your project report should be structured and formatted. The report must be a collective product of the group, and individual contributions should not be specified.

  1. Joint Report: The report must be the collective work of the group. It should not indicate who wrote what, as all group members are considered to have contributed actively.

  2. Front Page: The first page of the report must include:

    • The project title

    • Group name (e.g., Cars03)

    • Names and student numbers of the group members

    • Signatures (confirming that all members have actively participated in the project work)

    • Submission date

  3. Target Audience: The report should be understandable to a fellow student who has worked on a different project. This means that the report should be written with your peers in mind and should have a clear and logical structure that introduces the topic in an accessible way.

  4. Format and Structure:

    • Format: The report must be submitted as either a PDF file (we recommend using Latex/Overleaf) or as a Jupyter Notebook file. No other file types are accepted.

    • Independence: The report must be self-contained and understandable for a reader who has no access to the project roadmap/script. All necessary explanations and definitions should be included in the report.

    • Structure: Use a traditional structure with an introduction, foundational theory, methodology/implementation, results, discussion, and conclusion.

    • Clarity and Conciseness: The report should be concise, well-structured, and precise. Less important details, such as extensive Python documentation, can be placed in an appendix.

  5. Integration of Theory and Examples: In parts of the project where you are required to present a mathematical statement or concept, you should either provide a full proof or, if a proof is not feasible, at minimum illustrate the statement with concrete examples and figures. The project description often specifies the expected level of explanation. Consider combining theoretical discussions with practical illustrations (e.g., graphs or diagrams) to support your arguments.

  6. Reflection and Discussion: In addition to solving the specific tasks, you are encouraged to reflect on how the methods and models used contribute to the understanding of the overall topic.

  7. Submission:

    • Submission takes place online on DTU Learn.

    • The deadline is May 2, 2025.

    • An automatic plagiarism check is conducted after submission.

    • Name the PDF file with the group name you were assigned on Learn (e.g., Cars03.pdf).

Project Exam Day#

The project exam day is Wednesday, May 7, 2025, starting at 13:00. The exam day begins with an individual written 1-hour test on your specific project. The test is handed out on paper and must be completed and submitted on the provided paper. No aids are allowed during this test. Only writing accessories and a water bottle are allowed on the table.

If you have been granted extra time or a dispensation to use a computer during the exam, you must bring documentation. If you have been granted more than 25% additional time, you must contact Ulrik Engelund (uepe@dtu.dk) before the exam day.

After the written test, groups present parts of their report to the other groups and the supervisor. The supervisor will help the groups choose what parts to present from their project work. Each group has approximately 10 minutes for their presentation. There is no individual assessment during this part of the exam.

The project accounts for 20% of the course grade.

Project Appetizers and Scripts#

This year, three project topics are offered:

  • Transport of Pollutants

  • Solar Panels

  • Self-Driving Cars

Find appetizers for these project topics on DTU Learn. When the project period begins, detailed project roadmaps/scripts will be shared with the groups to guide their project work.

Contents