Andreas Klöckner
Andreas Klöckner
To find the time per session, simply compute the difference between these two: https://github.com/inducer/relate/blob/2186f96bfb1bb45d498c162cf8d824e9a84f6c4a/course/models.py#L880-L883 and insert the relevant HTML here: https://github.com/inducer/relate/blob/2186f96bfb1bb45d498c162cf8d824e9a84f6c4a/course/templates/course/gradebook-by-opp.html#L181 (you have access to the flow session as `grade_info.flow_session`.
FYI Github has a "draft" mode for PRs to express "WIP" status (under "Reviewers" in the sidebar).
That's also where you can request a review once you think it's ready for a look.
Thanks for your work on this!
Could you merge in master to get the latest CI? Also, could you remind me what the status is here?
I feel that if we could compute whether a given participant is expected to complete a certain flow (possibly by adding to the flow rules), we could compute to-do lists...
Thanks for working on this! I would argue that your changes don't really address the issue, as the rounded values could very well still add up to a value greater...
Thanks for your contribution! The behavior you removed, unfortunately, is an intentional (if ugly) workaround for the fact that submitting a grade for a code page will reexecute the code,...
Is this a grade book thing to you? Or a flow thing? Or both? FWIW, I'm not sure I'm super in favor of bolting some ad-hoc rule system for who...
> That sounds more reasonable. Not sure what you mean. *What* sounds more reasonable? > Because currently a flow can be used only once by a single grading opportunity. If...