ut it locking up again.
I'm told we have to wait for Grasshopper 2 wed to Rhino 6, in months or years from now since Grasshopper isn't multithreaded. It does look for the escape key but not reliably at all.
Here is a response from the developer to my same sort of question:
http://www.grasshopper3d.com/forum/topics/emergency-top-for-solutio...
David Rutten: "if it was doable, I'd do it, but Grasshopper runs on the main UI thread which means that no key presses come through until the process is done. Right now I check for escape key state (circumventing the key-press events) at certain points during the solution, but the more I check the more I slow down the solution, and there are large areas where I can't check because it's not my code that is taking up all the processor power in the UI thread."
I solved my own problem in that case by leaving the solver disabled in the menu and then invoking it manually as a recompute menu command that works once anyway. That won't help you with a rogue script though, but will let you set things up without Grasshopper recalculating each change.
With the solver disabled, when you have to manually invoke a recompute, that necessary action can help remind you to save first.
I tried assigning the Rhino command GrasshopperUnloadPlugin to F4 in Rhino settings but in the test case of populating a box with 1000000 random points (Vector > Populate 3D), the freeze up cannot be ignored as you access Rhino, which remains grayed out as a program even when you highlight its window, and nor can you get any Grasshopper command-S in while its running forever. That's only the equivalent of 100X100X100 points yet it still locks up Rhino so long. Thinking in this very simple case clarifies things, since it it won't let go then complex scripts may have some better chance but really the problem is in the system itself.
At least the Rhino close box works, so you don't need the Windows Task Manager :-).
There are also autosave options in Grasshopper preferences that creates an autorecovery file for the next time you open the same document.…
learn, or as an alternative to your morning coffee + cross-word puzzle.
Rules:
Contributions can be posted by anyone. Either selected from a previously posted problem from the general discussion (please acknowledge original poster), a selection from one of the many grasshopper+ primers (please include credits) something you think is fun, curious about, or even something you want to learn.
We should keep the entries dated so we can track them. One new problem per day (so if you see one posted for today- there is always tomorrow).
User(you) adds post titled: date-name of problem.
Solutions will be posted with breakdowns, either in logic procedure, etc. And in the spirit of the NY Times, an explained solution will be posted as well within the following days.
Remember there are multiple ways to solve a problem- however the “official” post should include a “clean and elegant” (or simplest) solution. So that all learning can develop better scripting habits.
Rules: an explanation.
1- Submission categories are as follows:
Native
Plug In
Scripted
Each category should have a difficulty rating - 1 to 5 perhaps.
They should be included in title for clarity-
Date_NameOfProblem_Native Plugin or Script_Difficulty
2. Since we are an international community, and this is an open group- a C+G day starts at the time of 10 am local poster’s time.
3.Anyone can set the next question. However the same person cannot set two days in a row. If a question is up- then next person needs to wait until the following day to post. You can PM Danny Boyes or Myself (Monique) if you are having posting issues- (i.e.: how to post, or have been trying to post, but keep missing the opportunity)
4. Answers are presented in the typical grasshopper community response way: in the form of examples, and/or screen shots. For screen shots: make sure the nodes are legible, if you do a function inside a node make sure we can see what you did. Verbal explanation. Maybe picture of result.
The difference between this group and the general discussion is that the poster should know how to solve the problem, be able to post a solution up themselves.
5. The poster judges the answer. They should offer a sample solution as well when they declare the winner.
However overall quality control may be checked by moderators of the group.
6. Still thinking about this one. …
cremental release is available for download. It fixes several bugs reported in the 0.9.0005 & 0.9.0006 versions. To wit:
Computer mice with smooth scrolling would not zoom well, this is fixed.
Previewable parameters with a lot of consecutive null items would crash, this is fixed.
Identical GHA files would collide during the loading process, this is handled.
GHA files with identical names would collide during the loading process, this is handled.
Solver Undo setting was not persistent, this is fixed.
Widget ZUI Zoom setting was not persistent, this is fixed.
Markov Widget Corner setting was not persistent, this is fixed.
Markov Widget Suggestion Count setting was not persistent, this is fixed.
Drag and Drop on Document and Template preview materials wasn't recorded, this is fixed.
AssignDataToParameter() COM-Access method was broken, this is fixed.
Geometry and Generic parameters with persistent data would not deserialize correctly, this is fixed.
Operator shortcuts via the Canvas popup instantiation menu no longer assigned data to the second parameter, this is fixed.
Cull Duplicates component did not always show the correct label upon deserialization, this is fixed.
Legacy VB/C# components would not correctly deserialize List access on input parameters, this is fixed.
Cloud Display component would still display old sprites on disconnect, this is fixed.
Minor changes to a document would trigger lengthy preview cache updates, slowing Grasshopper down. This is fixed.
Sphere 4Pt did not work correctly, this it fixed.
Failed data conversions in parameters would result in missing entries, this is fixed.
Text Tag components (2D & 3D) would not bake via the component menu, this is fixed.
There are also some new features:
Added Jump object for quickly navigating across a Canvas (Params.Util dropdown).
Added Relative Differences component which is basically the inverse of Mass Addition (Math.Operators dropdown).
Added tooltip wiggle controls to the Preferences window, Interface section.
'Draw Full Names' now also attempts to change the display of existing components, but only in the active document.
Drag+Dropping GHA, GHPY and GHUSER files onto the canvas now puts the original file into the bin.
Replaced Set Union component with a new one that has variable input parameters.
Replaced Set Intersection component with a new one that has variable input parameters.
Replaced And and Ternary And components with a single new one that has variable input parameters.
Replaced Or and Ternary Or components with a single new one that has variable input parameters.
Replaced Concatenate component with a new one that has variable input parameters.
Concatenate component now has a segment join option available via the component menu.
Added Digit options to the Transform Matrix Display object.
Integer parameters which represent options now have more informative context menus.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
…
Added by David Rutten at 11:06am on September 14, 2012
Rhinoceros y Grasshopper los participantes puedan desarrollar mediante un flujo de trabajo digital las técnicas de Diseño Paramétrico, mediante métodos algorítmicos generativos, para su implementación en procesos de diseño y representación de los mismos, a través de:
Proliferación en topologías complejas mediante Definiciones visualizados Estrategias de Mapeo y Análisis evolutivos en Tiempo Real Técnicas avanzadas de modelación 3D e imágenes foto realistas Vinculaciones entre criterios Predefinidos paramétricamente y Morfologías resultantes
Detalles: ∙ Instructores / Matías Casciotta y Salomón Escobar / Integrantes Ha-11 ∙ Todos los niveles de experiencias son bienvenidos ∙ Recursos: Interfaces Rhino + Grasshopper / Manuales PDF / Definiciones GH Preparadas ∙ Los participantes deberán traer su propia laptop con todo el software y actualizaciones (originales o versiones de demostración) previamente instaladas. (Se fijara una fecha unos días antes para revisar que todos los equipos estén en orden y listos para trabajar).
Fecha y Lugar ∙ 3 semanas a partir del 15 de Marzo del 2012 - Lunes y Jueves de 19:00hs a 21:00hs - ∙ El taller se dictara dentro del ámbito de cursos del Arquitecto Alejandro Correa.
INFORMES: Ha11 en Facebook ha.11.arquitectos@gmail.com…
Amuse yourself by trying to figure what kind of series logic could deploy (or not) these room unit combos across the blue space grid shown.
2. Let's assume that surgery etc etc departments are sited in some ground floor and their requirement for rooms is variable ... meaning that some kind of heuristic GH approach must be applied here (for instance : fill the first level with rooms required by all departments with min distance from a given core and if more are required go to next floor etc etc).
The real room unit cluster looks like that (all units are prefab)
3. Voids in the whole cluster deployment (avoid Soviet type of bloc aesthetics) mean that culling could be challenge here (we need ...er..."visual" culling , so to speak)
4. After finishing some solution create custom preview(s) in order to visualize what dept owns what rooms.
5. If in trouble with Architectural things > relax > be cool > open 3d PDF > be a great Architect in just 10 easy steps.
PS: of course I know GH clusters...but as they are they violate my rule N1: never walk the walk if no return is possible, he he. But assuming that David could resolve the return issue (sure he can) this is NOT the answer for my "proposal" for multiple Canvas - again like multiple Views in any CAD stuff these days. Just imagine clusters with some serious hierarchy depth > where am I ? what input comes from what output?
I'll be back with a chaotic case (Series in complete anarchy) in order to demonstrate the critical necessity for a visual Tree Manager/Viewer (a visual thing within the GH visual thing). For manager read : decomposer, composer, visual identifier (per data item/branch) tree re-mapper, anything actually.
more soon (and a in depth analysis about what a Tree Manager/Viewer should do - in an ideal world, that is)
Cheers, Peter
…
for this purpose. So, without paying attention to the video, this time, this is the synthesis of the process:1. generate 3d network from points and applying tensegrity physics via kangaroo:
2. option 1: generate surfaces from network using network fillet/patch tools from GeometryGym:
3. option 2: same as option 1, but this time the network is affected by the wooly paths script in order to create the 'tensioned' curves via attraction and then creating the surfaces with GeometryGym:
4. close-up:
The goal is to achieve "option 2" without using wooly paths so that the minimal surfaces are generated as the curve network is affected by kangaroo-driven tensegrity. I want the model to be a more 'real-time' simulation instead of generating the tensioned network and doing the surfaces as a post-process. I hope that explains my intention a bit more!
the wooly paths script I'm using is the "woolier paths" one or #2, I believe.
Thanks again! I hope you can help me, and sorry for any confusions!…
m, mind). These 2 are (a) the advent of large scale 3d printing and (b) the adoption of a totally new way to fabricate carbon fiber items (I mean big things like load bearing structural members - blame Volkswagen and Boeing for that).
For instance and in a very small scale see this CF chair:
Or that:
All these mean that you/we could consider possible to design large scale things (like a "monoblock" modular hangar where the roof is fused with the columns - exactly like the chair as above and/or your initial requirement - minus the ugly basement formation).
In the mean time get the new "divine" version (2 choices : either you or God decides things concerning the "bridges").
Until next update
1. TSplines 3.4. they don't give any preview (and pipe is EXTREMELY slow) whilst 3.5 they turn components red. Karma without any doubt. Beta 4 has more bugs than Madonna had lovers.
2. Choose "God" as the placement mode and observe that the main issue here is to "fuse" properly "bridges" that potentially clash (easy for TSplines).
3. Although random is the new trend in Architecture/Design (but trends come and go) ... controlling randomly AND properly geometry is more fuzzy than it appears on first sight ( for doing something that could(?) stand(?) any future critic, he he).
4. Rhino is actually a surface modeler ... meaning that stuff that CATIA/NX do are rather unthinkable especially concerning the "frozen" state of a polysurface (Smart Surface for those in the Microstation bandwagon). You'll see why I'm saying this when this definition starts to find the right route (for instance filleting complex stitched surfaces etc etc) . On the other hand various Rhino tools are not exposed to GH (VBA/C is needed).
More this weekend.
My mail is pfotiad0@remove this@hotmail.com
May the Force (the dark option) be with us, best, Peter …
to do once I figured out how you use only a small portion of each of my generated curves to make the 360 degree Loft surface. I had a huge AHA! moment when I realized the complete Loft surface really only needs a small portion of the generated curves rotated around to form a closed (except for top & bottom) surface. That is a major new insight for me and I appreciate you pointing it out.
I also tweaked the Twist angle parameter a bit so the resulting positive and negative Twist surfaces, when combined, yielded a result that was closer to my original shape. This is when I discovered something very interesting.
When I baked/exported the result using just one of the 2 twisted surfaces I got an STL file that had no errors, that 3D Builder was able to simplify from a 37 MB file to a 3 MB file, and that sliced A-OK. But, when I combined the left and right twisted surfaces, I was back with my same set of problems: the exported STL file had many errors, could not be fixed, and did not slice properly.
I went back to my original layout that uses the complete set of generated curves to create the Loft surface and found I got exactly the same results - using only one twisted surface worked fine, but nothing worked when the left and right twisted surfaces were combined. By nothing I mean I tried all the standard methods (GH Join and Sunion, Rhino Solid/Union, Join, etc.) What I think this means is that the Loft surface behaves the same, and apparently is the same, regardless if it is generated by rotating strips or by using complete closed curves.
Furthermore, I am guessing the problems with the combined/exported STL file made from both left and right twisted surfaces has to do with overlapping/coincident parts of each one - like the top & bottom planar surfaces and some of the wiggly parts.
If I am correct about this then it suggests to me that there is some sort of glitch in Rhino's STL Export function. This is surprising to me since I though an STL file only paid attention to the external shape of thngs,and did not know or care about any inside stuff. Of course this is all conjecture on my part, but at least for now seems it will be impossible for me to actually print the double-twisted geometry.…
Added by Birk Binnard at 3:52pm on September 23, 2016