Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do you use weasel to classify? #17

Open
mugenZebra opened this issue Dec 21, 2018 · 3 comments
Open

How do you use weasel to classify? #17

mugenZebra opened this issue Dec 21, 2018 · 3 comments

Comments

@mugenZebra
Copy link

This is a question. My understanding is Weasel transforms original continuous-valued features to bag of pattern, then how to do classification after the transformation?

@johannfaouzi
Copy link
Owner

WEASEL extracts features from the set of time series: it will transform a set of continuous-valued time series into a "standard" input X with shape (n_samples, n_features). Each feature corresponds to a tuple (window_size, n_grams). Not every possible tuple (i.e. features) are kepts, but only the most relevant ones (i.e. the ones with a pvalue below a given threshold for an ANOVA test).

Here is an example taken from the documentation.

After the WEASEL transformation, you can use any "standard" classifier to perform classification (logistic regression, SVM, random forest, naive bayes, etc.). You can use Pipeline from scikit-learn with WEASEL as all the estimators in pyts are scikit-learn-compatible.

I hope that it answers your question.

@mohataher
Copy link

Hi @johannfaouzi, what's your policy with this repo issues?

Typically I see maintainers allow opening issues for bugs/feature related questions. Any usability questions are asked on Stackoverflow. What do you think?

@johannfaouzi
Copy link
Owner

Right now I think that having all usability questions as issues is the best for several reasons. The amount of isues is pretty low, which makes it easy to answer them here. Moreover, you need a certain amount of reputation to create a new tag on stackoverflow.

If this project gets much bigger than it is right now, the policy will change in the way you mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants