4, 3, 7, 7, 7, 8
would need to be
5, 6, 7, 8, 4, 3, 7, 8
ideas?
current workaround (kangaroo dupPt component) removes all duplicates from list, tho does maintain order.
thx…
me. But if min = 5 and max = 12, then the range will be (12-5) = 7.
If you have only a fixed number of values, why not use a Value List to encode those?
You can still use a slider to select a value out of a list of presets, but the UI of the ValueList is more friendly, especially if the list of presets isn't particularly continuous. You can extend a single ValueList to have all 12 preset date+time combos as well.
Sliders values can be post-processed using an expression. For example you could add the 'x*3' expression to a slider, and then the value 0, 1, 2, 3, ... would be mapped to 0, 3, 6, 9, ...…
Added by David Rutten at 5:30am on January 21, 2016
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014
} (N=11) {0;1} (N=11) {0;2}(N = 11) {0;3}(N = 11) {0;4}(N = 11)
2. I run the Points that are coming out from the Divide Curve Components through the Path Mapper components with this definition:
{A;B} (i) > {A} (i)
3. I run data coming out from Path Mapper component through:
a) Parameter Viewer component and the result is:
{0} N=11 (data with 1 branches)
b) Point > Panel and the result is:
collection of 11 point (N=11) which is the exactly the same as the collection of point belonging to {0;4} (N = 11).
So, here is the question:
why the collection of points coming out from the Path Mapper {A;B} (i) > {A} (i) component is the same as the collection of points belonging to the curve {0;4}(N = 11) ?
Anyway ... It 's the first time I ask a question here... so I would like to thank you for what you do with your work! Thank you! You are really great!…
this, you'll have no horizontal force at the roller, but you will have it at the pinned support. If you wouldn't, then the structure will be displaced.
Usually, in 2 dimensional structures, if you want to know if an articulated structure is isostatic (as opposed to hyperstatic, which is what you have right now) is to use the following formula:
b+c-2·n=0;
b being the number of bars, c the number of constraints you have and n the number of nodes. In your case: b=19, c=3 (displacements constrained in X, Z at your pinned support and only constrained in Z at your roller support) and n=11, so: 19+3-2·11=0.
I recommend you to download the app SW Truss, as it's very useful to check your results instantly.…
)
3. KeyError(1417,)
4. KeyError(1417,)
5. KeyError(1417,)
6. KeyError(1417,)
7. KeyError(1417,)
8. KeyError(1417,)
9. KeyError(1417,)
10. KeyError(1417,)
11.......
i tried different weather file but also same result. it seems i have same problem. the file am working on is the radiation file i took from the examples . whats seems to be the problem?
thank you for your time…
a specific domain, for example:
0.) 0 to 1 -----> 11 random values from 0 to 1 (0.245,0.678,0.36,0.78,.28,0.18........)
1.) 1 to 2 -----> 11 random values from 1 to 2 (1.26,1.36,1.01,1.68,1.26,1.96.........)
3.) 2 to 3 -----> 11 random values from 2 to 3 (2.96,2.45,2.78,2.56,2.98,2.10..........)
4.) 3 to 4 and so on where I have a data set containing 11 paths with 11 values and the values fall within the specific domain.
Like my post above I have the correct path but I need to feed it the correct seed to get different values for each number. I tried grafting a series similar to the last post but it scrambles my data. Thanks so much for the help!
…