Some slides from a recent talk about genome assembly (and thoughts on evolving slide decks)

Last week I presented a talk about genome assembly at a UC Davis Bioinformatics Core workshop. The first time that I gave this talk, it concentrated almost exclusively on the the results from our Assemblathon 2 paper. In the handful of times that I've subsequently given this talk, it has always evolved:

  1. More background to better explain some of the more common terminology in this field
  2. Less detail about the specifics of the Assemblathon 2 results
  3. New information relating to the latest developments in sequencing and assembly
  4. Added an 'intermission' so I can explain why I think Next-generation sequencing must die

Even if I didn't add any new content to my talk, and even if I was giving the same talk twice in the same week, I would still almost certainly change some aspect of my presentation. Here are some reasons for why I often end up changing things:

  1. Things which seemed like a good idea when planning and making slides, don't always work as well in front of an actual audience. Sometimes this might be unnecessary detail which slows things down, or it might be something which is no longer as relevant (or exciting) as when you first gave a talk on this topic.
  2. Inevitably there will be some parts of my talk which don't flow as well as others. Sometimes I will switch the order of sections, or drop sections altogether.
  3. If people ask me questions during the talk, then this is often because something is unclear. I try to make mental reminders about this, as it might mean that there is something I can better explain.
  4. Some visual elements will look great on my screen, and even on certain projectors, but then I will give a talk somewhere where a different projector makes a slide look horrible. Most common it will be when two colors end up looking far too similar. Always a good idea to change things so that they look clear on any projector.
  5. If I know that the audience for a talk may contain many people that don't speak English as their primary language, I might add more text content on key slides.
  6. A final reason for changing content is just to keep your talk fresh. It's possible that you become stale when you give the exact same talk over and over again. Changing the order of sections, or adding/removing content, means that you have to re-engage with your own material.

But hey, enough of my yakking…here are the slides. Note that I include two versions; the first version doesn't have any notes (harder to follow as I often prefer to talk around what's on my slides). The second version has notes added below each slide (these notes try to capture the gist of what I talk about on each slide). Also, don't be alarmed by the high slide count, each animation step appears as a separate slide (so that you can almost capture all of the animated fun of a real Keith Bradnam presentation).



Designing a musical motif for the UC Davis Genome Center

Over the last month, I have spent much of my time helping to develop a new website for the UC Davis Genome Center (a site which will hopefully be launched very soon). In trying to bring the website into the modern era, I've been trying to set things up so that we can better promote any news that arises from the work of the talented faculty, staff, and students that we have.  

In particular, I'm keen to feature some video clips on the new site, and that made me think that we should have our own Genome Center 'ident' to use in any videos. Idents are a bit like stingers on radio stations, something that gives an audio signature that people might come to recognize (and maybe even like).

I have a smattering of music knowledge so I thought it might be fun to create something based on DNA. As there are four canonical DNA bases (A, C, G, and T), I thought that the musical motif should have four principle notes. I then decided to arrange the notes with musical intervals based on the intervals between the alphabet positions of A, C, G, and T. If you start this sequence on a C note, you end up with C, D, F# and G (one octave up). This progression feels like it needs to be resolved, and a basic G major chord seems to work.

So this is what I have come up with so far. This may end up being vetoed by the powers-that-be, but I'm still pretty happy with it:

Update: just to add that this piece was made entirely using GarageBand on my Mac. There are: three tracks that use Classic Electric Piano (I was using the onscreen keyboard which is why I ended up doing these as three separate tracks); one Tonewheel Organ track; one Upright Studio Bass track; one Classic Analog Pad track; and one String Ensemble track. The latter three tracks combine to form the final chord.