Skip to content

syllabus + hw #17

Description

@robertsj

Make it very clear what homework + regrade policy is. We haven't had too many issues this term, but solidify the process:

  1. Test with student tester. Can we have a final "all tests have run" message saying it should be good to go? Can we enforces a reset? Should we do from student_module import x, y, z or just use import student_module to avoid naming issues? Add checks to prevent name overwrites?

  2. Things will slip by this system. We'll allow one re-do capped at 4/6 credit. The offending code must be commented or returned to its template form. A written request must be made to the instructor and grader within one week of grades being released.

  3. File uploads must be verified. Uploading an incorrect file is not excuse to upload the correct file later after the due date. Hence, verify all uploads after the fact (the same goes for exams!).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions