things I need to keep in mind are that, 1) I'm the only tool guy on this project, and 2) I need to generate results in my application domain - and Rhino, Grasshopper and my own code are tools, not results. If I spend all my time developing tools (or learning how to develop tools) then we're never going to get across the finish line. I can perhaps take a longer view on my tool investment once I have the "core" functionality in place. But I'm not there yet.
I've mapped out the various algorithms I would use for each task of the toolset I'm developing. For example merging surfaces was supposed to simply involve intersection/split/cull/join. That intersection operations don't always return complete, accurate and usable results throws my plans into the air. Data flow programming of genetic algorithms fits my background of 30 years programming and 5 years of 3D design. Diving more deeply into the underlying math of B-rep geometry is a rabbit hole I didn't budget falling into.
You bring up other architectures like solid modeling and features. R/GH are just 2 of many, many tools I've looked at to achieve my goals. No single tool or ecosystem looks complete enough to meet all my needs. My prior stop on my quest was OnShape. I found much to appreciate there, but it's still VERY early in their development. (I personally think they are a decade away from having a solution worth investing in.) R/GH seems fairly mature, but I'm already hitting walls like this. There are always struggles and never an ideal solution.
Thanks for your insights,
- Bob…
Added by neobobkrause at 7:32am on September 2, 2016
it I must edit the contours that have buildings on them to create building pads under each building on the laser cut model. What I’ve done before is to edit them manually with ‘copy vertical->trim->join’ (attached images).
But this is a big manual operation especially when the building is on several contours.
So is there some way to get grasshopper to automate these actions? Just turning 10 clicks into 5 clicks would help me alot!
…
g? What can be done to speed up the process? Algorithmic Design Workshops is a platform created by ecoLogicStudio to engage these questions introducing novel parametric modeling techniques in the context of architecture and landscape design. Each event will be a opportunity for learning design techniques, testing new methods and debating their potential applications or evolution. Architects, Landscape architects, urban designers and students alike will find in the workshops a unique opportunity to improve their technical skills while confronting themselves with the most debated advanced design subjects.
This workshop, particularly suitable for beginner/intermediate users, offers a playful introduction to algorithmic and computational design with Grasshopper. The ambition is to generate 3 dimensional artificial landscapes based on the recognition of natural pattern formations (valleys, mountains, dunes, marshes, coral reefs, etc.), their subdivision in territories of occupation and the development of related path systems. The workshop will start from processing satellite images of natural formations and extracting patterns from them with the GH point set reconstruction tools. Applicants will than begin the process of generation of 3D architectural landscapes based on a series of structuring operations and negotiations with the project site. An evaluation process will than follow and will allow the recognition of inhabitable spaces, accessible slopes and ground movement volumes.
more information on:
http://algorithmicdesignworkshops.wordpress.com/2011/10/04/algorithmic-landscapes-gh-advanced-modeling-workshop-october-2011-ecologicstudio/…
d'applications.
Durée : 24 heures soient 3 jours
Public concerné
Utilisateurs souhaitant créer des modèles 3D pour la création d'images, de modèles d'usinage et de plans techniques 2D , une compréhension du système d'exploitation Windows est demandée. Niveau baccalauréat.
Moyens pédagogiques :
portable équipé de rhinoceros 5,0…
her bump on the road. I've evolved the original idea into something that remotely resembles this childish doodle:
That is, 3 different rows of panels with fixed heights but random widths. Each panel will be perforated in voronoi patterns that vary according to my original sun intensity diagram, but I'm thinking they'll have a fixed frame width and a small gap between them, kinda like this other childish doodle:
I've mastered the method of turning my original diagram into a voronoi panel that's denser where the sun hits harder thanks to Vicente's method. But it gives the voronoi frames a width by scaling each cell by .9, but that doesn't yield frames with constant width... which is fine for my 3D, but I wanna use the files to draw diagrams for laser cutting and actual building of the panels, so I guess I can't be too precise there.
Again thanks for all the useful (and funny) input! :)
…
e parallel lines:
http://www.grasshopper3d.com/profiles/blogs/marching-cubes-curve-wr...
It's at least real code I could translate to my native Python, but I still don't know if it's even possible to solve the math to make things not bulge, as his gives the same result at Millipede:
If I join the four corners of the main box, those four bulges nicely disappear.
His field calculation code is pretty simple, just returning a single field value for a 3D test point input, for a single point or curve being considered, but I don't yet see how they add together to form an overall isosurface:
…
nd give it love.2. Everything else is to know the nature of the data and components. Data is all: numbers, formulas, colors, lists, branches, graphics, visual representation, connection between data, hierarchies, etc.3. Work, work and work.Have information is know about data, have knowledge is to know how the data is related with everything else and have wisdom is to have the right mental-programs to process data. And then there's the creativity, divergent thinking, ingenuity and talent that make the mental architecture not be something rigid. Then, to carry out algorithms, the mindset I usually follow is, I start with data/parameters to perform a design, and decompose the process into smaller processes that can manipulate. If I'm at a point where I do not know how to do, two things can happen, that I know what I have to do but can not, or not know how to do, the first is probably lack of knowledge aboud data or components, therefore, it is time to learn; and second, rethink the previous processes if I can avoid the problem, which often leads me to redo the whole algorithm, which is not allways bad.In short, delves into the data and components, so your mental program of execution will be more optimal if you know more about posibilities. And think in terms of process, not in terms of outcome. And work, work, work does the rest. There is no trick, just eager to learn. I did not start to understand that it was really the 3d until I began to learn programming, but this way I will advise you when you have confidence using grasshopper.Perhaps is not what you expected, but it all boils down to devote more hours. Grasshopper is easy to use and hard to learn.…
ithin an Urban context and taking into account the shading of the surrounding context, and we are testing the Ladybug Thermal Comfort Indices component. For what we understand there are two ways to take into account the Mean Radiant Temperature, you can either plug the meanRadiantTemperature_ or the solarRadiationPerHour_. According to the meanRadiantTemperature_ description it seems that if we are doing the calculation outside in the sun we mustn’t plug in anything and we must work only with the solarRadiationPerHour_ (as you also do in the example). Is it correct?
solarRadiationPerHour_ can be calculated in two ways, the first one is shown in your example and uses Ladybug_Radiation analysis component (Very clear thank you so much! : ) ) The other one uses the Ladybug_Sunpath Shading component and from the description is supposed to be more precise. And here are the other questions:
1) there is a parameter that takes into account vegetation, with which degree of detail should it be represented? 2D(silhouette) or 3D surface? Should we separate the trunk from the crown?
2) In this component we can also insert an albedo value. Is this value taken into account in the PET calculation and if yes, how?
3) In the Ladybug_Radiation Analysis component we can input a geometry at the ground level to be calculated and then place an analysis grid at 1.1 _disFromBase. Using Ladybug_Sunpath Shading, where should we place the geometry to be calculated and how can we place the analysis grid like in the other case?
We apologise for the long post!
Thank you very much for all your efforts!!…
rves that "intersect" a plane placed on Z=6 above the first circle. I did this to have a collection of points from which to choose 3 and make a 3pt-circle.
[this second circle "fits" the catenary at a certain height, that's what I wanted to do]
Maybe it's obtuse but anyway that's the way I managed it.. I then used the "intersection" of the top circle with the original catenary curve to "split" the catenary into 2 parts, I then "Rail Revolution" the first part of it around the axis of the original circle, using the circle as a "rail", and I get a Brep surface.
It is a "open brep" surface, so now i'm having the problem of managing it if I want to subdivide it with Isotrim or other commands to control the number of subdivisions.
Is there a better way to go about this?
I am attaching the file.
About the image, I checked my code about 10 times to understand why it has those "lines" every 1 meter in the Z, and they already appear in the "rail revolution" component when it is visible, but in the "brep components" I can see the individual points along the rail curve.
I think this is what might be causing the brep to surface problem, but for the life of me I can't understand why the rail is not smooth and is "divided" into the 7 points instead of just one smooth revolution...
Thanks! :)
…
, Engineer and Researcher from France with broad programming experience. He is the author of the City in 3D Rhinoceros plugin for creation of buildings according to geojson file and with real elevation. Guillaume already created a new component: "Address to Location". It enables getting latitude and longitude values for the given address:
2) Support of Bathymetry data: automatic creation of underwater (sea/river/lake floor) terrain. This feature is now available through new source_ input of the "Terrain generator" component. Here is an example of terrain of the Loihi underwater volcano, of the coast of Hawaii:
3) A new terrain source has been added: ALOS World 3D 30m. ALOS is a Japanese global terrain data. Gismo "Terrain Generator" component has been using SRTM 30m terrain data, which hasn't been global and was limited to -56 to +60 latitude range. With this addition, it is possible to switch between SRTM and ALOS World 3D 30m models with the use of source_ input.
4) 9 new components have been added:
"Address To Location" - finds latitude and longitude coordinates for the given address.
"XY To Location" - finds latitude and longitude coordinates for the given Rhino XY coordinates. "Location To XY" - vice versa from the previous component: finds Rhino XY coordinates for the given latitude longitude coordinates. "Z To Elevation" - finds elevation for particular Rhino point. "Rhino text to number" - convert numeric text from Rhino to grasshopper number. "Rhino unit to meters" - convert Rhino units to meters. "Deconstruct location" - deconstructs .epw location. "New Component Example" - this component explains how to make a new Gismo component, in case you are interested to make one. We welcome new developers, even if you contribute a single component to Gismo! "Support Gismo" - gives some suggestions on how to make Gismo better, how to improve it and support it.
5) Ladybug "Terrain Generator" component now supports all units, not only Meters. So any Gismo example file which uses this component, can now use Rhino units other than Meters as well. Thank you Antonello Di Nunzio for making this happen!!
Basically just forget about this yellow panel:
This panel is not valid anymore, so just use any unit you want.
6) A number of bugs have been fixed, reported in topics for the last couple of weeks. We would like to thank members in the community who invested their time in testing, finding these bugs and reporting them: Rafat Ahmed, Peter Zatko, Mathieu Venot, Abraham Yezioro, Rafael Alonso. Thank you guys!!! Apologies if we forgot to mention someone.
The version 0.0.2 can be downloaded from here:
https://github.com/stgeorges/gismo/zipball/master
And example files from here:
https://github.com/stgeorges/gismo/tree/master/examples
Any new suggestions, testing and bug reports are welcome!!…
Added by djordje to Gismo at 5:13pm on March 1, 2017