FAQs

Organization

Q: Do you recommend creating a new dedicated repository for the class specific grading scripts? Or incorporate into a current lab solutions repository?

A: Up to you. I typically use separate grading and solutions repos. I do this because I give TAs access to the grading repos (they commit grades to CSV files), but I don’t typically give TAs access to our solution repository.

Q: Should I export separate grades CSV files from Learning Suite for each lab, or one big CSV file?

A: Either works. It’s easier to edit grades in smaller files, but quicker to import everything at once if you use one file.

Teams/Group Assignments

Q: Can do I do group grading

A: Yes.

For Github submissions, just make sure each group members has the same Github URL and they will automatically be formed into groups.

For Learning Suite submissions, use the set_learning_suite_groups() function to provide a CSV file indicating the group name of each students.

Q: What if I have multiple team-based assignments and I have to change some team members between assignments?

A: Keep your groups in a CSV file, and use one column for each assignment. When you start a new assignment, just copy the first column and make any adjustments as needed for each assignment. When you call set_learning_suite_groups() you can specify which column to use to form groups.

Other Options

Q: Grading each student takes a long time to compile/synthesize/simulate. What should I do?

A: You can use two-pass grading with build_only and run_only options. See the Pre-Building Student Code guide for details.

Q: Can I grade multiple items for a student at once? A: Yes, you can grade multiple columns. For each column you want your callback function invoked, use a separate call to add_item_to_grade.