h has 8760 branches each containing 9 values. I want to reorganise it to 9 branches each containing 8760 values. This example takes over 5 minutes (I have a reasonable machine). In a real application I'd need to work with 200 branches containing 8760 values.
Does anyone know why grasshopper is so slow to do this? How do I make it quicker? - I think my code is efficient so do I need to script it?
Any advise appreciated.
John
(For context, this relates to climate based daylight modelling. I made an application in grasshopper to model and present the calculation results. I built it all around DIVA for Grasshopper but I'm moving over to Honeybee. DIVA outputs results organised as hours per point where as Honeybee outputs as points per hour. To start, I want to reorganise the Honeybee results to match DIVA so I can make a point to point swap. I'll develop it further from there.)
…
d 5000 stiffness it usually works quite well but some overlap. If you put it much higher than 5000, it freaks out and explodes.
2. In order to make the spring network, it must create a spring between every circle and every other circle. This is a lot of springs. With 121 initial points, you have 7260 springs! On my old laptop, anything more than 200 points runs very slow.
3. You can swap between random and gradient radii with the toggle. See the note about swapping between large radii in center vs small radii at center.
Random Radii Start
Random Radii End
Large Radii at Center Start
Large Radii at Center End
Small Radii at Center Start
Small Radii at Center End
…
d octopus - with karamba causing octopus to crash when running (I believe).
I happen to have visual studio installed; and it reports the following error once it crashes:
"Unhandled exception at 0x00007FF9ADB520B0 (karamba.dll) in Rhino.exe: Fatal program exit requested. occurred"
Attached is the definition file with baked geometry if this helps.
I am currently running Rhino 6 with the latest karamba build.
Details
I aim to create a parametric bridge model - optimising weight and deflection (structural) as well as proximity of 3 movable loads (architectural). The geometry creation is a bit complicated, however I do not think this can ever fail; as I have stress tested this.
The setup for octopus is as follows:
Inputs (for octopus and the parametric model)
Geom. creation (parametric model)
Karamba analysis
Outputs (one is non-karamba, the other two are karamba based)
After an arbitrary number of phenotypes generated (usually around 200), Rhino quits constantly.
I have double checked the following:
Octopus can run with just the inputs (a fake output is created to allow for octopus to run). It does not crash here.
Octopus can run with the inputs and the non-karamba outputs. It does not crash here
Octopus cannot run with the inputs and the karamba outputs. It crashes here
Octopus cannot run with the inputs and all outputs. It crashes here
I have also checked the following:
Geometry generation is built ruggedly (by setting parameter limits appropriately & testing extreme scenarios)
Octopus never receives any value to make it quit (see if statement at the end of karamba parameters)
Any help is appreciated, as I'm currently on a deadline for my thesis on this!
Best,
Alex…
Added by AB to Karamba3D at 9:47pm on March 19, 2018
curves and loft manually, but for some reason when I loft in grasshopper I end up with a 5 sided instead of 4 sided poly surface. I attached GH file along with rhino file. Essentially the curves that are getting lofted (several hundred pairs)Result if done one pair at a time in rhino after baking curves
....nice and 4 sided.Result when lofted with same settings in grasshopper (doing all pairs at once or one at a time):
weird lopsided 5 sided polysurface.ideal result will fit between cross sectional ribs like so: …
Rhino5 SR9. PT will not load unless you update.2- Download the PT installer (PanelingTools_2014_08_24_00.rhi) from: http://www.rhino3d.com/download/rhino/5.0/PanelingToolsV5/2- Double click the downloaded rhi file and follow the prompts to install.3- Next time you open Rhino and grasshopper, you should see the new version installed and loaded.4- The updated toolbars should be also installed. You might need to load using "ToolbarLayout" Rhino command.Documentation:There are comprehensive manuals available. Please make use of them.1- PT-Rhino: http://wiki.mcneel.com/_media/labs/panelingtools.pdf2- PT-GH: http://
wiki.mcneel.com/_media/labs/panelingtools4grasshopperprimer.pdf
New in this Release:--------------------
PT-Rhino:
1- All 2D and 3D Paneling commands, now pay attention to the attributes of the source module. Morphed geometry is no longer added to a new layer and is placed in the same layer as that of the source module(s).2- ptPanel3DCustomVariable with mean option: added support to use multiple start/end modules.3- ptPanel3DCustomVariable command with mean option: added support to use points as part of pattern.
4- Fixed history bugs to custom2d and custom3d variable commands.5- ptOffsetBorder: added bitmap and draft angle options.6- Added history support to ptGridSurface* commands.7- ptPlanarLips command is discontinued and is now replaced with the new ptTabs. The new command has "Distance" and "Recess" options to create tabs with a miter. It works with planar surfaces and polysurfaces.8- ptUnrollFaces: Many improvements and new options.9- Many other minor bug and crash fixes.PT-GH:1- Added anew component to morph variable 3D components using mean or tween method between matching curves, meshes or surfaces.2- Added the new ptOffsetGrid component of a grid.3- Updated the ptMorph2dVariable component to accept a tree structure.4- Fixed a few miscellaneous UI bugs and crashes.Feedback:As always, feedback is ve
ry much appreciated. Please post questions and reports to the following:1- Rhino discourse forum (http://discourse.mcneel.com/)2- PT forums (PT-Rhino: http://v5.rhino3d.com/group/panelingtools) and (PT-GH: http://www.grasshopper3d.com/group/panelingtools).3- Email tech (tech@mcneel.com) or reach me directly (rajaa@mcneel.com).Enjoy!Rajaa IssaRobert McNeel & Associates…
ved in a later call to SolveInstance. Whilst the code previously worked in previous versions, I seem to be getting a component exception thrown: "parent doesn't have a valid document". It still goes on to remove the component, so I know I'm getting the canvas correctly and my component is being picked up.
Here's what happens:
I suspect the latest release must 'do' something to the document objects after SolveInstance has finished doing its business, but I'm not quite sure what and I've spent most of today struggling to resolve it.
Here is a code snippet from the class:
private GH_Component myComponent; protected override void SolveInstance(IGH_DataAccess DA) { // Get data bool token = false; DA.GetData(0, ref token); // Make a new component instance if (!token) { // Get a 'construct point' component from its guid myComponent = (GH_Component)Instances.ComponentServer.EmitObject(new Guid("3581f42a-9592-4549-bd6b-1c0fc39d067b")); // Add the component to the canvas OnPingDocument().AddObject(myComponent, false); myComponent.Attributes.Pivot = new PointF(200, 200); } // Delete the stored component else { OnPingDocument().RemoveObject(myComponent, false); return;
}
}
I wonder if anyone is having the same problem, although I suspect this may a question for you David - sorry!
Find attached.
Many thanks,
John.…
's work or some other examples in our forum:
LaN shelling
LaN shelling+WB
T-Splines
Kangaroo relaxtion
So can someone tell me how to do the relaxation?
Kangaroo? But most of the example works just with open mesh/brep.
Is it possible to relax a closed brep surface with kangaroo?????
Thanks!!!!
…
floorplate perimeter curve, breaking this into several points and then attempting to find the closest analysis value from DIVA.
Once the closest analysis point is found (no problem here), I am planning to take the VALUE of the same point and use it to modify the move/modify the floorplate points.
However, I'm having issues pulling the closest analysis values from the entire list of analysis points... I'm getting something, but the values are not correct or in the right order. It's a mess.
RED = DIVA based points / info
BLUE = RHINO geometry / points.
I suspect I'm messing up in splitting/sorting/dispatching the 'closest points' from the complete list of DIVA points. Hard to see, but the analysis points are all in the range of ±900 on the nearest side... and the blue 'selected values' are coming back at ±200. They should be the same as the nearest analysis value!
Help?!…
en it become shorter and shorter towards the end where they come together to the point they are like 5' tall. Also, I want the widest part to bend away from each other, start to come together towards the middle and then once past the middle they start to bend towards each other to the point the are touching and becoming one at the end where they meet.
I am a novice at best, I have tried several different methods and watch many tutorials with no luck on making this work. My biggest issue is with the bending.
What I did was draw my "fins" profile with curves and joined them so it was all one curve, then brought that curve into GH and arrayed it along an angled line so that I got the spacing I was looking for. I then extruded these shapes but they all extrude the same height. I don't know how I can go in and pick out one of the shapes to then start to manipulate it to bend how I'd like. I could possibly do extrude along a curve but then I would have to draw all the curves in and it ends up not looking concentric like I know grasshopper can do and I am having an issue that it twists. My idea was to get one side done and then just mirror the whole thing.Any help would be great, maybe I don't know a command, maybe I'm doing it in the wrong order (both likely) but I just don't know
Thanks in advance. I have attached my GH file with "fin" profile I am trying to use attached. I also attached two sketches, one shows the profile of the fin again, and the other shows the over all concept incase you have no idea what I was saying above…
Added by Katelynn Tate at 7:18am on November 24, 2015
tion) which would amount to -at a rough guess based on your image- about 1000 genes. I'm not sure how well Galapagos will be able to deal with such an amount (ironically the biggest problem will probably be the interface, not the solver algorithm).
The main theoretical problem I see is the fitness function definition for this. It won't be good enough to count intersections and minimize those. Reason being is that the number of intersections is an integer (it doesn't vary smoothly) and as such there's no 'selection pressure' towards better solutions. If you start with a setup like this:
it would have a 'fitness' of 2. We'd like to move these two shapes apart but even if we move them a large distance in the correct direction, we still have a fitness of 2:
It seems like a more useful metric would be the area of the overlap, at least then when leaves move apart, the fitness value will change, which allows the algorithm to make an informed decision.
Computing curve region intersections and areas will be a very intense step, making the whole process even slower than it already is. If I had to do this, I'd first try and tackle this using pixels, as computers are very good at dealing quickly with them. You could draw an image of all the shapes, drawing them each in a transparent black. Then, when two shapes overlap, the resulting pixel will be darker than the fill. If three shapes overlap it will be darker still. Then, once you've created the image, you could all the pixels and compute a value based on how many dark pixels there are.
This can probably be done in a reasonably low resolution, but you'd need to write some code to create and analyse the images.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…