m rnd As New random(666)
Dim field As New gh_field
Dim crvlist As New list(Of curve)
For i As Integer = 1 To 100 Dim pc As New gh_pointcharge
pc.Charge = rnd.NextDouble
pc.Location = bx.PointAt(rnd.NextDouble, rnd.NextDouble, rnd.NextDouble)
field.Elements.Add(pc)
Next
For i As Integer = 1 To 500 Dim p As New point3d(bx.PointAt(rnd.NextDouble * 0.5 + 0.25, rnd.NextDouble * 0.5 + 0.25, rnd.NextDouble * 0.5 + 0.25))
Dim pts As point3dlist = field.SolveSteps(p, 0.1, 30, gh_differentialsolver.RungeKutta4)
Dim crv As nurbscurve = nurbscurve.CreateInterpolatedCurve(pts.ToArray, 3)
crvlist.add(crv)
Next
a = crvlist
…
will not be created in plugin folder of my Rhino 5 Beta as it does in Rhino 4 while it did in my last computer (pc,windows vista).
I copy/pasted the Grasshopper folder from Rhino 4 to Rhino 5 Plugin folder, but it seems like this folder is not functioning at all since when I drop any gh file for addons, like MeshEdit or Kangaroo or python, in the component folder, nothing new gets created in component ribbon.
Please let me know if you have any suggestion.
Thanks,
Naciem
…
ans to manipulate PC easily (I mean we have a couple of CNC routers... just no staff to run them... thanks middle management) Plus the Lexan is uncomfortably close to my tutors work (he using Correx). And Honestly unless it was sheet (rather then corrugated) then it wouldn't be the desired aesthetic.
I think if it was to change to PC then I would get rid of the nodes as we know them and just connect the PC to itself from the mid point of each line (fully realising the semi-monocoque style. This would forgo the acute angle annoyance.
I agree that the larger would lend itself to MERO style, but as it is with the extrusion being 4*3mm its tiny screws would drive me bonkers. I would use NX or something for a component based approach.
If it was going to take this to the next level then a rethink of materials etc would mean a more stable work flow/object/outcome, but now I'm past the point of no return (not as dramatic as that sounds). Although it does all seem to be falling apart at the last hurdle [dun dun dunnn!!] ;)
…
find a solution. At least it looks that way on my PC.
I lowered the number of decimal places to 1 (to save the time), and this is the closest result:
http://www.dodaj.rs/f/3Y/Ih/4QqtFuQy/proba.jpg
…
ld be by no means a general benchmark of all arrays and lists, but it would give an idea of where List<T> and where T[] might be more appropriate.
Here is how you could set this up: on my PC, with 1'000'000 arrays/lists constructions and 50 inner loops on each, "arrays vs. list" has about 1:2 speed relationship, and "array vs. unknown length list" 1:9. You can test on your system and change the tests, too. If you do, remember to build in release mode and "Run without debugging".
- Giulio
____________________
giulio@mcneel.com
McNeel Europe, Barcelona…
ane since you already are extruding in z direction.
then instead of difference component you can use trim solid component which in my PC from 8 seconds of the difference component goes down to 400ms.
cheers
alex…
urves in the curve parameter and used Sort list component to rearrange the curves in a new list according to their lengths making the shortest curve item '0' and second shortest curve item '1' etc.
I can imagine there are many approaches to this problem depending on additional factors. Hope that helps, sorry can't make an image.…
add another "trivial" constrain to the puzzle (for instance the PC sheets are 1.2*2.2m > meaning the obvious). This is addressable ONLY via the black bill (don't even think to use GH components for solving similar stuff).
3. One-off nodes are probably OK BUT for larger scales you'll need MERO type of approach > meaning assembly/component concepts > meaning dealing with instance Rhino definitions: blocks in plain English (don't even think to use GH components for solving similar stuff).
4. "Engulfing" type of strut extrusions are rather the best option (use aluminum in this case) > meaning profiles that can "wrap" the triangle content edge (be that "paper" or Lexan/PC).
5. The whole thing appears "easy" but on a pro level is rather quite challenging and obviously totally undo able without the black pill.
6. So: mesh relaxation <> adapter topology matters <> pack issues <> component design <> triangle content design <> cost <> you named it (for <> read "interact").
Such a "simple" case ... eh? …
=mostaphaRoudsari&fork=hydra_1&id=Remove_Ladybug_and_Honeybee&slide=0&scale=1&offset=0,0
Restart my pc
Reinstall OpenStudio in C:\ProgramFiles
Reinstal Ladybug and Honeybee
still same error message
…
is on the right on my screen while my real hand is already gone to the left.
Do you have a 0 latency answer on your laptop? It may come from my pc.
Thanks again Andy.
…