I don't know if we need it (I'm not sure if we really need the extra methods for maxValue or maxIndex either).
I'm ok with it staying the way it is, although it's used incorrectly in the norm(double) implementation (see MAHOUT-267), probably because someone assumed maxValue() was symmetric about 0. On Wed, Jan 27, 2010 at 11:44 AM, Ted Dunning <ted.dunn...@gmail.com> wrote: > I would expect maxValue() to behave like Math.max. > > Perhaps we should have maxAbsoluteValue in addition. > > On Wed, Jan 27, 2010 at 8:32 AM, Jake Mannix (JIRA) <j...@apache.org> > wrote: > > > Right? MaxValue should be returning the max of the absolute value, not > the > > real max, right? And the maxValue of the zero vector is 0, not > MIN_VALUE, > > yes? > > > > > > -- > Ted Dunning, CTO > DeepDyve >
