Wiki¶

• Abstract for website

Topics we need to cover in the tutorial¶

Short form, e.g. for DAFx 90-min hands-off tutorial¶

Title: Pointers to more effective software and data in audio research
See also: DAFx2012 Workshop in private Management wiki

1. Motivation - Reproducible research
2. Software practice:
   • General good-practice overview (e.g. substance related to SWC "feedback loops")
   • Version control
   • Unit testing
   • Writing readable code
   • Working with others -- code reviews, pair programming etc
3. Data management
   • Why manage data ? Data as first-class research output
   • Documenting data
   • Licensing - why CC0
   • Backing up data - where ? how much ?
   • Archiving data
   • Publishing data
   • Planning data management
   • EPSRC principles
4. Software and data licences and copyright
5. Open access and open publication
   • Journal policies
6. Wrap up: Resources to review after the tutorial, links, handouts, etc

Timing breakdown

1. Motivation and introduction - Mark P - 15 mins?
2. Software - 30 mins?
   • Intro, best practices and how they hang together
   • Version control
   • Unit testing
   • Readable code + Working with others
3. Data management - 20 mins?
   • Intro, why manage data
   • The practice of it
   • Policy and principles
4. Software and data licences and copyright - 10 mins?
5. Open access, open publication, wrap up - 10 mins?
6. Q&A - 5 mins

Total 90 mins

Materials we already have, that we can draw from

• Data: Data management presentation from SoundSoftware 2012 (15 mins + questions)
• Data: Wiki material about planning and applying data management
• Data: Publication policies
• Motivation: SoundSoftware presentation from SoundSoftware 2012 (15 mins + questions)

Longer form, e.g. for ISMIR 3-hour hands-on tutorial¶

If we want to do hand-on data management, do we need a local server ? Do we use the C4DM test repository ? Would any users actually have any data to work with anyway ?

Things we must make¶

• Leaflets, handouts etc
  • What is version control? and why use it?
  • Unit testing and audio software
  • Data management and policy
  • Software licences and copyright