-
Notifications
You must be signed in to change notification settings - Fork 3
CTAT Detector Library
Ken Holstein edited this page Apr 16, 2018
·
11 revisions
All detectors below can be found here.
Gaming-the-system detectors
-
Cross-system detector of gaming-the-system
- Description: Cross-system gaming detector from Luc Paquette, Michal Moskal, and Ryan Baker
-
Gaming-the-system
- Description: [coming soon]
Detectors of student help-seeking behavior
-
- Description: [The Help Model from Vincent Aleven, Bruce McLaren, Ido Roll, et al., (e.g., see Aleven et al., 2006; 2015)]
- Free parameters: note that this demo version has some free parameters that can be tuned (e.g., thresholds on the duration that must elapse between attempts in the tutor in order for an attempt to be flagged as "deliberate")
- Outputs: strings representing assessments of students' help-seeking behavior (e.g., hint avoidance, non-deliberate attempts, hint abuse, as well as 'acceptable' and 'preferred' hint-use according to a normative model of hint use)
-
Help model (variant: prefer that student attempts step first, before asking for a hint)**
- Description: [A variant of the Help Model from Vincent Aleven, Bruce McLaren, Ido Roll, et al., (e.g., see Aleven et al., 2006; 2015)]
- Free parameters: note that this demo version has some free parameters that can be tuned (e.g., thresholds on the duration that must elapse between attempts in the tutor in order for an attempt to be flagged as "deliberate")
- Outputs: strings representing assessments of students' help-seeking behavior (e.g., hint avoidance, non-deliberate attempts, hint abuse, as well as 'acceptable' and 'preferred' hint-use according to a normative model of hint use)
Bayesian Knowledge Tracing
Detectors of unproductive persistence
-
- Description: A sliding window variant on the wheel spinning detector proposed by Beck and Gong.
-
Predictive Similarity:
- Description: [coming soon]
-
Predictive Stability:
- Description: [coming soon]
-
- Description: outputs alerts in response to fixed, user-specified thresholds on student idle time
-
Outputs: custom message after each specified time-interval
- the current format is a comma-delimited string, where the first element is a boolean stating whether the student is over some author-specified idle-time threshold, and the second is one of a set of author-specified milestone times that the student has exceeded
- (e.g., "0, > 0 s" indicates that the student is not considered idle for long enough to trigger an event/alert, and "1, > 1 min" indicates that the student has been idle for long enough... specifically: the student has been idle for more than 1 minute)
- the current format is a comma-delimited string, where the first element is a boolean stating whether the student is over some author-specified idle-time threshold, and the second is one of a set of author-specified milestone times that the student has exceeded
-
- Description: keeps a running count of attempts on each step in a tutor interface
-
Outputs: the running count of attempts on the most recent step the student has worked on
- (e.g., if a student has tried 30 times on a particular interface element, the output will be "30")