offers new design methods helping participants both in concept and practice. Active discussions on the contemporary issues of architecture and design will be held in order to provide participants with an opportunity to share their views and create their own project.The workshop is going to be used as a platform utilising multi-layered techniques and production processes which can control intelligent geometries, calibration of parts and behavioral taxonomies, normalizing an innovative field of predictability. Exploring material intelligence, formal logic efficiencies and precision assemblies.DETAILS///In the DYNAMIC MUTATIONS workshop we will emerge into Maya’s polygon modeling, pattern makingand animationtools, adaptive skin and kinetic structures, covering all the required basis and getting a taste of its more advanced features. We are going to simulate material properties and dynamic forces with Maya physics engine. Moreover, the design logic and generative processes, as well as the potential of parametric thinking as a resourceful tool for achieving diversity and complexity in generation and fabrication. Kinesis and morphosis will be the two keys of the workshop. The participants’ end result must present both characteristics of these aspects.The goal is creating a project that each participant can proudly include in his portfolio using the state of the art programs and techniques.For attending the workshop there is no previous software experience required.WHAT YOU WILL LEARN///- Introduction in Mayapolygons and NURBS modeling- Simulation of material properties and dynamic forces with Maya physics engine- Animation tools and Maya skeleton system to control complex morphologies - Visualization and rendering techniques - Maya MEL script for creating customized tools and interface- Introduction in Rhino 3D- Parametric surface articulation with Grasshopper - Strategies for 3D printing - Lecture on project presentationTUTORS///PavlinaVardoulaki / Greece & Bulgaria / AA School of Architecture, LondonJiteshJidhav / India / AA School of Architecture,LondonAPPLICATION///http://designmorphine.com/…
Red Sea . Jordan
FORMAT:
APPLY:
Limited Spaces are Available, Application form accessible here
A 60GBP deposit can be made to secure a space, remaining payment before programme start.
The AA Visiting School Jordan requires a total fee of 895GBP. This includes.
CONNECT:
You can Visit our website http://jordan.aaschool.ac.uk
or email us at jordan@aaschool.ac.uk
PAST WORKS:
…
ASS 2017 Conference in Hamburg, Germany. Join them to:
Learn how to use simulation-based optimization in Grasshopper
Learn about the differences between optimization algorithms in Grasshopper and when to use them
Learn how to assess the performance of optimization algorithms
Learn about differences between single and multi-objective optimization algorithms
Experiment with benchmark problems
Experiment with optimization problems from your own practice and research (bring your own optimization problems)
Experiment with optimization and visualization tools not yet released publicly
Thomas and Judyta are researchers in architectural design optimization. Thomas is the lead developer of the machine learning related optimization tool Opossum and Judyta a co-developer of the particle swarm optimization tool Silverye. Adrian is the founder and the owner of Architektura Parametryczna – the biggest Polish consultancy company in parametric design. (Find Thomas’ and Judyta’s work on ResearchGate here and here.) Registration closes on Tuesday, July 25, 2017.
Registration through the IASS website:
https://express2.converia.de/frontend/index.php?folder_id=943
Facebook event page:
https://tinyurl.com/ycv24m8g
…
' group that fixes it. Unfortunately, the kludge fails with my other test surfaces so I added a switch between "Method #1" and "Method #2" - hence the group label "Kludge":
This got the holes to work on the 'right eye' surface but 'both eyes' fails for a different reason...
So I decided to see what happens with a mashup of this code with MANU's code to produce facets instead of holes:
It works! The "Smooth" holes produce a twisted lofting that looks a little weird - oh well.
The "Sharp" setting looks pretty good, though there are small differences using 'PtCloudCntr' instead of 'Area' to get the centroids...
This code (attached) is ~4 times faster when the point count is increased from 100 to 200 (~16 seconds vs. ~70 seconds):
Thanks again MANU. It's really difficult to write FAST code that handles all surfaces well.
P.S. Since MANU's code is randomly scaling down the "holes" for the facet surfaces, the 'Scale' slider in the yellow 'Controls' group can be set to 0.99 - 1.0 fails for "Sharp", though it works for "Smooth".…
Added by Joseph Oster at 11:47am on December 23, 2015
interested in a certain area or floor of a scanned building.
Having access to the Scan positions, without the need to load tens of Gigabytes, allows to quickly select and import only scans in a certain height and range.
Here a small GH definition, which uses the A-House Scan June E57 file from data.duraark.eu (10.4GB in size, 16 scans covering two levels) The GH definition allows to select and subsequently import:
a) only scans from a certain range in height - lower scans
upper
b) only scans in a certain range in XYZ direction
The definition is not very sophisticated, but demonstrates how Volvox and Point Clouds can integrate into Grasshopper workflows. The GH definition can be found here
The scan can be directly downloaded from here
Here a full view on the A-house scan with 8% of points loaded:
…
holes on each so speed increases). Zero radius circles are skipped.
The image dimensions in pixels are defined in small panels (X=485, Y=759) and used to calculate height/width ratio. That is used to define height based on the 'X' slider (500), which defines width overall.
The 'cell size' slider is also in units and determines resolution indirectly. For any given X value, increasing 'cell size' reduces the number of grid cells (resolution) and vice-versa.
Independent of other parameters, 'Isotrim (SubSrf)' splits the base surface into sub-surfaces, onto which the circles are projected. The 'SrfSplit' does the heavy lifting (can be SLOW!) and finally, 'Sort' is used to select the resulting surfaces that contain the holes.
Benchmarks:
X = 500, cell size = 10, 3161 circlesnine subsurfaces: 'SrfSplit' = 6.6 minutes, 'Project' = 13 secs.16 subsurfaces: 'SrfSplit' = 2.3 minutes, 'Project' = 17 secs.
X = 500, cell size = 5, 12542 circles (shown)35 surfaces: 'SrfSplit' = 30.6 minutes, 'Project' = 57 secs.
As noted before, a very long-standing, well-known bug in Grasshopper fails to save the Image Sampler component when I save a copy of your file. Very annoying, but there is a work-around. Copy/paste and connect the Image Sampler from the code you posted above into the place I reserved for it.
"Pro Tip": Always work at low-resolution until your algorithms are proven before cranking up to 10K+ geometry counts!
Attached file has low resolution settings with 'Project' and 'SrfSplit' (red group) disabled.…
y part of existing files, you typically mark the old component as [Obsolete]* and write an entirely new component which has the changes. This allows you to open old files and have them work in the same way as before, by loading the obsolete component instead of the current one. You can then choose to add an automatic upgrader which is a class which knows how to replace an obsolete component with an updated version in situ. You can load all upgraders via the Solution->Upgrade Components... menu.
An upgrader is a class which implements the IGH_UpgradeObject interface. There's also a GH_UpgradeUtil class which provides some useful static methods for doing common upgrade stuff. For example, here's the upgrader for the [Polygon Centre] component:
public class Upgrade_PolygonCenterComponent : IGH_UpgradeObject { public Guid UpgradeFrom { get { return new Guid("{7BD7B551-CA79-4f01-B95A-7E9AB876F24D}"); } } public Guid UpgradeTo { get { return new Guid("{87E7F480-14DC-4478-B1E6-2B8B035D9EDC}"); } } public DateTime Version { get { return new DateTime(2011, 12, 7, 16, 30, 00); } } public IGH_DocumentObject Upgrade(IGH_DocumentObject target, GH_Document document) { IGH_Component component = target as IGH_Component; if (component == null) { return null; }
IGH_Component upgradedComponent = GH_UpgradeUtil.SwapComponents(component, UpgradeTo); Grasshopper.Kernel.Parameters.Param_Point extraParameter = new Grasshopper.Kernel.Parameters.Param_Point(); extraParameter.Name = "Center(E)"; extraParameter.NickName = "Ce"; extraParameter.Description = "Average of polyline edges"; upgradedComponent.Params.RegisterOutputParam(extraParameter);
return upgradedComponent; } }
* This can be done either by adding the string "OBSOLETE" to the component class name, or by adding the [Obsolete] attribute to the component. Do note you have to change the exposure to Hidden, otherwise the obsolete component will still show up on the panels.…
Added by David Rutten at 9:36am on October 21, 2017
le] demo):
1. A transformation Matrix is a 4*4 collection of 16 values that "deform" 3d things according the values in the cells. The orthodox way is to deploy "cells" left to right and top to bottom. Rhino does the opposite (why?) hence we need the transpose method.
2. Since "translate" and "perspective" are "symmetrical" the transpose boolean toggle (within the C#) "flips" rows with columns ... so we get perspective or move.
3. When in perspective "mode" the vanishing points are computed internally within a min/max limit (per X/Y/Z axis) thus avoiding the usual havoc with "extreme" perspective angles (very common "glitz" in pretty much every CAD app - CATIA excluded). Vanishing points (and limits) are oriented with respect the pos/neg value of a given control slider.
Note: slider values are percentages between min/max (mode: perspective) and/or actual values*100 (mode: move).
4.In order to start mastering the whole thing: don't change anything: just play with these 4 sliders selected:
5. The 123 sardine cans challenge: even with DeusExMachine = true (see inside C#: that one redirects the transformation per BrepFace and then joins the breps instead of applying it on a brep basis)... odd things (and/or invalid breps) occur ... thus what is required in order to make things working 100% ??.
he, he
best, Lord of Darkness …
he tools provided by System.Drawing (I know, there is a module called PIL that works in Python but I couldn't get it properly working so I just jumped to System namespace...).
The first problem that I found is that there is no a direct way to store colours into saved images in other format different than 8 bits per channel...
PixelFormat48bppRGB, PixelFormat64bppARGB, and PixelFormat64bppPARGB use 16 bits per color component (channel). GDI+ version 1.0 and 1.1 can read 16-bits-per-channel images, but such images are converted to an 8-bits-per-channel format for processing, displaying, and saving. Each 16-bit color channel can hold a value in the range 0 through 2^13.
From -> here.
...so the accuracy of the information stored is very very low (as much as 256 possible values per channel, ≈ 16M of different values per pixel) if I need to store the data in the hard-drive (thing that I would anxiously like to do for further processing).
So, is there any efficient way of storing at least 16bits (it's not an ideal solution but...it could work) per channel data into an image file using System namespace instead of an external library?.
...the thing is that I know that using:
imageTest = System.Drawing.Bitmap(mX,mY,System.Drawing.Imaging.PixelFormat.Format48bppRgb)
...I can create a 16bits per channel image, but how could I specify the 16bit color if System.Drawing.Color limit the range to 8bits values?
And ideally, does anyone knows how to work with and save directly floating point colours into image files using python?
Thanks in advance ;)
Ángel.
Sevilla, Spain.
…
hole new realm?
This Parametric Design Webinar will provide you with the necessary knowledge and ability to use Grasshopper, a free visual programming plugin in Rhinoceros.
If you already know Grasshopper and would like to uplift your parametric knowledge, then you can choose option 2.
Option 1: General WEBINAR for Beginners - 8 Days / 16 hours in total: Start 01.08.2022
Option 2: Intensive WEBINAR for Intermediates - 4 Days / 8 hours in total: Start 08.08.2022
TIME ZONE: CET
WEBINAR Language: ENGLISH
Kindly reserve your Tickets here:
https://billetto.eu/en/e/parametric-design-webinar-rhino-grasshopper-tickets-661419
WEBINAR LINK:
WEBINAR invitation link will be sent to all participants after registration via private Email
WEBINAR FORMAT:
The webinar's format is hybrid, with live introduction, Q&As and in-class questions, with the main lessons being recorded.This optimal structure has been reached to make sure that all webinar materials are covered within the time frame given and for your benefit, in case you had to miss any parts of the webinar.
If you miss parts of the webinar for any reason (work obligations, sickness, different time zone, other urgent matters), please let the webinar instructor know in order to run the missed parts on other times that suit you.
If you have a different time zone or the webinar time doesn't suit your schedule, please let the instructor know beforehand in order to run the webinar on other times that suit you.…