se enseñan los principios de modelado básico y orgánico en Rhinoceros. En Grasshopper se estudian los principios de Parametrización, panelización y análisis en Grasshopper, así como el proceso de manufactura digital para maquinaria de corte Láser y CNC.
UN solo pago anticipado $5,000.00
Pagos diferidos $5,500.00*
*reserva tu lugar con el 50%
De lunes a viernes de 10 am a 18 pm
Del 23 al 27 de julio de 2012
DURACION: 40 HORAS
SESIONES: 5 DE 8 HORAS
o info@dimensiontallerdigital.com
informes al 55 (50 16 0634) con Mayri Gallegos (o al cel. 55 28 85 24 73)
Incluye material para corte digital.…
need more code) AND in closed ones (see warnings).
2. The real stuff that I have in practice use solely C# code (even for Kangaroo2) and I have a strong feeling that this is not what you want (if you don't speak the language). It does that because GH is just a part (~10%) of the whole AEC arsenal (that is managed via C#) ... so everything must "fit" within the "general" production pipeline (code from some app "goes" to another with the fewer possible changes blah, blah).
So ... this attached could serve as an indicative guideline about the relaxation that Daniel does with his wonder thingy (Kangaroo, that is).
…
rella - Revit/AECOSim etc etc) then scripting is the only way to do business. In fact Dynamo/Generative Components would be your main parametric app ... but GH can offer a thing or two as well.
Other than that here's a very brief explanation upon the "steps":
1. Using connectivity trees (faces to edges, edges to faces, faces to faces) ...
2. ... Find the "internal" edges (meaning edges that are connected to more than ONE face) and store them in a tree. Doing this find the smallest edge as well (for defining the "module" of the pts divisions minus the start/end offset). Used an object type tree since I store the indices of the adjacent faces as well (an object type is a "general" container that can hold cats, dogs, numbers, bananas etc etc ... with the cost of un-boxing when an item is to be used [Note: un-boxing costs time but in this very simple case we can afford the "luxury"]).
NOTE: if you observe the paths on that tree you'll notice that they correspond 1:1 to the indices of the related edges in the EList List (of type Curve).
3. Loop withing the "interior" edges and define the coplanar vectors per edge related with the 2 adjacent faces. These vectors are the Cross Product (Google that) between the edge direction and the normal per face (at u/v: 0,0). Divide the edge (taking into account the start offset AND the ratio of the edge length/ minEdge [as derived from phase 2 as above]). Using these points create a "zing-zag" polyline and store it in the same path as the OEM edge.
NOTE: The polyline is not planar since each teeth is laying to the corresponding adjacent face plane (if the Brep Faces are not planar more "smart" stuff is required).
From this point (not included in V1):
4. Using Face to Edge connectivity data: IF a path exists (in the polyline tree as in 3 above) with the given index sample this polyline as Curve ... if not get the OEM Curve (case: "boundary"/perimeter Brep Faces). Join the Curves (take provision to report failures) and project them to the corresponding Brep Face plane (case: planar face) or ... to some suitable "mean" plane. Define a planar Brep out of the newly created closed planar Curve and extrude it (actually the Brep Face of it) both sides at once for doing a "solid". If Brep Faces are not planar ... well things are a bit more complicated (not nuclear science ... just another approach is required).
In fact ... is a bit more challenging than that since there's assembly tolerance AND clash issues around ... but this is the "general" idea anyway. …
hy? because instead of doing N*2 "cones", N balls and N rodes ... you should use instance definitions (blocks in plain English): ONE cone, ONE ball ... and unfortunately N rods (Rhino is not a feature driven CAD app, sorry). Complexity (and file size) increases "exponentially" if you want to mimic a real MERO system.
Recently a friend of mine send me (for inspection) a "big" canopy type of W MERO truss with 2300 nodes that was 500Mb (baked). After the "magic" treatment it become 1.2Mb (when baked).
Notify if you need such a C# based solution: (a) for solving any truss on any collection of surface Lists AND (b) putting "real" stuff (exact MERO members) on that (but is a "bit" complex).…
ime runs out, of unexplored planets. These masters of gravity risk their lives for the adrenaline, dodging gigantic rocks that could hit their ships crashing into planets and no hope that they can be rescued.
Requires Kangaroo and Human (and in full with Firefly).
Goal of the game
You have four minutes to get six stars and reach the goal. Or die trying.
If a satellite hits you, you will leave fired.
The game has three types of control
1 Using the keyboard (requires Firefly). 2 With an external device such as a smartphone or tablet (requires Firefly and TouchOSC app). 3 Using the mouse, from the grasshopper interface.
Download files
Gh, 3dm, touchosc and textures.
Video
http://www.grasshopper3d.com/video/space-riders…
wich is nice actually :-) But I had 2 problems that make every thing just impossible to use : DIRECTION OF STEPS :
The motor can just reach one direction (for exemple clockwise) and when comes time to switch... not possible.
Details : When I put a value in HD.SM in V input, I put for exemple 100 with a slider so i have 100 steps and it works. Then I write 200, still working. and when I put a value that is less than the last higher value, for exemple 180 in my case the motor go endless to an higher amount, i mean 201,202,203...1000 etc... Dont undestand why :-/ SPEED : The speed is really really slow.
Details : The Firefly stepmotor component use the same library as heteroduino wich is Accelstepper.h but still going way faster. I tried lot of values in the S input (speed) but is not changing the speed that much, and sometimes its even changing the steps.
If there is another place where I have to post this, let me know also and I'll do it :-)
See you soon and hope some people are interested in the same problem ^^thanks :-)…
CondoCreator2.apk). Through this process the user lays out and programs his/her unit, and selects priorities that are important to them. Once they are done they submit their unit. This uploads the unit to an online database (Fusion Tables) which is connected to grasshopper through GeoCloud (A grasshopper component library I will soon release: See Image Below). Grasshopper then pulls the newly submitted unit from the database and places it on the tower. Once the majority of units are received, the units are optimized using the priorities specified in the application by the user and other constraints. Since each unit is limited on either side, each unit maintains its view outward no matter what. Views to either side are controlled through a bidding process. As users specify there preference for views outward, a bid amount is also submitted. Through the optimization process, the first goal is to meet every units preferences. But if this isn't possible then the optimization process prioritizes the unit with the highest bid for that particular view. No matter what though the unit still maintains its view outward, providing the unit with at least 36 linear feet of view outward. Therefore light shouldn't be a problem on any of the units. The process is much more involved, but hope this sheds some light on the idea Sebastian. Let me know if you have other questions.
Zach
…