ere a way to set this up in a way that lets say when there are 28 it will go for one of 4, 7 or 14 and if it is a primer number it will exclude enough number of boats to obtain the closest suitable number - lets say there are 29 boats but it will only show 28 and go back to selecting 4,7 or 14.…
Added by Levent Ozruh at 10:40am on October 14, 2014
byte-accuracy red, green, blue channels) = 27 bytes. More likely 28 bytes as colours are probably stored as 32-bit integers, allowing for an unused alpha channel.
28 * 800,000 equals roughly 22 megabytes, which is way down from 9 gigabytes. That's a 400 fold memory overhead, which is pretty hefty.
Grasshopper stores points as instances of classes, so on 64-bit systems it actually takes 64+64+3*8 = 152 bytes per point*, which adds up to 122MB, still way less than 9GB. It would be interesting to know where all the memory goes...
* Grasshopper points also store reference data, in case they come from the Rhino document. This data will not exist, but even so it will require 64-bits of storage.…
Added by David Rutten at 4:13pm on December 11, 2014