-
Notifications
You must be signed in to change notification settings - Fork 5
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
Mode 2: Prediction evaluation #5
Comments
Hello Egor-Lebedev, In your question you are referring to mode 2 "prediction evaluation" of the tool transposon classifier RFSB, which is described on this page: https://github.com/DerKevinRiehl/transposon_classifier_rfsb. The intention to use mode 2 is for users who want to evaluate the performance of their classification. For this purpose you need to have the trueLabelFile (which means the true classification) and the predictLabelFile (that was produce by any classifier). Afterwards mode 2 will compare the predicted values with the true values and provide you with statistics on common evaluation measures for classification (such as F1 score, Accuracy, MCC, etc.). So in short: you need to know the true labels and provide the trueLabelFile. A format how to provide can be found in the example project here: https://github.com/DerKevinRiehl/transposon_classifier_rfsb/tree/main/demoFiles Hope this answer could help you, please let me know if you have further questions. Best regards, |
Hi, thanks for your answer. I'll write in more detail - I want to evaluate the classification using mode 2 "prediction evaluation" for honey bee transposons. Best, |
Dear Egor, You could for example let our tool classify your transposons and than assume our classification is 100% true, and use this to check how well your predictions are. But again, this means you need to work based on assumptions that something is true. Best, Kevin |
Hello! To use the Prediction evaluation module, you must pass trueLabelFile to the labels input. Can you please tell me how to get these labels?
The text was updated successfully, but these errors were encountered: