e in Euclidean space then the distance metric can be discontinuous:
Discontinuous means that a tiny change in input may result in a large change in output. Observe the image above, we start measuring euclidean distances from point A. At first the process appears to be continuous. We measure at distance b and we get point B. We increase the distance slightly to c and we get point C, which is very close to point B. We increase the distance slightly again to d, but now suddenly we're in a completely different location. This jumping behaviour can mean that certain questions (such as: "how do I divide this curve into 4 points, all equally far apart?") do not have an answer. It could be possible for 3 and 5, but not 4.
Another problem is that there may be multiple solutions. In the image above the point D isn't the only point that is d units away from A and coincident with the curve. There may be any number of those points depending on the shape of the curve, the location of A and the value of d. And of course once you have two (or more) solutions, you can have two (or more) answers. Then each of those solutions may yet again have more than one outcome for the next point in the chain and before you know it the question you asked has 35295 different answers and good luck trying to find one you like.
Now of course sometimes it is possible to answer your question unambiguously. I made a solution that uses Galapagos. It's pretty slow, and it'll get slower the more segments you want:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 4:26am on September 9, 2013
ation model, and I would be very grateful if you could help me to have a look.
1. The air change rate is assumed to be 0.5 times per hour and the infiltration rate is 0.1 times per hour, so I sum these two values and set the converted infiltration rate per area as 0.0005 m3/s-m2. I don’t know whether it is appropriate to sum these numbers and input them together in the “infiltration rate per area” part?
2. I found in the latest version, there is a component called “air flow”, which can edit natural ventilation, but if I set minIndoorTempForNatVent equal to the heatingSePt as you showed once in the forum, the simulation result of heating is ridiculous high (like 7000 kwh/m2a). If the minIndoorTempForNatVent value is set to be a little higher than the heatingSePt, the heating result looks much normal (like 200 kwh/m2a). I don't know whether there is anything wrong with my model or settings, and hope you could help me.
3. I want to add the cooling and heating COP values (2.8 and 0.8) in my simulation process. I have noticed that in the forum, you mentioned that the new component "setEPIdealAir" can help to add COP, but I am still very confused about how exactly it works. I would be very grateful if you could show me again here.
4. I tried to change the WWR and the U-value of the wall, but I found the results of cooling and heating (especially cooling) vary little, which is not supposed to be like that. I guess there should be something wrong...
That's all for my questions.
Thank you so much for your time in advance. I would be very grateful if you could help me in this model. It would be very helpful for my work.
Thank you again!
Cheers,
Yao…
component and connect to L data from A and to i data from B I would like it to make tree like :
path {0,0}
a
b
c
path {0,1}
b
c
d
path {1,0}
e
f
g
path {1,1}
f
g
h
…
; }
DA.SetDataList(0, crvS);
distance << is "double (input)".
But... still have error.
Even all there below have error.
crvList[0].OffsetOnSurface(brep.Faces[0], distance, 0.001));
crvList[0].OffsetOnSurface(brep.Faces[1], distance, 0.001));
crvList[0].OffsetOnSurface(brep.Faces[2], distance, 0.001));
crvList[0].OffsetOnSurface(brep.Faces[3], distance, 0.001));
crvList[0].OffsetOnSurface(brep.Faces[4], distance, 0.001));
I don't know why it's still doesn't work.
…
to be used. This to me was an exercise rather than as a plugin.
I'm not sure of your question, refers to this?
Gh_transform can concatenate the transformations (which without that perhaps this component did not have much sense), and also can of course split the concatenation. If you want the step 3 (index 2), then choose the transformations 0, 1 and 2 and concatenate them. The file above (and the video, at end) has an example of this. If you mean something else, please let me know.
Oh damn, I just saw that the undo has stopped working, shit xD you meant that? Something I changed at the last time that it crashed, I will fix it soon.…
them can be addressed before winter.
Bugs:
. Vector preview is great, but it doesn't refresh (clear) when you disconnect components. You must delete the component or reconnect to refresh the vector previews.
. When passing values through a note pad, note pad fails to update continuously. Moving the notepad updates the display.
. Cannot pass a notepad integer into an fx1
. Point preview in RH5 appears as large red blocks, not as red crosses. (This is an old bug, may have been fixed with RH5 update in the meantime.)
. After adjusting Graph in dialog box, graph appears to be a solid grey object until moved.
. After copying and pasting, a lot of components are broken, return nulls. Requires reconnect to recompute (haven't had this problem in a while, will see if I can find a file that recreates it)
. BIG ONE: Loading a graph mapper with a file not found creates broken file... graph mapper disappears off canvas and the output wire appears turns orange and appears to be coming from the 0,0 pixel of the canvas. This happens any time you try to port a .ghx file to another system with different drive letters/paths, etc.
Wish list:
Mass addition for vectors
Interactive domain control for Image Sampler (like with Gradient Mapper)
Allow Addition Component to handle String values (A + B = AB)
BIG ONE: Request Override for Icon display for Parameters, Wireless receiver, and script components if you change the name
BIG ONE: Add new behavior for Stream Filter and Stream Gate: Allow multiple index numbers. The Index number picks the value/object in the corresponding index position in the selected list.
For instance:
List 0: A, B, C, D, E
List 1: 1, 2, 3, 4, 5
List 2: .1, .2, .3, .4, .5
Index Stream: 0, 2, 2, 1, 1, 2, 1, 0, 1
Results: A, .2, .3, 4, 5 (This is new behaviour and more useful than Weaving)
I have attached a GHX that includes VB components that do this, but it would be better to have GH components with I/O manager options and data matching behavior, etc.
Thanks,
Marc Syp
Knowlton School of Architecture
The Ohio State University
Columbus, OH…
si à faire le tri avec Grasshopper et l'outil Points in Brep, comme je pensais. Je suis passé d'environ 400 000 points à uniquement 20 000 points autour de mes 3 rails. C'est très efficace (mais un peu dangereux avec tous ces points).
J'ai interdit au composant CircleFit de faire un cercle, s'il n'y a pas au moins 5 points présents sur la section. Car lorsqu'il y a seulement 3 ou 4 points, il suffit qu'il y en ait un pour que le cercle soit faux, alors qu'au delà, le cercle a plus de chance d'être "bon".
J'ai également créé des "Pipe" (créés à partir de portions de l'axe) au lieu des "Box » de sélection des points pour éviter de sélection trop de points que ne serait pas des points du rail.
J'ai ensuite créé des « panel » pour la moyenne des distances en X et en Y et la moyenne des distances centre à centre.
Tout cela fonctionne bien avec un axe et un tuyau. Mais maintenant j'essaie d'appliquer ça à plusieurs rails en même temps. Je crois avoir compris qu'il faut créer des « path » dans l'imput manager, et faire correspondre le « path » de l'axe et celui du Tuyau.
Dans mon exemple j’ai mis 3 courbes et 21 sections. Au moment où j'utilise les boîtes pour créer les portions des axes, il crée 63 « sous-path » de 1 courbe alors qu'il faudrait qu'il crée 3 "paths" de 21 courbes, enfin si j'ai bien compris.
Car une fois qu’il a créé les points à l’intérieur des « Pipe », il doit les projeter sur les plans correspondant. Et c’est là que le problème se voit. Il ne fait pas correspondre les points à projeter et les plans.
Je vous envoie la version à une courbe et un tuyau (c’est la v5 avec un fichier rhino ou la courbe d'axe est "bakée" pour pouvoir faire un zoom sur la zone plus rapidement) et je vous envoie également, celle avec 3 courbes et 3 tuyaux. Sachant qu’il faudra également attribuer un rayon pour un des tuyaux et un autre rayon pour les deux autres.
Tout ça est bien compliqué, j’espère que je ne vous embête pas trop.
Merci d’avance.…
my post to Lyndon whose understandably engaged.I'm gradually finding own answers, but If your not likewise preoccupied perhaps you've moments for a couple questions if familiar with process,.4) how to alter Lyndon's killer def. so it interpolates between Excel surface coordinates with different xyz points amounts and therefore "cell" amounts?,..i assume both culling and data matching are required, but when time please mention any known requirements\procedures?Lastly,5) as seen in 3 screenshots, when using Untrim, sDivide then Patch Surface(as target)&Trimmed surface(as Source) within Copy Trim, the results are Rotated 90 degrees counter-clockwise around Z. Might you know how to correct this?If i knew Rhino\GH so! powerful and fun, would've used them years ago.Thanks D,J…
d placing the fins see def attached. The "only" thing MIA is: (a) elaborated ways to design the profile, (b) a policy for creating "parts" (for fabrication) out of these rather big mono block fins, (c) an optional policy for "twisting" the planes used for orienting the profiles and ... er ... (d) the big thing: the "adaptive" surface that yields the sweep1 rail curves (see attached).
3. With regard doing an "adaptive" (so to speak) surface that "engulfs" a given building according some rules (and taking into account ways to "split" the big fins into "parts" + the required supporting system) ... this is certainly doable but if I'm going to give you some hints it would be solely via code: i.e. (a) creating a "gross" engulfing surface (or many), (b) modifying the control points with a variety of ways: proximity/altitude or other, (c) "testing" the "parts" for validity etc etc.
PS: Load Rhino file first.…
rks (explanations about the freaky half-lines top tree later on).
The bad news are ... well you know them already don't you? he ,he.
The ugly news are that you'll need a LOT of other stuff (most notably clash detection) in order to design a real-life truss. Activate all the 3 available boolean toggles and see what I mean. Clash detection is performed obviously via trigonometry and NOT via Brep to Brep soild "ops".
BTW: Given the opportunity, in general and in order to avoid using excess material I would strongly recommend to work on triangulated meshes (and/or line graphs). The real-life benefits in cost are pretty colossal. Of course by making negative the "d" you can control the triangulation "orientation" (usually the skin is applied there).
best, Lord of Darkness
…