|
|
|
CS 224N / Ling 284 — Natural Language Processing |
|
|
|
There will be four substantial programming assignments, each exploring a core NLP task. They are a chance to see real, close to state-of-the-art tools and techniques in action, and where students learn a lot of the material of the class. You have the choice to do the fourth programming assignment, or to do a final programming project on a topic of your own choosing.
There will also be simple online quizzes on the edX website, which will aim to check that you are paying attention to what you hear/read.
Finally, you will be rewarded for class participation. You may earn class participation credit for participating in class, attending coding sessions or office hours and answering questions on Piazza.
In summary, the final grade will be computed as follows:
Per our grading policy, participation is 7% of your grade. 3% of this is competitive grammar writing. The other 4% consists of up to 20 participation points awarded according to the following policy:
* The first one will be Kevin Knight's lecture on Nov 3rd, with others
potentially randomly selected.
** Any post that is not obviously trolling, off-topic, or wasting time is
considered good.
In addition, the top 10 answerers, top 10 endorsed answerers and top 10 endorsed askers on Piazza will receive 10 bonus points. The course staff will also have discretion to award participation points for other things.
In this way, 2 participation points per week is needed for full participation grades, or 4 participation points per week from now if you start at 0 now. Points beyond 20 will still be tracked, and at the discretion of the course staff, can be used to grant extra late days if needed.
To self report your participation, fill the participation claim form. To check your participation points, fill the self-check form.
For both the programming assignments and final project, you're free to work alone, but you're also allowed (and indeed encouraged) to work in teams. This means developing ideas together, writing code together, and submitting a joint report.
Ordinarily, all team members will receive the same grade for an assignment - though we reserve the right, in case of egregiously unequal contributions, to assign different grades to different team members. You can contact us in confidence in the event of unequal collaborations. Please ask if you have any questions about the collaboration policy.
A grading penalty will be applied to late programming assignments. We recognize that students may face unusual circumstances and require some flexibility in the course of the quarter; therefore each student will be granted a total of four free late (calendar) days to use as he or she sees fit. Once these late days are exhausted, any assignment turned in late will be penalized 10% per late day. Each 24 hours or part thereof that a assignment is late uses up one full late day.
Late days may be used for the final project report; however, no final project reports will be accepted after Monday 12/08/14.
When students collaborate on an assignment, and the assignment is submitted late, late days are deducted from each team member's balance. Altruistic team members are allowed to "donate" late days to a collaborator if they wish.
You should not look for programming assignment answers elsewhere. If material is taken from elsewhere, then you should acknowledge it. For programming assignments, you are not permitted to get programming help from people other than your partner. Normally, you are permitted to use pre-existing code, but you must acknowledge code that you have taken from other sources. In general, it is appropriate to make use of libraries, etc. for the final project, as needed, but it is normally not appropriate to use code from others in the programming assignments, except for ancillary functions or extra credit investigations. In these and other respects, we will act and expect you to act according to the Stanford Honor Code.
If you feel you deserved a better grade on an assignment, you may submit a regrade request in writing to the TA responsible. Your request should briefly summarize why you feel the original grade was unfair. Your TA will take a day or two to reevaluate your assignment, and then issue a decision. If you're still not satisfied, you can then appeal (again, in writing) to the course instructor, Chris Manning.
Note that in regrading an assignment, we may reevaluate any part of it, not just the part you bring to our attention.
Students who may need an academic accommodation based on the impact of a disability must initiate the request with the Office of Accessible Education (OAE). Professional staff will evaluate the request with required documentation, recommend reasonable accommodations, and prepare an Accommodation Letter for faculty dated in the current quarter in which the request is being made. Students should contact the OAE as soon as possible since timely notice is needed to coordinate accommodations. The OAE is located at 563 Salvatierra Walk (650-723-1066, http://studentaffairs.stanford.edu/oae).
If you're doing the class credit/no credit then there are no special changes to the workload versus people registered for a grade. You are graded on work as usual, per standard Stanford rules. The only difference is that providing you reach a C- standard in your work, it will simply be graded as CR. (So maybe you can take it a little bit easier.)