rà le strategie e le principali tecniche di FORM FINDING utilizzando il motore fisico KANGAROO integrato a plugin di analisi strutturale (MILLIPEDE e KARAMBA). Le tecniche saranno applicate a diversa scala: dall’architettura (modellazione di superfici e coperture a semplice compressione) al design del prodotto, dove la simulazione digitale sarà integrata a tecniche di refinement (WEAVERBIRD). Il workshop e rivolto a studenti e professionisti con conoscenze base di modellazione algoritmica con Grasshopper.
Tariffa EarlyBird entro il 28 marzo 2015
Main tutor: Arturo Tedeschi, Authorized Rhino Trainer, autore del primo manuale su Grasshopper “Architettura Parametrica”, di AAD_Algorithms Aided Design e co-director della AA Rome Visiting School (AA School London).
>scarica il pdf con tutte le informazioni: AAD GRASSHOPPER WORKSHOP SERIES…
visions). from what i can see from the image, this is generally a box form, with definable surfaces. I would start by creating an array of parallel lines along the length of the form.. maybe about 8 with an equal offset. what you can do with this is duplicate the lines then move this new set above the old set to give the form a general depth.
grab all of the lines and run a "rebuild" command, what you are doing with this is adding more points to the lines... lines are defined by two points you probably want to add about 6 to each line, this will allow you to have more control over what the line is doing, don’t add to many though because then the line becomes uncontrollable.
Now with the original set (the lower one) you can use the "points on" command found under the "Main 2" palette to access the points that define the geometry of the curve. manipulate these points for each curve into the form of the shape that you want... get used to this "points on" tool its extremely useful.
lastly grab all the lines in the lower set of line and run the "loft" command what this will do is create surface from the selected lines. then do the same for the top set.
just remember that in nurbs modeling al la this... that points define lines and lines define surfaces... and i guess you can also say that surfaces define polysurfaces.
good luck…
same simulation with two different settings, with _numOfCUPs_ set to 1 and again with it set to 10. I'm running it on a 6 core/12 thread CPU so I should have no problem handling 10 threads.
I've attached an Excel file with my results for how long it took with a single thread vs. how long each of threads took on the 10 thread run. What it amounts to is that with a single thread it took 51 minutes, and with the 10 thread option it took 47 minutes for it all to finish. With the latter the first 9 threads finished between 28-34 minutes which is a significant time savings over the single thread run, but the last thread still took almost as long and gave us only about an 8% time savings.
This is only one simple comparison and only one simulation type, but I've seen this same result happen over and over again over the past year or so with several simulations (annual, irradiance, illuminance,...). I also don't think it's necessarily a Honeybee problem, because even running the simulations myself by creating the octree mesh and running radiance and daysim from the command line I had the same issue where splitting a model up and running parallel simulations that were then recombined took just about as long as running it all in one thread. Add into this the time necessary to combine the different files at the end and your multithreading time savings become even less.
So is it me, my machine, radiance, bad karma?…
ou can ask your own specific questions to one of our Authors. Maybe you are working on something, and have gotten stuck, or have a general question about design technology- we'll open up your file, and you can ask these questions at Office Hours. Since its a live, interactive event, you will listen in to others' questions- which is a great way to learn too!
Our August 14th Office Hours is with David Lefevre, an architect from Gensler who is pretty amazing with Rhino & Grasshopper. He's also taught a online course at Black Spectacles entitled: Surface Modeling in Grasshopper.
Office Hours is on August 14th, and runs from 7:30pm CST- to 8:30pm CST. We'll take questions in the order in which people register. Once you register, you will receive an email confirmation with details on how to join the webinar, and a dropbox folder where you can post a file that we can open up during your question time.
Learn more & Register here:
http://blackspectacles.com/blog/office-hours-with-david-lefevre…
eration!
See an example work flow for designing, simulating and analysing a Photovoltaic system below.
Download a Grasshopper and Rhino example file:
https://www.dropbox.com/s/krbszlplj5i40dz/017_HBgeneration%20Rhino%20model.3dm?dl=0
https://www.dropbox.com/s/lxneuzal3mipd2q/017_HBgeneration.gh?dl=0
See a quick introduction and tutorial videos here: https://www.youtube.com/playlist?list=PLrx2KnyhaJ5YXo5hpk8Q9q4Vy99O5IegK
1. Select a building to mount a photovoltaic generator on (seen in Rhino in green).
2. Select a surface within that building to mount a photovoltaic generator on (seen in Rhino in green).
3. Create a Honeybee context surface from that surface.
4. Place a photovoltaic generator on that Honeybee context surface by using the Honeybee generation component. Honeybee_Generator_PV and connecting the context surface to it's input _HBSurfaces. Then you can specify both the performance and the financial data of the photovoltaic generator.
5. Create a Honeybee generation system which consists of the photovoltaic generator in 4. By using the component Honeybee_generationsystem and connecting 4 to its input PVHBSurfaces_. Then you can specify the annual maintenance cost of this system.
6. Run the simulation in Energy Plus by connecting 5. to the input HBGenerators_.
7. Read the results of the simulation:
- The electricity produced by the Honeybee generation system in 5.
- The net purchased electricity of the facility (the Honeybee zone) to which the Honeybee generation system is attached to. This is the electricity consumed by the facility less the electricity generated by the Honeybee generation system.
- The financial costs of the Honeybee generation system; capital, maintenance and replacement costs.
8. Calculate the net present cost of the Honeybee generation system in 5 assuming a 25 year lifetime.
9. Visualise the net present cost.
…
orkshop will give students a functional understanding of Grasshopper and Parametric design. This will allow them to build on this understanding into more advanced projects of their own including design optimization with RhinoCAM-NEST and creating their models on a laser machine. Basic knowledge of Rhino 5 is required to be able to take this training. Details...
Location: McNeel Miami 1538 NW 89th Court Miami, FL 33172 United States
More Info: e-mail: Jackie Nasser phone: 305 513 4445
Note: The course must reach a minimum of 5 enrolled students. If the course does not meet the minimum, it will be canceled.
*If you live outside the Americas and you wish to purchase this product, you should choose the United States as country of residence. The rest of the information should be correct.
*Si usted vive fuera de las Americas y desea comprar este producto, deberá escoger como país de residencia United States. El resto de la información debe ser la correcta.
McNeel Miami's RhinoFabStudio - Miami, Florida
.
…
o sensor Shield V5.0 - 2 standard servos (plugged into pins 9 and 10 in the sensor shield) - 7.5V wall power supply - USB cable to computer
I'm running Rhino SR 8 on a 32 bit Windows Vista machine I have Version 0.9.0014 of grasshopper (the latest) and Firefly_Build_1.0067 I have flashed my Arduino board with the latest firefly firmata (updated September 10th, 2012)
I have checked that I am using the "MEGA write" box I have got the right bits going to the right pins and I have checked that they all have "servo" ticked instead of "digital" or "pwm"
My servos and board work perfectly well with the normal Arduino software, but just not any longer with firefly since my computer was switched off.
The port shows correctly as COM 4 and opens fine.
When I move the slider to control the servos, the TX light is on and the RX light flashes, but no servos move... (everything works with the sweep example in arduino though, so I have eliminated power and wiring issues)...
Any ideas what might be the problem?
I've tried re-installing, switching off and on many times, changing cables, trying a different board (also doesn't work any more with the duemilanove), trying all pins on the shield, trying one servo without the shield, trying one servo with the shield, lots of googling, lots of searching forums, unblocking the firefly installation files in explorer, lots of things... I'm all out of ideas... And very confused as it was working just a few days ago... Am I just missing something really obvious or could there be an issue with the software at my end?…
been covered since 0051 (correct me if I'm wrong):
1) Shoot for the moon first -- "Control Panel Mode" which allows for advanced interface design. See Max/MSP for example of modal function. I spent a lot of time laying out control panels so they are nice for clients and team members to look at. I spend a lot of time disabling wire display and dragging sliders and panels and graphs around into nice little clusters. Could be something as simple as a mode that disables the view of all component handles, cleans up graph objects, sliders, etc. I know the Remote Control Panel has been requested over and over again since it disappeared, but honestly it wouldn't be much use to me unless it was a full blown customizable interface. In the meantime I'll stick to my own "Canvas Control Panel" methods. (See below...)
2) More control over graph objects. Right now the bar graph for instance automatically sets the lowest and highest value displayed. Would be nice to be able to set extents manually so that you can compare apples to apples on two different lists that have different extents. Also would love to force the bar graph to show all values along x axis, not just first and last. Same goes for showing the numbers of instances for each value. Now it only shows instance numbers in oddball cases. Would like to force them to show for statistical purposes. Love percentages, but usually I also want accurate tallies. I tend to use a member index sets to generate my own lists.
3) Color input for Vectors -- there are fakey fake workarounds but none that are as versatile as simply having a color input.
4) COLOR INPUT FOR TEXT TAGS -- sorry to yell... this one really frustrates me. I often build interactive feedback systems that involve a lot of different types of data, and it is difficult to convey that input when all text is red (or green when selected).
5) Ability to justify text tags using paragraph controls -- currently default is left-justified. Would like to be able to center text horizontally and vertically, among other things.
6) Ability for text tags to handle multi-line text. Not sure the best way to implement this, but often I find myself wanting to attach 3 items of information to a particular object, and I have to string it all together in one line. Would be great if I could insert a "^M" character that stands for carriage return and have that display as multiline text (used in conjunction with above justification controls).
7) More control over Text panels. Thank you for including justification options... but sadly now it begs the question for margin and header control. Text slammed up against the left edge is pretty unsightly. Moreover, if you have labeled a text box, the drop shadow from the title bar tends to overshadow the first line of text if you have Path display turned off. Would like to add some header space to fix the problem and create a cleaner look.
8) Easier access to text font size. Buried in a Special Font... menu. I want to be able to up up down down (left right left right select start) if you know what I mean.
I guess that's it for now... just the things on the top of my head in this category. Looking forward to installing the new release, have to wait until this major project is over though.
Cheers,
Marc
…