cortex: org/touch.org comparison

comparison org/touch.org @ 247:4e220c8fb1ed

first pass at rough draft complete

author	Robert McIntyre <rlm@mit.edu>
date	Sun, 12 Feb 2012 15:46:01 -0700
parents	63da037ce1c5
children	267add63b168

comparison

equal deleted inserted replaced

-:63da037ce1c5
+:4e220c8fb1ed
 Human skin has a wide array of touch sensors, each of which speciliaze
 in detecting different vibrational modes and pressures. These sensors
 can integrate a vast expanse of skin (i.e. your entire palm), or a
 tiny patch of skin at the tip of your finger. The hairs of the skin
 help detect objects before they even come into contact with the skin
 proper.
 Instead of measuring deformation or vibration, I surround each rigid
-part with a plenitude of hair-like objects which do not interact with
+part with a plenitude of hair-like objects (/feelers/) which do not
-the physical world. Physical objects can pass through them with no
+interact with the physical world. Physical objects can pass through
-effect. The hairs are able to measure contact with other objects, and
+them with no effect. The feelers are able to measure contact with
-constantly report how much of their extent is covered. So, even though
+other objects, and constantly report how much of their extent is
-the creature's body parts do not deform, the hairs create a margin
+covered. So, even though the creature's body parts do not deform, the
-around those body parts which achieves a sense of touch which is a
+feelers create a margin around those body parts which achieves a sense
-hybrid between a human's sense of deformation and sense from hairs.
+of touch which is a hybrid between a human's sense of deformation and
+sense from hairs.
 Implementing touch in jMonkeyEngine follows a different techinal route
 than vision and hearing. Those two senses piggybacked off
 jMonkeyEngine's 3D audio and video rendering subsystems. To simulate
-Touch, I use jMonkeyEngine's physics system to execute many small
+touch, I use jMonkeyEngine's physics system to execute many small
-collision detections, one for each "hair". The placement of the
+collision detections, one for each feeler. The placement of the
-"hairs" is determined by a UV-mapped image which shows where each hair
+feelers is determined by a UV-mapped image which shows where each
-should be on the 3D surface of the body.
+feeler should be on the 3D surface of the body.
 * Defining Touch Meta-Data in Blender
 Each geometry can have a single UV map which describes the position of
-the "hairs" which will constitute its sense of touch. This image path
+the feelers which will constitute its sense of touch. This image path
 is stored under the "touch" key.  The image itself is black and white,
-with black meaning a hair length of 0 (no hair is present) and white
+with black meaning a feeler length of 0 (no feeler is present) and
-meaning a hair length of =scale=, which is a float stored under the
+white meaning a feeler length of =scale=, which is a float stored
-key "scale". I call these "hairs" /feelers/.
+under the key "scale".
 #+name: meta-data
 #+begin_src clojure
 (defn tactile-sensor-profile
 "Return the touch-sensor distribution image in BufferedImage format,
 [#^Geometry obj]
 (if-let [image-path (meta-data obj "touch")]
 (load-image image-path)))
 (defn tactile-scale
-"Return the maximum length of a hair.  All hairs are scalled between
+"Return the length of each feeler. Default scale is 0.01
-0.0 and this length, depending on their color. Black is 0, and
+jMonkeyEngine units."
-white is maximum length, and everything in between is scalled
-linearlly. Default scale is 0.01 jMonkeyEngine units."
 [#^Geometry obj]
 (if-let [scale (meta-data obj "scale")]
 scale 0.1))
 #+end_src
 Here is an example of a UV-map which specifies the position of touch
-sensors along the surface of the worm.
+sensors along the surface of the upper segment of the worm.
 #+attr_html: width=755
 #+caption: This is the tactile-sensor-profile for the upper segment of the worm. It defines regions of high touch sensitivity (where there are many white pixels) and regions of low sensitivity (where white pixels are sparse).
 [[../images/finger-UV.png]]
-* Skin Creation
+* Implementation Summary
-=(touch-kernel)= generates the functions which implement the sense of
+To simulate touch there are three conceptual steps. For each solid
-touch for a creature. These functions must do 6 things to obtain touch
+object in the creature, you first have to get UV image and scale
-data.
+paramater which define the position and length of the feelers. Then,
+you use the triangles which compose the mesh and the UV data stored in
-- Get the tactile profile image and scale paramaters which describe
+the mesh to determine the world-space position and orientation of each
-the layout of feelers along the object's surface.
+feeler. Once every frame, update these positions and orientations to
-=(tactile-sensor-profile)=, =(tactile-scale)=
+match the current position and orientation of the object, and use
+physics collision detection to gather tactile data.
+Extracting the meta-data has already been described. The third step,
+physics collision detection, is handled in =(touch-kernel)=.
+Translating the positions and orientations of the feelers from the
+UV-map to world-space is also a three-step process.
 - Find the triangles which make up the mesh in pixel-space and in
-world-space.
+world-space. =(triangles)= =(pixel-triangles)=.
-=(triangles)= =(pixel-triangles)=
+- Find the coordinates of each feeler in world-space. These are the
-- Find the coordinates of each pixel in pixel space. These
+origins of the feelers. =(feeler-origins)=.
-coordinates are used to make the touch-topology.
-=(feeler-pixel-coords)=
-- Find the coordinates of each pixel in world-space. These
-coordinates are the origins of the feelers. =(feeler-origins)=
 - Calculate the normals of the triangles in world space, and add
 them to each of the origins of the feelers. These are the
-normalized coordinates of the tips of the feelers.
+normalized coordinates of the tips of the feelers. =(feeler-tips)=.
-For both of these, =(feeler-tips)=
+* Triangle Math
-- Generate some sort of topology for the sensors.
+** Schrapnel Conversion Functions
-=(touch-topology)=
+#+name: triangles-1
+#+begin_src clojure
+(defn vector3f-seq [#^Vector3f v]
+[(.getX v) (.getY v) (.getZ v)])
+(defn triangle-seq [#^Triangle tri]
+[(vector3f-seq (.get1 tri))
+(vector3f-seq (.get2 tri))
+(vector3f-seq (.get3 tri))])
+(defn ->vector3f
+([coords] (Vector3f. (nth coords 0 0)
+(nth coords 1 0)
+(nth coords 2 0))))
+(defn ->triangle [points]
+(apply #(Triangle. %1 %2 %3) (map ->vector3f points)))
+#+end_src
+It is convienent to treat a =Triangle= as a sequence of verticies, and
+a =Vector2f= and =Vector3f= as a sequence of floats. These conversion
+functions make this easy. If these classes implemented =Iterable= then
+=(seq)= would work on them automitacally.
+** Decomposing a 3D shape into Triangles
+The rigid bodies which make up a creature have an underlying
+=Geometry=, which is a =Mesh= plus a =Material= and other important
+data involved with displaying the body.
+A =Mesh= is composed of =Triangles=, and each =Triangle= has three
+verticies which have coordinates in world space and UV space.
+Here, =(triangles)= gets all the world-space triangles which compose a
+mesh, while =(pixel-triangles)= gets those same triangles expressed in
+pixel coordinates (which are UV coordinates scaled to fit the height
+and width of the UV image).
+#+name: triangles-2
+#+begin_src clojure
+(in-ns 'cortex.touch)
+(defn triangle
+"Get the triangle specified by triangle-index from the mesh."
+[#^Geometry geo triangle-index]
+(triangle-seq
+(let [scratch (Triangle.)]
+(.getTriangle (.getMesh geo) triangle-index scratch) scratch)))
+(defn triangles
+"Return a sequence of all the Triangles which compose a given
+Geometry."
+[#^Geometry geo]
+(map (partial triangle geo) (range (.getTriangleCount (.getMesh geo)))))
+(defn triangle-vertex-indices
+"Get the triangle vertex indices of a given triangle from a given
+mesh."
+[#^Mesh mesh triangle-index]
+(let [indices (int-array 3)]
+(.getTriangle mesh triangle-index indices)
+(vec indices)))
+(defn vertex-UV-coord
+"Get the UV-coordinates of the vertex named by vertex-index"
+[#^Mesh mesh vertex-index]
+(let [UV-buffer
+(.getData
+(.getBuffer
+mesh
+VertexBuffer$Type/TexCoord))]
+[(.get UV-buffer (* vertex-index 2))
+(.get UV-buffer (+ 1 (* vertex-index 2)))]))
+(defn pixel-triangle [#^Geometry geo image index]
+(let [mesh (.getMesh geo)
+width (.getWidth image)
+height (.getHeight image)]
+(vec (map (fn [[u v]] (vector (* width u) (* height v)))
+(map (partial vertex-UV-coord mesh)
+(triangle-vertex-indices mesh index))))))
+(defn pixel-triangles [#^Geometry geo image]
+(let [height (.getHeight image)
+width (.getWidth image)]
+(map (partial pixel-triangle geo image)
+(range (.getTriangleCount (.getMesh geo))))))
+#+end_src
+** The Affine Transform from one Triangle to Another
+=(pixel-triangles)= gives us the mesh triangles expressed in pixel
+coordinates and =(triangles)= gives us the mesh triangles expressed in
+world coordinates. The tactile-sensor-profile gives the position of
+each feeler in pixel-space. In order to convert pixel-dpace
+coordinates into world-space coordinates we need something that takes
+coordinates on the surface of one triangle and gives the corresponding
+coordinates on the surface of another triangle.
+Triangles are [[http://mathworld.wolfram.com/AffineTransformation.html ][affine]], which means any triangle can be transformed into
+any other by a combination of translation, scaling, and
+rotation. jMonkeyEngine's =Matrix4f= objects can describe any affine
+transformation. The affine transformation from one triangle to another
+is readily computable if the triangle is expressed in terms of a $4x4$
+matrix.
+\begin{bmatrix}
+x_1 & x_2 & x_3 & n_x \\
+y_1 & y_2 & y_3 & n_y \\
+z_1 & z_2 & z_3 & n_z \\
+1 & 1 & 1 & 1
+\end{bmatrix}
+Here, the first three columns of the matrix are the verticies of the
+triangle. The last column is the right-handed unit normal of the
+triangle.
+With two triangles $T_{1}$ and $T_{2}$ each expressed as a matrix like
+above, the affine transform from $T_{1}$ to $T_{2}$ is
+$T_{2}T_{1}^{-1}$
+The clojure code below recaptiulates the formulas above.
+#+name: triangles-3
+#+begin_src clojure
+(in-ns 'cortex.touch)
+(defn triangle->matrix4f
+"Converts the triangle into a 4x4 matrix: The first three columns
+contain the vertices of the triangle; the last contains the unit
+normal of the triangle. The bottom row is filled with 1s."
+[#^Triangle t]
+(let [mat (Matrix4f.)
+[vert-1 vert-2 vert-3]
+((comp vec map) #(.get t %) (range 3))
+unit-normal (do (.calculateNormal t)(.getNormal t))
+vertices [vert-1 vert-2 vert-3 unit-normal]]
+(dorun
+(for [row (range 4) col (range 3)]
+(do
+(.set mat col row (.get (vertices row) col))
+(.set mat 3 row 1)))) mat))
+(defn triangles->affine-transform
+"Returns the affine transformation that converts each vertex in the
+first triangle into the corresponding vertex in the second
+triangle."
+[#^Triangle tri-1 #^Triangle tri-2]
+(.mult
+(triangle->matrix4f tri-2)
+(.invert (triangle->matrix4f tri-1))))
+#+end_src
+** Triangle Boundaries
+For efficiency's sake I will divide the tactile-profile image into
+small squares which inscribe each pixel-triangle, then extract the
+points which lie inside the triangle and map them to 3D-space using
+=(triangle-transform)= above. To do this I need a function,
+=(convex-bounds)= which finds the smallest box which inscribes a 2D
+triangle.
+=(inside-triangle?)= determines whether a point is inside a triangle
+in 2D pixel-space.
+#+name: triangles-4
+#+begin_src clojure
+(defn convex-bounds
+"Returns the smallest square containing the given vertices, as a
+vector of integers [left top width height]."
+[verts]
+(let [xs (map first verts)
+ys (map second verts)
+x0 (Math/floor (apply min xs))
+y0 (Math/floor (apply min ys))
+x1 (Math/ceil (apply max xs))
+y1 (Math/ceil (apply max ys))]
+[x0 y0 (- x1 x0) (- y1 y0)]))
+(defn same-side?
+"Given the points p1 and p2 and the reference point ref, is point p
+on the same side of the line that goes through p1 and p2 as ref is?"
+[p1 p2 ref p]
+(<=
+0
+(.dot
+(.cross (.subtract p2 p1) (.subtract p p1))
+(.cross (.subtract p2 p1) (.subtract ref p1)))))
+(defn inside-triangle?
+"Is the point inside the triangle?"
+{:author "Dylan Holmes"}
+[#^Triangle tri #^Vector3f p]
+(let [[vert-1 vert-2 vert-3] [(.get1 tri) (.get2 tri) (.get3 tri)]]
+(and
+(same-side? vert-1 vert-2 vert-3 p)
+(same-side? vert-2 vert-3 vert-1 p)
+(same-side? vert-3 vert-1 vert-2 p))))
+#+end_src
+* Feeler Coordinates
+The triangle-related functions above make short work of calculating
+the positions and orientations of each feeler in world-space.
+#+name: sensors
+#+begin_src clojure
+(in-ns 'cortex.touch)
+(defn feeler-pixel-coords
+"Returns the coordinates of the feelers in pixel space in lists, one
+list for each triangle, ordered in the same way as (triangles) and
+(pixel-triangles)."
+[#^Geometry geo image]
+(map
+(fn [pixel-triangle]
+(filter
+(fn [coord]
+(inside-triangle? (->triangle pixel-triangle)
+(->vector3f coord)))
+(white-coordinates image (convex-bounds pixel-triangle))))
+(pixel-triangles geo image)))
+(defn feeler-world-coords
+"Returns the coordinates of the feelers in world space in lists, one
+list for each triangle, ordered in the same way as (triangles) and
+(pixel-triangles)."
+[#^Geometry geo image]
+(let [transforms
+(map #(triangles->affine-transform
+(->triangle %1) (->triangle %2))
+(pixel-triangles geo image)
+(triangles geo))]
+(map (fn [transform coords]
+(map #(.mult transform (->vector3f %)) coords))
+transforms (feeler-pixel-coords geo image))))
+(defn feeler-origins
+"The world space coordinates of the root of each feeler."
+[#^Geometry geo image]
+(reduce concat (feeler-world-coords geo image)))
+(defn feeler-tips
+"The world space coordinates of the tip of each feeler."
+[#^Geometry geo image]
+(let [world-coords (feeler-world-coords geo image)
+normals
+(map
+(fn [triangle]
+(.calculateNormal triangle)
+(.clone (.getNormal triangle)))
+(map ->triangle (triangles geo)))]
+(mapcat (fn [origins normal]
+(map #(.add % normal) origins))
+world-coords normals)))
+(defn touch-topology
+"touch-topology? is not a function."
+[#^Geometry geo image]
+(collapse (reduce concat (feeler-pixel-coords geo image))))
+#+end_src
+* Simulated Touch
+=(touch-kernel)= generates functions to be called from within a
+simulation that perform the necessary physics collisions to collect
+tactile data, and =(touch!)= recursively applies it to every node in
+the creature.
 #+name: kernel
 #+begin_src clojure
 (in-ns 'cortex.touch)
 (map touch-kernel
 (filter #(isa? (class %) Geometry)
 (node-seq creature)))))
 #+end_src
-* Sensor Related Functions
-These functions analyze the touch-sensor-profile image convert the
-location of each touch sensor from pixel coordinates to UV-coordinates
-and XYZ-coordinates.
-#+name: sensors
-#+begin_src clojure
-(in-ns 'cortex.touch)
-(defn feeler-pixel-coords
-"Returns the coordinates of the feelers in pixel space in lists, one
-list for each triangle, ordered in the same way as (triangles) and
-(pixel-triangles)."
-[#^Geometry geo image]
-(map
-(fn [pixel-triangle]
-(filter
-(fn [coord]
-(inside-triangle? (->triangle pixel-triangle)
-(->vector3f coord)))
-(white-coordinates image (convex-bounds pixel-triangle))))
-(pixel-triangles geo image)))
-(defn feeler-world-coords [#^Geometry geo image]
-(let [transforms
-(map #(triangles->affine-transform
-(->triangle %1) (->triangle %2))
-(pixel-triangles geo image)
-(triangles geo))]
-(map (fn [transform coords]
-(map #(.mult transform (->vector3f %)) coords))
-transforms (feeler-pixel-coords geo image))))
-(defn feeler-origins [#^Geometry geo image]
-(reduce concat (feeler-world-coords geo image)))
-(defn feeler-tips [#^Geometry geo image]
-(let [world-coords (feeler-world-coords geo image)
-normals
-(map
-(fn [triangle]
-(.calculateNormal triangle)
-(.clone (.getNormal triangle)))
-(map ->triangle (triangles geo)))]
-(mapcat (fn [origins normal]
-(map #(.add % normal) origins))
-world-coords normals)))
-(defn touch-topology [#^Geometry geo image]
-(collapse (reduce concat (feeler-pixel-coords geo image))))
-#+end_src
 * Visualizing Touch
 #+name: visualization
 #+begin_src clojure
 (in-ns 'cortex.touch)
 (defn touch->gray
 (dorun
 (for [i (range (count coords))]
 (.setRGB image ((coords i) 0) ((coords i) 1)
 (apply touch->gray (sensor-data i))))) image))))
 #+end_src
+* Adding Touch to the Worm
+#+name: test-touch
-* Triangle Manipulation Functions
+#+begin_src clojure
+(ns cortex.test.touch
-The rigid bodies which make up a creature have an underlying
+(:use (cortex world util sense body touch))
-=Geometry=, which is a =Mesh= plus a =Material= and other important
+(:use cortex.test.body))
-data involved with displaying the body.
+(cortex.import/mega-import-jme3)
-A =Mesh= is composed of =Triangles=, and each =Triangle= has three
-verticies which have coordinates in XYZ space and UV space.
+(defn test-touch []
+(let [the-worm (doto (worm) (body!))
-Here, =(triangles)= gets all the triangles which compose a mesh, and
+touch (touch! the-worm)
-=(triangle-UV-coord)= returns the the UV coordinates of the verticies
+touch-display (view-touch)]
-of a triangle.
+(world (nodify [the-worm (floor)])
+standard-debug-controls
-#+name: triangles-1
-#+begin_src clojure
+(fn [world]
-(in-ns 'cortex.touch)
+(speed-up world)
+(light-up-everything world))
-(defn vector3f-seq [#^Vector3f v]
-[(.getX v) (.getY v) (.getZ v)])
+(fn [world tpf]
+(touch-display
-(defn triangle-seq [#^Triangle tri]
+(map #(% (.getRootNode world)) touch))))))
-[(vector3f-seq (.get1 tri))
+#+end_src
-(vector3f-seq (.get2 tri))
-(vector3f-seq (.get3 tri))])
-(defn ->vector3f
-([coords] (Vector3f. (nth coords 0 0)
-(nth coords 1 0)
-(nth coords 2 0))))
-(defn ->triangle [points]
-(apply #(Triangle. %1 %2 %3) (map ->vector3f points)))
-(defn triangle
-"Get the triangle specified by triangle-index from the mesh."
-[#^Geometry geo triangle-index]
-(triangle-seq
-(let [scratch (Triangle.)]
-(.getTriangle (.getMesh geo) triangle-index scratch) scratch)))
-(defn triangles
-"Return a sequence of all the Triangles which compose a given
-Geometry."
-[#^Geometry geo]
-(map (partial triangle geo) (range (.getTriangleCount (.getMesh geo)))))
-(defn triangle-vertex-indices
-"Get the triangle vertex indices of a given triangle from a given
-mesh."
-[#^Mesh mesh triangle-index]
-(let [indices (int-array 3)]
-(.getTriangle mesh triangle-index indices)
-(vec indices)))
-(defn vertex-UV-coord
-"Get the UV-coordinates of the vertex named by vertex-index"
-[#^Mesh mesh vertex-index]
-(let [UV-buffer
-(.getData
-(.getBuffer
-mesh
-VertexBuffer$Type/TexCoord))]
-[(.get UV-buffer (* vertex-index 2))
-(.get UV-buffer (+ 1 (* vertex-index 2)))]))
-(defn pixel-triangle [#^Geometry geo image index]
-(let [mesh (.getMesh geo)
-width (.getWidth image)
-height (.getHeight image)]
-(vec (map (fn [[u v]] (vector (* width u) (* height v)))
-(map (partial vertex-UV-coord mesh)
-(triangle-vertex-indices mesh index))))))
-(defn pixel-triangles [#^Geometry geo image]
-(let [height (.getHeight image)
-width (.getWidth image)]
-(map (partial pixel-triangle geo image)
-(range (.getTriangleCount (.getMesh geo))))))
-#+end_src
-* Triangle Affine Transforms
-The position of each hair is stored in a 2D image in UV
-coordinates. To place the hair in 3D space we must convert from UV
-coordinates to XYZ coordinates. Each =Triangle= has coordinates in
-both UV-space and XYZ-space, which defines a unique [[http://mathworld.wolfram.com/AffineTransformation.html ][Affine Transform]]
-for translating any coordinate within the UV triangle to the
-cooresponding coordinate in the XYZ triangle.
-#+name: triangles-3
-#+begin_src clojure
-(in-ns 'cortex.touch)
-(defn triangle->matrix4f
-"Converts the triangle into a 4x4 matrix: The first three columns
-contain the vertices of the triangle; the last contains the unit
-normal of the triangle. The bottom row is filled with 1s."
-[#^Triangle t]
-(let [mat (Matrix4f.)
-[vert-1 vert-2 vert-3]
-((comp vec map) #(.get t %) (range 3))
-unit-normal (do (.calculateNormal t)(.getNormal t))
-vertices [vert-1 vert-2 vert-3 unit-normal]]
-(dorun
-(for [row (range 4) col (range 3)]
-(do
-(.set mat col row (.get (vertices row)col))
-(.set mat 3 row 1)))) mat))
-(defn triangles->affine-transform
-"Returns the affine transformation that converts each vertex in the
-first triangle into the corresponding vertex in the second
-triangle."
-[#^Triangle tri-1 #^Triangle tri-2]
-(.mult
-(triangle->matrix4f tri-2)
-(.invert (triangle->matrix4f tri-1))))
-#+end_src
-* Schrapnel Conversion Functions
-It is convienent to treat a =Triangle= as a sequence of verticies, and
-a =Vector2f= and =Vector3f= as a sequence of floats. These conversion
-functions make this easy. If these classes implemented =Iterable= then
-this code would not be necessary. Hopefully they will in the future.
-* Triangle Boundaries
-For efficiency's sake I will divide the UV-image into small squares
-which inscribe each UV-triangle, then extract the points which lie
-inside the triangle and map them to 3D-space using
-=(triangle-transform)= above. To do this I need a function,
-=(inside-triangle?)=, which determines whether a point is inside a
-triangle in 2D UV-space.
-#+name: triangles-4
-#+begin_src clojure
-(defn convex-bounds
-"Returns the smallest square containing the given vertices, as a
-vector of integers [left top width height]."
-[verts]
-(let [xs (map first verts)
-ys (map second verts)
-x0 (Math/floor (apply min xs))
-y0 (Math/floor (apply min ys))
-x1 (Math/ceil (apply max xs))
-y1 (Math/ceil (apply max ys))]
-[x0 y0 (- x1 x0) (- y1 y0)]))
-(defn same-side?
-"Given the points p1 and p2 and the reference point ref, is point p
-on the same side of the line that goes through p1 and p2 as ref is?"
-[p1 p2 ref p]
-(<=
-0
-(.dot
-(.cross (.subtract p2 p1) (.subtract p p1))
-(.cross (.subtract p2 p1) (.subtract ref p1)))))
-(defn inside-triangle?
-"Is the point inside the triangle?"
-{:author "Dylan Holmes"}
-[#^Triangle tri #^Vector3f p]
-(let [[vert-1 vert-2 vert-3] [(.get1 tri) (.get2 tri) (.get3 tri)]]
-(and
-(same-side? vert-1 vert-2 vert-3 p)
-(same-side? vert-2 vert-3 vert-1 p)
-(same-side? vert-3 vert-1 vert-2 p))))
-#+end_src
-* Physics Collision Objects
-The "hairs" are actually =Rays= which extend  from a point on a
-=Triangle= in the =Mesh= normal to the =Triangle's= surface.
 * Headers
 #+name: touch-header
 #+begin_src clojure
 (:import com.jme3.collision.CollisionResults)
 (:import com.jme3.scene.VertexBuffer$Type)
 (:import (com.jme3.math Triangle Vector3f Vector2f Ray Matrix4f)))
 #+end_src
-* Adding Touch to the Worm
-#+name: test-touch
-#+begin_src clojure
-(ns cortex.test.touch
-(:use (cortex world util sense body touch))
-(:use cortex.test.body))
-(cortex.import/mega-import-jme3)
-(defn test-touch []
-(let [the-worm (doto (worm) (body!))
-touch (touch! the-worm)
-touch-display (view-touch)]
-(world (nodify [the-worm (floor)])
-standard-debug-controls
-(fn [world]
-(speed-up world)
-(light-up-everything world))
-(fn [world tpf]
-(touch-display
-(map #(% (.getRootNode world)) touch))))))
-#+end_src
 * Source Listing
 * Next
 * COMMENT Code Generation
 #+begin_src clojure :tangle ../src/cortex/touch.clj
 <<touch-header>>
 <<meta-data>>
 <<triangles-1>>
+<<triangles-2>>
 <<triangles-3>>
 <<triangles-4>>
 <<sensors>>
 <<kernel>>
 <<visualization>>

Mercurial > cortex

comparison org/touch.org @ 247:4e220c8fb1ed