You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code Lab currently uses an hours/effort estimate to complete the lesson (usually 1-3), a hard-coded semester length measured in weeks (14), and course credit hours (around 3) to calculate the number of grade points earned by completing each lesson.
Here's the formula: round(lessonHours * maxGrade / (normalizedSemesterWeeks * course.credits))
Where:
maxGrade / normalizedSemesterWeeks approximates the number of grade points earned per week to achieve the max grade
lessonHours / course.credits is the proportion of credits per week the lesson is expected to take (course.credits is the number of hours per week a student is expected to spend on course work)
Example:
Lesson effort: 2
Semester weeks: 14
Credit hours: 3
Lesson grade points:round(2 * 4 / (14 * 3) = 0.19
This formula has several opinions or requirements that can vary or not exist depending on the course:
An unchangeable fixed program length
Assumption of credits earned
Assumption of a 4.0 grade scale
Strong connection between effort, hours, and grade points earned
There are many variations in which Code Lab is used that violate these requirements/assumptions. For example,
MI 349 at MSU only uses Code Lab for part of the grading scale, so not all 4.0 grade points are earned in Code Lab
MI 449 has a wide variety of experience of students and association between grade points and hours estimate can be misleading and make project planning difficult
Code Lab 517 programs run for 4-8 weeks and do not reward course credits
Besides being inflexible, it is complicated and has led to many similarly-named utility functions that may explain #266, and may contribute to performance issues on the Student Progress page.
Proposals:
Make normalizedSemesterWeeks configurable per course
Make maxGrade configurable per course
Make lesson grade points configurable per lesson instead of calculated
Add interactive calculator to frontend to help instructors determine lesson grade points using estimated hours/effort/grade/semester-length formula
The text was updated successfully, but these errors were encountered:
Code Lab currently uses an hours/effort estimate to complete the lesson (usually 1-3), a hard-coded semester length measured in weeks (14), and course credit hours (around 3) to calculate the number of grade points earned by completing each lesson.
Here's the formula:
round(lessonHours * maxGrade / (normalizedSemesterWeeks * course.credits))
Where:
maxGrade / normalizedSemesterWeeks
approximates the number of grade points earned per week to achieve the max gradelessonHours / course.credits
is the proportion of credits per week the lesson is expected to take (course.credits
is the number of hours per week a student is expected to spend on course work)Example:
round(2 * 4 / (14 * 3) = 0.19
This formula has several opinions or requirements that can vary or not exist depending on the course:
There are many variations in which Code Lab is used that violate these requirements/assumptions. For example,
Besides being inflexible, it is complicated and has led to many similarly-named utility functions that may explain #266, and may contribute to performance issues on the Student Progress page.
Proposals:
normalizedSemesterWeeks
configurable per coursemaxGrade
configurable per courseThe text was updated successfully, but these errors were encountered: