Currently the tree kernel framework has one entry point for defining kernels --
TreeKernel, which takes arguments about what kind of kernel to run, sst or ptk.
We should generalize this to an interface/abstract class approach where new
kernels can be defined by inheriting from TreeKernel and implementing their own
eval methods.
Original issue reported on code.google.com by tim.mil...@gmail.com on 2 Apr 2014 at 1:38
Original issue reported on code.google.com by
tim.mil...@gmail.com
on 2 Apr 2014 at 1:38