Scientific Software Club at Cornell

The Problem

1. No explicit training in
   • Scientific software best practices
   • Modern software to make science easier
2. No community to learn this independently!

Community of Practice

Community of Practice

• Promotes common tech / practices in a domain
• Supports
  • Newcomer training
  • Dissemination of knowledge
  • Ongoing development of expertise
• We need both novices and "old hands" involved

Potential models

• The Hacker Within
• Mozilla Science Study Groups
• Software Carpentry

Potential models

• Formats
  • Ordinary courses
  • Short bootcamp/workshop
  • Club/meetup
• We are the last, can organize/sync with others!

Logistical details

• We are a Cornell club
• Initial officers: David Eriksson, Stephen McDowell, Eric Lee
• Initial advisor: David Bindel
• We need you to enroll to justify resources (aka pizza)!
• We are still working on constitution and bylaws

Logistical details

• Requested mailing list: ssw-club-l@cornell.edu
• Meetings will be Mondays at 6
• We will probably move from Gates 122
• Have about 8 weeks of pizza funding for now

Logistical details

• Current resources for training
  • Totient cluster (local)
  • Google Cloud Platform
  • Amazon Web Services
• Working on
  • Microsoft Azure
  • Training accounts on DOE/NSF machines
  • Cornell local training

Short-term plans

• I posted plans for what I want
  • You may want something else!
• Short term
  • Today: Starting at the terminal
  • Next: Working with Git (+ totient login)