hopper concepts and Parametric design. Design professionals from all industries are welcomed. Rhino intermediate level is required to attend this class. You will need to bring a PC laptop with Rhino 5.0 and latest Grasshopper installed.
Registration already started! Limited seats available.
To register:http://www.akiyomatsuoka.com/#!rhino-training-schedule/con8…
e any simple way of getting my hands on the values of the parameters for the Pareto-front configurations ? For the moment I'm dealing with them by Copy-Pasting the list of data on a panel...
2. The data is given like a % of the parameters' sliders. Can't we get the slider values directly ?
3. Is there an easy way to view the shapes on Rhino while "travelling" on the Pareto-front ? I was thinking of clicking on the Octopus Pareto-front shape (line or surface) while having the corresponding parameters configurations (thus shape) on Grasshopper (and Rhino).
4. Finally, is it just my PC or why can't we see the shapes evolving while the algorithms is processing ?
Those features might be coming in the next versions of Octopus but still, if you have any idea of how you would deal with my questions for now...
Thanks in advance
Thomas…
rt, setup material qualities and run it. It calculates for a few seconds then it crashes Rhino. I have not done any work in the grasshopper version. I found that if I turn OFF ray tracing completely it will run to an answer. I have attached my test file. This is as far as I have gotten with learning Pachyderm.
Computer #2- On my other PC when I try to load Pachyderm into the system it does not appear in Rhino and Grasshopper does not load. I have to un-install Pachyderm from the Control Panel to get Grasshopper to even work. I have tried un-installing Rhino completely, re-installing it, then installing Pachyderm to no avail. Same problem remains. Is there some kind of a previous residual from a previous Pachyderm installation that is preventing it from installing properly? I have spent hours on this single problem and am flummoxed.…
rk for Rhino, this is a first go at a very simple tool to get an idea of how fast different computers are at performing the sort of calculations used in Kangaroo, with the aim of informing those buying or upgrading their machines.
If you could take a couple of minutes to download and run this definition (after closing other running applications), then post here the result and your PC specs, hopefully we can start building a basic picture of what effect different hardware really has on the speed Kangaroo runs.
Most of the information can be found in the System page of Control Panel.
RAM speed can be checked in your BIOS, or with a tool like CPU-Z (note that the reported frequency from this should be doubled to get the actual RAM speed rating - eg if the frequency is 800MHz you should write DDR3-1600. It's confusing I know - see some discussion of this here), or by searching online for the specs of your PC model number.
This definition is purely testing the speed of the internal physics calculation, not display, so graphics-cards are irrelevant.
For now this is just to get a single general measure of overall Kangaroo speed, but it might also be interesting later to run a variety of tests to see how the speed varies with the size and complexity of simulation.
Of course a way of benchmarking general Grasshopper performance would be very nice to have as well, but would involve a lot more variables, and I'd be interested if anyone has ideas about how that could work.
Note - I posted a couple of versions of this earlier with various errors that were causing incorrect results. If you downloaded the earlier KangaMark01.gh or KangaMark02.gh file, please disregard that and any results from it and use the one posted here below:…
t, and it worked great!I can already see some of the nice benefits of its usage. With the Google Earth component, you made a quite a remarkable addition to the Ladybug set of components! Keep up this great work!
Just as a mention: I am attaching a screenshot of two new components:The first one: "Terrain analysis" performs a couple of terrain analysis types, and the second one: "Flow paths" performing the water flow analysis.Screenshot example of both is given below:
It would be nice if your Terrain Generator component could benefit from using these two new ones.In order to do that, Terrain Generator would have to output the terrain in a form of surface as well. My modest advice would be to add the "type_" input, which will determine whether the "terrain" output is a mesh, or a surface. This will make it consistent with Terrain Generator 2 component.To create the terrain surface from a grid of points, use the NurbsSurface.CreateThroughPoints method:
import Rhino as rcuDegree = vDegree = 3uClosed = vClosed = FalseterrainSurface = rc.Geometry.NurbsSurface.CreateThroughPoints(pts, numberOfPtsIn_vDirection, numberOfPtsIn_uDirection, uDegree, vDegree, uClosed, vClosed)
Of course this is just a suggestion, I am not imposing anything.…
I am not knowledgeable about google maps nor google maps api, but from what I read the two components will definitely show a bit different results due to different topography sources.If it is judging by this 2010 article, your Terrain Generator component offers much higher precisions for USA. Precision goes up to a couple of meters, which is amazing!!On the global scale it offers either SRTM 1 or 3 arc-second data or 30 arc-second GLOBE data. Again this is from the mentioned article, I couldn't find this information by searching the Google Maps website.Terrain Generator 2 component always uses SRTM 1 arc-second data from opentopography.org, and it is limited to 60 degrees north and does not have data for Antarctica. It does not come with satellite image either which is another very convenient feature that you have!I couldn't find information about the allowed radius provided by the Google maps api free account. I limited the "radius_" input to 100 000 meters, even though opentopography.org provides more than that (I successfully downloaded 300 000, but Rhino 5 was not able to create a topography on my PC from such a large amount of data).Even though I couldn't compare the results from two components, by looking at your upper example_LB_terrain_generator.gh definition: set the "I" input of "Surface from points" component to True. In this way the surface will be interpolated through points, which is what we want.
Again thank you for the permission, and I look forward seeing those high precision topography that Google maps offers!!…
buildings_trees_streets.gh or color_the_buildings.gh. I think the reason why you had upper problem may have been fixed.
2) Ok, glad it worked! With my prehistoric PC, I sometimes need to leave it turned on all night long so that OSM 3D component can create buildings over a couple of hours.
3) I checked the location now. It seems that Paris in general is very poorly documented in openstreetmap.org when it comes to 3d data (having some of the following keys: height, min_height, building:levels...). But maybe this may be able to be somewhat improved by using "randomHeightRange_" input of "OSM 3D". The way you are doing it now manually with random extruding shapes. Still I may need your help on this, with testing.…
Added by djordje to Gismo at 10:06am on February 11, 2017
nstalling of 3 previous versions of Ladybird and Honeybee but nothing different happened. This was all happening on a desktop PC running windows 10 and with a wired connection to the internet router (via a switch). I then tried installing Ladybug and Honeybee on a MacBook Pro running Windows 7 on bootcamp. This computer was wirellesly connected to the same router. The installation of the latest version was very smooth and all the right files of the right sizes appeared without any problem on the first import of Honeybee-Honeybee. I then copied the files over to the other computer. Solved.
1. good thing I didn't know that as I wouldn't have kept on trying to resolve it!
2. Ok, sticking with it - besides I would hate miss out on such a major release!
3. Makes sense.
4. ok, I thought that that was the main file because of the EP in the title - I now have them both anyway.
5. Now that you say this when I click on the file in github and download it from the view raw link then I do get the right file size. But when I have been trying to download it directly from the root folder (i.e.Honeybee/resources) with "save link as" then I get the 36kB. Could it be that Honeybee_Honeybee was doing something similar?
Many thanks again to both of you - great work out there!
best,
Alex…
picture:
... and on a PC without anything attached to the serial port. When you open the port, start the read component and its timer, do you then get a stream of <empty> values in the log output? (hmmm... I suppose that's only reasonable - but still, you are also seeing this?)
I suppose that, because of the mutually exclusive behavior of both the spider and grasshopper (i.e. only one at a time can access the COM port), we can deduce that we are listening on the correct port.
Am I listening on the correct pin (if such a notion makes sense at all)? If I look back to the spider software, I see that 9 channels are listed and that it's only the measured value on channel 0 that changes when I press the load cell. Channels 1, 2, and 3 report OVERFLOW; 4, 5, 6, and 7 are pretty much constant at 0.000 to 0.005 V; and channel 8 says FFFF. I do not know how things like that work so I do not know if they reflect reading from the 9 pins on the D-sub 9 connector.
As for your BTW question: no, I don't need to record all of the sensor values. I suppose that the Out value on the Read component will always reflect the most current value and that's all that I need to get on with life. In the end, the idea is that we have 4 load cells in the 4 corners of a plate onto which a vertical pipe is fixed. Loads are then put on the top end of the pipe and we'll have to visualize both direction and magnitude of the bending moment that is calculated from the compression - tension readings from the load cells... We've done this on a scaled model and streamed load cell information into MatLab. Now we'll have to use a different datalogger and I was hoping to be able to do the post processing in Rhino.
wim…