Purdue University - Spring 2016
CS 54701: Information Retrieval
Days: Tuesday Thursday 3:00 - 4:15 pm
Credit Hours: 3
Classroom: Wang Hall 2555
Instructor: Chris Clifton (LWSN 2142F) 765-494-6005
email@example.com (LWSN 2149#5)
Introduction to Information Retrieval. Manning, C.; Raghavan, P.; Schütze, H. Cambridge University Press (2008).
The following also are worthwhile resources:
Search Engines: Information Retrieval in Practice. Croft, W. Bruce; Metzler, Donald; Strohman, Trevor. Addison Wesley (2008)
Information Retrieval: Implementing and Evaluating Search Engines, Stefan Buettcher, Charles L. A. Clarke, Gordon V. Cormack. MIT Press. (2010)
Modern Information Retrieval, Ricardo Baeza-Yates and Berthier Ribeiro-Neto, Addison-Wesley, (1999)
Midterm Exam (20%)
Final Exam (25%)
Written assignments (3-4) and programming projects (5-6) (20%)
Self-directed final project (25%)
Evaluation of instructors based on in-class contributions, discussions / email / Piazza communications, and overall performance (5%)
Exams will be open note / open book. To avoid a disparity between resources available to different students, electronic aids are not permitted.
Late work will be penalized 10% per day (24 hour period). This penalty will apply except in case of documented emergency (e.g., medical emergency), or by prior arrangement if doing the work in advance is impossible due to fault of the instructor (e.g., you are going to a conference and ask to start the project early, but I don't have it ready yet.)
Blackboard will be used to record/distribute grades (and, in some cases, for turning in assignments.)
The qualifying exam will consist of an hour-long supplement given at the end of the course. Passing the qualifier will require both suitable performance in the course and on the qualifying exam. All computer science students are encouraged to take the exam, even if you do not currently plan to pursue a Ph.D.
Policy on Intellectual Honesty
Please read the departmental academic integrity policy above. This will be followed unless I provide written documentation of exceptions. You may also find Professor Spafford's course policy(http://spaf.cerias.purdue.edu/cpolicy.html) useful - while I do not apply it verbatim, it contains detail and some good examples that may help to clarify the policies above and those mentioned below.
In particular, I encourage interaction: you should feel free to discuss the course with other students. However, unless otherwise noted work turned in should reflect your own efforts and knowledge.
For example, if you are discussing an assignment with another student, and you feel you know the material better than the other student, think of yourself as a teacher. Your goal is to make sure that after your discussion, the student is capable of doing similar work independently; their turned-in assignment should reflect this capability. If you need to work through details, try to work on a related, but different, problem.
If you feel you may have overstepped these bounds, or are not sure, please come talk to me and/or note on what you turn in that it represents collaborative effort (the same holds for information obtained from other sources that you provided substantial portions of the solution.) If I feel you have gone beyond acceptable limits, I will let you know, and if necessary we will find an alternative way of ensuring you know the material. Help you receive in such a borderline case, if cited and not part of a pattern of egregious behavior, is not in my opinion academic dishonesty, and will at most result in a requirement that you demonstrate your knowledge in some alternate manner.
Click the Edit button to add class information.
You have the option of deleting this announcement from just the course homepage or deleting this announcement from the course homepage and Q&A feed. What would you like to do?
You'll lose everything you typed, plus all the time it took to type it...