mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: How to tackle Vector->NamedVector and back conversion
Date Sat, 24 Apr 2010 19:12:36 GMT
Put in other words, this would mean that there is either one or two output
formats but most importantly only one input format that would always read
NamedVectorWritables, possibly by inserting default names.  Due to
inheritance, those objects would serve both purposes.

That sounds good and simple.

On Sat, Apr 24, 2010 at 11:31 AM, Robin Anil <robin.anil@gmail.com> wrote:

> > For algorithms that are accepting arguments of a particular type, it
> might
> > be reasonable to let NVW extend VW (I am not at all sure about the
> > unintended consequences of this, but it sounds plausible).   Then all we
> > need is a facade that exposes an NVW interface for a wrapped
> VectorWritable
> > with some kind of default labels (say the indexes as strings).
> >
> Or the other way around. Let everything be a NamedVectorWritable. during
> deserializing use explicit methods to use or skip the name

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message