metasyn / dreda Goto Github PK

we need to write a function that looks through the data on load, and decides on the best maximums for plan edge boundaries.

Right now, the edge (global variable) is hardcoded to 500 - if someone's data has a min of -2 and a max of 10, the xz-grid would dwarf the values.

Since the edge needs to be determined before initializing the scene, I'd think that if someone uploads data, this would need to be called before init to set edge to a reasonable size.

30?

cluster limit will be related but also bound by color choices

cluster limit will be related but also bound by color choices

I found the load takes over 30 seconds for your sample size of 20000.
I've got it down to ~18 milliseconds and will submit a pull request soon. The problem was using underscore to get the size in your loop; it had to execute that code for all 20000 iterations. My fix simply stores the size in a var before starting the loop. Should I use the group, or submit to your repo? I'm fine with your repo being the main one and ditching the group if you want to.

If the window is resized the 3D rendering gets stretched or smooshed. I'm going to look into using THREEx.WindowResize to fix this.

create renderer, scene, camera, floor (see through grid and y axis vector)

https://stemkoski.github.io/Three.js/Mouse-Tooltip.html

I think a modal should do:

http://semantic-ui.com/modules/modal.html

more classic example with more distinct clusters

for basic point