mpression bending test apparatus has been developed to measure the flexural properties of plywood-fiberglass composite slender beams. The number of fiberglass layers and the orientation of the fibres along the strip have been examined, in order to calibrate the bending behaviour of each strip segment, aiming to encode complex 3d form into flat 2d strips, which bent and anchored at both ends, form non-symmetrical arch shapes of variable curvature. The results show that the proposed method enables a unified materially informed form finding process, where the geometry is approximated according to local material specifications at macro, meso and micro scale. Informing physics based simulations with material properties data derived from the proposed mechanical testing scheme, allowed for fairly accurate material behaviour simulations, with deviations attributed, besides the non-standardized apparatus measurements, mainly to the manual fiberglass layup and the number of mechanical tests conducted for the calculation of the mechanical properties of each fiberglass layout variation.
more: https://www.researchgate.net/publication/329016703_Vision-based_compression_bending_test_apparatus_Stiffness_grading_of_plywood_fiberglass_composite_strips
Test report sample : https://vimeo.com/242117397
using:
Grasshopper for Rhino3D (David Rutten)
grasshopper3d.com/
Kangaroo 2 grasshopper plugin (Daniel Piker)
https://www.food4rhino.com/app/kangaroo-physics
K2Engineering grasshopper plugin (Cecilie Brandt)
https://github.com/CecilieBrandt/K2Engineering
Human grasshopper plugin (Andrew Heumann)
andrewheumann.com/#computation
Tracker Video analysis and modeling tool (Douglas Brown)
physlets.org/tracker/
compadre.org/osp/bulletinboard/home.cfm
Tracks:
Poptraume -Traume-fon by rubber-records(gr)
https://rubber-recordsgr.bandcamp.com/track/poptraume-traume-fon
Poptraume - 4m2m bios records#002…
onstrates the following:
1. The definition's functionality employing HumanUI for the custom user interface.
2. The evaluation of the definition's ability to handle different point cloud data sets.
3. Video reports with the definition's results, animating subsequent per deviation step frames.
This definition calculates best fitting plane deviations. The number of manual set parameters has been minimized to two the facade per World UCS axis selection and the search width. This defines a box, which is used to crop protruding architectural details, which do not contribute to the analysis, but also ensures that large deformations are included in the calculation.
For the automation of the vertical and horizontal sections creation, the analyzed cloud is clustered, according to user defined number of 2d grid cells. The deviations corresponding to each cell are averaged in mean and median mode.
The process is displayed mostly in real time, with some speed up in some parts. Too long calculations have been omitted during video edit. The setup is responsive and benchmarks show that changing between dense point cloud data sets and facades is pretty quick (6.5-7.5M points, 25-45 deviation steps, 44x22 clusters), updates are calculated in acceptable timings (3-6 minutes).
I would like to thank Heumann A. and Zwierzycki M. who provided direct support with HumanUI and Volvox. Also Grasshopper3d forum users Maher S. and Segeren P., who contributed with Rhino viewport manipulation scripts.
More on Volvox:
http://papers.cumincad.org/cgi-bin/works/Show?_id=ecaade2016_171&sort=DEFAULT&search=ecaade%20volvox&hits=2629
http://www.food4rhino.com/app/volvox
http://duraark.eu/
HumanUI:
http://www.food4rhino.com/app/human-ui?page=1&ufh=&etx=…
giornata inaugurale sarà dedicata alla free-lecture introduttiva finalizzata alla realizzazione di un modello d'architettura complesso attraverso l'utilizzo di comandi e tecniche avanzate di rappresentazione con Grasshopper (plug-in parametrica di Rhinoceros) e 3dsMax. Sarà illustrato inoltre il potenziale di V-ray per 3dsMax realizzando un rendering concettuale. Durante il mini-corso dell' openDAY verranno mostrate le caratteristiche e le potenzialità degli strumenti per far luce sui nuovi valori assunti dalla modellazione 3D. La modellazione 3D sta interessando un pubblico sempre più vasto inserendosi in una nuova fase di ampia disponibilità per conoscenze, software, hardware di prototipazione e modelli. Pur mantenendo tutti i suoi valori già noti la questione si è talmente ampliata fino ad interessare norme giuridiche (diritti sui modelli ,concorrenza con offerte di servizi apparentemente simili, informazioni deformate e onfusione nei media) Makers University[http://www.makersuniversity.com], in collaborazione con parametricart, vi propone un punto di vista ampio e sintetico su queste tematiche.
Al termine della free-lecture, sarà illustrata l'offerta formativa [CLICCA QUI] di parametricart riferita ai corsi che si terranno nei mesi di Gennaio e Febbraio 2013 inseriti all'interno della più ampia programmazione della Makers University. SONO PREVISTE TARIFFE PROMOZIONALI PER COLORO CHE SI ISCRIVERANNO AI CORSI durante l'OpenDAY.
La lezione e la presentazione si terranno nel nuovo spazio co-working il PEDONE.
PROGRAMMAZIONE
- I temi della Makers University [Leo Sorge];
- Modellazione della parametricTower (concept di architettura complessa) utilizzando Grasshopper, applicativo per la modellazione parametrica [VIDEO] [Michele Calvano];
- Modellazione di una copertura reticolare 3D a completamento della parametricTower con 3dsMax utilizzando tecniche di modellazione mesh complesse [Wissam Wahbeh];
- Rendering con V-ray per 3dsMax illustrando la nuova interfaccia nodale [Wissam Wahbeh].
- Question Time per chiarimenti sugli argomenti illustrati.
COME
L'openDAY sarà aperto a tutti gli interessati,completamente gratuito e sarà replicato in tre sessioni di uguali contenuti organizzate nei seguenti orari:
Sessione [1] 11,30 - 13,30
Sessione [2] 15,30 - 17,30
Sessione [3] 17,30 - 19,30
Per necessità di organizzazione è importante la prenotazione all'evento utilizzando il form in fondo alla pagina specificando nella stringa apposita, il nome dell'evento e la sessione (es. open day sessione 1) oltre agli altri dati richiesti.…
e chosen to dive into Grasshopper. I’m about 6 months in. If some of my comments are completely off, please take that to mean that a feature is too inaccessible to a newish user rather that it’s just missing, as I may have stated.
One of my primary pain points is this. Things that can be done in other programs are invariably easier in other programs. This is a big enough issue that I doubt there’s an easy solution that an armchair qb like myself can offer up.
The interface:
I’ve used a lot of 3D programs. I’ve never encountered one as difficult as grasshopper. What in other programs is a dialog box, is 8 or 10 components strung together in grasshopper. The wisdom for this I often hear among the grasshopper community is that this allows for parametric design. Yet PTC (Parametric Technology Corp.) has been doing parametric design software since 1985 and has a far cleaner and more intuitive interface. So does SolidWorks, Inventor, CATIA, NX, and a bunch of others.
In the early 2000's, when parametric design software was all the rage, McNeel stated quite strongly the Rhino would remain a direct modeler and would not become a parametric modeler. Trends come. Trends go. And the industry has been swinging back to direct modeling. So McNeel’s decision was probably ok. But I have to wonder if part of McNeel’s reluctance to incorporate some of the tried and proven ideas of other parametric packages doesn't have roots in their earlier declaration to not incorporate parametrics.
A Visual Programming Language:
I read a lot about the awesomeness and flexibility of Grasshopper being a visual programming language. Let’s be clear, this is DOS era speak. I believe GH should continue to have the ability to be extended and massaged with code, as most design programs do. But as long as this is front and center, GH will remain out of reach to the average designer.
Context sensitivity:
There is no reason a program in 2014 should allow me to make decisions that will not work. For example, if a component input is in all cases incompatible with another component's output, I shouldn't be able to connect them.
Sliders:
I hate sliders. I understand them, but I hate ‘em. I think they should be optional. Ya, I know I can r-click on the N of a component and set the integer. It’s a pain, and it gives no feedback. The “N” should turn into the number if set. AAAnd, sliders should be context sensitive. I like that the name of a slider changes when I plug it into something. But if I plug it into something that'll only accept a 1, a 2, or a 3, that slider should self set accordingly. I shouldn't be able to plug in a “50” and have everything after turn red.
Components:
Give components a little “+” or a drawer on the bottom or something that by clicking, opens the component into something akin to a dialog box. This should give access to all of the variables in the component. I shouldn't have to r-click on each thing on a component to do all of the settings.
And this item I’m guessing on. I’m not yet good enough at GH to know if this may have adverse effects. Reverse, Flatten, Graft, etc.; could these be context sensitive? Could some of these items disappear if they are contextually inappropriate or gray out if they're unlikely?
Tighter integration with Rhino:
I'm not entirely certain what this would look like. Currently my work flow entails baking, making a few Rhino edits, and reinserting into GH. I question the whole baking thing, btw. Why isn't it just live geometry? That’s how other parametric apps work. Maybe add more Rhino functionality to GH. GH has no 3D offset. I have to bake, offsetserf, and reinsert the geometry. I’m currently looking at the “Geometry Cache” and “Geometry Pipeline” components to see if they help. But I haven't been able to figure it out. Which leads me to:
Update all of the documentation:
I'm guessing this is an in process thing and you're working toward rolling GH from 0.9.00075 to 1.0. GH was being updated nearly weekly earlier this year. Then it suddenly stopped. If we're talking weeks before a full release, so be it. But if we're looking at something longer, a documentation update would help a lot. Geometry Cache and Geometry Pipeline’s help still read “This is the autogenerated help topic for this object. Developers: override the HtmlHelp_Source() function in the base class to provide custom help.” This does not help. And the Grasshopper Primer 2nd Ed. was written for GH 0.60007.
Grasshopper is fundamentally a 2D program:
I know you'll disagree completely, but I'm sticking to this. How else could an omission like offsetsurf happen? Pretty much every 3D program in existence has this. I’m sure I can probably figure out how to deconstruct the breps, join the curves, loft, trim, and so forth. But does writing an algorithm to do what all other 3D programs do with a dialog box seem reasonable? I'm sure if you go command by command you'll find a ton on such things.
If you look at the vast majority of things done in GH, you'll note that they're mostly either flat or a fundamentally 2D pattern on a warped surface.
I've been working on a part that is a 3D voronoi trimmed to a 3D model. I've been trying to turn the trimmed voronoi into legitimate geometry for over a month without success.
http://www.grasshopper3d.com/profiles/blogs/question-voronoi-3d-continued
I’ve researched it enough to have found many others have had the exact same problem and have not solved it. It’s really not that conceptually difficult. But GH lacks the tools.
Make screen organization easier:
I have a touch of OCD, and I like my GH layout to flow neatly. Allow input/output nodes to be re-ordered. This will allow a reduction in crossed wires. Make the wire positions a bit more editable. I sometimes use a geometry component as a wire anchor to clean things up. Being able to grab a wire and pull it out of the way would be kinda nice.
I think GH has some awesome abilities. I also think accessing those abilities could be significantly easier.
~p…
artes y Jueves 18:00 a 22:00 Sábado 10:00 a 14:00
Durante el curso el participante conocerá y entenderá los fundamentos de programación y sus aplicaciones usando Processing: una plataforma de desarrollo en lenguaje java, que surgió en MIT, creada por investigadores enfocados a procesos numéricos y/o generativos para arte y diseño. Se realizarán ejercicios programados para generar gráficas, volúmenes o situaciones kinéticas en tiempo real, basado en algoritmos o reglas complejas y en el procesamiento de datos, soluciones que permitirán comprender temas esenciales como datos primitivos y datos compuestos, algoritmos generativos, geometría 2D y 3D paramétrica, programación estructurada y programación orientada a objetos, control de flujo, variables y ámbito de variable, entre otros temas.
NOTA: Es requisito para cursar los talleres del Bloque 1 y Bloque 2 que los alumnos inscritos tegan bases sobre programación. Este taller forma parte del propedéutico para el Diplomado.…
Added by Alberto Lara at 9:37pm on February 12, 2012
ial-by-nao-box-morphing/), but there are several reasons as to why it wasn't suitable for what I'm trying to do;
1. I'm interested in using a 2D pattern rather than a 3D form, which will then be repeated within a Paneling point grid which is assigned to a surface. The repeated patterns are then pulled onto the surface, which are then used to trim the surface.
2. The surface I'm using has high curvature, and using box morphing intersects the surface, so it doesn't conform to the surface as closely as I'd like it to unless the number of repeats along U and V are increased.
3. The surface I'd like to use has various trimmed regions on it. Paneling Tools is great for me, because the 2D pattern is repeated on a Surface Domain point grid, so it is initially repeated over the the trimmed regions, but once since the Pull setting is used, only the repeated pattern curves that lie over the kept surface remain (see Paneling tools jpeg).
The surface I've used in the images isn't the surface I need to use, but hopefully it shows what I'm trying to do. Also, I've managed to get the patterning that I need on the paneling tool example, but the reason why I want to use Grasshopper is that it allows me to scale up/down the UV ratio of the paneling points by using a slider tool, so the user can change the pattern density. The only trouble with this is that I can't bake the points out of Grasshopper into Rhino so I can use paneling tools.
Also...I'd quite like to know how the VB module works, because I'm curious, and I'd like to learn more!
Sorry if this is a bit wordy, but I can't think of a better way of explaining what I need.
Cheers, Abs…
up before you can produce a nice render. If you are using vray for Rhino you need to first learn how to set up (as an architect) a nice solar daylight system with environment, is actually very easy. (1 - set up sun lighting, 2 - set up environment, 3 - choose correct settings, such as activating indirect illumination)
However, since sketchup is the perfect draft tool for architectural design, it happens to have an environment with daylight defined already when you open an empty file. Vray for sketchup knows how to use all these settings so the only thing you need to do is to hit render. Apart from that you need to learn some simple material settings, which you find here: http://www.vray.com/vray_for_sketchup/manual/, the same manual for rhino here: http://www.vray.com/vray_for_rhino/manual/
The advantage of using vray for sketchup rather than for rhino (although if you can handle vray for one program its exactly the same for the other), is that you can easily import models from 3d warehouse. Sketchup is an excellent render set-up platform, except its only 32-bit so a to complex scene will simply not render. Rhino 64-bit will handle this better.
Conclusion, learn vray, whatever you learn can be applied to sketchup, rhino and 3ds max. Sketchup is probably a tool you already use and vray for sketchup will render with correct settings by default. Later when you take it to the next step you can go one and learn vray 2.0 for 3dsmax.
Personally I like using Luxology render engine that comes with Microstation, simply because I handle it better and Microstation is the best tool for architects in my opinion. However Vray is similar but more powerful.…
Added by Martin Hedin at 4:11pm on October 21, 2011
something in 3d, explode it to single surfaces, reference it to GH in proper order -manually- then unfold it with gh).
To make it really elegant you could try to make some "topology language" - have you seen this talk by Robert Lang http://www.ted.com/talks/lang/en/robert_lang_folds_way_new_origami.... ?
You can always make only few parametric types of structures - like leg, hand etc. (this is much easier than Mr.Lang's ) which can change its sizes, but topology stays the same.
Beside - Your sandwich looks really good, i played something similiar before.... have you tried thin PE (polyethylene) sheets ? Its similiar to PP (polypropylene) but a little bit softer. It is (PP) commonly used as tic tac box cap ( http://www.absolutelynarcissism.co/wp-content/uploads/2011/09/Tic-T... ) and some say that it can fold/unfold about 1000000 times. It would really simplify the whole production (just one cnc router needed to obtain full structure). Of course bending it will require prefabrication to look like e.g. http://www.grasshopper3d.com/video/the-swarm-2012 by Mr. Wieland Schmidt.
To clear things up :
1. It certainly can be done with rhino/gh
2. You should write some more on how should it all work (what you provide as geometry)
3. You should also provide some more info how 2d drawing looks now.
EDIT : I forgot about kinematics - use kangaroo. There are forces now like bending resistance etc.
…
ont. outputs 2 lists. a with neighbors in front and b without.
i have attached a final screenshot, a rhino testfile with ca points and the final definition.
this is the code:
'Declare and Initialize data
Dim i As Integer = 0
Dim j As Integer = 0
Dim pts_count As Integer = pts.Count() - 1
Dim new_ptsA As New List(Of On3dPoint)
Dim new_ptsB As New List(Of On3dPoint)
Dim temp_pt1 As On3dPoint
Dim c As Integer = 0
'Loop through base points
For i = 0 To pts_count
c = 0
For j = 0 To pts_count
If pts(j).x = pts(i).x And pts(j).z = pts(i).z And pts(j).y = pts(i).y - 10 Then
Print("neighbor in front")
temp_pt1 = pts(i)
new_ptsA.Add(temp_pt1)
c = 1
End If
Next
If c = 0 Then
Print("NO neighbor in front")
temp_pt1 = pts(i)
new_ptsB.Add(temp_pt1)
End If
Next
'Assign new points
A = new_ptsA
B = new_ptsB
be aware that the code assumes a grid width and depth of 10x10.
volker.
…