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
I found comments, that there should be a way to use transforms without the need of a trainer/learner (i.e., building a "processing / transform - pipeline instead of an LearningPipeline, cp. #259 (comment)). Unfourtunately, I could not find out, how to achieve this.
In my usecase, I want to determine similarity of documents with n-gram vectorization and cosine distance. The functionalty for featurization is given by the TextFeaturizer (https://docs.microsoft.com/de-de/dotnet/api/microsoft.ml.transforms.textfeaturizer). In this usecase I don't want to do a training (yet), but am interessted in the output in the result of the TextFeaturizer itself.
Accessing the results of partial steps could be helpful for debugging LearningPipelines too (cp. discussion here: #259). @TomFinley
The text was updated successfully, but these errors were encountered:
However, once we build the final API (see #583), you will be able to access the output of transforms without having to train a model.
In fact, the 'trained model' will be just one form of 'transformer', and you will be able to have as many of them chained together as you want (including 0), and mix and match them with other transformers, like TextFeaturizer.
I found comments, that there should be a way to use transforms without the need of a trainer/learner (i.e., building a "processing / transform - pipeline instead of an LearningPipeline, cp. #259 (comment)). Unfourtunately, I could not find out, how to achieve this.
In my usecase, I want to determine similarity of documents with n-gram vectorization and cosine distance. The functionalty for featurization is given by the TextFeaturizer (https://docs.microsoft.com/de-de/dotnet/api/microsoft.ml.transforms.textfeaturizer). In this usecase I don't want to do a training (yet), but am interessted in the output in the result of the TextFeaturizer itself.
Accessing the results of partial steps could be helpful for debugging LearningPipelines too (cp. discussion here: #259).
@TomFinley
The text was updated successfully, but these errors were encountered: