2 During The Research » History » Version 1
Steve Welburn, 2012-08-22 03:41 PM
1 | 1 | Steve Welburn | h1. WP1.2 Online Training Material |
---|---|---|---|
2 | 1 | Steve Welburn | |
3 | 1 | Steve Welburn | {{>toc}} |
4 | 1 | Steve Welburn | |
5 | 1 | Steve Welburn | We consider three stages of a research project, and the appropriate research data management considerations for each of those stages. The stages are: |
6 | 1 | Steve Welburn | * before the research; |
7 | 1 | Steve Welburn | * during the research; |
8 | 1 | Steve Welburn | * at the end of the research. |
9 | 1 | Steve Welburn | |
10 | 1 | Steve Welburn | {{include(Before The Research)}} |
11 | 1 | Steve Welburn | |
12 | 1 | Steve Welburn | h2. During The Research |
13 | 1 | Steve Welburn | |
14 | 1 | Steve Welburn | During the course of a piece of research, data management is largely risk mitigation - it makes your research more robust and allows you to continue if something goes wrong. |
15 | 1 | Steve Welburn | |
16 | 1 | Steve Welburn | The two main areas to consider are: |
17 | 1 | Steve Welburn | * [[backing up]] research data - in case you lose, or corrupt, the main copy of your data; |
18 | 1 | Steve Welburn | * [[documenting data]] - in case you need to to return to it later. |
19 | 1 | Steve Welburn | |
20 | 1 | Steve Welburn | In addition to the immediate benefits during research, applying good research data management practices makes it easier to manage your research data at the end of your research project. |
21 | 1 | Steve Welburn | |
22 | 1 | Steve Welburn | We have identified three basic types of research projects, two quantitative (one based on new data, one based on a new algorithm) and one qualitative, and consider the data management techniques appropriate to those workflows. More complex research projects may required a combination of the techniques from these. |
23 | 1 | Steve Welburn | |
24 | 1 | Steve Welburn | h3. Quantitative research - New Data |
25 | 1 | Steve Welburn | |
26 | 1 | Steve Welburn | For this use case, the research workflow involves: |
27 | 1 | Steve Welburn | * creating a new dataset |
28 | 1 | Steve Welburn | * testing outputs of existing algorithms on the dataset |
29 | 1 | Steve Welburn | * publication of results |
30 | 1 | Steve Welburn | |
31 | 1 | Steve Welburn | |
32 | 1 | Steve Welburn | The new dataset may include: |
33 | 1 | Steve Welburn | * Selection or creation of underlying (audio) data (the actual audio may be in the dataset or the dataset may reference material - e.g. for [[Copyright|copyright]] reasons) |
34 | 1 | Steve Welburn | * creation of ground-truth annotations for the audio and the type of algorithm (e.g. chord sequences for chord estimation, onset times for onset detection) |
35 | 1 | Steve Welburn | |
36 | 1 | Steve Welburn | The content of the dataset will need to be [[documenting data|documented]]. |
37 | 1 | Steve Welburn | |
38 | 1 | Steve Welburn | Data involved includes: |
39 | 1 | Steve Welburn | * [[Managing Software As Data|software]] for the algorithms |
40 | 1 | Steve Welburn | * the new dataset |
41 | 1 | Steve Welburn | * identification of existing datasets against which results will be compared |
42 | 1 | Steve Welburn | * results of applying the algorithms to the dataset |
43 | 1 | Steve Welburn | * documentation of the testing methodology - including algorithm parameters |
44 | 1 | Steve Welburn | |
45 | 1 | Steve Welburn | Note that *if* existing algorithms have published results using the same existing datasets and methodology, then results should be directly comparable between the published results and the results for the new dataset. In this case, most of the methodology is already documented and only details specific to the new dataset need separately recording. |
46 | 1 | Steve Welburn | |
47 | 1 | Steve Welburn | If the testing is scripted, then the code used would be sufficient documentation during the research - readable documentation only being required at publication. |
48 | 1 | Steve Welburn | |
49 | 1 | Steve Welburn | h3. Quantitative research - New Algorithm |
50 | 1 | Steve Welburn | |
51 | 1 | Steve Welburn | bq. A common use-case in C4DM research is to run a newly-developed analysis algorithm on a set of audio examples and evaluate the algorithm by comparing its output with that of a human annotator. Results are then compared with published results using the same input data to determine whether the newly proposed approach makes any improvement on the state of the art. |
52 | 1 | Steve Welburn | |
53 | 1 | Steve Welburn | Data involved includes: |
54 | 1 | Steve Welburn | * [[Managing Software As Data|software]] for the algorithm |
55 | 1 | Steve Welburn | * An annotated dataset against which the algorithm can be tested |
56 | 1 | Steve Welburn | * Results of applying the new algorithm and competing algorithms to the dataset |
57 | 1 | Steve Welburn | * Documentation of the testing methodology |
58 | 1 | Steve Welburn | |
59 | 1 | Steve Welburn | Note that *if* other algorithms have published results using the same dataset and methodology, then results should be directly comparable between the published results and the results for the new algorithm. In this case, most of the methodology is already documented and only details specific to the new algorithm (e.g. parameters) need separately recording. |
60 | 1 | Steve Welburn | |
61 | 1 | Steve Welburn | Also, if the testing is scripted, then the code used would be sufficient documentation during the research - readable documentation only being required at publication. |
62 | 1 | Steve Welburn | |
63 | 1 | Steve Welburn | h3. Qualitative research |
64 | 1 | Steve Welburn | |
65 | 1 | Steve Welburn | An example would be using interviews with performers to evaluate a new instrument design. |
66 | 1 | Steve Welburn | |
67 | 1 | Steve Welburn | The workflow is: |
68 | 1 | Steve Welburn | * Gather data for the experiment (e.g. though interviews) |
69 | 1 | Steve Welburn | * Analyse data |
70 | 1 | Steve Welburn | * Publish data |
71 | 1 | Steve Welburn | |
72 | 1 | Steve Welburn | Data involved may include: |
73 | 1 | Steve Welburn | * the interface design |
74 | 1 | Steve Welburn | * Captured audio from performances |
75 | 1 | Steve Welburn | * Recorded interviews with performers (possibly audio or video) |
76 | 1 | Steve Welburn | * Interview transcripts |
77 | 1 | Steve Welburn | |
78 | 1 | Steve Welburn | The research may also involve: |
79 | 1 | Steve Welburn | * Demographic details of participants |
80 | 1 | Steve Welburn | * Identifiable participants (Data Protection]) |
81 | 1 | Steve Welburn | * Release forms for people taking part |
82 | 1 | Steve Welburn | |
83 | 1 | Steve Welburn | and *will* involve: |
84 | 1 | Steve Welburn | * ethics-board approval |