ap value = True
Shift List = 1 --> (B,C,D,A)
Shift List = 2 --> (C,D,A,B)
You can also use negative values.
Shift List = -1 --> (A,B,C)
Shift List = -2 --> (A,B)
and with Wrap = True
Shift List = -1 --> (D,A,B,C)
Shift List = -2 --> (C,D,A,B)
The most useful Shift List action I use is to either get rid of the first or last item in a list and sometimes both.
Shift list = -1 --> (A,B,C) Shift list = 1 --> (B,C)
In the example posted above you are creating a shift list value equal to its location along the curve. The first section = 0 doesn't get shifted, the second section gets a shift = 1, third = 2, forth = 3 and because the wrap value is set to true the fifth section gets back to 0, sixth = 1 etc etc. creating the twisting effect.
The "one more stupid question" answer is Mass Addition. You will find the component on the Math tab or you can type it into the Keyword search feature (by double clicking the canvas). This component has two outputs a total amount for each list and a partial set of results giving:
List (3,6,9,12)
{0} = 3
{1} = 3+6 = 9
{2} = 3+6+9 = 18
{3} = 3+6+9+12 = 30…
e a list of coordinates which I need to sort in groups as per a series of numbers in another list. Both are txt files which I'm reading to bring a series of points in but those points are generated with a corresponding index.
Of course the lists are not sorted in any way, but the numbers are corresponding so it looks like a series of 9, 6, 7, 2, 8, 0, 9, 5, 6, 4, 2, 3, 8, 5, 5, 6, 9, 4 in one file( and series of (X, Y, Z) coordinates in the other.
The question is how can I make it to sort the list and then split it per index... if it is possible... or should I just do this in excel and bring clean lists in?
My idea, if it works, is use the series of points to generate paths and work with them.
I'll attach the lists just if it helps making a clear idea.
Any advice will be very welcome.…
1) to each length. For example you have a length of ten and you create a domain from 9 to 11. later you want to group all lines by as less as possible domains.
If you have a look to the image...you see 6 lines and their red dotted ranges. to group them by the domain of 3 and 5 would be the best result with the less domains. (here 2)
if you would use the domain of line 0,1 or 3 you could not include line 4 and you would have 3 instead of just 2 groups.....
later on it is important for me to group as much as possible lines in less as possible domains.
I hope this is somehow understandable.…
Added by horst Becker at 11:15am on November 2, 2013
vector * number
8. number * point
9. point * number
10. complex * complex
11. colour * colour
12. colour * number
13. number * colour
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 10:39pm on November 12, 2010
d sequentially.
In your case, your question is a bit vague: you divide each circle into 4 points, so if you were to connect all your points horizontally, you would end up with 9 horizontal curves (3 for each circle) and 12 verticals (3 for each circle again). But you mention only 3 & 4 curves. Is this what you want the surface to look like (Blue Lines)?
…
ld be the best UI.
I think difference is made by 'Slider = 10' vs 'Slider = 10.000' more than by simple input/component initialization so, why to stop when it could be even more powerful?
Slider = 0 To 5 --- Slider in [0, 5]
Slider = {3; 0 To 5}
Slider = {3;0;5}
Slider = 3;0;5
Slider = 3 0:5
Slider = 3,0,5
Slider = 3 0 5 --- Value and range (min max)
3 0.0 5 --- 3.0 0.0 5.0
3 0 5.0 --- 3.0 0.0 5.0
3.0 0 5 --- 3.0 0.0 5.0
-1 0 5 --- 0 0 5 (-1 -1 5)
6 0 5 --- 5 0 5 (6 0 6)
Slider = 0:2:6 --- Even numbers: 0, 2, 4, 6.
Slider = 1:2:7 --- Odd numbers: 1, 3, 5, 7.
0:2:5 --- 0:2:4 (or 0:2:6)
3:2:8 --- 3:2:7 (or 3:2:9)
3 1:2:7 --- 1 3 5 7 (value 3)
Bang! = 7 --- 7 outputs
Merge = 5 --- 5 inputs
What's your opinion about Bang! = 7? As it's setting number of inputs, should it use different format? Bang! 7? Bang! (7)? Bang! i7?
+ * - / \ % ^ & | ! = > --- Addition, Multiplication, Subtraction, Division, Integer Division, Modulus, Power, AND, OR, NOT, Larger than, &c.
= could be a problem.
\ Integer division or Set difference?
! could be NOT but also Factorial.
| could mean intersection.
& could mean concatenate.
1+ --- Addition: input A = 1
2* --- Multiplication: input A = 2
+{0,1,1} --- Addition: input B = {0,1,1}
0-, 1/, 2^, 10^, e^ have their own components
Flatten = {7} or Flatten = 7 --- Input P = {7} (off-topic: Why can’t P be a list?)
Pt = {1, 2, 3} --- Point XYZ, X = 1, Y = 2, Z = 3.
Swatch = 129,239,231 (102)
Swatch = 129 139 231 102
F2 = "x^2+y"
"List Length" and "List Insert" don't work properly: "Value List" is choosen. Why? What's the reason to this choice? Well, I'd like to know how the whole thing (search by keywords) works, David.
Name and nickname can be now used as keywords. "Larger" works for ">" but "greater" doesn't. Could it be improved? Could synonyms be used? Could a short description even be used (I know this could be a bit weird)?
more than --- >
more or less --- Similarity
more less --- Similarity
red green --- Sets.List components should be showed
lightning --- Split Tree
What about use Curve.Analysis or Math.Boolean to display those Tab.Panel components? Param, Math, Sets, Vector? Primitive, Special, Util? Tab, Panel, and Tab.Panel as keywords.
At the moment that I write this, I check that ignoring accents in keywords has almost been included (0.8.0009): p`anel, pañel, pánel --- panel (almost)
Shouldn’t 'Dom2' work for Dom²?
What about nested search? You type some keywords (say 'Params' or 'Params.Geometry', or 'red green', or 'lst') and then you make a fine-tunning search over previous results/keywords. Tab.Panel and/or nested geometry could be useful when search by plug-in is desired or when you want to search among .ghuser components (first 'ghuser' or 'Extra.MyPlugIn' or 'lst' keyword and then fine-tunning, specific, search).
Is 'list length' performing this nested search right now ('lst' > 'length')? Anyway, I am thinking about UI (graphical) changes; successive searches.
As I said, description (and even words from the help info) could be used to search. What about "some kind of tags"? I mean that if 'list l' to finally choose List Length has been used for a while, that could be learned. Eventually, an XML file could store these tags, so you could even edit them. That could implement description, name, nickname, help info, Tab.Panel, .ghuser, synonyms (lots of them), tags/shortcuts or wathever.
How could flatten/graft/reverse be used? Initialize graft+Simplify or graft+Bang! could be really useful.
What about expressions? I don't how could it be done properly: would Slider = x^2 (expression) work? I mean, aren't expressions parsed when initializing?
Is Panel somehow doing this? 'panel = wathever' always suppose that wathever is a string, so you can't use 'panel = <pi>'. Sets.Strings components also do this.
I've been about to write several paragraphs about height/width (resizable components: Panel, Graph Mapper, Slider, &c.), input/output names (Scripts, F components; or any component with editable input/output names), orientation (Scribble), type hint and access option, nickname, &c. but, to sum up: being able to set any property when initializing would be really useful. I'd like to know the best choice of syntax but I'm sure that, David, you're closer to the answer. What do you think about this?
Slider: 3 0 5 "MySlider" "Slider^2"
Panel: "This is the content" "This is the title"
VB: "N" List Integer 7 "r" Item Double
Addition: A 1 B 2
I guess that any unified syntax would be elegant and useful, but additional ad hoc syntax (per component) could be even better (cleaner).
What about use lists of values? I'm not sure about format: panel = ("Hello", "Bonjour", "Hola")? If any valid format/syntax is found, maybe more sophisticated fetaures could be achieved: panel = {0;0} ("A", "B", "C") {0;1} ("1", "2", "3") How would you like this to be implemented?
There is a much simpler and interesting feature that would be useful, in my opinion: being able to initialize more than one component. I mean say 7xSlider = 10.0 and get 7 sliders and I also mean multiline (multi-component) initialization: Ctrl+Intro when you want to start a new line and Intro (or even some Accept/Cancel buttons when you activate multiline mode) to initialize (every line/component), for example. I mean:
3 x Slider = 1
Panel
Mass addition
Panel
And the whole bunch of components that were in mind (pre-thinked definition) is initialized. It speeds up the workflow, making more dynamic to add components that are only available via the drop-down panels.
Should this multiplier be something like a text box adjacent to search field more than '7x'?
These are some of my thoughts about intitializing. Please let me know your opinion :]
…
fused now because I'd like to use brute-force instead of genetic/swarm algorithms. I am worried about fitness landscape and local extremes with my variables. On the other hand Colibri Iterator would compute millions of combinations in my case.
I'd like to use Colibri brute force+Design Explorer to explore different solutions. I am not sure how many combinations there would be but I assume that up to 10^7. That is a lot of data to compute and look through. Probably impossible to do.
I looked into 3rd example on Design Explorer page (the building one) which is pretty close to what i want to do. As far as i understand the graph, there are 9 variables. Each has different domain. My calculation for number of combinations (going from left to right - from 'elevator width' to 'solid wall amount') is 3*5*5*10*6*4*10*50. That is 72.000.000 combinations. On design explorer page there are around 250 solutions. I probably do not understand something or there is a way to filter data somehow.
My questions are - Is it even possible for Colibri Iterator to go through such huge data? Have you got any tips how to filter that data so that only chosen solutions are saved to *.csv file? Maybe I am missing something and there is another way used for design explorer examples? Any tips or tricks? :)
Thank you for your time and help,
Have a nice weekend…