On Mon, Aug 15, 2011 at 10:27 AM, Jörn Kottmann <[email protected]> wrote:
> On 8/15/11 2:55 PM, [email protected] wrote: > >> Thanks Jörn, I'm trying the suggested to improve my pos tagger. >> >> Now back to the misclassified report interface. I could not find a good >> design for it because I could not take advantage of the sample classes, so >> what I proposed was 3 methods to handle different methods: >> >> // for the sentence detector >> void missclassified(Span references[], Span predictions[], String >> referenceSample, String predictedSample, String sentence) >> >> // for namefinder, chunker... >> void missclassified(Span references[], Span predictions[], String >> referenceSample, String predictedSample, String[] sentenceTokens) >> >> // for pos tagger >> void missclassified(String references[], String predictions[], String >> referenceSample, String predictedSample, String[] sentenceTokens) >> > > I had something like this in mind > void misclassified(T gold, T predicted); > where T is the generics type for the Sample object. > > What do you think? > > An implementation would then need to figure out the exact > differences it is interested in. > > Jörn > Should I modify the hierarchy of the sample classes?
