rs of PBM (bitmaps). On Rhino one can export as STL for a number of printing solutions. However, to my knowledge, it cannot export more than one image file and unfortunately only as jpg (not as PBM or bmp). I've automated contours at successive heights of thickness, but I don't know how to export as a series of bitmap PBM into a CSV file. Does anyone know a single program solution? It would be great to script this through Grasshopper. Any ideas would be appreciated. Thanks in advance for your thoughts.…
reated after the python component itself. Also sometimes with the existing ones, but that looks really random, I can't figure out why.
Any idea ?
Here is the code I used :
"""Retrieve a named slider's domain. Args: Sliders: Slider NickNames. Update: Set to 'True' to update information. Returns: Start: Slider domain start. End: Slider domain end. Domain: Slider bounds as domain.""" # Name componentghenv.Component.Name = "Slider Domain Retriever"ghenv.Component.NickName = 'Slider Retriever' # Import librariesimport Grasshopper as gh # Get to the GH objectsgh_objects = ghenv.Component.OnPingDocument().Objects ghenv.Component.Params.Input[0].NickName = "Sliders"ghenv.Component.Params.Input[0].Name = "S"ghenv.Component.Params.Input[1].NickName = "Update"ghenv.Component.Params.Input[1].Name = "U"ghenv.Component.Params.Output[0].NickName= "Start"ghenv.Component.Params.Output[0].Name= "Start"ghenv.Component.Params.Output[1].NickName= "End"ghenv.Component.Params.Output[2].NickName= "Domain"#ghenv.Component.Params.Output[3].NickName= "Value" if Update: # Iterate objects for obj in gh_objects: # Set the named slider values if obj.NickName in Sliders: # Get [Number Slider] objects with NickNames if type(obj) is gh.Kernel.Special.GH_NumberSlider: # Find mininimum and maximum values Start = obj.Slider.Minimum End = obj.Slider.Maximum Domain = str(Start)+' to '+str(End) #Value = obj.Slider.Value # Update slider information obj.ExpireSolution(True)…
noceros 3D, en caso de aprobar satisfactoriamente el examen, se les otorga un reconocimiento avalado por el CMJ y la Secretaría del Trabajo. Este workshop va dirigido principalmente a estudiantes de arquitectura; sin embargo, ya que la parametrización es una herramienta que abarca diferentes ámbitos del diseño, se pueden integrar estudiantes de diseño industrial, artistas o estudiantes que tengan relación con lo gráfico y lo formal. Al finalizar el curso, los asistentes serán capaces de manejar Rhinoceros y Grasshopper en un nivel medio, con el objetivo de que el alumno pueda continuar aprendiendo con alguno de nuestros workshops subsiguientes o de manera autodidacta.
Las personas inscritas deben tener conocimientos básicos de geometría y de preferencia utilizar algún programa de dibujo en 2D o modelación en 3d. Rhino.GetMe Rigid // Enfocado a construir un objeto de diseño parametrizado a cualquier escala, el workshop se divide en tres módulos: Módulo 1 // Rhinoceros 3D // Una sesión de cinco horas. Módulo 2 //Grasshopper // Una sesión de cinco horas. Módulo 3 // Ejercicios prácticos /Tres sesiones de diez horas c/u. Es necesario traer el equipo necesario para trabajar, se cuenta con equipos en caso de que algún alumno no cuente con laptop pero son limitados, por favor avísanos a la brevedad si lo requieres. Se les recomienda que traigan dispositivos de almacenamiento en caso de que necesitemos compartir información.
El costo del Workshop es de $6500.00 para profesionales y $5000 pesos para estudiantes.
Pre-venta únicamente para estudiantes, hasta el día viernes 29 de junio, con un costo de $3500.00 pesos.
El cupo del evento es limitado puedes apartar tu lugar y terminar de liquidar antes del 29 de junio en pre-venta, antes del 6 de junio en admisión general.
Para hacer tu registro al workshop por favor envía un correo a workshop@transformalab.com incluyendo:
Nombre
Universidad u oficina de procedencia
Teléfono móvil
En el caso de estudiantes por favor incluyan una copia escaneada de su Constancia de Estudios para hacer válido su descuento.
Una vez recibida su información se les enviará un correo con la información necesaria para realizar su pago mediante depósito bancario, y posteriormente un mail de confirmación de su participación en el Workshop.
www.transformalab.com…
ack to .ghx?
This is in relation to a discussion I've been having with David Rutten & Scott Davidson about GH consuming memory in a relatively large GH definition (~. I think what I've learned from this is that one should limit the size of the GH file, or put some incremental stops in the definition to limit the length of calculations that it runs at once. Is this a valid conclusion?
The GH file we're talking about is 7Mb & the Rhino file is about 120Mb, but when working w/ the GH def. I try to only keep about 2 curves turned on.
Here's a summary of the discussion:
Hi Mike,thanks for sending it over. I've been fiddling with the file for about 10 minutes and it climbed from 1.7 GB to 1.9GB, but then I've been switching previews on which means more meshes get calculated so you'd expect a higher memory consumption. It is possible we're leaking memory, but if you're working for hours on end, memory fragmentation might also explain part of the increase. Basically, memory gets fragmented just like disks get fragmented after prolonged use, difference is that memory cannot be defragmented unless you restart the application and allow it to start with a clean slate. I'll try and find any leaks we may have missed in the past.Goodwill,David
──────────── David Rutten
On 09/03/2011 06:19, Mike Calvino wrote:
Thanks very much David for the quick response. I've attached the files zipped. I can't figure out what's doing it. After working in the file for awhile, the memory usage in the Windows Task Manager climbs . . . it's gotten to 1.57+Gb before I exited GH & Rhino5Wip & let it dissipate, then restart & work for awhile before it does it again. It probably takes like 4 or 5 hours before it gets that high. That's the highest it's gotten, & that only happened while I was working in a Rhino file that had all of the elements baked into it - turned off at least, but it still climbed to 1.57+Gb. It seems to climbs when you work in the file & move around in both the GH def. & the Rhino file. Like turn on a few of the Extr components at the right end of the "StandareRibExtuder" groups, you can watch the MemUsage go up, but when you turn them off, it does not go down. - goes up fast at this point. Maybe I need to figure out how to do the definition with fewer components, I'm sure that's part of it, but I must confess, I think I'm still early on in the learning curve.I really hope that this is not operator error on my part & I do apologize up front if it is. I have done a disk cleanup, I have tried excluding .3dm & .ghx files from my NOD32 antivirus, no change. I hope you can find something.Let me know if you have any trouble with the files.See if you find anything & please let me know . . . thanks!Cheers! --Mike CalvinoCalvino Architecture Studio, inc.www.calvinodesign.com
…
this workshop is to materialize a chair designed with help of generative algorithms via robotic fabrication. To design the form of the chair we will go through an intensive course of generative design techniques, k-means clustering, structural analysis and optimization done with the help of Anemone, Galapagos, Millipede and other plugins. Finally we will employ a 6-axis robot with custom tooling to fabricate the chair via robotic rod bending. No prior experience with Grasshopper or robotic fabrication is required, although basic knowledge in 3d modelling would be an asset. // APPLICATION The deadline for application is 13.03.2017 Apply by sending email titled ‘workshop_chair’ to workshops@aan1.net // INFO If you have any more questions check the www.aan1.net website or contact us with email workshops@aan1.net // FEE We have special pricing for students, as well as an early bird offer. Check the Eventbrite list to get more details. Please bear in mind that a limited amount of seats is available (minimum 8 people, maximum 16). ORGANIZERS: Maria Smigielska, Mateusz Zwierzycki, AAn+1 TUTORS: Maria Smigielska, Mateusz Zwierzycki PRICES: Early Bird Student 280 E Early Bird Pro 320 E Regular Student 300 E Regular Pro 350 E…
in a "bigger" scale, he he). Divisions are proposed to suit variable area schedules (small airport with 3 divisions bigger wow stuff with more). My initial intension was to design this via insulated tensile membranes (THE engineering purity) bit client thinks that these are only suitable for some gypsy campus.
2. Goal is to outline a collection of "boundary" surfaces (so far the definition deals only with the exterior skin and an indicative WIP "base") that could define "in-between" them space trusses. See a primitive "generic" outside boundary in the Rhino file (second not shown). Of course ideally this type of forms is actually T-Spline territory, but never mind.
Back to GH thing:
3. See results with C# Surf rebuild and odd results with closed stuff as well.
4. It's obvious that mess relaxation (Geo Gym stuff) methods are required here - working solely with nurbs is a clear dead end (unless applying "weaving" in dense U/V areas) .
Stupid questions section:
(a) how we can trim surfaces in GH? - help in components...er...hmm...is this help?
(b) by what means can we fillet, variable fillet and/or blend surfaces in GH? Of course given an infinitive amount of time one could do that by defining a myriad of suitable curves - but this is CAT not CAD (T=torture).
Best, Peter (one step before Plan A, no actually there's no Plan A since Microstation/Gen Comp can't blend/fillet correctly a thing (or two), he he)…
I want is a definition to optimize an existing Surface Grid to match with any curves that I put on the surface.
let's just say I have this existing Surface UV during the first stage of the design=
and then somehow, I want to cut this surface. so I made 2 boundary curves represent the boundary in which the surface will be trimmed later.
if I did not change my UV Grid, the mullion will not be trimmed right at their intersection point
the goal is to reconstruct a new Grid Cell that still inherit the original surface UV direction, but have different UV interval.
this optimization technique so far I have seen in Kangaroo and Evolute Tool. and I have no plan to purchase evolute so I hope I can achieve the same technique with Galapagos.
here I attached my full definition. pardon for the big mess in that file. because I havent got time to tidy it up.
I will study both your definition first (Riccardo and Peter). and try to digest it first :)
I hope u get what I mean…
switch to the other cases until you get the gist of the available options (push/pull, reverse, 2 surface creation modes, distance values remap etc etc).
Push/Pull:
The main point here:
In plain English: a capability is added to exclude "peripheral" control points from the sample of modified points > toggle this bool in pink (shown: the false option) to get the gist of it and think: a sphere (or any closed in U/V surface) is in fact a "rolled"/"wrapped" variation of that flat thingy. Imagine what happens if you attempt to modify the sphere "star" points ...
I hear you: but ... you start (gradually) replacing components with these C# freaky things of yours > is this help? Well ... er... can I have the next question please? he, he.
Next update (V4): 10+ "tiling" options (patterns) for that poor surface. Plus random/chaotic stuff. Plus 12,34 divisions by zero
have fun, best, Peter…