Skip to content
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

Discrepancy between the train time and evaluation time #193

Closed
rth opened this issue Mar 14, 2019 · 5 comments
Closed

Discrepancy between the train time and evaluation time #193

rth opened this issue Mar 14, 2019 · 5 comments
Labels

Comments

@rth
Copy link
Collaborator

rth commented Mar 14, 2019

The training times shown on RAMP don't seem to be consistent with the evaluation time.

For instance, for the solar_wind problem, the starting kit says that the train time is 0.54 s (and test is 0.17 s), while to evaluate that submission it takes ~25min on the same server.

The evaluation time is consistent with what I get by running the ramp_test_submission locally, and the reported train/test time is faster by 3000x which doesn't make sense even allowing for multiple CV folds.

@rth
Copy link
Collaborator Author

rth commented Mar 14, 2019

As a side note, @glemaitre don't you think that having a "Frontend" etc. labels would be easier to manage that renaming each issue :)

@glemaitre
Copy link
Collaborator

I feel stupid now :) I like only to use 10% of GitHub ;)
I will create those.

@glemaitre
Copy link
Collaborator

Be aware that the reported time for training is only on a single fold. So you need to multiply by the number of folds. However, x3000 seems kinda of unlikely :)

@kegl
Copy link
Collaborator

kegl commented Mar 15, 2019

You also need to score which is slow sometimes.

@glemaitre glemaitre added the bug label Mar 15, 2019
@glemaitre
Copy link
Collaborator

Uhm we solve this issue. We were reporting the validation time instead of the training time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants