as follows.
We have a grid which consists of a collection of columns, where each column consists of a list of points. You said flattening is out of the question, so we need to cull items from each list individually.
Let's say our culling pattern is KDDDKDD (repeat as needed). K = Keep, D = Ditch. If a column contains 18 points, the pattern needs to be repeated until it is 18 items long. In this case:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
K D D D K D D K D D D K D D K D D D
We can now cull each column, but they will all be culled in the same way. By shifting the pattern one more index for each column, we can cycle the culling.
The fix incidentally is to Shift the pattern PRIOR to repeating it. Then it works as expected:
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 2:49pm on October 2, 2013
not sure about my method used to obtain the result.I think is really complex; do you know a smart method to simplify all my equation?
thanks guys!! :D…
ge on top) of Sameer's definition he used:
{A;B} (i) > {A} (i)
Let's suppose that you have 5 curves selected in your definition. So you will have:
- Data with 5 Branches
- N=11 (as default value from Divide Curve)
- data structure (0;0) (0;1).....(0;4)
Here the question: WHY?? the points coming out from this Path Mapper belong to the fifth curve (and not the fourth, the third...etc.)?
Thanks a lot!…
he default for Rhino, degree=5 gives you smoother curves, but each control point matters less, degree=11 is the highest degree Rhino allows. Apart from 2, degrees tend to be odd rather than even, though Rhino supports both.
In addition to the degree and the control points, Nurbs curves have knots. A single knot is just a number, and the list of all knots is called the knot-vector of a curve. The number of knots depends on both the degree and the control-point count, and the spacing of the knots affects the shape of the curve a little bit. If there are <degree> knots with the same value, then the curve is somewhat discontinuous at that location which could manifest itself as a kink or as a clamped end-point. However it is not possible by just looking at the shape of a curve to say where stacked knots might be, but you can use the Rhino _List command to inspect all details of a Nurbs curve.…
NONE, in SIZING:PARAMETERS". I'm not sure of where to start in troubleshooting this. I've attached the file.
Thank you,
See the errors and warnings below:
{0;0;0}
0. Current document units is in Meters
1. Conversion to Meters will be applied = 1.000
2. [1 of 8] Writing simulation parameters...
3. [2 of 8] Writing context surfaces...
4. [2 of 8] Writing context surfaces...
5. [3 of 8] Writing geometry...
6. [4 of 8] Writing Electric Load Center - Generator specifications ...
7. [5 of 8] Writing materials and constructions...
8. [6 of 8] Writing schedules...
9. [7 of 8] Writing loads and ideal air system...
10. [8 of 8] Writing outputs...
11. ...
... idf file is successfully written to : R:\Green\SuRG\Building_Performance_Analysis\2016_analysis_studies\Energy_Analysis_Comparison\Honeybee_+_Ladybug\tutorial01\EnergyPlus\tutorial01.idf
12.
13. Analysis is running!...
14. ...
...
Done! Read below for errors and warnings:
15.
16. Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.31 11:39,IDD_Version 8.5.0
17.
18. ************* IDF Context for following error/warning message:
19.
20. ************* Note -- lines truncated at 300 characters, if necessary...
21.
22. ************* 24 Sizing:Parameters,
23.
24. ************* Only last 1 lines before error line shown.....
25.
26. ************* 25 None, !- Heating Sizing Factor
27.
28. ** Severe ** IP: IDF line~25 Invalid Number in Numeric Field#1 (Heating Sizing Factor), value=NONE, in SIZING:PARAMETERS
29.
30. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
31.
32. ** ~~~ ** Possible Invalid Numerics or other problems
33.
34. ** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
35.
36. ...Summary of Errors that led to program termination:
37.
38. ..... Reference severe error count=1
39.
40. ..... Last severe error=IP: IDF line~
, value=NONE, in SIZING:PARAMETERS
41.
42. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
43.
44. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
45.
46. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
47.
48. ************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
49.
50. ************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 9.34sec
51.…
}
0,3
{7}
1,2
{8}
1,3
{9}
2,3
{10}
0,1,2
{11}
0,1,3
{12}
0,2,3
{13}
1,2,3
{14}
0,1,2,3
I want it to be parametric so I can have it for any set of indexes
I have tried to solve it with points and then removing duplicate points but it's not helping much
any help is truly appreciated
…
I've attached a rh and ghx file. http://we.tl/ghsd0UTxji - wetransfer link. I'm guessing the trick is to correctly define the Range (R) / Domain in the Random component, so that the circles' radi can vary between the fixed and static domain of 10 or 12 or 14 or 18 or 20. Meaning that the radi can only be 10, 12, 14, 18 or 20 - and not, lets say.. 11, 13, 15, 16, 17 or 19 for that matter. Thanks in advance, i hope someone can figure it out, because i can't seem to find anything online about how to set up such as specific domain.
…
them into one solid).
By the reversed order of the Loft Curves, the SolidDifference is still not working when I trim the surface by a box1 which is scaled over the z axis. But it does work around the problem of the deleting curve number 13 or 11 or 5 or 4 or 0. Strange, strange strange..... Maybe something for David?
Is there an explanation why the reversed order of the lofting curves is working better?
Cheers,
Bas…