Re: Dirichlet Mapper assumes DenseVector?

[Jeff Eastman]

I committed a fix a couple of days ago. The code should have been calling AbstractVector.decodeVector and not DenseVector. The recent fix is type-agnostic.

Ted Dunning wrote:

I don't think that there should be such a preference.  If this is inherent
in the structure of decoding, then we should probably fix that.

On Sat, Jun 13, 2009 at 1:31 PM, Sebastien Bratieres <sb...@cam.ac.uk>wrote:

One of the two implementations of decodeFormat is required at this point if
I understand the code well; should there be a preference towards
SparseVector ?

PGP.sig
Description: PGP signature