|
|
|
Log messageSeveral changes and bug fixes in the Construction Evaluator. CompositeCase: 'strategyName' is now just 'name'. CompositeCaseSimilarityMeasurer: many changes - both max and min number of cases are used to weight the numeric similarity between strategies (not only min) - the max number of relations between both strategies is used to average the relation-similarity (not the number of relations of the examplar strategy, which sometimes produced too high similarities because it did not consider spurious relations in students' constructions) - default sorting method is GREEDY, not EXHAUSTIVE. Small but important bug. - simple cases in a strategy are tagged marking their order (to define relations that can be compared; 1 can be compared to 1, but pointers to cases in different data structures (i.e. strategies) cannot - big bug). - numericSimilarity has been given a more descriptive name of numericDistance; the other name caused a bug. - weighting of relation-similarity has been changed - corrected. - general weights of relations- and numeric-similarity have been changed. Now similarity is really [0-10]. - Double.MIN_VALUE in non-negative. Small but important bug when you are looking for a max and have many zeroes. Changed Double.MIN_VALUE for -1.0. ConstructionEvaluation: now holds all the evaluations, not just the best (better for testing, more general, makes the code simpler, is more powerful, does not curtail functionality...) ConstructionEvaluator: better doc, lots of improved fuctionality to convert from eXpresser data representation to eGen data representation, main method for testing... oh, and now it gives proper evaluation measurements. ConstructionEvaluatorConnector: minor change, this class is not used at the moment (Durham TLRP/TEL meeting, lunch time) SimpleCase: - simple cases in a strategy are tagged marking their order (to define relations that can be compared; 1 can be compared to 1, but pointers to cases in different data structures (i.e. strategies) cannot - big bug). - relations are not stored anymore, they are computed every time they are needed; at the moment, this is not a bottleneck |
||||||
