Teaching basic lab skills
for research computing

Summary of June 2014 Lab Meeting

At our monthly lab meeting yesterday (June 26), we discussed a wide range of topics (though only about half as much as was on the agenda). Details notes and votes are below; the key points are:

  1. We would like to do what we can to help the careers of people who volunteer for Software Carpentry. In particular, we'd like to find a way to highlight people who have taught lots of bootcamps, contributed lots of material, or both, without discouraging people who haven't, or getting into a situation in which bootcamp hosts ask, "Why aren't you sending your most experienced people to us?" We've opened a GitHub issue for people who'd like to discuss this topic, and we'd be grateful if you could share experiences with other systems and suggestions about what we could do.
  2. We will have a meeting on Thursday, July 3 to discuss plans for the July 22-23 sprint. The time and connection details will be posted here on July 2.
  3. People were either neutral or in favor of switching to Python 3. There was concern about compatibility, but it seems that most scientific packages are now Py3-compatible (and that there are some that only work with Py3, and not with Py2). In practice, this will mean:
    • changing what people have on their machine when they leave the bootcamp, and
    • minor modifications to our lessons (e.g., print as a function).
  4. By default, Mercurial launches a GUI diff/merge tool when there's a conflict rather than displaying a textual diff. Novices seem to find side-by-side merge easier to work with, which raises the question: should we use a graphical tool for diff and merge when teaching Git as well? Again, most people were either neutral or in favor, subject to ease of installation. We'll try this at a couple of workshops in the coming months and report back.
  5. Should we install Matt Davis's ipythonblocks module by default? Nobody was opposed, but it turned out that only a handful of people actually use it in teaching. We'll poll our instructors to find out more about usage before making a final decision.
  6. In order to make it easy for people who want to teach regular expressions to do so, we'll integrate the software that runs regexpal.com (which ironically is down at the time of this writing) into the bc repo so that instructors can create a page in their bootcamp site where learners can play around.
  7. Jonah Duckles has created a pull request that would change the way installation instructions are managed. Instead of editing _includes/setup.html, instructors would add a list of topics to the header of index.html that Jekyll's templating logic would use to control what is and isn't displayed. Most people were in favor, so we'll merge this once the PR is finished.
  8. Many people are still not happy with the way our lesson materials are organized, or with what pre-requisite knowledge we actually expect. We will organize a meeting for next Thursday (July 3) to talk about options, then open a discussion issue on GitHub if we can come up with concrete alternatives.
  9. Raniere Silva has been working over the last few weeks to generate EPUB and PDF from our materials. The goal is to allow anyone who wants to produce book-form notes to do so for use in a regular class, to give to learners after a bootcamp, or for self-study. He's been making good progress, but there are still lots of small problems (particularly with the PDF). We'll be hacking on this at the sprint.


Attendees (Second Round)

  • Greg Wilson (Mozilla, Toronto)
  • Gabriel Devenyi (McMaster, Hamilton, @staticwave_ace)
  • Matt Davis (Synthicity, Berkeley (@jiffyclub))
  • Jeramia Ory (King's College, PA @DrLabRatOry)
  • Jens von der Linden (University of Washington, Seattle)
  • Kwasi Kwakwa (Imperial College London)
  • Xu Fei (New York, NY)
  • Jeremiah Lant (Louisville, Kentucky)
  • Christian Jacobs (Imperial College London, UK)
  • Erika Mudrak (Cornell, Ithaca @ErikaMudrak)
  • Bernhard Konrad (Vancouver, BC)
  • Tim McNamara (Auckland, NZ)
  • Aron Ahmadia (Washington, D.C.)
  • Chris Beitel (UC Davis; Eisen Lab; @datascimed)
  • Ben Marwick (U of Washington, Seattle, @benmarwick)
  • Katy Huff (UCBerkeley)
  • Damien Irving (University of Melbourne, Australia / @DrClimate)
  • Amanda Harlin (Uni of Oklahoma, @amandaharlin)

Attendees (First Round)

  • Raniere Silva (University of Campinas, São Paulo, Brazil
  • Rémi Emonet (University of Saint Étienne, France)
  • Jonah Duckles (University of Oklahoma, Norman, Oklahoma @jduckles)
  • Brian Northan
  • Pauline Barmby, (Western U, London Canada, @PBarmby)
  • Russell Alleen-Willems (Diachronic Design, Seattle, Washington, @DiachronicD)
  • Marios Isaakidis (@misaakidis)
  • Denis Haine (U of Montreal)
  • Ethan White (Utah State University / @ethanwhite)
  • Emily Davenport (University of Chicago)
  • Lex Nederbragt (University of Oslo)
  • Stephen Turner (University of Virginia, @genetics_blog)
  • Karin Lagesen (University of Oslo, @karinlag)
  • François Michonneau (University of Florida, @FrancoisInvert)
  • John Blischak (University of Chicago)
  • Brian Glanz (@openscience, Wash DC today)
  • Dana Bauer (Rackspace, Philadelphia)
  • Azalee Bostroem (Space Telescope Science Institute)
  • Sheila Miguez (Chicago, IL)
  • Abigail Cabunoc (OICR, @abbycabs)
  • Tracy Teal (@tracykteal)
  • Rob Davey (@froggleston - joined late!)
  • Amy Brown (@amyrbrown)



July 22-23 Sprint

  • Planning: https://etherpad.mozilla.org/swc-sprint-2014
  • Meet with hosts/project leaders/anyone else who's interested next Thursday (July 3) to talk details - if you're interested in being part of the meeting, please sign up below
    • Raniere Silva
    • Azalee Bostroem
    • François Michonneau
    • Brian Northan
    • Brian Glanz
    • Chris Beitel
    • Matt Davis
    • Amanda Harlin
    • Damien Irving
    • Tim McNamara
    • Xu Fei
    • Gabriel Devenyi
    • April Wright

Other Business

  • Google Hangouts/Helpouts

Volunteers/Reviewers Wanted (we didn't get to this because time ran out)

Dialogue & Discussion

Comments must follow to our Code of Conduct.