2GB RAM and a GeForce 4 mx 4000 128MB (and I suspect is not working for Rhino or Gh, because in my openGL preferences Rhine says I have only 64mb of video memory), and still within a couple of months I was able to do my entire graduation thesis, modeled 95% in Gh.. So a basic pc is not an excuse thanks to you guys :D
final renders..…
Added by Diego Xavier at 11:08am on February 7, 2013
which doesn't exist in the actual problem spec. If galapagos is allowed to change the column position in all possible directions, it is less likely to get stuck in some local optimum.
Let's assume that (all other things being equal) column 20 would yield the best possible answer. The current state of the system though is at column 26, which is pretty good too, just not as good. Galapagos is more likely to 'mutate' the state a little bit instead of a lot, so it'll explore the columns near 26. However 20 isn't near 26 at all, only 25 and 27 are nearby, and maybe 24 and 28. But they'll all worse answers, so after sampling in those directions GP will abandon that as fruitless.
If however you specify the columns using two variables, then the columns near 26 are 20, 25, 27 and 32. That's a far richer space to explore which much better approximates the real problem.…
are not copy with the number that belong to each other, like:
untrimmed surface0 should be 41 pieces
untrimmed surface1 should be 28 pieces
untrimmed surface1 should be 21 pieces
it result like this
exclude the 1st and 2nd pieces,the others all is untrimmed surface 1
and the attachments is the result that i want, I done it one by one.…
es, and these sum up to ~7100. I shall see if I can post a screenshot of everything.
I have no idea how to script that, sorry. But maybe could be a more optimized workflow - just feed one object B at a time, maybe that makes the math behind it more relaxed.
I should emphasize that it is not about 'fault' in the operation, and rather a very slow calculation - the difference does eventually get calculated with no errors whatsoever, the only problem is the unbelievably inefficient, or unproductive time it takes to do so. I think the problem could be the proportion of the objects, one very large, and one very small (28 / 6 / .1cm vs. .05cm), maybe that does something funky to the bounding box calls, I have no idea. And one other thing I suspect is the number of faces in the object, as I progress to let's say 700 cuts, I have then created 700*4 new faces in the object. I don't know if this is indeed something of concern. …
Added by DumDaDaDum at 7:03am on September 29, 2011
6, 7, 8, 9, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, etc
In addition to the components in the attached file, I have also tried using Cull Index but that did not do much. I tried using a number slider set to whole numbers with the range equal to the values I have set up in the integer, but it just increases the size by 1 every time. Any help on steps in the right direction would be great thanks.…
Join Somewhere Something in Downtown Los Angeles for Summer 2016 workshop series.
Physical Computing with Firefly / August 27
GIS in Grasshopper / August 28
Grasshopper Plugins / September10+11
Mmm really nice post. Usually light electronic Trip Hop, or spanish Hip-Hop.
Portishead
Radiohead
Massive Attack
Propellerhead
SFDK
Juaninacka
Tote King
Best Regards ;)
port.
In my case, I downloaded arduino installer again from arduino website, then I chosen correct port that "control panel > device and printer > Arduino Uno > choose correct COM".
Finally, I could enjoy arduino and firefly!
Thank you Andy!…