-
Notifications
You must be signed in to change notification settings - Fork 186
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
Predict over text not present in the DB #62
Comments
+1 |
Has there been any progress on this @rafacarrascosa @jmansilla ? |
@iScienceLuvr sorry, nothing on this yet |
@rafacarrascosa what other research has been done on this? |
@iScienceLuvr nothing at all... the issue with this issue is that there are many queries to the DB here and there that need to be 'tapped' somehow to work with something that is now in the DB. if you want the ticket it's all yours! |
@rafacarrascosa so how can I do this project? Idk where to start |
@iScienceLuvr sorry for the absurd delay. |
Actually, if I recall correctly, that method is already working under the assumption that evidences are not in the DB. The challenge would be to build in your scripts Evidences resembling those that are created from the DB. |
@rafacarrascosa @jmansilla I do not undersrand how this code works... So predict() is the function that learns to classify? And what are the questions the are asked to the user? |
It would be great to provide a functionality to predict a relation over some text without asking you to insert that text in to the database.
This could be really useful for applications where IEPY is mounted as a service and the corpora is not known in full a-priori.
The text was updated successfully, but these errors were encountered: