which I understand analyses only 2 octave bands (500 Hz and 2 kHz) instead of the 8 bands (for which the STI component requires background noise.)
Or have I misunderstood this metric and the three values mean something else?
For reference / a minimal definition I have the open office example (gha and 3dm attached) which includes 20 receivers and the sti results show three values for each (see the image).
Thanks in advance Roly…
the baked result into a mesh in Rhino
3) Select the mesh, in Rhino and type "ReduceMesh".
4) Set the number of meshes as simple as possible (i.e. visually - click preview) without destroying the main structure. You'll see that the spheres dissapear. 500 seems to be good when handling the entire structure
5) insert the resulting, reduced, mesh into Grasshopper and subsequently into the script. The image only shows a section of the structure since the operation takes a while.
Exploding the mesh takes out the bulgy node effect we're after.
But, experiment with it.…
ern
2 - use the b+w values for a circle packing
3 - keep the circle center points
4 - copy them across (and above/below if you want a doubly periodic pattern)
5 - make the voronoi (or delaunay in your case)
6 - keep only the curves whose center lies in the original bounding box
…
almost 60 seconds to compute, 50x50 points x 35 samples each x 3 rectangles = more than a quarter million curve|curve intersections), but at least not fossilised dog slow.
The inputs of the component are:
P = Plane in which to shoot the isovist sample rays, plane origin equals sample point
N = Number of rays per sample point
R = Maximum radius of sample rays. Any obstacles beyond the radius are ignored
O = List of obstacles (curves only). They will not be projected onto the sample plane, so you can have curves that are only partially 'active'.
Outputs:
P = Point at end of ray (at distance R from sample point) or point at closest obstacle along ray view direction.
D = Distance from sample point to P
H = Boolean indicating whether the ray hit an obstacle or not
--
David Rutten
david@mcneel.com
Poprad, Slovakia
…
nd stress of a plate that is supported at two opposite sides (rotational degrees of freedom are allowed) and gravity load is applied. By now I can only verify the displacement of the plate with a deviation of less than 3 % using ANSYS Workbench. Kirchhoff's plate theory as an analytical approach gives a similar result with 10 % deviation.
The van Mises stress and Principal stress results in Karamba are approximately 200 times higher than the results in ANSYS and the analytical results. I tried to find the mistake for several days now and would appreciate any help or similar problems with validating the shell stresses.
Here are the values of the plate:
length: 1 m, width: 0.2 m, thickness: 0.01 m
Material: Steel 'S235' (standard)
resulting gravity load: 0.157 kN
displacement in Karamba: 0.000583 m
stress in Karamba: 116 kN/cm² (=1160 MPa = 500 % utilization!)
stress in ANSYS: 0.57 kN/cm² (=5.7 MPa)
The utilization of 500 % for a steel plate under its own dead weight makes we wonder what is wrong... See the grasshopper definition and the picture attached.
Best regards and thanks for any help,
Robert…
ome struggling i managed to get the effect i wanted but i have three problems:
1) i can't really scale these, hexagons were moved in the easiest way, so i have no control over the pattern
2) i feel that i made it pretty messy with all the dispatches, rotations etc - does it make the definition run slow? how could i simplify my definition?
3) most important i have no idea how to transfer it to hexagonal grid (so i can use jpg as attractor) for a bigger pattern. i tried starting from the hexagonal grid but couldn't get it and eventually got lost, but maybe thats the right way?
Pardon my english, hope i will get some help from you, have a good day :)…
on excel (leaving 0,0 cell blank and also making sure there are no commas in the names ) Also let's call the names "ID"
2 - For the weight, use numbers ranging from 1 - 10 where 10 is the highest dependancy.
3 - Save the file as a Unicode CSV from excel
4 - Create another file on excel that has the attributes of your spaces, with the names of your spaces under the header ID (let's start with a simple "area" and "SNo" attribute but you could add more features for sorting and manipulating your data)
5 - Open Gephi and further open your matrix CSV file
5 - Import it as "," (comma delimited file) and make sure you check "matrix" for the data type
6 - Ensure the import is nondirectional as well (or Gephi adds silly arrows)
7 - Not gonna go into the gephi bit too much but select a force atlas layout and set the force to something high 1000 or 10000 depending on the size of the data and the attraction to a 1000th of that 1 or 10. Go to the data lab and import your excel with the attributes and append to your existing datasheet.
8 - Set the node attributes to use the area for the node size and color scheme to SNo
9 - Play around with all the layout options and finally go to your preview. Once you're happy with it, export it to a GDF graph file.
the GDF now has the coordinates of the circles and the diameters. as well as the edge connections.
I've written a very amateur script that converts this to GH geometry (below)
Hope this helps someone out, I'm still figuring out the gephi streaming API but I've only started with python about a month ago so might take a while to get there.
You can use the second half of the GDF files to also create dependency chord diagrams online as shown in the third image.
https://flourish.studio/2018/07/25/how-to-make-a-chord-diagram/
Cheers,
Sanjay
…
思った感じになりません。
balls の代わりにplanarカーブを直接入れてみましたがエラーが出ます。
ファンクションにしてみたところ、forループので作った数値が反映されていません。
ファンクションのインスタンス?を出力していないと思い上記のようにしましたがエラーが出てしまいます。
以上の事から自分の認識が正しいのかよくわからなくなりました・・・
python自体の深いところをわかっているわけではないので余計こんがらがりました。
そこで、for b in ballsはどのような条件または使い方であれば使えるのでしょうか?
そして、上記のように別のオブジェクトに対しての使い方はどのようにすればできるのでしょうか?
2:同じファンクション内のdist = rs.Distance(self.pos,b.pos)についてですが
この文章も for b in balls によってbはBallのインスタンスであると定義?されたためb.posがbの位置であると分かるのでしょうか?
pythonは定義しなくても動いてしまうのでどのような時に使えるのか文章見ただけではよくわかりません・・・
大変細かいことかもしれませんが、よりpythonをしっかりと理解するためにも、どなたかわかる方ご教授いただけると幸いです。…
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.…
edefining the axis variables, logarithmic scales, display thresholds, better marking management - or at least add contrast!
Hey Fred,
thanks for the feedback! This is a basic version, and personally I used a custom component to read and parse the history files from the canvas to be able to e.g. scroll through generations and solutions or display more solutions at once (via pathes, mostly requires modification of the initial setup) ...
but you are right. I would love to bring the solution's navigation directly into the rhino viewport but I think that would be a major hack .. unless you can give me a hint how to do that. the displaying and user-preference-handling are besides a re-entrant history, some more algorithms and parallelization the next things to tackle, but display is definitely one of the easiest, so ... soon! work will begin in january i guess, since the project then starts i hope - but it will start for sure.
best
r
…