ream (level 1) { Exception has been thrown by the target of an invocation. TargetInvocationException }
Object: WebCam_VideoStream (level 2) { The type initializer for 'Firefly_X.WebCam_VideoStream' threw an exception. TypeInitializationException }
Object: WebCam_VideoStream (level 3) { Attempted to read or write protected memory. This is often an indication that other memory is corrupt. AccessViolationException }
Upon closing the dialog box, grasshopper starts normally, and there is a tab for firefly as promised. :)
Just wondering if this error means something.
System details:
Rhino : Version 5.0 (5.1.20927.2230, 27-Sep-12) (Evaluation)
Grasshopper: Build 0.9.0014
Firefly: Build 1.0067
OS: Win7 - 32bit
…
from C# to Python, but as they are two different languages, I've gotten stuck on a specific function.
I can already make a point within python by using Rhino.Geometry.Point3d(x, y, z), but I can't figure out how to use Rhino.Geometry.Transform.Rotation.
The below function takes an input of two Point3d objects (points a and b, in this case).
Two points are then found between the points-- 1/3 between the two and 2/3 between the two points (p1 and p2, respectively). What I am trying to do is rotate p2 about p1. I'm not sure where to introduce p2 into the function I made in order to do this.
--------------
def PtB(a, b): p1 = a + ((b - a) / 3) p2 = a + (2 * (b - a) / 3) Rhino.Geometry.Transform.Rotation(-math.pi / 3, Rhino.Geometry.Vector3d.ZAxis, p1)
--------------
The way this is done in the C# script I am referencing is the following:
Transform trans = Transform.Rotation(-Math.PI / 3, Vector3d.ZAxis, p1)
p2.Transform(trans)
Does anyone have any tips?
Also, I've been working in grasshopper 1.0.0004 in Rhino 6 WIP since Rhino 5 crashes when I try to open the python script editor within the older version of grasshopper.…
e this week - you will be presenting the top 2 in class
Links:
Rendering resources
http://www.archdaily.com/777432/6-websites-for-ethnically-diverse-render-people
https://www.pinterest.com/jiwaskiw/section-perspectives/
https://www.youtube.com/channel/UC_eRv_Rzr671BaKFtpYSi4A
https://visualizingarchitecture.com/
3D printed houses back in the news
http://archinect.com/news/article/149995791/in-24-hours-get-a-3d-printed-house-that-will-last-175-years
Filament Pavilion
http://www.archdaily.com/806242/elytra-filament-pavilion-icd-itke-university-of-stuttgart…
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.
…
the piece, that is mapped to the world XY plane & with as many parts as you define.
The definition is a sketch right now & so is not labeled so much, but the brep component at the left is where you reference the component you want to make a 2d of, then you use the slider labeled "Face#(percentage of # of faces)" to select the correct face(I think I can make a component that will automatically do this) , then adjust the X spacing of the 2d drawings, select the #Pieces, & bake the "Curves to Bake" component. Maybe it's a little involved at this point, but it's a start & beats doing all of that manually. This gets you the 2d of the parts you need to cut. Next would be a way to automatically generate the toolpath lines whether it's a "cutout"(being inside & outside of 'grouped' lines) or outside or inside cuts.
Then it would connect to your definition for defining feedrate, stepdown, end depth etc. + the g-code output.
I agree, a nesting program is not what this is about right now.
I actually think CAMel is along the lines of Lobster & Beaver - something more specific & involved.
That's why I'm excited about yours as a general plugin that can produce general 3, & eventually 4 & 5 axis G-code for production & cutting. I think with that platform working we can then tweak it or modify it to accommodate more experimental stuff. But for now, many need to be able to generate production code in a tightly integrated workflow like Rhino/Grasshopper.
A Rhino4 file in .zip format is attached that can go with the gh file.
Let me know what you think - maybe I'm miles behind . . .
Cheers!…
yet accessible features that have been well factored.
I’m impressed with the mainline experience overall. BUT, and this is a huge but, Rhino5 has an absolutely massive bug right in the middle of the engine. I, of course, refer to the Boolean Problem. I’ve put the product down cussing 4 times already after realizing that I’d just lost 3 hours trying to figure out why something doesn’t work, only to realize that I’m up against yet another derivation of The Boolean Problem.
I’m written McNeel tech support about the issue. They’ve offered file-specific workarounds in response. But these workarounds don’t allow a solution that can be used resolve generalized characterizations of the bug in Grasshopper programs. Brian, the support tech I’ve dealt with on this problems goes on to say that I shouldn’t expect any significant fixes for this problem.
I’m shocked that major revision 5 of a seemingly mature product as Rhino is has such a gigantic, mainline bug in the very core of its engine. But even more surprising is Brian’s suggestion that perhaps I’m just not ready for a product like Rhino. He further suggests that I post, as I’m doing here, to see what other people think about this bug.
So what am I missing? Where do experienced Rhino/Grasshopper users find themselves on the continuum between this being a big hairy bug that should have been fixed long ago and my just not being ready for Rhino?
I’ll accept any input and consensus that prevails.
- Bob…
Added by neobobkrause at 2:34pm on October 3, 2016
vid Rutten (the creator of Grasshopper) as the leading poster. Amassing just over 7000 posts. I have been a regular contributor since this forum starter 5 years ago and I am only half way there.
The line between "the only stupid question is the unasked question" and the "why is no one here answering my questions question" needs to be walked with care.
We have all been where you are now. Admittedly it was probably easier for me as there wasn't that much to the program when I started using it and my learning curve has been an incremental one as things get added.
It doesn't help that all the documentation that is around is out of date as soon as it gets published, but that is the nature of software in BETA... things change. I know of a concerted effort by the powers to be to document Grasshopper better. But this is a little way of from completion.
If it helps I can think of two examples of questions that I either should have asked or did and regretted.
Firstly I had no idea you could bake geometry into the rhino document when I first used Explicit History (former name of GH) I mean what the hell does a fried egg have to do with it :) so I simply ignored the plug-in for a month or so. If I'd asked how do I get my Red transparent surfaces into Rhino, I would have been using it a lot sooner.
Secondly I wished for a way to display the output of a component so that I could see it without having to hover over the tool tip each time. I didn't realise that Post-it Note (or Panel as it is now due to copyright issues) had an input as well as an output.
The most important thing to remember is that Grasshopper is an extension of Rhino. By not knowing Rhino you are at a greater disadvantage than the rest.
If you don't know how you should go about modelling something in Rhino how are you going to be able to develop meaningful algorithms in Grasshopper.
Danny…
he Summer in the City program, part of the Portland School of Architecture and Allied Arts (an extension to University of Oregon).
Using both Grasshopper and the Firefly plug-in, this workshop will focus on the design of innovative facade prototypes that are configurable, sensate, and active. Students will become familiar with the terminology used in interactive facade design including an overview of hardware (ie.sensors, actuators, and programmable microcontrollers) as well as software interfaces terminology. We'll learn new prototyping techniques and develop digital and physical models which can respond to a plurality of environmental and user driven forces. This workshop will take a hands-on approach, and you will walk away with the ability to build your own custom electronic circuits (using the Arduino), as well as create interactive simulations and models.
This course will primarily focus on physical computing techniques. Unfortunately, given the time constraints of the workshop, I will not be able to provide an extensive overview of the Grasshopper interface (it is suggested that participants have some familiarity with the Rhino/Grasshopper environment). There are many great online resources to get you up to speed relatively quickly if you are new to this software. This is a good place to start.
The course will be held at the School of Architecture and Allied Arts in Portland, OR. The date/times of the workshop are as follows:
Friday July 19, 5:00-7:50 P.M.
Saturday July 20, 9:00 A.M.-3:50 P.M.
Sunday July 21, 1:00-3:50 P.M.
If you are a designer, architect, or anyone who is interested in learning about the digital tools and technology trends that are revolutionizing design today, this workshop is for you. Make sure to click here to find out more about registration and enrollment in this exciting new workshop.…
I have the IES files from the manufacturers. I am able to get the IES files to load and run in Honeybee. However the light levels being produced are low and very localized to the light source. I am trying to determine if it’s some scaling, etc that needs to be modified. Within Honeybee there is a “CandelaMultiplier” which allows me to increase the values, but I don’t want to do it arbitrarily nor am I sure this is truly solving my problem.
If anyone has any insight as to importing IES files into Honeybee and things that need to be factored and considered that would be appreciated. I'm experiencing the situation with other IES files as well.
Thank you!
Screenshots: 1 candela multiplier, 5 candela multiplier, 5 candela multiplier 2 lum web, legend and screenshot of grasshopper interface:
Files attached: SunCentral IES file, Rhino, and Grasshopper
…
diseño, construcción y entendimiento de nuestro entorno.
BIM está poniendo a disposición de los diseñadores y gestores auténticas bases de datos que pueden generarse, conectarse y editarse de forma paramétrica, proporcionando una sólida capa de realidad a los ejercicios de diseño generativo y computación que son objeto de estudio en Algomad, el seminario que busca popularizar la programación y la parametrización en el diseño y en la experiencia de nuestro entorno construido.
Tras un paréntesis en 2015, Algomad vuelve con el objetivo de demostrar cómo una visión computacional del BIM es una oportunidad para mejorar la forma de trabajar de ingenieros, arquitectos, constructoras y operadores de edificios e infraestructuras, tendiendo un puente entre las técnicas de diseño digital más avanzadas y la realidad de la construcción.
Algomad 2016 tendrá lugar en el centro de Madrid, en IE School of Architecture and Design, IE University, los días 3, 4 y 5 de Noviembre de 2016 y comprenderá 4 talleres así como ponencias a cargo de expertos de primer nivel.
Estructura de Algomad 2016
Algomad 2016 se estructura en torno a tres áreas temáticas principales:
BIM, como la metodología total específica para el sector de la construcción.
Computación, englobando las aplicaciones de programación y parametrización al diseño de edificios e infraestructuras.
Realidad, como marco de trabajo, buscando siempre resolver problemas reales a través de los dos puntos anteriores.
Público objetivo
Arquitectos, arquitectos técnicos, ingenieros y en general académicos, estudiantes de últimos cursos y profesionales del mundo inmobiliario y de la construcción que compartan un interés por la digitalización de nuestro sector. Se espera un nivel mínimo en el uso de herramientas BIM y de parametrización. Algomad proporcionará formación adicional y gratuita en las herramientas básicas a emplear en los talleres para asegurar un correcto desempeño.…