m
-Area of blue line: min. 80% of the rectangel a x b
-Max. hight h of the top point: h,max = a
-Min. Volume between rectangel a x b and membrane: 500 m3
Can anyone help me?…
p of the other(they could be extruded but its still the same thing). This is a bit different from what you were doing so far.
So for adding time into the equation, I can think of 2 approaches:
1. Use metaballs to draw smooth circular outiles around the points and subtract those from the rectangle. Repeat the above for every time step and stack those surfaces in layers.
This can easily be constructed using plexiglass layers with standoff fasteners:
2. For each vessel, draw a curve that rises in Z direction and draw pipes around those curves. This is better if you want to focus on the the vessels' routes but I can't think of a direct way to construct it.
Anyway, see how these work out and I am waitting for your feedback.
Good luck, Nikos …
Added by nikos tzar at 6:03am on November 17, 2014
pull incrementally.
As a random example, let's say I wanted to move vertices 120 through to 150 in one direction, I would like to have those vertices enumerated such that vertices 120 through to 150 would be along a given row or column. Perhaps it would be every 5th vertex, or nth vertex, that would would define that row or column.
Instead, what I'm experiencing is a somewhat random number sequence such that I can't perceive a culling pattern. In the example I attached there are vertices in the 500's adjacent to vertices in 100's or 200's, etc. I was hoping to find a way to organize, or redefine, the vertex numbering, so I can easily call-out every nth vertex, that would be defined along a row or column, or quad to move in a particular direction without typing in a list each vertex one-by-one.
I hope this helps explains my question a little further.
Thanks for responding.
Jerry
…
ind that a ?^@&@% door for your next 7 series (avoid that car at any cost) is rated about 10M (the so called development cost) whilst the whole car may require 500++ M. Did you know that the software used in a 7 series exceeds 70M lines of code? Therefor ... blah, blah.
Back to real-life things:
One "suitable" solution for flattish stuff the likes that you've captured is:
1. Make a BoundingBox and make a Point3d grid using, say, the bottom 4 corners (a single dimension tree)..
2. Declare a nullable Point3d grid [ DataTree<Point3d?> hitsTree = new DataTree <Point3d?>();].
3. Shoot a Ray3d from each point using some Vector3d (for instance using p4 - p0 out of the box points). If the Ray hits a brepface get the point if not put a null. That way you have a tree of equal List sizes and "combining" things (Points) for your patterns is greatly simplified [you can use the crude try{} catch{} approach].
4. If all these sound a bit freaky to you ... post a flattish test case (with different U/V) and give some hints about what "pattern" means to you.
best…
holes on each so speed increases). Zero radius circles are skipped.
The image dimensions in pixels are defined in small panels (X=485, Y=759) and used to calculate height/width ratio. That is used to define height based on the 'X' slider (500), which defines width overall.
The 'cell size' slider is also in units and determines resolution indirectly. For any given X value, increasing 'cell size' reduces the number of grid cells (resolution) and vice-versa.
Independent of other parameters, 'Isotrim (SubSrf)' splits the base surface into sub-surfaces, onto which the circles are projected. The 'SrfSplit' does the heavy lifting (can be SLOW!) and finally, 'Sort' is used to select the resulting surfaces that contain the holes.
Benchmarks:
X = 500, cell size = 10, 3161 circlesnine subsurfaces: 'SrfSplit' = 6.6 minutes, 'Project' = 13 secs.16 subsurfaces: 'SrfSplit' = 2.3 minutes, 'Project' = 17 secs.
X = 500, cell size = 5, 12542 circles (shown)35 surfaces: 'SrfSplit' = 30.6 minutes, 'Project' = 57 secs.
As noted before, a very long-standing, well-known bug in Grasshopper fails to save the Image Sampler component when I save a copy of your file. Very annoying, but there is a work-around. Copy/paste and connect the Image Sampler from the code you posted above into the place I reserved for it.
"Pro Tip": Always work at low-resolution until your algorithms are proven before cranking up to 10K+ geometry counts!
Attached file has low resolution settings with 'Project' and 'SrfSplit' (red group) disabled.…