t "AddMesh" command.
On a related note, does anyone know how to modify an existing Plankton Mesh to get a valid new one in Python? For example, I fed a Plankton mesh called "PMesh" in to a Python script component with the following code:
PMesh.Vertices.Add(0, 0, 0)
PMesh.Vertices.Add(20, 0, 0)
PMesh.Vertices.Add(20, 20, 0)
PMesh.Vertices.Add(0, 20, 0)
PMesh.Faces.AddFace(0, 1, 2, 3)
The resulting Plankton mesh has the new vertices, but the face doesn't show up. Do I have to add something to the half-edge lists as well?
Thanks,
Dave…
ld go
Slider at 1 -> 1°, 2°, 3°.
Slider at 2 -> 2°, 4°, 6°
Slider at 3, etc.
And when the angle was too much that it surpassed 90 before connecting the 20 points, that line was not created. Maybe using a series instead of a range...mmm
Everything helps, thanks
…
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!
…
could accomplish this by adding something like '5.0 + Slider * 3.0' into the expression field... (and having an integer slider with domain 0 to 6).
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 10:19am on February 24, 2011
ut at this point in the quarter, I don't have time to learn to do this properly. I'll definitely have to come back to it though, as I'd like to become more proficient. Thank you for the help, though. I'll have plenty to dig through when I get back to it.…
ber of mesh vertices is defined as (precision_+1)^2.So if you would like to have its beam, diffuse and ground-reflected components as well, that means 3 * 8760 values per single point.Example: if you set your precision_ input to 20, the number of values would be a couple of millions:
(20+1)^2 * 8760 * 3 = 11 589 480 hourly values
Check the attached definition below. The outputs that you need are: "Ebeam", "Ediffuse", "Eground".They contain annual hourly values for each tilt and azimuth combination (that's what upper mesh vertices represent) in a data tree.…
l my students they can do anything. However, when one of them comes to me and wants to model a dual snub hexpropello dodecahedron here, I know I'll need help. This student is an exceptional learner, though. Most students don't even think to ask that question. We've got 3 months to get it. I hope we can get there.
How hard of a task do you think it actually is?
If we are completely out of our league, we will content ourselves with the platonic solids.
With the program :),
Judson …