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
the slider? They could be less or more? Actually I have data coming from changing values of a slider but defininig 10 configuration and I want to stream the 10 configuration data on 10 different sheet of the same file (i guess it is possible with your tool). I need to associate a different sheet number from 1 to 10 to each configuration and input it the Sheet input right? Thank you.
Francesco
…
he implementation of the Component more autonomous without the need for user intervention.
At present you have 1 main input for the data to be placed on a single sheet as per the input and the option to add more sheets manually.
Would it be possible to alter this to have a Data input and a Sheet Name Input so that the Path Structure dictates which sheet gets what data and the optional Name input gets applied.
For example
{0;0;0}(N=10) is Range A1:A10 on Sheet 1
...
{0;0;9}(N=10) is Range J1:J10 on Sheet 1
{1;0;0}(N=10) is Range A1:A10 on Sheet 2
...
{1;0;9}(N=10) is Range J1:J10 on Sheet 2
etc.
I realise that this would have to be very particular, making sure that only Place Holder A has influence over what sheet is used If there is a distinction of multiple sheet names.
For Example if you had a list of:
{0}(N=10)
{1}(N=10)
{2}(N=10)
{3}(N=10)
Place holder A could either be sheets or Rows so it would have to only work when there was a corresponding Sheet Names List for {0}, {1}, {2} and {3}
At present I have to do this manually using Explode Tree etc. Whenever I expand on the conditions (different Draft or Heel) Then I have to increase all of the outputs for the components highlighted in Pink
…
x and min values for x,y,z and calculate energy for each optionand collect these results in excel sheet ...
option No. x y z Annual coiling demand(by DIva)
1 10 10 10
2 10 15 20
3 11 10 19
4 12 14 17
5 15 16 15
6 16 11 14
7 18 12 12
.
.
etc
Regards ...
hossam
Hossam.wefki@gmail.com…