ctorial component to go to higher factorials/permutations just to determine easily permutations. For instance I have 30 tile colors and I wanted to see their permutations quickly, I realize I can use 30*29*28 etc but I thought I could do this using the simple definition that one can see in the pic.
RM
…
eased to announce the Beta Release of version 2.0
LINK TO FOOD4RHINO
Images tagged: Mesh(+), mesh(+)
The current version of mesh(+) is developed for:
- Rhino 5 (32 & 64)
- Grasshopper version 0.9.0056 (For Rhino 5)
- Recommended Download: Weaverbird…
e
7. True
8. True <-- this one
9. True
10. False
11. True
12. False
13. True
14. True <-- this one
15. True
16. False
17. True
18. False
19. True
20. True <-- this one
21. True
22. False
23. True
24. False
25. True
26. True <-- this one
27. True
28. False
29. True
30. False
31. True
32. True <-- this one
33. True
Any idea how I can solve this?
Thanks!…
vas
Closing and creating a new file (memory resets when this is done) @4:00, 5:57, 6:53
System slow down and crashes @ 8:16 (takes 5 minutes to end the process - perhaps not the most entertaining movie to watch until the end - a good point to turn the kettle on)…
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