Computers have revolutionized modern biological research, by providing biologists with the means to manage and analyze the large amounts of data generated through high-throughput experiments. This course provides a practical introduction to the main algorithms, databases, and tools used in bioinformatics, at the same time providing insight into the biological problems being addressed.
Many of the techniques you learn in this course are applicable beyond the bioinformatics domain and are relevant to other data-driven fields of computer science.
No knowledge of biology is required for this course.
Instructor: Max Leiserson (email@example.com)
Instructor office: IRB 3244
Instructor office hours:
Thursdays in IRB 3244 with alternating times or by appointment
1st/3rd/5th Thursday of the month (e.g. Feb 7): 11am-12pm
2nd/4th Thursday of the month (e.g. Feb 14): 1pm-2pm
TA office hours: Mon 10-11am, Fri 2-3pm, AV Williams 4101/4103
Class Location: Edward St. John 2204
Class Days/time: Tue/Thu 9:30-10:45am
Friday 2/8 - Last day to drop without a W
Tuesday 3/5 - Midterm 1 (in class, regular time)
Sunday 3/10 - Daylight Savings Time begins (reset your clocks and check smoke detectors)
Sunday 3/17-3/24 - Spring Break (no class)
Tuesday 4/9 - Midterm 2 (in class, regular time)
Friday 5/17 - FINAL EXAM 8-10am (same classroom)
Both volumes of the second edition of the textbook are REQUIRED for the course. It is available at the University Bookstore - http://umcp.bncollege.com
The second editions also used to be available through the following link for less money, but that seems no longer to be the case: http://bioinformaticsalgorithms.com/
- Translate a biological problem into an algorithm and a software implementation
- Learn algorithmic strategies for processing strings of letters (also relevant beyond computational biology)
- Learn about biomedical questions of current relevance
- Learn to work in teams
See: Resource page, which includes links to slides from each class.
A full list of University policies governing undergraduate classes is available here: http://www.ugst.umd.edu/courserelatedpolicies.html . Please also read carefully all the information below.
Grading (see below for details)
- Quizzes/in class participation - 15%
- Programming projects - 25%
- Two in-class midterms - 30% (15% each)
- In-class final - 30%
You can submit up to 2 programming assignments up to 2 days late without any penalty. All other programming assignments received late will incur a 10% penalty for up to 2 days, after which no credit will be given. Note that the due date on Rosalind will be for the LATE submission deadline i.e., 2 days after the true submission deadline in ELMS.
For all other assignments (reading quizzes, exit tickets, etc.) no late submissions are allowed. Instead, the lowest 5 scores will be discounted when computing your grade.
Please notify me in advance if you will miss any exam due to a University sanctioned excuse (medical absence, religious observance, etc.). In case of sudden illness that causes you to miss an exam you must provide me with a medical note documenting the illness, and clearly specifying the days/times that you were incapacitated due to illness.
Part of the class grade is participation/quizzes. Reasonable absences will be accommodated when grading - please inform me in advance if you will miss a class. Please see here: https://faculty.umd.edu/teach/attend_student.html and below for further details.
Any student who needs to be excused for an absence from a single lecture, recitation, or lab due to a medically necessitated absence shall:
- Make a reasonable attempt to inform the instructor of his/her illness prior to the class.
- Upon returning to the class, present their instructor with a self-signed note attesting to the date of their illness.
Each note must contain an acknowledgment by the student that the information provided is true and correct. Providing false information to University officials is prohibited under Part 10(j) of the Code of Student Conduct (V-1.00(B) University of Maryland Code of Student Conduct) and may result in disciplinary action.
The self-documentation may not be used for exams (midterm or final) and it may be used for only 2 non-consecutive class meetings during the semester. Any student who needs to be excused for a prolonged absence (2 or more consecutive class meetings), or for an exam, must provide written documentation of the illness from the Health Center or from an outside health care provider. This documentation must verify dates of treatment and indicate the time frame during which student was unable to meet academic responsibilities. In addition, it must contain the name and phone number of the medical service provider to be used if verification is needed. No diagnostic information will ever be requested.
Late arrival. Late arrivals to class are very disruptive. If you will be more than five minutes late to class, you will be required to sign in and will not receive credit for any in-class participation.
You must notify me within 2 weeks from the beginning of class if you will miss a class or exam due to a religious observance. Requests received after two weeks will not be accommodated. Please check university policies from the following 2 links.
Accommodations for disabilities
You must notify me within 2 weeks from the beginning of class if you require special accommodations due to disabilities. All such requests must be accompanied by documentation from the Accessibility and Disability Service. Requests received after this deadline will not be accommodated.
Communication is key
Please participate in Piazza discussions, interact with your colleagues, and contact the instructors and the TA if you have questions or concerns.
For general questions about class materials and discussion use Piazza.
To contact the instructors and TA directly, please use ELMS rather than our individual emails. This ensures that all emails are recorded and associated with the course, and also that no emails get lost in spam folders or the general email deluge that we are often faced with.
Simply put: cheating will not be tolerated under any circumstance. While you are allowed to prepare for assignments together, you must complete all individual assignments by yourselves. Also, all exams are strictly individual.
In particular, the code you submit to Rosalind must be your own. We will run plagiarism detection software, and we are well aware of the various code floating around github and other online forums.
Further information on academic integrity is available here: http://www.cs.umd.edu/class/resources/academicIntegrity.html .
IMPORTANT: A large number of academic dishonesty cases are due to students in their final year. The fact that you just need a few more credits to graduate is not an excuse. Cheating and plagiarism have led to students failing to graduate, and also for diplomas to be revoked retroactively. I will refer all cases of academic dishonesty directly to the Office of Student Conduct. In other words - I will not provide you the opportunity to "make a deal" or provide an excuse.
Prior to each class you will have to complete a quiz that tests that you have prepared for the class (read material, watched videos, etc.) These quizzes will not test that you fully understand the material, just that you have done your due diligence in preparing. I anticipate there will be about 20 such quizzes.
Each reading quiz submitted on time counts as 1 point. To get this point you must answer more than half of the questions correctly. For example, if the quiz has 6 questions and you answer 4 correctly you get the point, but if you answer only 3 you do not.
Class participation and in-class activities
In-class time will be split between approximately 75% lecture and 25% in-class activities. In-class activities will be completed in small teams, and teams will be assigned at the beginning of class. Each team will submit their answers through an online system (e.g. Socrative). These answers will not be graded, but will be used to identify which topics are clear or need more attention, and to keep track of in-class participation. After each team has submitted an answer, we will then reconvene to discuss as a whole class.
During lectures and in-class activities, I will call on random students to encourage everyone to participate, not just those who sit in front. For in-class activities, I will give you some time to think and discuss with your team before I pick on you - i.e., I'm not going to try to trip you up with questions for which you cannot possibly know the answer. I will, however, record whether the answer was satisfactory - not necessarily correct, but demonstrating that you were paying attention and participating. These records will also be taken into account when I decide the final grade in the class.
See http://www.umd.edu/emergencypreparedness for more information.
If you are sick, don't come to class - no need to get others sick.
Please report sickness on http://grades.cs.umd.edu and through ELMS to the instructors.
The syllabus page shows a table-oriented view of the course schedule, and the basics of course grading. You can add any other comments, notes, or thoughts you have about the course structure, course policies or anything else.
To add some comments, click the "Edit" link at the top.