R Hackathon 1/Teleconferences

From Phyloinformatics
Revision as of 17:39, 15 November 2007 by Bco (talk)
Jump to: navigation, search

1st Teleconference 11/16/2007


  1. Welcome, review of purpose and general objectives (TJV)
  2. Outline of planning schedule ahead (HL)
  3. Priorities and subgroups so far identified (SK, BCO) Note that this is preliminary...
    • Original list
      • Analysis holes: Purvis
      • Visualization: Peter Cowan, need others!
      • Interface w/ C/C++ (large data sets): O'Meara, Meade
      • R to NCL/NEXUS: ?
      • Interface w/ Mesquite: Wayne Maddison,
      • Interfacing w/ CIPRES: Swofford, Holder?
      • Interfacing w/ other C programs: Pagel
      • Internal data representation: Paradis, someone who does gene tree/species trees?, Luke Harmon might be good - his work w/ time slices might challenge the model
      • Documenters/testers: Clements, Sam Price, Amy, others?
    • New list
      • Analysis holes: __
      • Visualization: Peter Cowan
      • Interface w/ C/C++: __
      • R to NCL/NEXUS: __
      • Interface w/ Mesquite: Wayne Maddison
      • Internal data representation: Paradis, someone who does gene tree/species trees?, Luke Harmon might be good - his work w/ time slices might challenge the model (I think this is a main goal of the workshop we should settle early, so that any new code will not need to be re-coded and all can help craft the standard. A subgroup can then work on converting existing packages or creating a conversion function/package ----Bco 16:39, 15 November 2007 (EST))
      • Clocking trees: Waddell, ?Swofford, ?Bell
      • Documenters/testers: Clements, Sam Price, Amy, others?

  1. Preparations (HL)
    • Lightning talks - purpose, topics, and presenters (These and bootcamps have been suggested, but have we decided to do them? Regarding lightning talks, my inclination would be for people to communicate that information (say, package overview, relevant package programming info, and package future) using the wiki: both the talks and the wiki are primarily text-based, so the info communicated could be the same, but the wiki 1) creates a permanent record of this information which we can refer to during the hackathon, 2) allows people to develop questions/start discussions over the course of weeks rather than 5 minutes, and 3) doesn't take time during the hackathon. But maybe we have decided to do lightning talks and I blocked it out? -- --Bco 14:53, 15 November 2007 (EST)) I think we should ask the participants tomorrow whether they think lightning talks and bootcamps would be useful to them or not --Sprice 15:19, 15 Nov. 07 EST
    • Bootcamps - purpose, needs, and presenters
    • Reading list - suggestions
    • Give list of functions, ideally with R-format help files, to be posted in the function spreadsheet. (Added by --Bco 14:57, 15 November 2007 (EST))
    • Converting data to internal formats using the datafiles available here, then posting this info to the wiki (Added by --Bco 15:00, 15 November 2007 (EST))
    • Other preparations we or others can facilitate or help with?
  2. Documentation & testing (SP, SK)
    • R vignette writing
      • Who has experience, and would be willing to help train the users? Examples to draw from?
      • Sweave - is it a good idea?
    • Collection of data for testing and validation
  3. Source code repository (or repositories) (HL)
    • Survey of current source code repository and versioning setup for participating packages
    • Assessing need for help with publicly accessible repository
    • Assessing need(s) for NESCent-run repository
    • Code branching needs
    • Other source code-related preparation needs
  4. IT logistics (HL)
    • Computers - will we need loaners?
    • Network access - will anyone need wired network?
    • File share needs
  5. Other homework?
  6. Q & A


Action Items: