EDAP15 Program Analysis

Number	Start	Week	Team	Duration	Repository	Description	Notes
0	2024-01-18	CW 3	Group	1 week	https://git.cs.lth.se/creichen/edap15-2024-exercise-0.git	description
1	2024-01-24	CW 4	Group	2 weeks	https://git.cs.lth.se/creichen/edap15-2024-exercise-1.git	description	Updated 2024-02-08 (removed line in `examples/type-errors.teal`)
2	2024-02-07	CW 6	Solo	1 week	https://git.cs.lth.se/creichen/edap15-2024-exercise-2.git	description	Updated: 2024-02-08 19:00 (several fixes) 2024-02-08 20:45 (removed warning about SmallSet, which is fine to use in its new version) 2024-02-09 13:10 (Fix for default nullness of parameters, not critical for exercise)
3	2024-02-14	CW 7	Solo	1 week	https://git.cs.lth.se/creichen/edap15-2024-exercise-3.git	description	Updated: 2024-02-16: Fixed CodeProber freeze when using nested probes with circular attributes 2024-02-21: Relaxed requirements for Task 3 in response to possible JastAdd bug
4	2024-02-21	CW 8	Solo	1 week		description	Optional / not graded

The specified duration is the recommended duration for working on the homework assignment (see "Homework Priorities" below).

Homework Priorities

For homework presentations during lab hours, the TAs will prioritise presentations of solutions for the "current" exercise. The table below explains which exercise is "current" for the different labs:

Calendar Week (CW)	3	4	5	6	7	8	9	10 (uppsamlingslabb)
Presentation priority	0	0	1	1	2	3	3	3

Process:

Follow homework instructions.
Push your solutions to git. (Also push partial solutions / intermediate steps — these may help you answer TA questions later.)
Book a time with the teaching assistant and present your solution.
- This can be in the labs or (at the TA's discretion only) via Zoom.
- You are guaranteed one presentation slot per week.
- You can only present one exercise to the TA at a time.
- You may ask the TA for an additional slot the same week after presenting. Please respect the TA's decision: our TAs have many other responsibilities in addition to this course.
- The TA decides between:
  - Pass: You are done with this lab.
  - Minor revision: You do not need to present again but have to make some changes and notify the TA once you are done. Unless stated otherwise, you have three working days to complete the changes. You have not passed until the TA has explicitly approved your change.
  - Major revision: You must present again. This may happen even if you have solved the technical problems presented in the lab, since the TAs will also grade your ability to explain your solution and to justify your design rationale.
- You can only book one slot per week directly.
- You do not have to complete the labs in the recommended time frame, but strongly recommend that you try.
- For violations of academic integrity, especially plagiarism, the university has clear guidelines that we will follow.
If you have successfully presented all exercises, you have completed the course and are eligible for the oral exam.
Exemptions for special circumstances apply, though you may need to provide documentation and may have to present your solution to the instructor instead.
Don't wait too long to get started: you only have a limited number of guaranteed slots.

Updating git repository:

Despite our best efforts, we sometimes need to release updates to an exercise via git after the exercise is published. You can merge these updates as follows:

Web UI: Press the "Update Fork" button in your CourseGit repository (shown directly under the blue "Code" button, if CourseGit finds that your repository is "behind" the upstream one)
Command line: Make sure that you have the correct upstream repository set (see the table above):
git remote add upstream https://git.cs.lth.se/creichen/edap15-YEAR-exercise-NUMBER.git
Now you can use various merging methods, such as:
git pull upstream main

If you have any Merge Conflicts, you will have to resolve them. On the command line, git gives you instructions for how to resolve conflicts; read the instructions that git prints out carefully before you start resolving conlicts.

Normally we only release fixes, helper code, or clarifications to the exercise instructions.
This means that your code should normally take precedence over ours (if in doubt).
If you have solved the exercise without our updates, you can ignore the updates.