-
Notifications
You must be signed in to change notification settings - Fork 3
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
Added normalize column to export grade book to remote gradebook #190
Added normalize column to export grade book to remote gradebook #190
Conversation
@pwilkins I made changes can you verify it. |
course, | ||
get_grades=True, | ||
use_offline=use_offline, | ||
get_score_max=True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for
normalise = true => get_score_max=False
normalise = False => get_score_max=ture
Do you want me to change this logic? |
I'm not sure I understand. Are you saying that 0.0/1.0 points indicates the user hasn't attempted the problem and 0.0/max points would make it look like the user attempted & got 0 points? Wouldn't a problem with a max of 1.0 look the same, whether the user attempted or not? |
yes. This is what i am saying
|
if get_score_max is True: | ||
add_grade(grade_item['label'], earned, possible=possible) | ||
else: | ||
add_grade(grade_item['label'], grade_item['percent'], possible=1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Reverted code for normalize calculation as previous code, shared in meeting https://github.com/mitocw/edx-platform/blame/df5b2dadda636184116fa394105ea37e3ab3b867/lms/djangoapps/instructor/views/legacy.py#L731
- Added
possible=1
because code above (https://github.com/mitocw/edx-platform/pull/190/files#diff-5dd41ae768fed10fe37df53a1d9e78c8R268) is expecting a tuple (earned, possible). - If this is an issue the i need to modify code to release data without possible in
https://github.com/mitocw/edx-platform/pull/190/files#diff-5dd41ae768fed10fe37df53a1d9e78c8R268 ??
gradeset = student_grades( | ||
student, request, course, keep_raw_scores=get_raw_scores, use_offline=use_offline | ||
) | ||
log.debug(u'student=%s, gradeset=%s', student, gradeset) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we use student_grades in this code branch progress_summary in the other code branch?
Can't we use progress_summary for both?
71fd151
to
4328dbb
Compare
Fixed @pdpinch |
percent = earned / float(possible) | ||
percent = round(percent * 100 + 0.05) / 100 | ||
add_grade(label, percent, possible=1) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this can be more DRY, since the only difference between the branches is the calculation of the percentages and the call to add_grade()
It's going to be a problem if we export the long (user-friendly) name instead of the short assignment name & number. Those short labels appear on the student progress page in the graph, so that data has to be in the view somewhere. |
I think you've got this merging into the wrong branch, hence the merge conflicts. Instead of master, merge it into mitx-cypress.1-hotfix.3 (but check with @bdero before actually merging!) |
4328dbb
to
395478e
Compare
…ssue using gradebook summery
395478e
to
6a9278f
Compare
add_grade(grade_item['label'], earned, possible=possible) | ||
else: | ||
add_grade(grade_item['label'], grade_item['percent'], possible=1) | ||
except (IndexError, KeyError): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment explaining when you expect to hit this exception
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
closed by #201 |
Background
This PR resolves #147, resolves #187 and resolves #188
What is done in this PR
Studio Updates: None
LMS Updates:
@pdpinch @pwilkins