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
Sktime: Python implementation of HIVE-COTE #842
Comments
+1 |
Another question is how does the class_weight parameter in sktime work? |
hi, we are working on hive-cote for python, just tidying up and testing some features for the java version first. Once term has finished @MatthewMiddlehurst and I can give it our full attention. |
The python version has all sorts of pythonesque issues, memory intensive, slow etc which require significant engineering and we are not really python programmers, so it is painful. In the short term, if anyone wants to run HIVE-COTE v2 just email me ajb@uea.ac.uk, we can help you get it running in java (very easy, we can just give you the jar file and you can run it on command line or with a script) or we can run it ourselves and just send you the results files. |
Heya! Thank you for the feedback :) |
Hi guys!
|
Hi @paultt, its hard to know exactly whats going on without knowing a bit about the data. STC is definitetly one of the more under-developed classifiers. We are hoping to sort out all our sktime classifiers after this teaching term at UEA ends. |
Hi @MatthewMiddlehurst, |
Im a bit late for the previous comments on this issue, but when it comes to preprocessing I would look at the data_loading and classification notebooks in the examples folder. HIVE-COTE uses the same data format as other sktime classifiers. HIVE-COTE can only take univairate data currently, not datasets with multiple series per instance. |
update on this, Matt now has equivalence with tsml on DrCIF, TDE and Arsenal. Just STC to sort out now, which is a summer objective for my group |
Close to completion, see #1504 |
The sktime master branch has an implementation of HIVE-COTE 2.0 and an updated version of HIVE-COTE 1.0 after the merge of #1504. If any issues with these arise they can be a separate issue. |
Is your feature request related to a problem? Please describe.
I'm new to sktime and time series classification.
I have installed sktime toolkit. I trying to apply HIVE-COTE 1.0 to my dataset. The codes are shown as follows, x_train, y_train, x_test, and y_test are my prepared dataset. I call HIVE-COTE directly through the module HIVECOTEV1, but I am not sure if this is the correct way to reproduce hive-cote algorithm. Is this HIVECOTE1 module includes ensembling part (like TimeseriesForestClassifier)?
Another question is the time series dataset I have is 3d array, which is in the format of (number of samples, time steps, number of features). But when I fed the dataset into the Timeserisforestclassifier, the error information is shown as follows. After processing the dataset with the module 'columnconcatenator()', it can run smoothly. Does that mean only 2d array can be fed into the algorithm as well as HIVE-COTE?
The shape of x_train, y_train, x_test, and y_test: (28, 1918, 62) (16, 1918, 62) (28,) (16,)
error information:
Traceback (most recent call last):
File "h:/scipt/prediction/stacking for classification/HIVECOTE.py", line 73, in
clf.fit(x_train, y_train)
File "C:\Anaconda3\envs\lib\site-packages\sktime\series_as_features\base\estimators\interval_based_tsf.py", line 86, in fit
coerce_to_numpy=True,
File "C:\envs\ARTC\lib\site-packages\sktime\utils\validation\panel.py", line 187, in check_X_y
coerce_to_pandas=coerce_to_pandas,
File "C:\Anaconda3\envs\lib\site-packages\sktime\utils\validation\panel.py", line 87, in check_X
f"X must be univariate with X.shape[1] == 1, but found: "
ValueError: X must be univariate with X.shape[1] == 1, but found: X.shape[1] == 1918.
Describe the solution you'd like
It will be very appreciated that if you can provide a demo of Multivariate time series classification with HIVECOTE in python on Github or sktime documentation. I think that will be very helpful for us to apply this state-of-the-art algorithm for industry application.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: