Figure 1
Figure 1 shows the TextureBrowser when it first launches. The browser opens the Versant database, reads in the desired image, and also the related ConceptSpace.
The window in Figure 1 is mostly taken up by the image display pane. It is here where the image can be seen, scaled, and generally manipulated.
In the upper-left of Figure 1 can be seen the texture-list pane. It is here where the iconic representations of all the textures present in the current image are shown. Currently, there is no meaning to the order of the textures in this pane.
The number of textures in the texture-list pane depend on the number of categories decided upon during the SOM segmentation process. Also, the size of the textures (pixel block size) is also decided during the segmentation process. In this example, 32x32 pixel blocks were used. Eventually, the texture icons in the texture-list pane will be labeled with names from the database, such as "water" and "pine forest," but that meta-data is not yet available.
The lower-left of Figure 1 is the related-texture-list pane, but is empty upon startup.
Figure 1
When a texture in the texture-list pane is selected, two things happen. First, the pixel block areas in the image are highlighted. Right now, the texture blocks are simply colored white, but eventually, they will simply be colored a different "hue" - such as yellow or light blue. Second, the ConceptSpace is queried for a list of "related textures" which are related to texture selected. This list of related textures is displayed in the related-texture-list pane.
In this case, "relatedness" is defined by the frequency that one texture is in proximity to another texture. For instance, in Figure 2, texture 91 is the texture which occurs in proximity to texture 81 with the highest frequency. Texture 76 is the texture with the second highest frequency, and so forth. The textures displayed in the related-texture-list pane are in order from highest frequency to lowest frequency.
Figure 2
When a texture in the related-texture-list pane is selected, the pixel block areas in the image which correspond to that texture are also highlighted - this time in a different color, black. In Figure 3, it can easily be seen that the new black pixel blocks are indeed in close proximity to the originally selected white blocks.
Figure 3
As one goes down the list of textures in the related-texture-list pane, the proximity of the black colored blocks becomes smaller and smaller. This can be seen in Figures 4 and 5: Texture 76 is slightly less related to texture 81 than texture 91, and texture 198 seems to be not related at all to texture 81.
Figure 4
Figure 5
Figures 6, 7 and 8 simply show the same concepts as above in Figures 2, 3 and 5 except using a different starting texture (texture 137).
Figure 6
Figure 7
Figure 8