Earlier quoted context omitted.
> Turnaround time for exams was sub-one-day. What's the current status on accurately grading mistakes? From the exams I remember (Fall 2015), the exams autograded perfect answers well, but gave similar marks to nearly correct, but still wrong answers as complete gibberish. I felt that unless I had the answers exactly correct, it was hard to demonstrate my knowledge of the topic.
When I was studying software engineering, "nearly correct" answers would get you the same grade as "complete gibberish" on purpose. Partially correct programs would have no more value than completely incorrect ones. In retrospect, I think it was crucially important for students to learn the price of their mistakes. Most of my previous classmates are reputable engineers now.
CMU Computer Systems: Self-Grading Lab Assignments (2018)
41–48 of 48 posts
Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#42Earlier quoted context omitted.
What on earth would 200% test coverage mean?
Coverage for all the code that was written, and all the code that has yet to be typed, of course. All thanks to quantum computing :)
(Even code with 100% branch coverage may have common weaknesses like those that these (great) labs have students exploit)
Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#43Also worth noting the plagiarism detector actually did its job, at least in some of the most egregious cases that I heard of.
Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#44Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#45Oh malloc lab.
Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#46Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#47Earlier quoted context omitted.
I ran an in-class test/competition once where students submitted C code to a web server running on my laptop. My laptop compiled and ran their code - then checked it against a test suite and graded it all live. One student asked about security - and we got into a great discussion about permissions and what havoc he could and couldn’t pull off with the restricted user account. I encouraged him to figure out how to wri…
Ah, how simple it would have been to run in a virtual machine.
If my laptop were fully protected from that attack, it wouldn't have been as much fun for my student to wreck my machine in front of everyone. And so he might not have done it, and my class would have missed out on a beautiful demonstration and discussion of practical security engineering.
Re: CMU Computer Systems: Self-Grading Lab Assignments (2018)
#48Earlier quoted context omitted.
At UNSW we had a similar system. The marking was a test suite, and each passing test would give you a portion of your grade. The system had a couple of simple smoke tests which were ran on submission time (to catch issues that would make the entire test run fail erroneously). As a TA I spent a fair bit of time fixing trivial issues - eg, sometimes a student would get 3/10 on the auto marker with a basically working s…
When did you TA? I was TA for 1911 (I think?) around 2008-2009 and don't recall any automated grading system. It would have been so nice too, as labs would end up with students trying (struggling!) to complete the lab, get the lab graded, and ask questions about lecture material they hadn't yet understood. The grading would inevitably take up almost all the lab...
We didn't have automated grading for the labs then either, but we did for all the assignments. Still manual marking on style though, which to this day I have complex feelings about.