-
Notifications
You must be signed in to change notification settings - Fork 146
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
Accuracy vs Cost #4
Comments
Hi, |
@JosefHook You are right. It seems it's the bug in the code and the reported 80-90% accuracy is not correct. I think the only way is to retrain and research for the correct hyperparameters. |
@JosefHook @JosefHook cost,acc = [np.mean(x) for x in zip(*perfs)] is the right code? |
Hi! |
Hi @onesmileapp I couldn't find it either. Maybe after the recent commits for the version compatibility, it has been changed to something else. If you check my fork from this directory it's showing this function in line 83, tsc_main.py . |
@AziziShekoofeh yes, I have found it . thank you~ |
Hi,
Thanks for the nice example. I have a question about your check_test() function. When you're running the session and generating the output, it's [model.cost, model.accuracy] but after append and tuple you have [accuracy, cost]. I'm afraid to say that it's a swap between accuracy and cost. Even, when I ran it on another time-series dataset, it generates the accuracy of greater than 1, which is definitely incorrect.
Thanks,
Shekoofeh
The text was updated successfully, but these errors were encountered: