31:T643,md`# Using three.js for 2D data visualization _This notebook was created for the [Cloudera Fast Forward Labs Blog](http://blog.fastforwardlabs.com/). I'd love to hear any comments on twitter [@grantcuster](https://twitter.com/GrantCuster) or grantcuster at gmail dot com._ This notebook shows the results of my efforts to use [three.JS](https://threejs.org/) to make a 2D data visualization. I was making an interactive t-SNE visualization, but these methods will be useful for anyone who wants to make an interactive visualization of a lot of points (in my project it was over 50,000). This demo is only using 1000 points, but you can [check out my working Codepen demo featuring 100,000](https://codepen.io/GrantCuster/full/QQXRqj/). I used three.js because it can render more points more smoothly than SVG or canvas. Because three.js is not designed with these types of visualizations in mind, there was some friction in getting everything set up the way I wanted. This notebook documents my finished set-up and solutions to the issues I ran into. The main features I'm going to highlight are: 1. Mouse-directed zoom and pan (using d3-zoom) 3. Rendering circular points (three.js defaults to squares) 4. Coloring points 5. Displaying a tooltip when you hover over a point I show the finished interactive visualization below and then walk through the code that makes it work. If you really want to dig in and modify the code. I'd recommend forking the notebook [so you can take advantage of code changes syncing across browser windows](https://twitter.com/GrantCuster/status/966468276153757696).`32:T43e,md`## 0. Camera and render set-up Before we get into zoom, we should briefly talk about how this visualization exists in the three.js world. Objects in three.js exist in a three-dimensional space with x, y, and z axes. Your view of those points is determined by the camera, which also exists in three-dimensional space. This allows a bunch of stuff like zooming past 3D objects, or rotating around them, that we don't need for this 2D visualization. What I want to do is put all my points at 0 on the z axis and then pull my camera back so I can see them all. Zoom then involves moving the camera closer to the points. Besides the camera's position, you also need to set certain parameters, like field of view angle (fov), aspect ratio, and the near and far plane thresholds, on set-up. I made [another notebook breaking down what those settings mean](https://beta.observablehq.com/@grantcuster/understanding-scale-and-the-three-js-perspective-camera). We're also going to use the fov, near and far plane thresholds in our zoom handler so I've broken those out into their own cells.`33:T422,md`## 1. Mouse-directed zoom and pan To get zoom and pan working I needed something to translate mouse and touch events (like scrolling and pinch-to-zoom) into zoom and movement values. I used d3's zoom behavior for this because I was familiar with it from past projects and I knew it had a feel I liked (in this case "feel" is how fast it zooms in response to mouse events). To get [d3-zoom](https://threejs.org/docs/#manual/introduction/Creating-a-scene) to work I needed to translate d3-zoom terms into three.js terms. d3-zoom starts with a scale of 1 and increases that scale as you zoom in (this works out of the box for svg and canvas transforms). As discussed above, in three.js the scale is determined by the z position of the camera. I needed a way to map d3's scale to three.js's camera position. I found the solution in the code for the [three.map.control plugin](https://github.com/anvaka/three.map.control), which showed how to use the field of view angle, the camera position, and trigonometry to find the current scale of the visualization.`34:T458,md`## 2. Rendering circular points A less math-y, but still important, issue was getting three.js to render points as circles, rather than the default squares. From [three.js examples](https://threejs.org/examples/#webgl_points_billboards), it was clear I needed to use a sprite to get a circle render. The main challenge was figuring out what kind of sprite would get the best looking circle across different colors. A lot of the examples used sprites with drop shadows. I did not want a drop shadow so I made a simple flat white circle (the white will take the colors we assign below). The biggest issue was determining how to handle the edge. By default photoshop will use anti-aliasing on the edges of a circle to smooth things out. This caused issues for me when I assigned colors, so I turned antialiasing off. An alternative suggested solution is to use a sprite with anti-aliasing and set the alphaTest property to around \`0.5\`. I included both approaches below. You can switch the config used in \`sprite_settings\` and check the visualization to see the difference (I have a hard time seeing any).`35:T6bc,md`### A note on sizeAttenuation In the above code for pointsMaterial I've set sizeAttenuation to false. When set to true (the default value) sizeAttenuation rescales the points based on the camera's z-position so that they appear to get bigger as you get closer to them. This makes sense for a simulation of real objects, but for data visualizations it's often preferable to have the points remain the same size. It gives you a better view of global structure when zoomed out and local structure when zoomed in. When I've done similar, non-three.js, visualizations I've achieved the same effect by rescaling the points with zoom to make them stay the same size. In three.js you basically get that for free. There's an [open issue](https://github.com/mrdoob/three.js/issues/10385) on whether the default should be false that also has more info on just what is happening. Turning sizeAttenuation off can make zooming in close feel a little weird – since the points spread out it can feel like the one you were hovering over is running away from you. Partly for that reason I think the best user experience is to have the points stay mostly the same size but rescale to get a bit bigger as you zoom in very close. I set that up in the project this is based on but am leaving it out of this example. Basically on zoom you look at the camera z position and choose certain thresholds and size targets. Then you can set up functions to tween those size targets on zoom. I first saw this technique in [Mapbox GL](https://www.mapbox.com/mapbox-gl-js/api/) where they have it set up so you can determine the size of labels at different zoom levels. I think there is a lot of this going on in maps to make things feel smooth.`36:T8ad,md`## 5. Extensions and caveats ### 5.1 Click on a point to zoom I figured this example is long enough, but I did want to point the way towards another common feature for interactive visualizations: clicking on a point to zoom (and probably show more detail information in a sidebar). Basically all the components for that are in this example. You'll use raycaster to find which point is clicked, and then you'll want to use a library like [tween.js](https://github.com/tweenjs/tween.js/) to animate the camera's zoom in. There are several three.js + tween.js guides out there like [this one](https://medium.com/@lachlantweedie/animation-in-three-js-using-tween-js-with-examples-c598a19b1263). ### 5.2 GeometryBuffer I set the geometry in for the points in this example using the Geometry class. For better performance the three.js docs recommend using [BufferGeometry](https://threejs.org/docs/#api/core/BufferGeometry), which requires you to be a bit more specific in how you set it up. I used BufferGeometry in my final project but I'm not going to go into it here. You can always start with Geometry and make the move to BufferGeometry as part of your optimizations. ### 5.3 renderOrder Probably the biggest issue I had that I don't feel like I really ever got my head around has to do with renderOrder. three.js does not guarantee that the objects will render in the same order they are added to the scene. This can cause issues when you add objects on top of other objects (like the enlarged points I render on hover). I don't have any issues with this example, but as I was doing more complex things in a project I did run into problems. There is a method, [suggested by WestLangley here](https://stackoverflow.com/questions/12666570/how-to-change-the-zorder-of-object-with-threejs) to make sure an object always renders on top: \`mesh.renderOrder = 999;\` \`mesh.onBeforeRender = function( renderer ) { renderer.clearDepth(); };\` I got this to work in some situations, but ran into trouble when I was working with objects within different containers. I found workarounds for the specific case, but I would love to look at (and will perhaps sometimes make) a reduced test case of how and when it works.`37:[{"id":"2b2730725b22b3fc22600a55c3f7ce65ddb390a701a5eab7bcb9515789b81a36118ad6c879855df6e92024cedb009a9fc5aff9f9953a1b76e6a3bdd4ab2b39e5","href":"https://static.observableusercontent.com/files/2b2730725b22b3fc22600a55c3f7ce65ddb390a701a5eab7bcb9515789b81a36118ad6c879855df6e92024cedb009a9fc5aff9f9953a1b76e6a3bdd4ab2b39e5","name":"PSC_cluster_scatter.json","type":"application/json","lastModified":1651267769463.464,"size":10478901},{"id":"f1aaa3b1f9c8c15d0a2ec23ab1525c50742e50e73b244434eb825b7dd688c07f9baf44bdf5b6e271e3ac2af2121769a8882b27e24ed59ce39f7c5dbeaf0a1ad4","href":"https://static.observableusercontent.com/files/f1aaa3b1f9c8c15d0a2ec23ab1525c50742e50e73b244434eb825b7dd688c07f9baf44bdf5b6e271e3ac2af2121769a8882b27e24ed59ce39f7c5dbeaf0a1ad4","name":"PSC_clusters.json","type":"application/json","lastModified":1651267767336.327,"size":235432}] 2f:{"title":"Using three.js for 2D data visualization","cells":[{"id":0,"value":"$31","pinned":false,"hidden":false,"mode":"ojs"},{"id":371,"value":"md`## The visualization`","pinned":false,"hidden":false,"mode":"ojs"},{"id":877,"value":"function cToHex(c) {\n var hex = c.toString(16);\n return hex.length == 1 ? \"0\" + hex : hex;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":879,"value":"function greyToHex(f) {\n return \"#\" + cToHex(Math.round((1-f)*255))+ cToHex(Math.round((1-f)*255)) + cToHex(Math.round((1-f)*255));\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":4,"value":"canvas = {\n camera;\n renderer.setSize(viz_width, height);\n renderer.setPixelRatio(devicePixelRatio);\n try {\n while (true) {\n renderer.render(scene, camera);\n let html_render = html`

\n ${renderer.domElement}\n

${tooltip_state.name}

${[0,1,2,3,4].map((i) => \"\"+JSON.parse(tooltip_state.group)[i].word+\" \")}

\n\t\t

`\n yield html_render;\n }\n } finally {\n renderer.dispose();\n }\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":379,"value":"$32","pinned":false,"hidden":false,"mode":"ojs"},{"id":406,"value":"fov = 40","pinned":false,"hidden":false,"mode":"ojs"},{"id":297,"value":"near = 1","pinned":false,"hidden":false,"mode":"ojs"},{"id":299,"value":"far = 100","pinned":false,"hidden":false,"mode":"ojs"},{"id":849,"value":"viewof pointSize = Inputs.range([0, 8], {value: 1, step: 0.1, label: \"Point Size\"})","pinned":true,"hidden":false,"mode":"ojs"},{"id":6,"value":"camera = {\n let aspect = viz_width / height;\n return new THREE.PerspectiveCamera(fov, aspect, near, far + 1);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":666,"value":"md`Note: The \\`far + 1\\` adjustment is because I was having issues with the hovered points not rendering when zoomed out. Theoretically it should not have been an issue, but since adding 1 to the threshold was a simple fix that doesn't hurt anything I didn't dig any further into it.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":791,"value":"md`You'll also need to make a scene and add your points (which we'll define later) to it`","pinned":false,"hidden":false,"mode":"ojs"},{"id":793,"value":"scene = {\n let scene = new THREE.Scene();\n scene.background = new THREE.Color(0xffffff);\n scene.add(points);\n return scene;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":389,"value":"md`Finally, you'll need to set up a rendering loop and a canvas element (for this demo that code is behind the visualization block). The [three.js docs](https://threejs.org/docs/#manual/introduction/Creating-a-scene) are a good resource on how to do that. There are no 2D specific adjustments you need to make for the render step so I'm not going to discuss it here.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":59,"value":"$33","pinned":false,"hidden":false,"mode":"ojs"},{"id":402,"value":"function getScaleFromZ (camera_z_position) {\n let half_fov = fov/2;\n let half_fov_radians = toRadians(half_fov);\n let half_fov_height = Math.tan(half_fov_radians) * camera_z_position;\n let fov_height = half_fov_height * 2;\n let scale = height / fov_height; // Divide visualization height by height derived from field of view\n return scale;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":425,"value":"md`I go into detail about the math behind this in [my other notebook](https://beta.observablehq.com/@grantcuster/understanding-scale-and-the-three-js-perspective-camera). We'll also need a function that does the reverse: translating from d3's scale value into a camera z position.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":434,"value":"function getZFromScale(scale) {\n let half_fov = fov/2;\n let half_fov_radians = toRadians(half_fov);\n let scale_height = height / scale;\n let camera_z_position = scale_height / (2 * Math.tan(half_fov_radians));\n return camera_z_position;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":446,"value":"md`With those two functions in hand, we're ready to make our zoom handler. It takes the transform supplied by d3-zoom, which includes x, y, and k (scale) values and transforms them into a coordinates for the three.js camera. Crucially, the x and y coordinates get us mouse directed zoom, where the zoom follows where the mouse is pointed (you're probably familiar with this from google maps), often I see this intuitive feature left out of zoom set-ups. The x and y settings are automatically used for click-and-drag panning as well.\n\nWe find the z value from the scale using the function above. We have to make some additional adjustments to the x and y values to translate d3's x and y values, which locate (0,0) at the top left, to three.js's, which put (0,0) in the middle of the visualization. We also divide the x and y values by the scale to remove the scale adjustment built into the d3 transform.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":450,"value":"function zoomHandler(d3_transform) {\n let scale = d3_transform.k;\n let x = -(d3_transform.x - viz_width/2) / scale;\n let y = (d3_transform.y - height/2) / scale;\n let z = getZFromScale(scale);\n camera.position.set(x, y, z);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":461,"value":"md`We place our zoomHandler within d3 zoom handler. Here we also set the scaleExtent for d3.zoom using the values from our near and far plane settings translated from camera positions to scale by our getScaleFromZ function. Really you don't need these to eactly equal each other, you just need to make sure your thresholds contain the scale extent (otherwise your points will disappear when you cross the threshold), but it feels nice to have them exactly synced up.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":63,"value":"zoom = {\n let d3_zoom = d3.zoom()\n \t.scaleExtent([getScaleFromZ(far), getScaleFromZ(near)])\n \t.on('zoom', () => {\n let d3_transform = d3.event.transform;\n zoomHandler(d3_transform);\n });\n return d3_zoom;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":467,"value":"md`After you have your d3-zoom behavior all set up you attach it to the view DOM element. The last thing you need to do (which tripped me up for a bit) is sync the initial position of d3 zoom transform and the camera position. This means setting their scale and z position to be equivalent, and offsetting d3's x and y position to compensate for three.js's different coordinate system.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":124,"value":"view = d3.select(renderer.domElement)","pinned":true,"hidden":false,"mode":"ojs"},{"id":54,"value":"{\n function setUpZoom() {\n view.call(zoom); \n let initial_scale = getScaleFromZ(far);\n var initial_transform = d3.zoomIdentity.translate(viz_width/2, height/2).scale(initial_scale); \n zoom.transform(view, initial_transform);\n camera.position.set(0, 0, far);\n }\n setUpZoom();\n return setUpZoom;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":472,"value":"md`With that, you've got a mouse-directed zoom and pan set-up that works across desktop and mobile.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":474,"value":"$34","pinned":false,"hidden":false,"mode":"ojs"},{"id":477,"value":"md`#### Circle: anti-aliasing off`","pinned":false,"hidden":false,"mode":"ojs"},{"id":479,"value":"html`

`","pinned":false,"hidden":false,"mode":"ojs"},{"id":630,"value":"circle_sprite= new THREE.TextureLoader().load(\n \"https://blog.fastforwardlabs.com/images/2018/02/circle-1518727951930.png\"\n)","pinned":true,"hidden":false,"mode":"ojs"},{"id":481,"value":"md`#### Circle: antia-aliasing on`","pinned":false,"hidden":false,"mode":"ojs"},{"id":483,"value":"html`

`","pinned":false,"hidden":false,"mode":"ojs"},{"id":643,"value":"circle_sprite_aa= new THREE.TextureLoader().load(\n \"https://blog.fastforwardlabs.com/images/2018/02/circle_aa-1518730700478.png\"\n)","pinned":true,"hidden":false,"mode":"ojs"},{"id":485,"value":"sprite_settings = {\n \n // Non anti-aliased settings\n let circle = {\n map: circle_sprite,\n transparent: true\n }\n \n // Anti-aliased settings\n let circle_aa = {\n map: circle_sprite_aa,\n transparent: true,\n alphaTest: 0.5\n }\n \n // Switch out which settings object is returned to change settings\n return circle_aa;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":493,"value":"md`After a bit of experimentation, I settled on 256x256 for the size of the sprite. I'd love to know more about how different sizes affect appearance or peformance. I think the sprites in the final visualization turned out pretty well but sometimes I still feel the edges look a bit\nrough on high-resolution screens.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":496,"value":"md`## 3. Coloring points\n\nIn three.js, you create a Points object using pointsGeometry and pointsMaterial. To color points you set an array of colors on pointsGemoetry and you set the vertexColors property on the pointsMaterial.\n\nBelow is the code for setting up the points for the visualiztion. I'm using fake generated data (generated_data below) in this example.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":498,"value":"points = {\n let pointsGeometry = new THREE.Geometry();\n \n let colors = [];\n for (let datum of generated_points) {\n // Set vector coordinates from data\n let vertex = new THREE.Vector3(datum.position[0], datum.position[1], 0);\n pointsGeometry.vertices.push(vertex);\n if( datum.group > -1 ) {\n let color = new THREE.Color(color_array[datum.group]);\n colors.push(color);\n } else {\n let color = new THREE.Color(0xefefef);\n colors.push(color);\n }\n }\n pointsGeometry.colors = colors;\n \n let pointsMaterial = new THREE.PointsMaterial({\n size: pointSize,\n sizeAttenuation: false,\n vertexColors: THREE.VertexColors,\n });\n \n // Add settings from sprite_settings\n for (let setting in sprite_settings) {\n pointsMaterial[setting] = sprite_settings[setting];\n }\n \n return new THREE.Points(pointsGeometry, pointsMaterial);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":504,"value":"md`In this example I'm coloring my data based on their group. The group is an integer from 0-6, I'm using that to select from a premade array of colors and pushing the color for each item into the colors array, which I then set on pointsGeometry. It took me a while to get used to the three.js specific syntax (like remembering which things I set on geometry and which on material), but, overall, coloring by category was relatively straightforward.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":509,"value":"$35","pinned":false,"hidden":false,"mode":"ojs"},{"id":524,"value":"md`## 4. Hover interaction\n\nTo add hover interaction to the points in our visualization, we first need to figure out when we're hovering over a point. Since we're rendering on a canvas element, the points are not DOM elements and don't have their own mouse events. If you were doing your own custom canvas thing, you'd have to devise a way to keep track of zoom and object position and then compare that to the mouse position (an interesting but time-consuming route). Thankfully, three.js has a built-in method that takes care of things for us. The idea is to project a ray from the camera through the mouse and find which objects it intersects with. This evidently comes up often enough that the three.js maintainers made a class for it called Raycaster.\n\nTo get started we create a raycaster we can reuse and attach a function to the view to check for intersects whenever the mouse moves over the visualization.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":534,"value":"raycaster = new THREE.Raycaster()","pinned":true,"hidden":false,"mode":"ojs"},{"id":532,"value":"{\n view.on(\"mousemove\", () => {\n let [mouseX, mouseY] = d3.mouse(view.node());\n let mouse_position = [mouseX, mouseY];\n\tcheckIntersects(mouse_position);\n });\n return view;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":538,"value":"md`To get the intersect we first tramslate the d3 mouse coordinates into a three.js vector.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":614,"value":"function mouseToThree(mouseX, mouseY) {\n return new THREE.Vector3(\n mouseX / viz_width * 2 - 1,\n -(mouseY / height) * 2 + 1,\n 1\n );\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":608,"value":"md`The raycaster takes the mouse vector and the camera and returns a list of intersects. We then sort those intersects by the property distanceToRay. This is a gotcha I'll talk more about below. The first object in the sorted intersect array is the point we're hovering over. We get the index from that point and look up the data for it by using the index to select the relevant object from our original points data set. An alternative approach would be to add the relevant fields to the three.js points when you create them. See this [StackOverflow discussion](https://stackoverflow.com/questions/18319154/with-three-js-can-i-attach-information-to-an-object-such-as-a-url) for more information on that.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":541,"value":"function checkIntersects(mouse_position) {\n let mouse_vector = mouseToThree(...mouse_position);\n raycaster.setFromCamera(mouse_vector, camera);\n let intersects = raycaster.intersectObject(points);\n if (intersects[0]) {\n let sorted_intersects = sortIntersectsByDistanceToRay(intersects);\n let intersect = sorted_intersects[0];\n let index = intersect.index;\n let datum = generated_points[index];\n highlightPoint(datum);\n showTooltip(mouse_position, datum);\n } else {\n removeHighlights();\n hideTooltip();\n }\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":569,"value":"md`#### A note on ray point threshold and sorting by distanceToRay\n\nAfter I got my ray working I was stumped by an issue where the first intersect object was not the one directly under my mouse. If I highlighted all the points returned as intersections they formed an area defined around my mouse position, but much bigger to it. Searching led me to this [StackOverflow answer](https://stackoverflow.com/a/44999959/8691291) which suggested adjusting the point threshold property on the raycaster params to match the size of your points (it defaults to 1).`","pinned":false,"hidden":false,"mode":"ojs"},{"id":544,"value":"{\n raycaster.params.Points.threshold = 1;\n return raycaster;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":571,"value":"md`Changing the point threshold definitely had some effect (making it bigger made the threshold bigger) but setting it to match the size of the points did not mean it only triggered the intersects when you were directly over a point. It seems like the threshold scales with the camera position, while my points, because I've set sizeAttenuation to false, do not. Anyway, it turned out to be kind of a moot point because I figured out I could sort the intersects by the property distanceToRay. After sorting the first point is the one nearest the mouse. The fact that the ray is larger than the points turns into a feature: it means that when I'm near a point I see a tooltip, rather than having to be directly over the point. Since the points in the visualization are pretty small this is more convenient for the user. Still, it would be nice to figure out exactly how the threshold interacts with zoom so you could have precise control over the interaction (please let me know if you do).`","pinned":false,"hidden":false,"mode":"ojs"},{"id":546,"value":"function sortIntersectsByDistanceToRay(intersects) {\n return _.sortBy(intersects, \"distanceToRay\");\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":577,"value":"md`### 4.1 Enlarging a point on hover\n\nSoon we're going to add a tooltip to on hover, but it's also good to add some indicator to the point itself that it's registered the hover. If we had CSS at our disposal we could do something like add a black border on with the :hover selector. We are far from CSS, however. In fact, we don't want to change the point we've already rendered at all. Instead we want to draw a new point (with the style we want) directly on top of the point we're hovering over. For me, getting used to three.js was a lot about getting used to the idea that is often easier to draw a completely new thing than modify an existing one. To handle the points we add on hover we're going to create an Object3D to use as a container for them and add that to the scene. This makes it easier to keep track of and clear the objects we add on hover.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":582,"value":"hoverContainer = new THREE.Object3D()","pinned":true,"hidden":false,"mode":"ojs"},{"id":586,"value":"{\n scene.add(hoverContainer);\n return scene;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":580,"value":"md`When we hover over a point we create a new point and add it to hoverContainer. This point is styled in the same way as the existing points, just at a larger size. You don't have to use a point object here, in the prototype this code is based on I used a mesh object to show a book cover when you hovered over a point.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":558,"value":"function highlightPoint(datum) {\n removeHighlights();\n \n let geometry = new THREE.Geometry();\n geometry.vertices.push(\n new THREE.Vector3(\n datum.position[0],\n datum.position[1],\n 0\n )\n );\n if( datum.group > -1 ) {\n geometry.colors = [new THREE.Color(color_array[datum.group])];\n } else {\n geometry.colors = [new THREE.Color(0xefefef)];\n }\n\n let material = new THREE.PointsMaterial({\n size: 10,\n sizeAttenuation: false,\n vertexColors: THREE.VertexColors\n });\n \n // Add settings from sprite settings\n for (let setting in sprite_settings) {\n material[setting] = sprite_settings[setting];\n }\n \n let point = new THREE.Points(geometry, material);\n hoverContainer.add(point);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":596,"value":"md`One nice thing about this method compared to doing similar things with CSS and the DOM is that there you often have issues where the enlarged hover object intercepting your hover and blocking it from reaching nearby objects. Here you are only checking for intersections on the original points, not anything you draw on hover.\n\nTo clear objects when you un-hover, we just use the hoverContainer's remove function. You run it every time you run highlight point to clear the highlights from previous runs.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":560,"value":"function removeHighlights() {\n hoverContainer.remove(...hoverContainer.children);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":599,"value":"md`You also want to be sure to remove highlights when the mouse leaves the visualization.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":564,"value":"{\n view.on(\"mouseleave\", () => {\n removeHighlights()\n })\n return view;\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":602,"value":"md`### 4.2 Hover tooltip\n\nTo add the tooltip we step out of the world of three.js and back into HTML, appending a div over the visualization and using CSS absolute positioning to pin it to the mouse. This is the approach the [three.js docs recommend](https://threejs.org/docs/#manual/introduction/Creating-text), I think because working with text in three.js is difficult.\n\nIn my project I was using React, so I passed the relevant info (mouse position and point data) up into the containing component and used that to set the state for the HTML div. The code below does a similar thing but is a more minimal technique designed just to work in the notebook (note the default div styling is set up in the code block for the visualization at the top of the page). The important thing to note is how to get the information from the point, after that you can set it in React of JQuery or any way you like.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":909,"value":"empty_tooltip_group = \"{\\\"id\\\": -1, \\\"max\\\": 0.0, \\\"0\\\": {\\\"word\\\": \\\"\\\", \\\"weight\\\": 0.0}, \\\"1\\\": {\\\"word\\\": \\\"\\\", \\\"weight\\\": 0.0}, \\\"2\\\": {\\\"word\\\": \\\"\\\", \\\"weight\\\": 0.0}, \\\"3\\\": {\\\"word\\\": \\\"\\\", \\\"weight\\\": 0.0}, \\\"4\\\": {\\\"word\\\": \\\"\\\", \\\"weight\\\": 0.0}}\"","pinned":true,"hidden":false,"mode":"ojs"},{"id":186,"value":"tooltip_state = { \n return {display: \"none\", group: empty_tooltip_group } }","pinned":true,"hidden":false,"mode":"ojs"},{"id":192,"value":"function showTooltip(mouse_position, datum) {\n let tooltip_width = 240;\n let x_offset = -tooltip_width/2;\n let y_offset = 30;\n tooltip_state.display = \"block\";\n tooltip_state.left = mouse_position[0] + x_offset;\n tooltip_state.top = mouse_position[1] + y_offset;\n tooltip_state.name = datum.name;\n if(datum.group>-1) {\n tooltip_state.group = cluster_signature[datum.group].label_data;\n } else {\n tooltip_state.group = empty_tooltip_group;\n }\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":127,"value":"function hideTooltip() {\n tooltip_state.display = \"none\";\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":674,"value":"$36","pinned":false,"hidden":false,"mode":"ojs"},{"id":726,"value":"md`## 6. Wrapping up\n\nI hope this was enough to get people started who, like me, are moving into three.js from other visualization frameworks. I think interest in what machine learning systems are doing is going to continue to grow, and that by developing better interfaces for visualizing it we can increase understanding and open doors to human-machine collaboration. I hope this helps people develop those visualizations and interfaces.\n\nAlso a last big thank you to all the people who work on three.js and d3 and answer questions about them on StackOverflow.`","pinned":false,"hidden":false,"mode":"ojs"},{"id":767,"value":"md`– Grant ([@grantcuster](http://twitter.com/GrantCuster), grantcuster at gmail dot com)`","pinned":false,"hidden":false,"mode":"ojs"},{"id":658,"value":"md`## 7. The rest of the code`","pinned":false,"hidden":false,"mode":"ojs"},{"id":414,"value":"function toRadians (angle) {\n return angle * (Math.PI / 180);\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":754,"value":"mutable viz_width = Math.min(width, 1400)","pinned":true,"hidden":false,"mode":"ojs"},{"id":16,"value":"height = 700","pinned":true,"hidden":false,"mode":"ojs"},{"id":806,"value":"unmapped_data = FileAttachment(\"PSC_cluster_scatter.json\").json()","pinned":true,"hidden":false,"mode":"ojs"},{"id":811,"value":"generated_points = unmapped_data.map(d=> Object.assign( \n {position: [d.x, d.y],\n name: d.text,\n group: d.cluster_id\n }\n))","pinned":true,"hidden":false,"mode":"ojs"},{"id":861,"value":"raw_cluster_data = FileAttachment(\"PSC_clusters.json\").json()","pinned":true,"hidden":false,"mode":"ojs"},{"id":925,"value":"function compare( a, b ) {\n if ( a.id < b.id ){\n return -1;\n }\n if ( a.id > b.id ){\n return 1;\n }\n return 0;\n}\n","pinned":true,"hidden":false,"mode":"ojs"},{"id":920,"value":"cluster_signature = raw_cluster_data.sort(compare)","pinned":true,"hidden":false,"mode":"ojs"},{"id":30,"value":"point_num = generated_points.length","pinned":true,"hidden":false,"mode":"ojs"},{"id":26,"value":"function buildColorArray(n) {\n let color_array = []\n for (let step = 0; step < n; step++) {\n let c = Math.floor(Math.random()*16777215).toString(16);\n color_array.push(\"#\"+c)\n }\n return color_array\n}","pinned":true,"hidden":false,"mode":"ojs"},{"id":828,"value":"color_array = buildColorArray(point_num)","pinned":true,"hidden":false,"mode":"ojs"},{"id":8,"value":"renderer = new THREE.WebGLRenderer({antialias: true})","pinned":true,"hidden":false,"mode":"ojs"},{"id":10,"value":"THREE = require(\"three@0.89.0/build/three.min.js\")","pinned":false,"hidden":false,"mode":"ojs"},{"id":12,"value":"d3 = require(\"https://d3js.org/d3.v5.min.js\")","pinned":false,"hidden":false,"mode":"ojs"},{"id":14,"value":"_ = require('https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.5/lodash.min.js')","pinned":false,"hidden":false,"mode":"ojs"}],"files":"$W37","stdlib":"1","titling":"auto"}