Function to score a submission #10
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mehdidc
force-pushed
the
score_submission
branch
from
7ef4a6b
to
8d33a6d
Compare
aboucaud
reviewed
May 7, 2018
There was a problem hiding this comment.
Thank you for this PR @mehdidc.
One point that is not clear to me at this point: when you call the scoring
submission.compute_test_score_cv_bag(session)on which machine does the actual computation occur ? The backend or the RAMP server ?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was missing from the last PR. I adapted score_submission from db_tools.py in ramp-backend.
To make the classes in model.y a bit less stateful I put session as an argument in all functions that need it.