ades del Espacio en 1981). En este, O'Neill propone la colonización del espacio para el siglo XXI mediante el uso de ingeniería espacial construida con materiales de lugares como la Luna o asteroides. Consta de dos grandes cilindros de rotación opuesta, con dimensiones de 3,2 km de radio y 32 km de largo, que están conectados en cada extremo por una varilla a través de un sistema de rodamientos. Rotan a fin de proporcionar gravedad en sus superficies interiores, que estarían acondicionadas como un medio de vegetación natural con árboles, hierba, arroyos y lagos y es el lugar donde se desarrollaría toda actividad. La circunferencia del cilindro se dividiría en seis regiones, tres “valles” habitables alternando con tres hileras de ventanas que permitirían el paso de la luz solar. Además existiría un anillo exterior para la agricultura de quince kilómetros de radio, el cual gira en una velocidad diferente a los cilindros. La zona industrial y la fabricación estaría localizada en eje del cilindro, detrás de la antena parabólica. En esta zona la gravedad es mínima, algo que se tendría en cuenta en algunos procesos de fabricación y otras actividades de la colonia.…
ades del Espacio en 1981). En este, O'Neill propone la colonización del espacio para el siglo XXI mediante el uso de ingeniería espacial construida con materiales de lugares como la Luna o asteroides. Consta de dos grandes cilindros de rotación opuesta, con dimensiones de 3,2 km de radio y 32 km de largo, que están conectados en cada extremo por una varilla a través de un sistema de rodamientos. Rotan a fin de proporcionar gravedad en sus superficies interiores, que estarían acondicionadas como un medio de vegetación natural con árboles, hierba, arroyos y lagos y es el lugar donde se desarrollaría toda actividad. La circunferencia del cilindro se dividiría en seis regiones, tres “valles” habitables alternando con tres hileras de ventanas que permitirían el paso de la luz solar. Además existiría un anillo exterior para la agricultura de quince kilómetros de radio, el cual gira en una velocidad diferente a los cilindros. La zona industrial y la fabricación estaría localizada en eje del cilindro, detrás de la antena parabólica. En esta zona la gravedad es mínima, algo que se tendría en cuenta en algunos procesos de fabricación y otras actividades de la colonia.…
t the maximum potential with the bridge BIM+PARAMETRIC DESIGN ;D
During this Intense Week, we will learn about the power of Rhino + Grasshopper + ArchiCAD with Professional and Useful examples for our Normal Working day :D
You will get Advanced Library Files + Personal Web + Knowledge and Skills to start using this incredible Methodology ;D
Also, the week is having Lectures from different Experts sharing their Computational Working Experiences ;D And Jam Sessions! opening the door to 5 interesting topics to research, learn and experiment together :D
2020 is your YEAR ;D !!!
Complete details and registration……
onents (radiation, sunlight-hours and view analysis) which let you study the effect of the orientation of your building and the analysis result. When you come to a question similar to "what is the orientation that the building receives the most/least amount of radiation?" is probably the right time to use this component.
HOW?
I'll try to explain the steps using a simple example. Here is my design geometries. The building in the center is the building to be designed and the rest of the buildings are context. I want to see the effect of orientation on the amount of the radiation on the test building surfaces from the start of Oct. to the end of Feb. for Chicago.
First I need to set up the normal radiation analysis and run it for the building as it is right now. [I'm not going to explain how you can set up this since you can find it in the sample file (Download the sample file from here)]
Now I need to set up the parameters for orientation study using orientationStudyPar component. You can find it under the Extra tab:
At minimum I need to input the divisionAngle, and the totalAngle and set runTheStudy to True. In this case I put 45 for divisionAngle and 180 for the totalAngle which means I want the study to be run for angles 0, 45, 90, 135 and 180.
[Note1: The divisionAngle should be divisible by totalAngle.]
[Note 2: If you don't provide any point for the basePoint, the component will use the center of the geometry as the center of the rotation.]
[Note 3: You can also rotate the context with the geometry! Normally you don't have the chance to change the context to make your design work but if you got lucky the rotateContext input is for you! Set it to True. The default is set to False.]
You're all set for the orientation study, just connect the orientationStudyPar output to OrientationStudyP input in the component and wait for the result!
The component will run the study for all the orientations and preview the latest geometry. To see the result just grab a quick graph and connect it to totalRadiation. As you can see in the graph 135 is the orientation that I receive the maximum radiation. Dang!
If you want to see all the result geometries set bakeIt to True, and the result will be baked under LadyBug> RadaitionStudy>[projectname]> . The layer name starts with a number which is the totalRadiation.
Mostapha…
her people) a tremendous amount of time creating them by hand. Dog Treat was far from perfect, however it was good enough to use almost daily.
Three years is a long time. Since 2016 my Gh knowledge has expanded and I’ve seen how dodgy some of the scripting is. With this in mind I started work on a new build. Many things have been tweaked and some things have been rebuilt from the ground up.
Everything has been designed to be leaner and be a general solution to the problem of creating dog bone corners on geometry for quick, efficient and safe CNC fabrication.
Some of these things are:
Adding prompts about user geometry to make them aware about open curves, varying curve heights and if their geometry had been altered (mostly removing unnecessary points on curves).
Smooth Transfers. If you’re in a rush and need to speed through cutting, smooth transfers mean that a lead in geometry is now created alongside the actual dog bone arc. This means the router bit doesn’t have to come to a minute stop at every corner. This is turned on by default.
Acute Angle Condition If the angle between the two curves adjacent to a dog bone point is acute, previously the dog bone corner was useless. This was because the distance between the end points of the dog bone arc were less than the diameter of the router bit. There are many ways this condition could be addressed. I chose to circumscribe a larger arc based on the original angle between the adjacent curves. While it removes more material from the corner, it minimises tool wear and any potential for material to burn.
Single Curve A single curve can now be input into Dog Treat. It will be output with both internal and external treatments.
I’ll continue to update Dog Treat as the need arises, it’s become somewhat of a hobby now. Maybe one day it will become part of a Plug-in… once I learn to code it though!
Happy Treating!
Hi Everyone,
Here's a tool I've been working on for the past 4 months or so in my free time. It's a dog bone corner generator, however it's a little different to some of the existing ones. It's designed to be used for large amounts of geometry and as such, it avoids using any curve boolean operations that are computationally taxing. You don't have to split your curves up into internal and external lots either, it works it all out so you can be lazy. I've also incorporated Lunch Box's Object Bake Component for a one click operation that bakes geometry back out to Internal and External profile layers.
Let me know how it goes, will update where necessary.
Best,
Darcy
Change Log
06/11/19 - Version 2.0 SECOND DINNER - Rebuild
29/09/17 - Version 1.3 - Now with smooth corners option, True for smooth default/False for original
18/05/17 - Version 1.2 - Now includes variable angle domain input (defaults at 90°) for angled corners
13/11/16 - slight change to enable acceptance of very large interior curves
…
Added by Darcy Zelenko at 8:44pm on November 9, 2016
propose new models of infrastructural self-organisation, urban automation and mobility systems.
Adaptive networks based on multi-agent principles and crowd simulation are used to solve complex architectural and programmatic conditions in a three-dimensional urban environment. We will explore towards an intelligent architecture, defined by flows of information and its materialization in speculative infrastructure and architectural scenarios. A responsive infrastructure that is deployable in multiple regions.
Our design process will be driven by a direct feedback loop of different simulation software, each informing another as input for emerging connectivity networks and interrelated urban systems, driven by site specific urban and topographical parameters.
The workshop aims to develop ideas of adaptive and evolutionary space-making beyond deterministic and finite solutions. In a series of algorithmic design exercises, different network principles and speeds, users behavior and needs are tested and evaluated, both by observation and parameter based criteria.
Students will propose an architectural intervention in dense urban scenarios, that is both tested for optimised efficiency and stimulating in its embodiment.
METHODOLOGY
Students will be introduced to expertise in generative, algorithmic and parametric design approaches. Tutors and students will engage experimentally with computational simulation, analysis, design and production to query the design repercussions of these information-based technological methods for urbanism. During the workshop, students will develop design proposals responding to studio briefs using Processing with Rhino and Grasshopper. The final results of the workshop will be visualized using V-Ray for Rhino and the Adobe Suite.
Basic knowledge of Rhino and Adobe Suite is required. Advanced knowledge of Grasshopper and Processing is not mandatory.
…
milar thing as Amaraa's (http://www.grasshopper3d.com/group/ladybug/forum/topics/finding-an-...), to explore an optimal pv array with the most AC energy production.
Have in mind, that Amaraa's topic dealt with PV system integrated into a facade. And as far as I understood you would like to put your PV modules on a roof. So it may be that some of my replies from that topic, may not apply to your roof PV system.
Also, Amaraa's topic did not deal with optimal PV system size (DC rating in kW). You would like to calculate that one as well?
I plan to set three parameters (orientation, tilt angle and distance of pv), and use Galapagos to make a best horizontal pv grid of most AC energy. So the most important is to avoid the dark core-shadows from shelf shading. If so, I wonder whether the gh document you uploaded in the discussion named "Finding an optimal size of PV panel in given array" will be helpful to me. And should I use the Sun Path component to calculate the self shading?
Ok, so you decided to go with the upper 2)a) solution?
Did I understand that correctly?Btw. sorry if you receive three emails for this reply. For some reason I had to delete it, and post it again. Grasshopper forum is working strange in the last couple of weeks.…
work. As payload it uses protocol buffers which is optimised for transport and storage, and is Google's lingua franca for data. It would be great to use it for extensibility in grasshopper.
As gRPC supports both C# and Python I didn't think it would take many lines of code, but I have so far failed to put it together. Could anyone please describe to me best practice is in such case, and/or want to collaborate on the project? I can picture an open repo on gitHub or similar.
My main qustions are:
Should I use C# or Python?
Can I use Visual Studio 2017? All the VS 2015 installers have failed on my computer.
Do I have to use Visual Studio, or can I get away with the built-in editor? What are the main limitations using one over the other?
Can I build Rhino5 GH components in VS2017? I have built a Rhino 6 GH component from the McNeel template, but it did not work when opened in Rhino 5 GH (currently only R6 templates are available for VS2017).
Can Rhino 5's old ironPython deal with the newer gRPC package?
What's the best way to do rapid iterations and version controll building GH comps?
TL;DR: I want to build a very simple gRPC.io client GH component, and appreciate all help I can get.
Many thanks, Martin…
gust 5th, we will be covering CLIMATE DATA + DAYLIGHT WORKFLOWS WITH LADYBUG + HONEYBEE. The morning will cover weather data visualizations as participants learn the basic principles for generating customized climate graphics with Ladybug. The afternoon will explain the workflows for daylight modeling with Honeybee as participants learn to automate and run more advanced studies. This session is perfect for people who have some background in climate analysis are are looking to harness the capabilities of visual scripting in their workflows.
On Sunday August 6th, we will be covering ENERGY + ENVELOPE DESIGN WITH HONEYBEE OPENSTUDIO + THERM. The session will focus on building energy modeling and envelope U-value modeling with the Honeybee plugin for Grasshopper. In the morning, participants will setup a parametric energy model and use it to perform a sensitivity analysis to inform intermediate stages of design. In the afternoon, instructors will explain the basics of modeling construction details with Honeybee THERM.
The workshops are in conjunction the 2017 International Building Simulation Conference and will be held at the Pacific Energy Center. You do not need to be registered for the conference in order to attend the Ladybug workshops.
Registration for the workshops can be done here:
http://www.bs2017.org/register/
If you are not interested in attending the conference, just select the "Workshop(s) Only" option in the registration form.
Cheers!
-Chris…