Biostatistics & Medical Informatics 576
Computer Sciences 576
Introduction to Bioinformatics (Fall 2017)

General Course Information
Course overview
Syllabus, Readings, Lecture Notes
Homework Assignments
Grading criteria

Homework Assignments

  • HW0: Due Tuesday, September 19th by 11:59pm
  • HW1: Due Thursday, October 5th by 11:59pm
  • HW2: Due Thursday, October 19th by 11:59pm
  • HW3: Due Thursday, October 26th by 11:59pm
  • HW4: Due Wednesday, November 22th by 11:59pm
  • HW5: Due Wednesday, December 6th by 11:59pm
  • HW6: Due Friday, December 15th by 11:59pm. No late days.
Programming assignment policies:
  • C, C++, Java, Perl and Python are the preferred programming languages for the homework assignments. If you want to use R or Matlab, make sure that the TA can run your code on the biostat servers.
  • No third-party libraries may be used. Only the standard library for the chosen language may be used.
  • Code must compile and run on the biostat servers (Linux).
Written assignment policies:
  • Written assignments and problems are also to be submitted electronically in the appropriate "handin" directory.
  • We strongly recommend that written problems be written up in a word processing program and graphics be created by computer.
Homework submission policies:
  • Homeworks are due at midnight on the due date.
  • Homeworks should not be emailed to the instructor.
  • Each student has five free late days to use during the semester. Once these are exhausted, late homeworks will be penalized 10 points per day.
  • Each day counts as a late day (e.g., if the HW is due on Friday and you turn it in the following Monday, it is 3 days late).
  • Issues related to homework/grades must be resolved within 1 week of distribution of grades.
  • No homeworks will be accepted more than five days late.

Academic Misconduct:
All examinations, programming assignments, and written homeworks must be done individually. Cheating and plagiarism will be dealt with in accordance with University procedures (see the Academic Misconduct Guide for Students). Hence, for example, code for programming assignments must not be developed in groups, nor should code be shared. You are encouraged to discuss with your peers, the TAs or the instructor ideas, approaches and techniques broadly, but not at a level of detail where specific implementation issues are described by anyone. If you have any questions on this, please ask the instructor before you act.