-
Notifications
You must be signed in to change notification settings - Fork 38
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
I can not reproduce your train AUC, & valid AUC scores #1
Comments
Hello, what scores did you get? |
My AUC scores for training and validating are 75% and 77%, respectively. |
The scores you are mentioning, are they related to a specific plane or to the global (stacked) model? |
I just tested only ACL diagnosis with Sagittal plane. Because I guess the plane has the most important tasks for the diagnosis, especially for ACL. And this condition should be the highest AUC score? I've read both papers from Stanford Uni (first author: Nicholas Bien) and Croatia + Turkey group. I know you try to reproduce the experiments of Stanford Uni paper. |
Can you share the code? or the hyperparameters you used? |
I don't have HPC so I use Google Colab to reproduce your experiment! I don't know how do authors of the paper (https://doi. org/10.1371/journal.pmed.1002699) do exact to get their AUC scores? I have test certain codes following the paper. However, I have never seen they reach the scores. |
yeah, i also could not reproduce the AUCs. I saw that you are optimizing AUCs but in the papers, they are minimizing the error rate |
Hi, im getting an error while building global acl classifier. I used the code from your blog for that.
particularly in now its throwing error at X[:, 0] = results['axial'] values are not getting assigned here to X. What do i do now? What im doing wrong here. |
Dear Besbes,
Firstly, I thank for your sharing code. It is very nice. I test with sagittal dataset with anterior cruciate ligament tear. However, I could not reproduce your results like train & valid AUC scores. So could you explain to clarify the issue? Or maybe I acquire a mistake somewhere?
Best regard. Linh
The text was updated successfully, but these errors were encountered: