18 |
19 | |
26 | 27 | |
28 |
|
32 | 33 | CS 224N / Ling 284 — 34 | Natural Language Processing 35 | 36 | |
37 |
| 41 | 61 | | 62 |
|
16 |
17 |
18 |
19 | |
20 |
21 |
22 |
|
66 |
67 |
71 |
72 |
73 |
74 |
75 | |
80 |
81 | 82 | This page describes assignments and grading policies for CS224N / Ling 284: 83 |
103 | Grading104 | 105 |106 | Course grades will be based 60% on the three programming assignments (20% each), 34% on the final project, and 6% on the quizzes (0.33% for 109 | each). 110 | 111 | 112 | 113 | 114 | 115 | 116 |117 | Quizzes118 | 119 |120 | During each class, a question will be asked in class, related to the 121 | topics covered that day. The response to each question determines 122 | 0.33% of your final grade, totaling to 6% over all 18 lectures 123 | scheduled for this quarter. Use the quiz submission script at Quiz Submissions. 124 | 125 |126 | The responses for any week's classes must reach the course staff by 127 | 5pm on the following Sunday. (E.g., responses to the questions asked 128 | in class on Monday 1/10/11 and/or Wednesday 1/12/11 must reach the 129 | course staff by 5pm on Sunday 1/16/11). 130 | 131 |132 | Programming Assignments133 | 134 |135 | There will be three substantial programming assignments, each 136 | exploring a core NLP task. 137 | 138 | 139 |
194 | Final Project195 | 196 |197 | In addition, there will be a final programming project on a topic of 198 | your own choosing. See the final 200 | project guide for more information. 201 | 202 | 203 |204 | A short, ungraded project proposal will be due on Wednesday 2/9/11. 205 | Final project write-ups will be due on Wednesday 3/9/11. Students will 206 | give short project presentations on Thursday 3/17/11, from 12:15pm to 207 | 3:15pm. 208 | 209 | 210 |211 | You may find it helpful to look at final projects from 213 | previous years. 214 | 215 | 216 | 217 | 218 | 219 |220 | Collaboration Policy221 | 222 |223 | For both the programming assignments and final project, you're free 224 | to work alone, but you're also allowed (and indeed encouraged) to 225 | work in teams. This means developing ideas together, writing code 226 | together, and submitting a joint report. 227 | 228 | 229 |
241 | However, if you collaborate, your submission must include a 242 | statement describing the contributions of each collaborator. 243 | For example, "We did the entire project as pair programming over 244 | several late nights in our dorm rooms". Or, "Sue built the initial 245 | parser, while Joe worked on improving parse quality through the use 246 | of features and on improving runtime speed by profiling." 247 | 248 | 249 |250 | Ordinarily, all team members will receive the same grade for an 251 | assignment—though we reserve the right, in case of egregiously 252 | unequal contributions, to assign different grades to different team 253 | members. 254 | 255 | 256 |257 | Please ask if you have any questions about the collaboration 258 | policy, and make sure you adhere to it. 259 | 260 | 261 | 262 | 263 | 264 |265 | Electronic Submission266 | 267 |268 | For each programming assignment and for the final project, you'll 269 | submit your program using a Unix script that we've prepared. 270 | To submit your program, first put all the files to be submitted in 271 | one directory on a Leland machine (or any machine from which you 272 | can access the Leland AFS filesystem). This should include all 273 | source code files, but should not include compiled class files or 274 | large data files. Normally, your submission directory will have a 275 | subdirectory named src which contains all your source 276 | code. When you're ready to submit, type: 277 | 278 | 279 |280 | /afs/ir/class/cs224n/bin/submit-pa1 281 |282 | 283 | 284 | (Or submit-pa2, or submit-pa2, or 285 | submit-fp, as appropriate.) This will (recursively) copy 286 | everything in your submission directory into the official 287 | submission directory for the class. If you need to resubmit it 288 | type 289 | 290 | 291 |292 | /afs/ir/class/cs224n/bin/submit-pa1 -replace 293 |294 | 295 | 296 | We will compile and run your program on the Leland systems, using 297 | ant and our standard build.xml to compile, and 298 | using java to run. So, please make sure your program 299 | compiles and runs without difficulty on the Leland machines. If 300 | there's anything special we need to know about compiling or running 301 | your program, please include a README file with your 302 | submission. Your code doesn't have to be beautiful but we should 303 | be able to scan it and figure out what you did without too much 304 | pain. 305 | 306 | 307 | 308 | 309 |310 | Late Day Policy311 | 312 |313 | All assignments are due at 5pm on the assigned due date. A grading 314 | penalty will be applied to late assignments. We recognize that 315 | students may face unusual circumstances and require some 316 | flexibility in the course of the quarter; therefore each student 317 | will be granted a total of 318 | five free late (calendar) days to use as he or she sees 319 | fit. Once these late days are exhausted, any assignment turned in 320 | late will be penalized 10% per late day. Each 24 hours or part 321 | thereof that a assignment is late uses up one full late day. 322 | 323 | 324 |325 | Late days may be used for the final project report; however, no 326 | final project reports will be accepted after 327 | Monday 3/14/11. 328 | 329 | 330 |
331 | To hand in the report late, there is a hand-in box in the basement of Gates, near the bottom of the A-wing stairwell.
332 | You can find directions to it here. To get into the basement after the building is locked,
333 | slide your SUID card in the card reader by the main basement entrance. For code submitted late,
334 | please write the date and time of submission on your report and sign it before placing it in the box.
335 |
336 | 340 | When students collaborate on an assignment, and the assignment is 341 | submitted late, late days are deducted from each team member's 342 | balance. Altruistic team members are allowed to "donate" late days 343 | to a collaborator if they wish. 344 | 345 | 346 | 347 | 348 |349 | Regrading requests350 | 351 |352 | If you feel you deserved a better grade on an assignment, you may 353 | submit a regrade request in writing to the TA responsible. 354 | Your request should briefly summarize why you feel the original 355 | grade was unfair. Your TA will take a day or two to reevaluate 356 | your assignment, and then issue a decision. If you're still not 357 | satisfied, you can then appeal (again, in writing) to 358 | the course instructors, Bill MacCartney and Prof. Gerald Penn. 359 | 360 | 361 |362 | Note that in regrading an assignment, we may reevaluate any part 363 | of it, not just the part you bring to our attention. 364 | 365 | 366 | |
| 368 | |
|
382 | 383 | | 384 |
385 | 386 | Site design by Bill MacCartney 387 | 388 | |
389 |