IDyOM Output » History » Version 1

Marcus Pearce, 2014-06-16 11:09 AM

1 1 Marcus Pearce
h1. IDyOM Output
2 1 Marcus Pearce
3 1 Marcus Pearce
{{>toc}}
4 1 Marcus Pearce
5 1 Marcus Pearce
When used with the <code>:output-path</code> argument, the <code>idyom</code> function writes the output of the modelling to a file. The format is *space-separated values* which can be read directly into software such as R, matlab and excel for further analysis. The output differs depending on the degree of detail requested with the <code>detail</code> argument. The following describes the rows and columns at each level of detail.
6 1 Marcus Pearce
7 1 Marcus Pearce
h2. detail = 3 (Note level)
8 1 Marcus Pearce
9 1 Marcus Pearce
Each line in the file represents a note in a composition and each column represents a property of that composition. The columns are:
10 1 Marcus Pearce
11 1 Marcus Pearce
*Database identifiers*
12 1 Marcus Pearce
13 1 Marcus Pearce
* dataset.id
14 1 Marcus Pearce
* melody.id
15 1 Marcus Pearce
* note.id
16 1 Marcus Pearce
* melody.name
17 1 Marcus Pearce
18 1 Marcus Pearce
*Musical properties of the event*
19 1 Marcus Pearce
20 1 Marcus Pearce
These correspond to the basic viewpoints listed in the [[List of viewpoints]].
21 1 Marcus Pearce
22 1 Marcus Pearce
* articulation
23 1 Marcus Pearce
* comma
24 1 Marcus Pearce
* voice
25 1 Marcus Pearce
* ornament
26 1 Marcus Pearce
* dyn 
27 1 Marcus Pearce
* accidental
28 1 Marcus Pearce
* mpitch
29 1 Marcus Pearce
* phrase
30 1 Marcus Pearce
* bioi
31 1 Marcus Pearce
* deltast
32 1 Marcus Pearce
* barlength
33 1 Marcus Pearce
* pulses 
34 1 Marcus Pearce
* tempo 
35 1 Marcus Pearce
* mode 
36 1 Marcus Pearce
* keysig 
37 1 Marcus Pearce
* dur 
38 1 Marcus Pearce
* cpitch 
39 1 Marcus Pearce
* onset
40 1 Marcus Pearce
41 1 Marcus Pearce
*Properties of the model* 
42 1 Marcus Pearce
43 1 Marcus Pearce
There are columns representing the order used in predicting the event for each PPM model used in prediction. The column names are labelled according to the target basic viewpoint predicted by the model, the model type (stm or ltm) and the source viewpoint used for prediction (e.g., <code>cpitch.order.ltm.cpint-cpintfref</code>). 
44 1 Marcus Pearce
45 1 Marcus Pearce
There are columns representing the order used in predicting the event for each PPM model used in prediction. The column names are labelled according to the target basic viewpoint predicted by the model, the model type (stm or ltm) and the source viewpoint used for prediction (e.g., <code>cpitch.weight.ltm.cpint-cpintfref</code>). The weights for the STM/LTM combination are also recorded for each target viewpoint (e.g., <code>cpitch.weight.ltm</code> and <code>cpitch.weight.stm</code>).
46 1 Marcus Pearce
47 1 Marcus Pearce
*Output of the model*
48 1 Marcus Pearce
49 1 Marcus Pearce
There are columns representing the probability, information content and entropy estimated by the model for each target viewpoint predicted. For example,
50 1 Marcus Pearce
51 1 Marcus Pearce
* cpitch.probability
52 1 Marcus Pearce
* cpitch.information.content 
53 1 Marcus Pearce
* cpitch.entropy
54 1 Marcus Pearce
55 1 Marcus Pearce
The full distribution is also recorded in columns named to represent both the target viewpoint and the value of the element in the distribution. For example, 
56 1 Marcus Pearce
57 1 Marcus Pearce
* cpitch.60 
58 1 Marcus Pearce
* cpitch.61 
59 1 Marcus Pearce
* cpitch.62 
60 1 Marcus Pearce
* cpitch.63 
61 1 Marcus Pearce
* cpitch.64
62 1 Marcus Pearce
* ...
63 1 Marcus Pearce
64 1 Marcus Pearce
Finally, the overall probability, information.content and entropy are recorded using the following columns:
65 1 Marcus Pearce
66 1 Marcus Pearce
* probability
67 1 Marcus Pearce
* information.content
68 1 Marcus Pearce
* entropy
69 1 Marcus Pearce
70 1 Marcus Pearce
If there is only one target viewpoint, then these values will be equal to those for the single target viewpoint. If there is more than one target viewpoint then these reflect the joint probability distribution computed from the individual distributions for each target viewpoint.
71 1 Marcus Pearce
72 1 Marcus Pearce
h2. detail = 2 (Composition level)
73 1 Marcus Pearce
74 1 Marcus Pearce
Each line in the file represents a composition in the dataset and each column represents a property of that composition. The columns are:
75 1 Marcus Pearce
76 1 Marcus Pearce
* melody.id
77 1 Marcus Pearce
* melody.name 
78 1 Marcus Pearce
* mean.information.content
79 1 Marcus Pearce
80 1 Marcus Pearce
h2. detail = 1 (Dataset level)
81 1 Marcus Pearce
82 1 Marcus Pearce
Not yet implemented. However, the <code>idyom</code> function returns a single number representing the average information content of the entire dataset.