urs x 365 days ), and with modulus in the screenshot above, i could manage to do for every hour. but sometimes in my definition, i have a range from 1 to 35040, which is 365 x 24 x 4 ( 4 here defines every 15 minutes), on other word, when the number is one, then i have 01:00 O'Clock, when the number is 2 then i have 01:15 O'clock, when the number is 3 then i have 01:30 O'Clock...etc , so when the number is 97, which is the next day ( and after the number 96 which is equal 24 hours x 4), then I should have again 01:00 O'Clock.
I hope my idea is clear, thanks in advance!
Nassif…
GH) > then define (still in GH) some instance definition (or many: case variants) > then place it according some "policy" (3d point grid and the likes). Note: Only doable with code, mind (C# in my case).
Obviously you can skip the creation part and instruct GH to deal with instance definitions already listed in the Block Manager (say: find the block named "cell666_B3" blah, blah) ... but that means that you can only use them (meaning a rather "limited" parametric approach) and not make them from scratch (meaning a true parametric approach).
But I guess that you've tried the block way in the Rhino environment already. That said I use rather solely this approach in GH and yields quite manageable object collections - I would say "real-time" response (up to 20K instances) but I use dedicated Xeon E5 1630 V3 workstations (with NVida Quadros K4200 and up for the graphic response part of the equation) so the "performance" is rather a subjective thing.
Modifications:
easily doable with GH (on instance definitions at placing time: since you need only to scale them and not vary their topology).
Anyway post a portion of the R file.…
FORE MeshMachine (rather better) or after
BTW: For a mesh with 7M points ... well... you'll need some proper CPU to deal in a reasonable amount of time (what about a Xeon E5 1630 V3?).
Alternatively find a friend who knows very well Modo ... and see first hand what the US Movie Industry is all about.…
closest point to the very first would be removed from the list, so the initial list reduces from 100 to 98. From the 98 i pick one and search the remaining 97 for the closest. From the remaining 96 i pick again one and search in the 95,...
(The product I want to result is:
having a number of random lines in 3D space, produced by an even number of points as discribed, this shall be the initial springs for a ("selfadjusting") tensegrity. Each one of these lines (later springs in kangaroo) get divided in three areas - that means four points. These four points again are the "attractor points" of neighbor springs, so the strut "knows" where to set the next elastic connection,...the rest I´ll have to figure out)
angelos…
more complex geometries, nothing works anymore and the output is weird: every test point has the same value (97% DA) and it's impossible to visualize these values even if a text tag 3D is assigned to points (check Result.jpg)
The output that we get is a uniform mesh.
To check this output we also run an illuminance analysis using the same test surface, giving 300lux as high and low bound and some areas didn't reach the target value - which means that there must be some areas below that threshold.
Another thing: as you can see from Screenshot.jpg at one point we get the string saying *.dgp not found. Is that a problem?
Attached you can find the Grasshopper file.
Thank you all!
Simone
…
untime error:
Runtime error (PythonException): unable to add point to document Traceback: line 97, in AddPoint, "C:\Users\AKIDRIBM\AppData\Roaming\McNeel\Rhinoceros\6.0\Plug-ins\IronPython (814d908a-e25c-493d-97e9-ee3861957f49)\settings\lib\rhinoscript\geometry.py" line 136, in Point, "" line 47, in toGH, "" line 187, in RunScript, ""
Could anyone help me figure out what's causing it? The code for adding the point is below:
# Plots points/text dots def Point(self, pointSource): print pointSource, type(pointSource) pt = rs.AddPoint(float(pointSource.value.x.value), float(pointSource.value.y.value), float(pointSource.value.z.value)) return pt
pointSource is a custom object that stores information about the point. Its only relevance here is to obtain the point coordinates. I do not get this error all the time, so I'm having trouble figuring out what is exactly causing it.…