Course Catalog 2009-2010 Postgraduate Basic Pori International Postgraduate Open University |Degrees|     |Study blocks|     |Courses|

Implementation 1

Lecture times and places:

Per 2 :
Monday 10 - 12, TC303
Thursday 10 - 12, TC303

Description:

Student will learn basic programming skills with R. In addition, most often used packages provided by Bioconductor will be in use.

Person responsible:

Tommi Aho

Target groups:

DI-Opiskelijat
International Students
Jatko-opiskelijat
Kandiopiskelijat

Assessment scale:

Numerical evaluation scale (1-5) will be used on the course

Methods of instruction:

Methods of instruction	Hours
Lectures	30.0
Excercises	24.0

Methods of instruction	Hours
Bioinformatics and Computational Biology Solutions Using R and Bioconductor	10.0

Other measurings
Sum of all	64.0

Contact teaching: 30 %
Distance learning: 0 %
Proportion of a student´s independent study: 70 %

Additional information of course implementation:

Timetable: Week 44: chapters 1, 2 Week 45: chapters 3, 4 Week 46: chapters 5, 13 Week 47: chapters 6, 7, 8 Week 48: chapters 9, 10 Week 49: chapters 11, 12 INFORMATION ON THE CODING ASSIGNMENT (CODING EXAM): * The coding assignment will be on Friday 11.12.2009 at 9:00 - 12:00. The place is TC303. * For the second time, the coding assignment will be arranged on Tuesday 6.4.2010 at 9:00 - 12:00. The place is TC303. There is no need to register to this assignment in beforehand. * For the third (and last) time, the assignment will be arranged on Monday 30.8.2010 at 9:00 - 12:00. The place is TC303. Register to the assignment by sending an email to tommi.aho@tut.fi on Monday 23.8.2010 at latest. * Basic mathematical skills are required but nothing will go deeper into statistics. There will be no tasks which require understanding about biology. * You may use any material you like (printed, electronic, web). Only communication with other people is forbidden. * The assessment is based on (1) the correct result returned by the code, (2) the correct use of specific data structures and functions in tasks where those are asked, (3) clear coding style including enough comments and descriptive names for functions and variables (the code should be easy to read).