MATH-312, 314, 316 and 317 were the first round. Some of the necessary changes included:
- sparse iterators for sparse vectors - view semantics for sub-matrix and sub-vectors - additional sparse vector types for specialized applications - introduction of an unbounded sparse matrix/vector that simply remembers the highest bound set - introduction of abstract classes to allow off the cuff inner implementations of virtual vectors - introduction of additional decomposition classes - introduction of row and column label abstraction for matrices and vectors - higher performance implementations The 5 issues that Jake filed were mostly address the first point. That stalled out when he hit resistance to change. Since then we have adopted Colt as our matrix/linear algebra/collections implementation and we don't really need any changes to MATH. On Sat, Dec 12, 2009 at 8:35 AM, J.Pietschmann <j3322...@yahoo.de> wrote: > On 09.12.2009 20:58, Jake Mannix wrote: > >> The commons-math linear APIs have been described as effectively locked >> until 3.0, due to back-compat requirements. >> > > Can you give a short summary of the API changes which are necessary > to incorporate and use the functionality you need? Some functionality > I've seen mentioned here could probably be pressed in the existing > API, but I may have missed some details. > > J.Pietschmann > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- Ted Dunning, CTO DeepDyve
