gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/AGPU irregu.txt paper.txt


From: Janne V. Kujala
Subject: [Gzz-commits] manuscripts/AGPU irregu.txt paper.txt
Date: Mon, 14 Apr 2003 08:51:51 -0400

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Janne V. Kujala <address@hidden>        03/04/14 08:51:50

Modified files:
        AGPU           : irregu.txt paper.txt 

Log message:
        cleanup, notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/AGPU/irregu.txt.diff?tr1=1.10&tr2=1.11&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/AGPU/paper.txt.diff?tr1=1.12&tr2=1.13&r1=text&r2=text

Patches:
Index: manuscripts/AGPU/irregu.txt
diff -u manuscripts/AGPU/irregu.txt:1.10 manuscripts/AGPU/irregu.txt:1.11
--- manuscripts/AGPU/irregu.txt:1.10    Mon Apr 14 07:39:47 2003
+++ manuscripts/AGPU/irregu.txt Mon Apr 14 08:51:49 2003
@@ -12,6 +12,7 @@
 Shape
 -----
 
+XXX: what illusion?
 In order to maintain the illusion, the animation has to be appropriate:
 having the shape of the jagged edge remain while the viewport moves over
 the canvas would still *feel* like a window. The shape of the jagged
Index: manuscripts/AGPU/paper.txt
diff -u manuscripts/AGPU/paper.txt:1.12 manuscripts/AGPU/paper.txt:1.13
--- manuscripts/AGPU/paper.txt:1.12     Mon Apr 14 08:28:40 2003
+++ manuscripts/AGPU/paper.txt  Mon Apr 14 08:51:49 2003
@@ -1,18 +1,18 @@
-XXX: should we mention the accepted manuscript?
- - YES, since it was accepted
-
+In [Kujala, Lukka, "Rendering recognizably unique textures",
+to be published in Information Visualization'03 conference,
+preprint available on request], we introduced the use
+of procedurally generated unique background textures
+as a visualization of document identity.
 In this work, we are not using the GPU to try to obtain a specific
 appearance or effect.  Instead, we use the GPU to produce an infinite
 amount of different, novel textures, with the goal that they
 should be recognizable by users. 
-The procedurally generated unique textures are used as a
-backgrounds to documents for visualization of document identity. 
 In our approach, each document has
 a different, easily distinguishable background texture.  
 The user can
 thus identify an item at a glance, even if only a *fragment* of the
 item is shown, without reading the title (which the fragment may not
-even show). See Fig.1.
+even show) [Fig.1].
 The user should be able to learn the textures of the most
 often visited documents, as per Zipf's law.
 An initial experiment has shown that the generated textures are indeed
@@ -25,7 +25,7 @@
 
 Plain OpenGL 1.3 does not by itself provide enough flexibility in the
 fragment pipeline to allow for generating features nonlinearly from
-the basis textures.  Because of this, and the availability of stable
+the basis textures[Fig.3].  Because of this, and the availability of stable
 Linux drivers, our main platforms are NV10, i.e., OpenGL 1.3 +
 GL_NV_register_combiners, and NV25, i.e., NV10 +
 GL_NV_texture_shader3.  We will be  working on an implementation based on
@@ -47,7 +47,7 @@
 combiner parameters chosen randomly from the seed number.  For this,
 we use dot products of texture values with each other and with random
 constant vectors, and scale up with the register combiner output mappings
-to sharpen the result (see Fig. 4).  The resulting values
+to sharpen the result [Fig.4].  The resulting values
 are used for interpolating between the palette colors.
 On the NV25, we use offset textures to allow the creation of new 
 shapes by texture shading.
@@ -79,7 +79,7 @@
 distribution of feature vectors with maximum entropy.
 
 Fig.3. The complete set of 2D basis textures used by our
-implementation.  All textures shown in this article are built from
+implementation.  All textures shown in this proposal are built from
 these textures and the corresponding HILO textures for offsetting.
 
 Fig.4. How the limited register combiners of the NV10




reply via email to

[Prev in Thread] Current Thread [Next in Thread]