Grading and Demo Policies
When and how do I demo my work?
Your work in computer science often consists of creating code based on
a particular specification. To earn credit for that code, a student
must typically do the following:
While some of the above criteria can be checked automatically, you
are typically requred to demonstrate your code and its correct
operation to a TA.
- Ensure that the code passes all tests.
- Make sure the code conforms to style standards.
- Make sure the code is written as clearly as possible.
If you are required to demo your work to a TA, please take note of
and abide by the following:
Work that is judged by a TA may be demoed only in our lab spaces,
only during our class's lab times, and only by a TA who is officially
Asking a TA to demo your work outside of the allowable places or times puts
both of your academic careers in jeopardy. Don't do it!.
- Credit given or received for work outside of those boundaries is a violation of our community standards.
- TAs or students engaging in such activities will
How are grades computed?
We recognize that students enter CSE131 with a wide variety of
CSE131 strives for a non-competitive learning environment. Our aim is to
help you learn, not filter you out. To avoid putting you in competition
with your classmates, we will not compare students in the determination
of grades for CSE131. No means are used and there are no curves.
Your semester score is computed as the following weighted average:
| Component ||Weight|
| Quizzes || 3% |
| Studios || 7% |
| Labs || 25% |
| Final Project || 7% |
| Extensions || 25% |
| Best 3 out of 4 Exams || 30% |
| Participation || 3% |
- Quizzes will be be posted online after all work for a given module
has been submitted.
We use Google Docs to administer quizzes. The information you supply about
yourself, in particular your WUSTL key, must be correct or the quiz will
not be counted.
- Each quiz has a completion date and time. You must complete the
quiz by then to receive credit.
- Quizzes are graded robotically
- The results of your quiz are returned in your repository, in the
As usual, you must update to see changes made externally to your repository.
- We will automatically drop your lowest quiz
- No make-up quizzes will be given.
- Some advice:
You should do these quizzes on your own, without any help.
- For the quizzes, you can use any
resources, online or otherwise, that you need for the quiz.
- However, on an exam you
will be limited to a single two-sided sage page.
- It would be wise of you to note what you needed from your resources
for the quiz so you can include that on your exam sage page.
- You earn credit for studios simply by participation. The studios are
an important component of how material is learned in this course. They
are essentially a substitute for lecture, except that you learn actively
by doing rather than by listening.
At the end of each studio session, you are cleared by a TA and your
participation is automatically recorded.
You are allowed one unexcused studio absence without penalty.
- Any excused absence can be made up with the TAs during their office hours.
is required from an instructor for the absence to be considered excused.
- Any other studio absence
drops your overall studio score to zero, which can lower your final
grade in the course by one letter.
- Each module of this course has a lab assignment. Most labs are
graded by the demo you perform in front of a TA. The TA will inspect your
code, watch your demo, and pass you on that lab assignment if both are
The TA will ask you some simple questions about your work, and may ask
you to modify your lab if it does not meet
the style standards
for this course. In such cases you can fix up the lab
during your lab section or you can resubmit the work as a late
lab (see below).
Labs are due as posted on the course calendar and
Your lab score is the fraction of labs you have completed as compared
to those assigned. Thus, your lab score will be 100% if all labs
are completed as described above.
- Final project
- A final project (game) will be designed and posted.
This project integrates
your work from the semester and provides an opportunity for you to
add creative components.
A contest with prizes will be held with TAs judging the winning entries.
- While the labs test your basic knowledge of the course material, the
extensions serve both to reinforce each module specifically but also to
integrate techinques between the modules.
Extensions are demonstrated like labs, with
a TA evaluating both your code and its functionality. Please read the following
carefully concerning how extension points are counted.
- Each extension is worth a certain number of points, as shown on the extension's
page and in
this table .
- Points for the extensions you successfully demo accumulate and count towards
your extension score, subject to the constraints articulated below. If you meet
the contraints, let's call the associated points valid.
- Your fractional (or percentage) score for extensions, overall, is simply the
sum of your valid extension points, taken out of 75 total possible extension
- The maximum number of points you can earn for extensions is 75 points.
do not count toward any aspect of your grades
for this course.
- The validity of your extension points is associated with turning in a certain
number of points by deadlines that are shown on the course calendar.
- The calendar will divide your extension points into n groups. If
we number the deadlines 1, 2, …, n, then i/n points are due at
the ith deadline.
For example, if there are 3 deadlines, 1/3 of your points are due at the first deadline,
2/3 are due by the second deadline, and all of your points are due by the third deadline.
- Important! At each deadline, the maximum number of points you can earn
is limited by how many you have at that deadline. Each deadline i limits the total points
you can earn for extensions to n/i the points you have at the ith deadline.
Continuing the example, you will be awarded no more than 3 times the points you
have at your first deadline, 3/2 the points you have at your second deadline, and
3/3 the points you have at the third deadline.
- No valid points can be earned after the final deadline.
Extensions can be submitted at any of the following times:
- During lab times.
- During studio times once you have finished your studio work
and if TAs are available to demo your extensions.
- During any of the extensions fests that are held
during the semester. These are shown on the
course calendar and syllabus.
- We will give four exams for this course:
- Three are given in-term, as announced on the
couse web page. These are not intentionally cumulative, as they emphasize
material from a particular portion of this course. but it is fair to assume you
know the material from previous exams.
- A final exam is the fourth exam and is scheduled as announced on
the course web page.
No make-up exams are given, but we will drop your lowest exam score, thus
counting the best 3 of 4 exams that we give.
It is your responsibility to ensure that you are available for the exams
you wish to take.
- Credit is earned by doing both of the following:
How are grades assigned?
Your letter grade in this course is based on your semester score, computed
as described above. No rounding is performed on your semester score: you
must have at least the stated number of points to earn the associated grade.
The following table explains how the score is converted
into a letter or pass/fail grade:
| Score || Grade |
| 93 ||A ||Pass|
| 90 ||A- |
| 87 ||B+ |
| 83 ||B |
| 80 ||B- |
| 77 ||C+ |
| 73 ||C |
| 70 ||C- |
| 60 ||D ||Fail|
| 0 ||F |
What if I feel my work was not graded properly?
Once a grade for an assignment has been posted to blackboard,
you have one week
to ask for a review of that grade.
It is your responsibility to check your grades and make an appeal, if
appropriate, in the alloted time period.
- A request of this nature will trigger a regrade of all aspects of the
work associated with that grade. It is possible this review will result
in a lower, not higher score. So proceed carefully.
- If the work in question was of a written nature, the work must be
submitted with no alteration of the contents.
- A cover letter must be supplied that explains the nature of the
Appeals made beyond the one-week consideration period will not be considered.
Emails or piazza posts concerning regrades past the
one-week consideration period will not be answered.
Last modified 14:40:12 CDT 22 August 2017
by Ron K. Cytron