Quiz #1 Graded
I have run the automatic batch self-check tests for Quiz #1 (checking
correctness) and the TAs have examined problem 1 and the code (checking
requirements: e.g., statements/solution) and the grades are now recorded
assignment grades and
Grades(zipped .xlsm file) files, whose
details are discussed below, in Announcement #7.
The class average was about 77% and the median was 88%, meaning that most
students correctly solved most problems (43%), and 20% of the class correctly
solved all the problems.
Overall there were 43% As, 17% Bs, 13% Cs, and 27% Ds and Fs for those students
who submitted work; most of the students who scored a 0submitted code
that we could not run (see the paragraphs below for possible regrading by
FYI, the previous Fall quarter the grades were
57% As, 11 Bs, 10% Cs, and 22% Ds and Fs for those students who submitted
About 44% of the students submitted early (although there are no extra credit points on quizzes for doing so), and these early submitters scored much better than students submitting on the due day (83% compared to 73%): a difference of one full grade (students submitting 2 days early had an average of 92%). I am assuming that some students ran out of time before they finished all the problems, and will plan to get started earlier on later quizzes.
In the assignment grades spreadsheet, Column A contains the ID Hashed of all students (in sorted order) and Column B contains an X if we believe the student submitted work on time. Column C shows deductions for
Rows 4 and beyond show the number of failed tests for each student (a blank indicates no failed tests: equivalent to 0 failed tests). To compute the number of points you scored for a problem/in a column, compute the percentage of successful tests and multiply it by the number of points the problem is worth. So for example, if a student missed 2 of 6 tests on a 5 point problem, he/she would receive (6-2)/6 * 5 = 3.3 (actually, 3.333...) points. Columns P-R show each student's cumulative Score, the score Rounded to an integer (that integer is the score entered in the Grades spreadsheet) and Percent, based on the number of points the assginment is worth (here 25).
TAs graded problem 1 and the function requirements for all students in their labs. The TAS will distribute these pages in labs this week only; after that, the papers will be archived in my office. The rubric for this problem was as follows: each part was worth .5 pt.
Requirements points for the functions were deducted only for too many statements. Many students created extra/temporary lists:
Students should talk to the TA for their Lab first, if they do not understand why they received the marks they did or dispute any of these marks. The best time to talk with your TA about grades is during one of your Labs, when both student and TA are physically present to examine the submission and the grade, possibly running the solution on a computer they can share.
Students should examine their graded work immediately and get any regrade issues settled as soon as possible (within a week of when the grade is assigned). Show up to lab and settle these issues immediately.
IMPORTANT Information about Student Grades
Programming Assignment #0 Graded
The TAs have graded (and I have recorded the grades for) Programming
As with most assignments, there are two files that you should download, unzip,
and examine to understand your performance on this assignment, and your
cumulative performance in this class.
Both of these files are sorted by Hashed IDs (which are computed from the 8-digit UCI IDs of all the students in the class). To determine your Hashed ID, see Message #6 below.
IMPORTANT: Scores wil revert to 0, if I do not receive a signed Academic Integrity Contract from you (we are tabulating them this week). Please come by during my office hours as soon as possible if you need to fix this problem.
This assignment was designed to test you on whether you have mastered the basics of using Python in Eclipse, the Eclipse Debugger perspective, and batch-self-check files in the driver.py module (in courselib). It was also designed to see if you could follow instructions and ask questions: more on that below.
The class average was 28 (or about 94%) and the median was 29 (or about 97%). For those students submtting work, there were 82% As, 10% Bs, 2% Cs, and 6% Ds and Fs.
The assignment was not meant to be hard, but it was not trivial either, and there were many opportunities to lose points (and learn from your mistakes). Your work in the Eclipse/Python Integrated Developement Environment (IDE) throughout the quarter will leverage off the understanding and skills that you acquired in this assignment.
Let me talk about what will probably be the most contentious single point of the 1,000 points that this course is worth (thus .1% of the grade): this point was lost by about 14% of the students submitting work. I took off 1 point if you corrected the misspelling Inteprxter (and two points if you didn't have either spelling: in this second case you obvious failed to meet the specifications because you did not print what was required). When some students hear about this point deduction, their heads explode and they cannot believe that I am taking off a point for correcting what you thought was my mistake. But... I am trying to foster an atmosphere where nothing is taken for granted in the instructions that I give: if anything seems confusing or plain wrong, I should be questioned about it -preferably in public, on a MessageBoard forum- so others can learn if there really is a problem, and if so the correction.
Also, some students did not carefully read the instructions in the Debugger Perspective document for the quiz part, which required them to change a line in the craps script before running it with the debugger to gather the required information. With this change in your program, we can check your answers for correctness; without it, we cannot check you answers for correctness.
Finally, about 52% of the students submitted the program 2 or more days early; about 14 submitted the program 1 day early. So, about 66% of the students submitted this assignment early. Keep up the good work: you can earn 12 extra points if you turn in every Programming Assignment 2 or more days early (upping your grade by 1.2%): for some students, this boost will be enough to raise their final grade. Over the course of a two week assignment, it will be to everyone's benefit -students and staff alike- if students try to finish and submit early.
IMPORTANT If you believe that we graded your work correct, please examine the files mentioned above first, then contact the TA who graded it, to discuss the issues with him/her. Such a discussion can have only positive outcomes: either he/she will agree with you that you deserve more credit (and, we do want you to receive all the credit that you are due), or you will come to understand the question, program, or solution better and realize why you lost points. This is certainly a win-win situation. Please read my solution and the assignment grades spreadsheet carefully before contacting your TA; ensure that you understand what is the correct answer and what points were deducted from your assignment and why. If there is a problem, your TA will email me a revised summary about your program, and cc a copy to you. I will update the grades spreadsheet as appropriate (it might take a bit of time for all these events to cumulate in a changed grade) and email you.
If you feel there is still an unresolved problem after talking to your TA, please contact me (but always contact your TA first). Also, because of the size of this class, if you have a grading issue, we will consider it only if you bring it to your TAs attention within a week of when I return the materials. This policy is in place to avoid grade-grubbing late in the quarter.
|When we grade assignments, we often distribute/update various spreadsheets with the relevant grading information. These spreadsheets are indexed and sorted by each student's Hashed ID. The course web-page has a Find ID Hashed (grade key) link, right below the Grades(zipped .xlsm file) link, which you can use to retrieve your Hashed ID (or click Find ID Hashed). Use the result it shows when examining any spreadsheets of grades; I suggest that you find this number once, and write it down for future reference.|
without Losing Points
ICS-33 uses software that automatically grades most quizzes and programming
assignments; it uses (self-checking) testing cases that we supply with the
testing instruments that we distribute.
You will learn about these tools in Programming Assignment #0.
Here are a few hints to ensure that you will understand the grading process
better and minimize your point loss.
After an assignment is graded automatically, the Announcement for it will contain a link to an Excel file that you can examine for detailed information about how your score was computed.
If this information does not match your expectations from running the assignment's self-checks while developing your code, contact your TA. It is best to meet with your TA during lab hours: he/she can talk to you about your code and run it while you are present, to help resolve the difference. But, if we have to modify your code to grade it properly (see the typical source of problems above), then we will deduct points. I hope that by students carefully writing/submitting their code, these grading anomalies and point deductions will be minimized during the quarter.
There are many ways to communicate with me (and other staff and students).
Here is a quick overview.
Note that for questions that are not specific to you -questions that are relevant to the entire class- it is best to ask them on the appropriate Message Board Forum.
I expect students to attend all their scheduiled labs (unless they have
already finished the current programming assignment).
Programming Assignment #0 is assigned before the first lab of the quarter; so
if you have not already finished it, I expect you to attend your first lab
and work on it there.
Generally, you can get invaluable help from the TAs and Tutors for understanding Python and debugging your code: don't expect them to debug your code for you, but instead expect them to help you learn how to debug your own code in general, using your current problem/code as a concrete example.
Install Course Software
All students with computers should download and install the course Software:
Java (to run Eclipse), Python, and Eclipse.
All three products are available for free on the internet.
Students can view instructions for downloading and installing this software
by following the
If you are using a Mac there are special instructions for you
(e.g., Java is already installed)
If you have installed a version of Python prior to 3.6, you should install the current version of Python 3.6 (and the most up-to-date version of Eclipse as well).
Although students can work on their programming assignments on the computers in the UCI labs, I expect students with computers to download and install this software by the end of the first week of the quarter. If you are having difficulty with this task, the TAs and Lab Tutors will help you during the first Lab meeting (or beyond, if necessary: bring your computer to the lab). If you have successfully downloaded and installed this software, please help other students do so too. Finally, you can also use the class MessageBoard Forums to ask questions about installing this software and help other students install it.
I strongly suggest that you BACKUP YOUR WORK daily: computers can malfunction, break, or be stolen.
Welcome to ICS-33.
I am going to post and archive important messages about the class in this
announcements web page: each entry will be numbered, dated, and labeled.
The entries will appear in reverse chronological order.
Whenever you follow the link to this page, scan its top for new announcements;
scan downward for older announcements.
This message will always appear at the bottom of this file.
I will never remove a message from this page
I have already posted some important messages before the start of the quarter. Expect a few new messages to be posted here each week, mostly regarding returned and graded work.
Check this Announcements page, along with your email and the MessageBoard Forums, daily.