Wiki » History » Version 2
Version 1 (Luis Figueira, 2012-08-14 03:56 PM) → Version 2/14 (Redmine Admin, 2012-08-15 11:51 AM)
h1. Wiki
h2. Requirements
Third day of a three-day Software Carpentry bootcamp. Hours are 0900-1630 approx.
Should consist of working through introductory examples of audio processing techniques in Python, with small-group exercises for self-guided learning (helpers should be available in the room). Topics of interest should include reading audio data from files, synthesising signals and playing them, saving results back to audio files, simple filters, simple analysis techniques, and interactive plotting.
The material will need to follow from the subjects covered in the first two days of the bootcamp, such as unit testing and test-driven development, writing readable code, use of version control (we'll be using Mercurial in the bootcamp but the principles should mostly be general ones), selection and use of the most appropriate existing Python modules, etc.
h2. Related Links
* Bootcamp announcement: http://soundsoftware.ac.uk/york2012-bootcamp
* Software carpentry site: http://software-carpentry.org
* Audio Presentation (Becky's): http://software-carpentry.org/4_0/media/audio/
h2. Open questions
Can we come up with some good examples of simple audio processing problems that readily admit test-driven solutions? I think there will be a lot of interest in the question of how to apply automated testing and unit tests to audio research software.
h2. Requirements
Third day of a three-day Software Carpentry bootcamp. Hours are 0900-1630 approx.
Should consist of working through introductory examples of audio processing techniques in Python, with small-group exercises for self-guided learning (helpers should be available in the room). Topics of interest should include reading audio data from files, synthesising signals and playing them, saving results back to audio files, simple filters, simple analysis techniques, and interactive plotting.
The material will need to follow from the subjects covered in the first two days of the bootcamp, such as unit testing and test-driven development, writing readable code, use of version control (we'll be using Mercurial in the bootcamp but the principles should mostly be general ones), selection and use of the most appropriate existing Python modules, etc.
h2. Related Links
* Bootcamp announcement: http://soundsoftware.ac.uk/york2012-bootcamp
* Software carpentry site: http://software-carpentry.org
* Audio Presentation (Becky's): http://software-carpentry.org/4_0/media/audio/
h2. Open questions
Can we come up with some good examples of simple audio processing problems that readily admit test-driven solutions? I think there will be a lot of interest in the question of how to apply automated testing and unit tests to audio research software.