Ah ok, in the case of initial the problem is the following. When you apply
an aggregation, then only the aggregated fields are valid. Data in the
other fields doesn’t necessarily correspond to the element where the
maximum value, for example, has been found. This becomes clear when you
compute the
Sorry I was not clear:
I meant the initial DataSet is changing. Not the ds. :)
> Am 22.03.2016 um 15:28 schrieb Till Rohrmann :
>
> From the code extract I cannot tell what could be wrong because the code
> looks ok. If ds changes, then your normalization result should change as
> well, I w
>From the code extract I cannot tell what could be wrong because the code
looks ok. If ds changes, then your normalization result should change as
well, I would assume.
On Tue, Mar 22, 2016 at 3:15 PM, Lydia Ickler
wrote:
> Hi Till,
>
> maybe it is doing so because I rewrite the ds in the next
Hi Till,
maybe it is doing so because I rewrite the ds in the next step again and then
the working steps get mixed?
I am reading the data from a local .csv file with readMatrix(env, „filename")
See code below.
Best regards,
Lydia
//read input file
DataSet> ds = readMatrix(env, input);
/**
Hi Lydia,
I tried to reproduce your problem but I couldn't. Can it be that you have
somewhere a non deterministic operation in your program or do you read the
data from a source with varying data? Maybe you could send us a compilable
and complete program which reproduces your problem.
Cheers,
Til
Hi all,
I have a question.
If I have a DataSet DataSet> ds and I want to
normalize all values (at position 2) in it by the maximum of the DataSet
(ds.aggregate(Aggregations.MAX, 2)).
How do I tackle that?
If I use the cross operator my result changes every time I run the program (see
code bel
