" (idiomatic) and easy way of doing things.So here come some basic questions:
Is there a way to create custom components by grouping an existing sub-network together? I'm looking for a way to re-use parts of a program (something similar to subroutines), and to make the network look less cluttered. I found that it is possible to group components (ctrl-g), but this still displays them as separate blocks (too much clutter), and provides no way to re-use a sub-network in such a way that if it is modified in one place, all it's instances (all the places where it is re-used) also get modified.
Is there a component that does nothing, just passes a signal through? Suppose I need to connect block A to blocks B1, B2, B3 (all three get the same input). Then I change my mind, and I decide to connect block C to these three, not A. In this case it will be necessary to change three connections, not just one. I'm looking for an easy way to do this by a single rewiring, not three. (This came up in a practical situation).
Finally, a related question: is there a component that acts as a switch, so I can choose which signal it passes through out of a possible set of choices? For example, suppose that a set of objects can be coloured based on a number of different properties (size, positions, rotation, etc.) I'm looking for a way to switch between these very easily, without the need to do much rewiring.
Thank you in advance for any replies / useful comments, even general ones on how to easily structure a large Grasshopper program/network.…
see in my bottom post image there is only one isocurve showing in U and V.
In Grasshopper there's no surface rebuild? Well, the same old Grasshopper Patch command will let you specify spans I guess, to make a surface from a planar curve, but it won't work for things with holes since they will just fill in!
You can recreate a surface painfully by untrimming, adding many UV points, rebuilding from those points, then retrimming with the original surface info, but the retrimming simply fails.
If you make a planar surface from a curve in Rhino, you end up with utterly no point editability:
No wonder my CreatePatch tests were a failure. The starting surface could not be distorted except in the extreme case of moving four corner points!
I have no idea how to successfully rebuild a surface akin to the Rhino rebuild command. It's great to be able to prototype in Grasshopper, but with Python I can rebuild easily ( http://4.rhino3d.com/5/rhinocommon/?topic=html/M_Rhino_Geometry_Surface_Rebuild.htm ;), so I guess I should start a collection, like peter, of little script components for prototyping with.…
Added by Nik Willmore at 6:18am on February 26, 2016
limate based sky, and then use that sky to do a radiation analysis with ambient calculations turned off (i.e. a -ab 0 run).
Daysim approximates the position of the sun, which can be in as many as unique 3000 locations on an annual basis, to only 65 odd locations in the sky. GencumulativeSky, which is used for the cumulative studies in the Hydra examples, takes the annual radiation data and creates a Tregenza Sky pattern .... While a Tregenza pattern might be fine for an annual simulation, using it for hourly simulations isn't going to be very accurate.
There are actually some thermal comfort examples on the Hydra website that you might find useful.
…
lies on gradient-free optimization algorithms, delivering fast and deterministic results. At every run, goat will yield the same optimal result.
goat is a drop-in replacement for galapagos. It is based on David Rutten's galapagos GUI and interfaces NLopt, a collection of mathematical optimization libraries.
Tutorials
For getting started with optimization in parametric modelling environments in general and with goat in special, check out our presentation slides on Geometry and Optimization with several comprehensive examples.
Once you are familiar with the basics of optimization, head over to our comprehensive documentation on goat's different configuration options.…
bursts of calcium which interacts with a photoprotein to create flashes of light.
In the Pacific Canada Pavilion gallery at the Vancouver Aquarium, the public can excite origami jellies into creating beautiful patterns of colour and light using a touch screen controller.
When left alone, free from human intervention, the origami jellies instinctively react to each other. Random, generative displays of drifting coloured glow are triggered, not unlike jellies in their natural environment.
Jelly Swarm overhangs the gallery space. The soft, coloured light emitted by the jellies reflects on the aluminum surface. Viewed from below, the visual effect evokes looking up to the ocean's surface from undersea.
The installation features 94 origami jellies, folded in Tyvek. Each jelly contains its own RGB LED module. The 472ft² hanging surface was custom designed in 3D and fabricated from 6061T6 aluminum. Water jet cut and anodized on both sides, it comprises 154 generated triangles and 430 connector pieces.
Programed as self-contained objects capable of interacting with their closest neighbours, the Jelly LED modules are interrupted only by external intervention - the public engaging with the small display interface. Data is sent from an AIR app to each LED module via mbed wirelessly.
Credits -
Concept: Alex Beim & Joseph Wu
Design: Reynaldo Tortoledo & Alex Beim
Jelly Design & Fabrication: Joseph Wu
Programming: Reynaldo Tortoledo & Pablo Gindel
Electronics: Pablo Gindel, Dong Yang & Mike Manning
Surface Fabrication: Burak Ataman
Engineering Consultant: Leigh Christie
Design Assist: Pam Troyer & Kenji Rodriguez
Plinth Fabrication: Ken Sullivan
Installation: TI team & Don Knudson
Electrical: Evan Maxwell
Production: Andy Meakin
Video: Neil Fisher & Kenji Rodriguez
@tangibleint…
n en el diseño y fabricación digital de formas complejas y euclidianas.
Tomando como plataforma Grasshopper con RHINO, se explora y optimiza el diseño y fabricación de topologías complejas bajo los entornos de "Grasshopper", "RhinoNest" y "RhinoCAM" así como la parte de renderizado tipo high-end con Brazil.
D-O-F De 8:00 AM a 12:00 PM y de 1:00 PM a 5:00 PM
Contenidos:
1. Modelado Avanzado y sus Tecnicas. Aplanado y Desarrollo de Superficies.Anidado y distribución Nesting.
2. Introducción al Diseño Paramétrico.Definiciones Avanzadas de Grasshopper,posibilidades y limitaciones. Ajustes de escala para impresión y corte.
3. Introducción a la Manufactura en CNC - RhinoCAM 2.0.
4. Guía Paso a Paso para la realización de un Renderizado usando Brazil 2.0. Presentación DIGITAL de proyectos.
Docentes:
Andrés González - CEO McNeel Miami
Ovidio Cardona - Especialista en RhinoCAM y Zebra
Juan David Moreno - Especialista en Rhino y Brazil
Inversión:
$650 000 (Incluye licencia Educativa y Certificación de McNeel)
$550 000 ( Incluye Certificación de McNeel)
Informes:
Bits LTDA Tel: 412 30 15
Laboratorio de Imagen Facultad de Arquitectura Tel: 430 94 32…
h Shading--DC to AC derate Factor--Photovoltaics Module, can calculate the ACenergy of different pv arrays by Galapagos. The process can evaluate the self shading from the input analysisGeometry and surrounding shading from the input context.
2. PV SWH Systemsize, can also do that, but there would be no second type of self shading for the chosen minimalSpacingPeriod_ criteria.
3. TOF outputs optimal angle and azimuth.
So my question is, if I choose to make a curved roof to form a best pv array with best ACenergy, whether should I only choose the first above, the second PV SWH Systemsize can only deal with the angled or flat surface, not the curved? What's the relationship between TOF and PV SWH Systemsize?
Also, I'll do my best to make a parametric model as soon as possible and upload it to you, so we can make the discussion more detailed.
Best regards.…
face, the larger the number of modules and system size, there for the higher annual energy generation.baseSurface_ - this input exists only for "PV SWH system size" component. It's purpose is to represent a mounting plane on which the PV modules will be put onto. The dark blue colored roof in the photo below is that mounting surface in this case:
So the size of area of the baseSurface_ is not important but its plane.
2) It is important. It basically sets the initial losses of the system.
If that is the soiling value you have, then yes, you need to add it to the DC to AC derate factor component, and then plug its output to "DCtoACderateFactor_" input. I did that in the attached definition below.
3) The north vector/numeric value is not propagated due to possible independent usage of components.I plugged the 0 value to all three component's which have "north_" input. You can change it to what ever value you need.
Please let me know if I didn't answer completely to your questions, or if you have more of them.…