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
which will result in creating a check for each branch with one item to be 'matched' (in this case to see if it is included in the domain) with all three domains in the single list. so in the end you get a data tree with 8 branches (derived from the 8 grafted values) with 3 items in each branch, that are the check of each initial value with the 3 items domain list.
thank you for sharing the other option too!.
cheers
alex…
an't remember it) that will only give you the resulting whole number that results from any given division...modulus division will give the exact opposite, or only the fractions of numbers that result. In code they would be forward slash, back slash, and percent symbol, respectively. That's the case for VB and most other languages as well...here's a simple example...
8/3 = 2.66666
8\3 = 2
8%3 = 0.6666
HTH…
0, 5, 10, 15, 20
1, 6, 11, 16, 21
2, 7, 12, 17, 22
3, 8, 13, 18, 23
4, 9, 14, 19, 24
and if i'm here is because i'm not able... :)
can you help me?
thank you
…