|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Assignments (Online Submission Site) (Online Grades)
Programming projects will consist of larger problems
that help you build your problem solving skills. Refer
to the advice page if you need tips on how to tackle these problems.
Note that we share some due dates with CS100J,
i.e. expect the labs to be especially busy around then,
so plan accordingly.
You can download the assignments, provided below:
(also J due date) |
p1PartC: .java | .txt |
||||
(also J due date) |
|||||
data |
P5.1: rewrite.txt P5.2: condorcet.m P5.2: election.m P5.3: polygon.m |
||||
R1.6, R2.2 revisited |
|||||
(also J due date) |
Card and Pile code |
Back to Top
Each programming project turned in will receive three distinct grades for
Note: The style score cannot be more than 2 points higher than the correctness score: S <= C+2.
If you work with a partner, both you and your partner will receive the same correctness and style grades for that assignment. See below for information about having partners.
At the end of the semester, we add
the style and correctness points from ALL projects to yield a total amount
of core points for your project score. We will drop the equivalent of 1.5
projects:
P = min(50, P1+P2+P3+P4+P5+P6+P7+P8) * 100 / 50
That is, you need only 50 out of the possible total of 65 points to
receive a perfect project score P. (If you score above 50, the excess
points are converted to bonus points.) For example, suppose you score
the following for 7 projects: 4/3/0, 4/3/0, 4/5/0, 4/5/5, 4/5/1,
4/5/0, 1/2/5. You would have a total of 7+7+9+9+9+9+3=53 core
points for your projects out of a possible 65 points. This is above
50, so you get a perfect project score P = 100! (Plus 53-50=3 bonus points.)
Omitted Projects: If you do not turn in a project at all and do not have a valid excuse, it counts as -2 out of 10 points, not as 0! As explained in Philosophy below, there are many good reasons to do the projects, and as long as you make a good faith effort, you should receive most of the credit, so there is no good reason not to do them.
Back to Top
Since projects "count" for a relatively small percentage of the total score, some students are tempted to skip them (or let their partners do most of the work) and plan to learn the material by reading the sample solutions. This process does not work for most people. This material is learned by actively doing the projects, not by passively watching a partner or reading the sample solutions. Thus, failure to actively do the assignments is likely to hurt your grade.
We expect projects to teach you how to solve more complex/larger problems. We grade mostly for feedback to let you know how you are doing. To reduce stress, projects are worth a relatively "small" percentage of the course score. Plus, we will not require you to do all the projects perfectly to get a perfect project score (see Grading). Thus, as long as you make a sincere effort on most of the projects, you should get a good project score.
Back to Top
Back to Top
From P3 onwards, you must submit your projects online unless we explicitly specify otherwise. Unless we explicitly grant you permission, you may not submit by e-mail.
Early Bonus: We will award bonus points for submitting the entire project early: No early bonus points for partial submissions.
When we request hardcopy, you have two options for submitting hardcopy:
We do not accept late submissions.Submit requested hardcopy in lecture on the due date. Homework will not be accepted after lecture, and if there are too many disruptions with students submitting homework in the middle of lecture, homework will be accepted only at the start of lecture. Submit requested hardcopy in Carpenter Lab for early submissions only. You must give the project to a consultant, personally!
For each project you must do the following:
Note: Submit work online, unless hardcopy is requested. Never submit as e-mail or on disk unless explicitly requested to!Print all your work as hardcopy, such as programs, output, and discussion answers. Please, no disks!For requested hard-copy, staple or bind together all sheets of paper. "Bind" means ring or folder, not twist-ties, string, or such nuisances Submit entire code unless directed otherwise. Type all work and responses to discussion questions. Include the following comment block (e.g. using % for MATLAB and // or /* for Java) with your information filled in at the top of each program:
Name: your name Partner: partner's name ID: your ID ID: partner's ID Section: your section's instructor, day, time Section: partner's section's instructor, day, time Date: due date Project: number and title Ensure correct alignment of tab stops in programs with no "chopped" line of code.
Back to Top
Look here if you wish to submit a regrade.Projects are usually graded in about 1 week. We usually return graded assignments in section and before&after Review Sessions. Near a Prelim, we might return things in Carpenter. You may retrieve unclaimed assignments from the consultants at Carpenter Lab at the end of the week in which they were returned in sections.
Back to Top
Partners
We encourage you to work with a partner on the programming
projects. (Why, or why not? Look here.)
If you work with a partner, you must adhere to the following
rules:
If you have any questions, please do not hesitate to ask the staff.You can have only one partner for each project. You cannot have different partners for different parts of the project. You can pick a different partner for each project. You and your partner receive the same correctness and style grade for the entire project. You and your partner may attend different sections. You must submit only one project with both your names, IDs, signatures, and section information, as specified in the Submission Rules. You cannot take your exams with a partner. You should avoid "divorcing" partners before submitting your project. Why? What if your partner submits a duplicate version of your programs? All the graders will see is an academic violation, so be careful.
Back to Top
Back to Top