This is just a place to keep track of notes and suggestions for things to add/substract or change, based on feedback etc..
-
Should we do (like 708) a one hour lecture and 2 hour tutorial (across two days)
-
Definitely need to have this formally scheduled as the number of students is too great.
-
More introduction to sed and awk for manipulating simple text files.
- Maybe reformating and selecting a few columns from BED and GTF files as an example.
-
Process managements (to go along with submitting long jobs and shell scripts).
- Did BG introduce
screen
ortmux
in 2018?
- Did BG introduce
-
More command line tools for genomics
seqtk
,bioawk
,samtools
,bedtools
,tabix
. I think we only barely usedfastQC
,trimmomatic
andbwa
-
More on common genomics file formats?
This does not include every suggestion that was made to Brian and Ian, but the subset of realistic ones to consider. Some (allowing groups to work on individual assignments) are not sensible for the class model we are using. Even still I am not sure all suggestions are feasible for this graduate class, but here is the list.
-
DataCamp assignments. Too many? Some way to make at least some optional like we did at the end.
-
More timely feedback.
-
Slow down on the fundamentals, with more detailed examples or in class problems.
- i.e. fundamentals of computational thinking, not just practical skills.
-
More detailed course outline.
-
More consistent assignment schedule
-
Specific office hours.
-
Use coloured cards for in class help (one colour for technical help, a different colour for help help.)
-
Some felt it was too much content this year. However, we actually went slower than in previous years. Given that this is effectively a remedial computational skills class, I am not sure I would advise this.