Congrats for making it to the half way point of the term. I hope you're looking forward to you week off (sort of) next week! 13 days until our next lecture. There are no lectures and tutorials in week 6.
There are help sessions, and you do have to complete your second assignment.
This is due on
Monday 13th of July (week 7) at 8pm.
Reminder to double check the late penalty, as the assignment 1 late penalty was an exception to the rule. 2% per hour off maximum for this one.
If you need assignment 2 help, continue to make use of help sessions and the forums!
You will be receiving your assignment 1 marks and comments back sometime between now and 8pm Monday. Our intention is to give you your results back at least one full week prior to your second assignment being due. You can check here intermittently to get your marks and feedback.
The delay has largely come down to the complexity of automarking these assignments - marking one student is a 10+ minute intensive series of tests and when that scales to hundreds of students things just take
. Thanks for being patient, and we're very glad that you'll get it back with ample time before ass2 due date.
If you feel there has been a mistake with your automark/performance marks, please email
If you feel there has been a mistake in your or clang-format mark, or C++ practices or quality-of-tests mark, then please follow these simple steps:
Please note: If you ask for your marks to be reconsidered, it's always possible that your mark can go
. Sometimes when correcting poor judgements on marking in your favour, it's possible to uncover other poor judgements not in your favour! So don't just think "I'll just nag for more marks, I have nothing to lose".
When you collect your submission, go to the bottom of the result. It tells you the zid of the tutor who marked it. Simply email
and it will go to the person who marked it :)
See you on Wednesday in week 7 for our lecture on introduction to templates!
Some key updates for you below. Any further updates this week (if any) will be provided in the first moments of lectures this week.
Congrats to nearly everyone for completing assignment 1. 👏 👏 👏 👏
Assignment 1 is currently being automarked. This will take another few days (lots to run!) and then your tutors will do the manual marking for good C++ style and other sanity checks.
At the moment the intention is to have your marked assignments back to you by the Wednesday lecture in week 5. If we miss this deadline (your tutors have lives too), it may be another day or two. We'll do our best.
Due to extensions that some students have, we're unable to release any marks prior to census date. So if you're tossing up dropping the course, don't wait for any revelation that you don't already have. The one word of advice I'd probably give to you is that if you've managed the course so far, you'll manage it for the rest of the term. The course doesn't get exponentially harder, it's all just moderately hard and stays that way.
Assignment 2 has been released. You can view it here . Currently it's due at the start of week 7. Much of assignment 1 can be completed with knowledge covered this week (week 4) in lectures. The rest of the knowledge will be covered next week in lectures (week 5). No reason you can't start now, however, if you didn't start for a week and a bit you'll be fine.
Chris will be doing a non-assessable bonus lecture on Friday 1pm-3pm this week (week 4). It will cover topics outlined in this piazza post . The link to the zoom call is on the timetable ! It will be recorded so you can always watch later.
You're not expected to learn anything from his lecture, but many of you have been curious.
Assignment 1 late penalty has been REDUCED by a factor of 4. 10pm Sunday hard deadline unchanged. The 2% reduction off maximum mark per hour submitted late has been adjusted to 0.5%. Regardless, just like before, after 50 hours (Sunday 10pm) we will still enforce a hard 0.
If you're struggling or confused about assignment 1, we will spend the last 30 minutes of the Wednesday lecture (tomorrow) discussing it. We will answer questions, talk about ways to solve the problem, as well as help some people overcome any overwhelmed feelings they're having about ranges / abseil etc. We'll also go over gitlab one last time and how to accept merge requests pushed by us if you have conflicting code. If you're someone who didn't feel they'd complete the assignment satisfactorily by Friday 8pm, we'd encourage you to drop in or at least watch the recording later that evening. We will stop and start the recording again, so it may appear as 2 recordings in the link (please
check this image out
if you don't know what we mean)
We understand that some students are struggling to wrap their head around some parts of C++ for the first assignment. We don't like the idea of extending the deadline so close to due date - mainly because we know that there are students out there who made decisions this week (skipping social gatherings, spending less time with family) to devote to their assignment on the due date they were given. To extend it so late is (in my view) to disrespect those who've already made compromises. HOWEVER, we also want to alleviate pressure off those who are struggling to find the time in these early weeks, those struggling to adjust to online learning, etc. So the compromise is to simply relax the penalties for late submissions.
Maximum mark achievable
for reduction of
2% per hour off due date
||Maximum mark achievable for reduction of 0.5% per hour off due date|
Our advice with assignment 1 is still to approach it simply to start. Use algorithms and data structures that are basic (e.g. std::vector, std::queue) just to get going until you can nail the logic and get the outputs you expect.
Just get it working
. You don't
to use the abseil/ranges things to get a great mark, so start with something less intimidating and work your way up. If this just sounds like words to you, come by the last 30 minutes of the Wednesday lecture.