Changes between Initial Version and Version 1 of Ticket #320


Ignore:
Timestamp:
Feb 7, 2008, 4:24:00 PM (15 years ago)
Author:
Peter
Comment:

removed CamelCase links

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #320 – Description

    initial v1  
    33There are two choices. First, if the kernel matrix should be calculated on-the-fly or calculated once and cached. Second, what type of !KernelFunction is used to calculate an element in kernel matrix.
    44
    5 These choices are currently allowed through dynamic polymorphism. The KernelFunction structure resembles a lot from how Distance previously worked for NCC. For the first choice, typically you want to cache the matrix, and therefore it would be nice to templatize this and make caching default.
     5These choices are currently allowed through dynamic polymorphism. The !KernelFunction structure resembles a lot from how Distance previously worked for NCC. For the first choice, typically you want to cache the matrix, and therefore it would be nice to templatize this and make caching default.
    66
    7 I am not sure how far the templates propagate, but I would guess also KerneLookup need to be templatized, and since SVM holds a KernelLookup. This is a bit unclear though, especially since ticket:287 is not finished.
     7I am not sure how far the templates propagate, but I would guess also !KerneLookup need to be templatized, and since SVM holds a !KernelLookup. This is a bit unclear though, especially since ticket:287 is not finished.