and B inputs. This gives the odd results. I replaced the B Panel with an integer slider and the Pow component works properly.
When I use a Panel for B I get the following results (A panel is 10):
B=0 R=10
B=1 R=100
B=2 R=10,000
B=3 R=100,000,000…
Added by Steven Hall at 7:38pm on September 7, 2010
earch Founder ofPachube.com and CEO of Connected Environments LtdBillie Faircloth KieranTimberlake Research DirectorCraig Schwitter & Gijs Libourel Buro Happold + Adaptive Building Initiative
Lisa Amini IBM's Smarter City Lab Dublin, LeaderMette Ramsgaard Thomsen Head of the Center for Information Technology and Architecture (CITA), Denmark
Additional speakers for the Talkshop day, including panel sessions and workshop reviews, will be posted to the website soon.
For more information, click here.
We are also very pleased to announce the launch of our new website at www.smartgeometry.org. It is a soft launch, meaning we are still adding new features to the page. However, Workshop Clusters are setting up their online homes for use before and during our workshops, and we'll be premiering all sorts of new features and content over the build-up to sg2011.
Come check it out to see how things are developing!…
What are B and C supposed to be? I mean, they have to resolve to actual numbers.
So given the tree:
{0} [0;1;2;3]
{1} [0;1;2;3]
{2} [0;1;2;3]
{3} [0;1;2;3]
What is it you're after?
Added by David Rutten at 8:59am on October 21, 2017
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