-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
use different query strategies #41
Comments
Can you post the error messages here? Without them, I cannot tell for sure. Does your model work without modAL? Can you train it with your data? Because I don't think the 3D shape is a problem for modAL, since the data interacts with the model only. (I have tried other 3D shapes for image classification problems, they work fine.) |
This is the error message fot batch_uncertainty_sampling: |
This is the error for expected_error_reduction: Since this is the same code I used for the default query strategy and the same data I dont know how to tackle this error. |
What is the type and shape of your training data? Especially |
x_pool is a numpy array with a shape of (31982, 10, 6) and type float. |
I'll try to figure out what went wrong soon. Not sure I can look into this during the weekend, but I'll fix this by the end of next week! |
Quick update: the bug is definitely in modAL, I am preparing a fix, it will be ready soon! |
thanks a lot for your effort! Sent with GitHawk |
The fix is in! Now these query strategies work with multidimensional data. You can update your local installation by installing directly from the master branch: pip install git+https://github.com/modAL-python/modAL.git Let me know if there is a problem! A small note. Expected error reduction will only work with scikit-learn models since this requires cloning and retraining the classifier, which might not work with Keras. |
I am using keras/tensorflow models with this framework and the activelearner class.
As soon as I try to change the query strategy, different errors occur.
What do I have to change to implement the different strategies. The trainings_input is 3D shape.
I tried up to now all uncertainty methods of which only the default selection did work. Now I was trying the expected error_reduction strategy, but there occur errors as well.
I am afraid the 3D shape of the training data is killing all the other algorithms, but for a LSTM this kind of shape is required.
The text was updated successfully, but these errors were encountered: