Currently, an index is created, and all columns are reduced the same way, and only in case the index is not unique, a reduction is applied to the value list. What we need is an individual, column-based reduction index. I suggest to introduce this functionality very flexibly:
introduce a new "reductionidx" member of a column, that accepts both simple integers, "None" (the default), and String Tuples.
Assume an evaluation index of three elements [a,b,c]. The current functionality would use this evaluation index and reduce the values in the data frame to match this three-level index in case that there are more. However, it might be interesting to learn about the "minimum" value for every index element in a x b regardless of the values of c. A reduction over c would then be achieved by specifying a reduction index of 2, or -2. Similarly, it should be possible to reduce by specifying 'a b' as the reduction index ('c' is now left out). Whenever a sublist of [a b c] is wanted as reduction index, it is enough to use an integer. In the more complicated case that a reduction index consists of nonconsecutive or whatever parts of the evaluation index, a string tuple must be specified.
Currently, an index is created, and all columns are reduced the same way, and only in case the index is not unique, a reduction is applied to the value list. What we need is an individual, column-based reduction index. I suggest to introduce this functionality very flexibly:
[a,b,c]. The current functionality would use this evaluation index and reduce the values in the data frame to match this three-level index in case that there are more. However, it might be interesting to learn about the "minimum" value for every index element in a x b regardless of the values of c. A reduction over c would then be achieved by specifying a reduction index of 2, or -2. Similarly, it should be possible to reduce by specifying 'a b' as the reduction index ('c' is now left out). Whenever a sublist of [a b c] is wanted as reduction index, it is enough to use an integer. In the more complicated case that a reduction index consists of nonconsecutive or whatever parts of the evaluation index, a string tuple must be specified.