You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the #142 implementation, in order to evaluate a classifier, the classifier instance needs to support a uniform interface of train, classify, categories and reset methods. I have recently added reset functionality to all classifiers #143 as it could be useful even when not evaluated.
Is it OK if I add train, classify, categories, and perhaps untrain method as well in the LSI while internally utilizing existing methods and not breaking any backwards compatibility?
As far as I understood LSI, in order to get the list of all known categories, I will have to scan all the indexed items. Is there any other faster way to get that information?
The text was updated successfully, but these errors were encountered:
As per the #142 implementation, in order to evaluate a classifier, the classifier instance needs to support a uniform interface of
train
,classify
,categories
andreset
methods. I have recently addedreset
functionality to all classifiers #143 as it could be useful even when not evaluated.Is it OK if I add
train
,classify
,categories
, and perhapsuntrain
method as well in the LSI while internally utilizing existing methods and not breaking any backwards compatibility?As far as I understood LSI, in order to get the list of all known categories, I will have to scan all the indexed items. Is there any other faster way to get that information?
The text was updated successfully, but these errors were encountered: