X, Y & Z parameters. At the moment 'Z' parameter is set to 0.
Now when i use a planar surface components it works well. But because i have Z parameter i need Edge surface component to work well. Edge surface gives me a funny shape, not like planar surface.
Essentially with Z parameter as 0, edge surface should look like planar surface, or not?
When i try edge surface with simple 4 points it works. The moment it gets relatively complex i do not get desired result.
All the points 1-26 in the curve were formed progressively in order i.e. 1, 2, 2...26 in GH not in Rhino.
What m'i doing wrong?
cheers
aB
…
e.
i have come as far as creating a mesh entirely in GH to my desired form. Could any-1 please help me with creating fenestrations / holes into this mesh in GH?...
I have been stuck with this since a week now...not able to find any solution to move ahead!
i have Tried Voronoi by converting this mesh in to surface...it doesn't really work on the mesh that i have created...
any-1 with some suggestions?
cheers
aB
…
in 10 minutes or so!
If you are interested to know about the process of putting the Ladybug together, what's going on right now and what's coming next, just check the workshop website for webcast information! Here: http://www.nrel.gov/buildings/2013_radiance_workshop.html
Cheers,
Mostapha…
below:
The comand prompt window (see attached image) seems to put -ad 1000 as default even if it seems to be set to 512 in grasshopper. In contrast to -ad, the modification of -ab to 3 has been taken into account. Have you set minimum values for RADparameters? If yes, would it be possible to force them to custom values?
Thanks in advance for your help
Best regards,
Aymeric…
oxes in the most efficient way within boundaries of object and follow the following constraints. The Goal: To fit 125 boxes in the most efficient way inside the total area. Starting Variables: (1) 40% of the Boxes need to be between 60 and 85MSQ. (2) 40% of the boxes need to be between 86 and 110MSQ.
(3) 20% of the boxes need to be between 111 and 125mSQ. The breakdown doesn’t have to be exact to give the script some flexibility. Meaning you can have 41% +39% +20% = 100%.
Constraints:
1. A total MAXIMUM area of approximately 1600M per layer.
2. A maximum of 8 layers for a total of 12,800M per layer. Optimization can make as little or as many as 8 layers vertical to accommodate all boxes. So if script can achieve with 3 levels great. If needed all 8 levels, that's fine too. However, pay attention to next constraint (#3).
3. Approximately 15% of that space on each layer is off limits. (internal area) (blue area in example script) and the shape of the boundary cannot be modified to accommodate box design resulting in jagged lines for the internal area.
4. All generated squares/rectangles must have at least 3m touching an outside border (The Green lines).
5. All boxes must also be touching minimum 1M of border of the blue line.
6. If the boxes generated go outside the green boundary, they must be fillet to maintain the straight lines of the green boundaries.
7. Get as many of the boxes as possible a view towards the dots.
Could any one provide me a method or a way to start, if there are any useful links, please share with me. Thank you!…
Boxes in the most efficient way within boundaries of object and follow the following constraints.
The Goal: To fit 125 boxes in the most efficient way inside the total area. Starting Variables:
(1) 40% of the Boxes need to be between 60 and 85MSQ. (2) 40% of the boxes need to be between 86 and 110MSQ.
(3) 20% of the boxes need to be between 111 and 125mSQ. The breakdown doesn’t have to be exact to give the script some flexibility. Meaning you can have 41% +39% +20% = 100%.
Constraints:
1. A total MAXIMUM area of approximately 1600M per layer.
2. A maximum of 8 layers for a total of 12,800M per layer. Optimization can make as little or as many as 8 layers vertical to accommodate all boxes. So if script can achieve with 3 levels great. If needed all 8 levels, that's fine too. However, pay attention to next constraint (#3).
3. Approximately 15% of that space on each layer is off limits. (internal area) (blue area in example script) and the shape of the boundary cannot be modified to accommodate box design resulting in jagged lines for the internal area.
4. All generated squares/rectangles must have at least 3m touching an outside border (The Green lines).
5. All boxes must also be touching minimum 1M of border of the blue line.
6. If the boxes generated go outside the green boundary, they must be fillet to maintain the straight lines of the green boundaries.
7. Get as many of the boxes as possible a view towards the dots.
Could any one provide me a method or a way to start, if there are any useful links, please share with me. Thank you!
…
re is my problem... I need to arrange Boxes in the most efficient way within boundaries of object and follow the following constraints.
The Goal: To fit 125 boxes in the most efficient way inside the total area. Starting Variables:
(1) 40% of the Boxes need to be between 60 and 85MSQ. (2) 40% of the boxes need to be between 86 and 110MSQ.
(3) 20% of the boxes need to be between 111 and 125mSQ. The breakdown doesn’t have to be exact to give the script some flexibility. Meaning you can have 41% +39% +20% = 100%.
Constraints:
1. A total MAXIMUM area of approximately 1600M per layer.
2. A maximum of 8 layers for a total of 12,800M per layer. Optimization can make as little or as many as 8 layers vertical to accommodate all boxes. So if script can achieve with 3 levels great. If needed all 8 levels, that's fine too. However, pay attention to next constraint (#3).
3. Approximately 15% of that space on each layer is off limits. (internal area) (blue area in example script) and the shape of the boundary cannot be modified to accommodate box design resulting in jagged lines for the internal area.
4. All generated squares/rectangles must have at least 3m touching an outside border (The Green lines).
5. All boxes must also be touching minimum 1M of border of the blue line.
6. If the boxes generated go outside the green boundary, they must be fillet to maintain the straight lines of the green boundaries.
7. Get as many of the boxes as possible a view towards the dots.
Could any one provide me a method or a way to start, if there are any useful links, please share with me. Thank you!
…
oCommonSDK, I modified a working C# component that does something similar (ReduceMesh, written by Andrew Heumann). Both scripts are attached.
Aside from changing the component name and eliminating the P parameter, I made two modifications to the script:1) changed line 87 from private void RunScript(Mesh M, double P, ref object A) to: private void RunScript(Mesh M, ref object A)2) changed line 93 from: Rhino.RhinoApp.RunScript("_-ReduceMesh _ReductionPercentage " + Convert.ToString(P) + " _Enter", false); to: Rhino.RhinoApp.RunScript("_-MatchMeshEdge " + " _Enter", false);When I run the ReduceMesh component, the mesh object I feed it gets baked, the ReduceMesh command is run, the temporary object is deleted, and the reduced mesh result is returned. (Thanks, Andrew).When I run the MatchMeshEdge component, the mesh object I feed it is baked, the MatchMeshEdge command is run, but the temporary object is not deleted and no result is returned. The runtime error reads: "Sequence contains no elements (line 0)". I have a feeling that the command line string I am handing to RunScript is incomplete. When I enter it manually on the Rhino command line I see that it wants a mesh and three parameters. Of course I can hit Enter to accept the default values, but when you invoke a command through RunScript do you have to supply all parameters regardless? Also, where would I find details on the argument types that the command wants? For example, the last parameter reads "RatchetMode=On" or "RatchetMode=Off". How do I know if the type is Bool or the literal string "On" or "Off"?I am a complete novice at this so any help you can provide would be greatly appreciated! …
correct:
- the right value in the 0. path {0;77} is the smallest one.
- right value in the 1. path {0;78} is the value which is closest to the chosen value in the preceding path
- ..and so on for {0;79} and {0;80}
but when the paths change their first level, the iteration should start from the beginning:
- right value in the 4. path {1;32} is the smallest one.
- right value in the 5. path {1;33} is the closest to the chosen one in {1;32}.
- right value in the 5. path {1;34} is the closest to the chosen one in {1;33}.
..to be continued.
..this is, what I want to achive in the VB code, I implemented at the beginning of the discussion.
..and this is how I designed the input-parameter of the VB-element:
if someone could help me .. super-great!
…
Mac due to its versatility , but given this new laptop will be using mainly on Rhino, GH , i have some doubts whether to switch to a window based laptop.
I have a look at some high-end window laptops, Dell Alienware for example, with same specs as MBP and found the price are even more expensive than MBP , about 10-15 %.
With the new Rhino 5 is coming , will Bootcamp be good and efficient enough to run Rhino, GH and some rendering programs?
From my experience i find Rhino and Gh run smoothly on Bootcamp , but never run those programs on window based laptop myself , it's impossible for me to know the differences.
Some say BootCamp only deliver 80% performance of the program , if it's true i would really consider switching to window based laptop.
Any suggestions?
and if you suggest me to switch , what brand should i go for ?
Thank you,
…