User Tools

Site Tools


compositional_hierarchical_model_visualization

====== Differences ====== This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
compositional_hierarchical_model_visualization [2014/10/26 04:48]
matevz created
compositional_hierarchical_model_visualization [2014/10/26 05:28] (current)
matevz
Line 1: Line 1:
 +====== Visualizing the Compositional Hierarchical Model ======
 +====== The Goal ======
 +
 The goal of this hack was to update existing visualization of compositional hierarchical model for spectral input data and provide some sort of visualization for symbolic input data. The goal of this hack was to update existing visualization of compositional hierarchical model for spectral input data and provide some sort of visualization for symbolic input data.
  
Line 12: Line 15:
  
 Thus, a second visualization was created for the spectral model some months ago (later extensions were put on a TODO list with no priority whatsoever). The rose pedals indicate the activations (magnitude equals to the size of the pedal) and their location in spectrum (clockwise). Thus, a second visualization was created for the spectral model some months ago (later extensions were put on a TODO list with no priority whatsoever). The rose pedals indicate the activations (magnitude equals to the size of the pedal) and their location in spectrum (clockwise).
 +
 +===== Goal no. 1 - fix the issues of the current visualization =====
  
 The first goal of this hack was to fix some graphic issues with the visualization,​ causing the application to consume too much memory. The second goal was to provide additional visualizations of connecting nodes across layers. The first goal of this hack was to fix some graphic issues with the visualization,​ causing the application to consume too much memory. The second goal was to provide additional visualizations of connecting nodes across layers.
Line 19: Line 24:
 Besides the unvisible optimization issues resolved, the visualization now outputs the subtree of each node (marked blue in the Figure above). Besides the unvisible optimization issues resolved, the visualization now outputs the subtree of each node (marked blue in the Figure above).
  
-The third (but unfortunately unfinished) hack was to provide a visualization of symbolic data. Eventhough the XNA works great and all, the framework is no longer supported (and it only compiles for the x86 platform). Thus, I started working on a JavaScript prototype (using d3.js library) for visualizing the symbolic data. In theory, it should look like this (abstraction):​+===== Goal no. 2 - provide a new visualization for symbolic data ===== 
 + 
 +The second ​(but unfortunately unfinished) hack was to provide a visualization of symbolic data. Eventhough the XNA works great and all, the framework is no longer supported (and it only compiles for the x86 platform). Thus, I started working on a JavaScript prototype (using d3.js library) for visualizing the symbolic data. In theory, it should look like this (abstraction):​
  
 {{:​symbolicrepresentation.png?​nolink&​300|}} {{:​symbolicrepresentation.png?​nolink&​300|}}
Line 29: Line 36:
 The black dots represent the MIDI note onsets, while the red squares represent the patterns. The patterns only represent the location and the length of pattern. For each layer of nodes in the model, a new "​row"​ of patterns is formed (there are two layers shown in the Figure above). The black dots represent the MIDI note onsets, while the red squares represent the patterns. The patterns only represent the location and the length of pattern. For each layer of nodes in the model, a new "​row"​ of patterns is formed (there are two layers shown in the Figure above).
  
-This hack still needs A LOT of work to become actually useful. Planned features are the following: observing occurrences by selecting a part, a layer, a subtree (composition ​of parts); developing a 3D visualization (and make it turnable); playing ​the selected patterns, ​and others.+The majority ​of the time was dedicated ​to the adjustment ​of the model and transformation of the data. 
 + 
 +==== Future work (or TODO for the next hack day) ====
  
 +This hack still needs A LOT of work to become actually useful. Planned features are the following: ​
 +  * observing occurrences by selecting a part, a layer, a subtree (composition of parts); ​
 +  * developing a 3D visualization (and make it turnable) using d3.js; ​
 +  * audio output - playing the selected patterns.
  
  
compositional_hierarchical_model_visualization.1414313283.txt.gz · Last modified: 2014/10/26 04:48 by matevz