Upload folder using huggingface_hub

.gitattributes

@@ -58,3 +58,6 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 # Video files - compressed
 *.mp4 filter=lfs diff=lfs merge=lfs -text
 *.webm filter=lfs diff=lfs merge=lfs -text
+AllData_problem_2011F.csv filter=lfs diff=lfs merge=lfs -text
+AllData_student_step_2011F.csv filter=lfs diff=lfs merge=lfs -text
+AllData_transaction_2011F.csv filter=lfs diff=lfs merge=lfs -text

AllData_problem_2011F.csv

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3fa315fa47c30a4cd16703f5ee70624f2216e3fd9440da1a5120cc27b0647336
+size 14316730

AllData_student_step_2011F.csv

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8ba76de29f34cf9ffbbb6ef49b83875a6971af25a449a066da6371257edd99d9
+size 66574002

AllData_transaction_2011F.csv

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:876af159ba67e9ee97f82b2fc6df78af73ac36b92b26c35b76c378338f90fdd9
+size 180060756

OLI_data.zip

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ecf7a2162b5138c7c34f13e921e0823c061b04e778d0f7fac216df20ad79459
+size 30429585

help_table1.csv

@@ -0,0 +1,35 @@
+,Field,Annotation
+0,Row,A row counter
+1,Sample Name,"The sample that contains the transaction. If a transaction appears in multiple samples,                    the transaction will be repeated, but with a different sample name."
+2,Transaction Id,A unique ID that identifies the transaction. Currently used for annotating transactions with                    custom fields via                    web services.
+3,Anon Student Id,"DataShop-generated anonymous student ID. To obtain original student identifiers or to                    learn more about data anonymization, see About data anonymization                    below."
+4,Session Id,A dataset-unique string that identifies the user's session with the tutor.
+5,Time,"Time the transaction occurred. For instance, if a student types ""25"" and presses return, the                     transaction time is at the point in which they press return."
+6,Time Zone,"The local time zone (e.g., EST, PST, US/Eastern)."
+7,Duration (sec),"Duration of the transaction in seconds. This is the time of the current transaction minus                    that of the preceding transaction or problem start event��whichever is closer in time to the                    current transaction. If this difference is greater than 10 minutes, or if the prior transaction occurred                    during a different user session, DataShop reports the duration as null                    (a dot). If the current transaction is preceded by neither another transaction or a problem start event,                    duration is shown as null. The duration is formatted without decimal places if the two times used                    in the calculation were without millisecond precision."
+8,Student Response Type,"The type of attempt made by the student (e.g., ""ATTEMPT"" or ""HINT_REQUEST"").                    This is logged in the                     semantic_event element."
+9,Student Response Subtype,"A more detailed classification of the student attempt. For example,                    the CTAT software describes actions taken by the tutor on behalf of the student                    as having subtype ""tutor-performed""."
+10,Tutor Response Type,"The type of response made by the tutor (e.g., ""RESULT"" or ""HINT_MSG"")."
+11,Tutor Response Subtype,A more detailed classification of the tutor response.
+12,Level (level_type),"The problem hierarchy name (e.g., ""Understanding Fractions"") of the type                    specified in the column header (e.g., ""Unit""). There may be multiple ""Level"" columns if                    the problem hierarchy is more than one level deep. Level is logged in                    the                     level element."
+13,Problem Name,"The name of the problem. Two problems with the same ""Problem Name"" are                    considered different ""problems"" by DataShop if the following logged values are not                    identical: problem name, context, tutor_flag (whether or not the problem                    or activity is tutored) and ""other"" field. These fields are logged in the                                        problem element."
+14,Problem View,"The number of times the student encountered the problem so far. This counter increases                    with each instance of the same problem. See ""Problem View"" in the ""By Student-Step"" table below."
+15,Problem Start Time,"If the problem start time is not given in the original log data, then it is set to the time                    of the last transaction of the prior problem. If there is no prior problem for the session,                    the time of the earliest transaction is used. Earliest transaction time is equivalent                    to the minimum transaction time for the earliest step of the problem. For more detail                    on how problem start time is determined, see Determining                    Problem Start Time."
+16,Step Name,"Formed by concatenating the ""selection"" and ""action"". Also see the                    glossary entry for ""step""."
+17,Attempt at Step,"As of this transaction, the current number of attempts toward the identified step."
+18,Outcome,"The tutor's evaluation of the student's attempt. For example, ""CORRECT"", ""INCORRECT"", or ""HINT"".                    This is logged in the                     action_evaluation element."
+19,Selection,"A description of the interface element(s) that the student selected or                    interacted with (for example, ""LowestCommonDenominatorCell""). This is logged in the                    event_descriptor                    element."
+20,Action,A description of the manipulation applied to the selection.
+21,Input,"The input the student submitted (e.g., the text entered, the text of a menu item or a combobox entry)."
+22,Feedback Text,"The body of a hint, success, or incorrect action message shown to the student.                    It is generally a text value, logged in the                     tutor_advice element."
+23,Feedback Classification,"The type of error (e.g., ""sign error"") or type of hint."
+24,Help Level,"In the case of hierarchical hints, this is the depth of the hint. ""1"", for example, is an initial hint,                    while ""3"" is the third hint."
+25,Total Num Hints,The total number of hints available. This is logged in the                    action_evaluation                    element.
+26,Condition Name,"The name of the condition (e.g., ""Unworked"")."
+27,Condition Type,"A condition classification (e.g., ""Experimental"", ""Control""); optional at the time of logging."
+28,KC (model_name),"The knowledge component for this transaction. It is a member of the knowledge component model                    named in the column header. One ""KC (model_name)"" column should appear in the export for each KC model                    in the dataset.                    "
+29,KC Category (model_name),"The knowledge component ""category"" logged by some tutors.                    It is a member of the knowledge component model named in the column header. One ""KC Category (model_name)""                    column should appear in the export for each KC model in the dataset."
+30,School,The name of the school where the student used the tutor to create this transaction.
+31,Class,The name of the class the student was in when he or she                    used the tutor to create this transaction.
+32,CF (custom_field_name),"The value of a custom field. This is usually information that did not fit into any of the                    other logging fields (i.e., any of the other columns), and so was logged in this                    special container.                    "
+33,Event Type,"Allowed values are ""assess"", ""instruct"" and ""assess_instruct"". Blank is also allowed.                    Only ""instruct"" and ""assess_instruct"" values are treated as learning opportunities.                    "

help_table2.csv

@@ -0,0 +1,23 @@
+,Field,Annotation
+0,Row,A row counter.
+1,Sample,"The sample that includes this step. If you select more than one sample to                    export, steps that occur in more than one sample will be duplicated in the export."
+2,Anon Student ID,The student that performed the step.
+3,Problem Hierarchy,The location in the curriculum hierarchy where this step occurs.
+4,Problem Name,The name of the problem in which the step occurs.
+5,Problem View,"The number of times the student encountered the problem so far. This counter increases                     with each instance of the same problem.                    Note that problem view increases regardless of whether or not the step was                    encountered in previous problem views. For example, a step can have a ""Problem View"" of                    ""3"", indicating the problem was viewed three times by this student, but that same step                    need not have been encountered by that student in all instances of the problem. If this                    number does not increase as you expect it to, it might be that DataShop has identified                    similar problems as distinct: two problems with the same ""Problem Name"" are considered                    different ""problems"" by DataShop if the following logged values are not identical:                    problem name, context, tutor_flag (whether or not the problem or activity is tutored)                    and ""other"" field. For more on the logging of these fields, see the  description of the                    ""problem"" element in the Guide to the Tutor Message Format. For more detail                    on how problem view is determined, see Determining                     Problem View."
+6,Step Name,"Formed by concatenating the ""selection"" and ""action"". Also see the glossary entry for ""step""."
+7,Step Start Time,"The step start time is determined one of three ways:                                            If it's the first step of the problem, the step start time is the same as the problem start time                        If it's a subsequent step, then the step start time is the time of the preceding transaction,                         if that transaction is within 10 minutes.                        If it's a subsequent step and the elapsed time between the previous transaction and the first                         transaction of this step is more than 10 minutes, then the step start time is set to null as it's                         considered an unreliable value.                                        For a visual example, see the Examples page."
+8,First Transaction Time,The time of the first transaction toward the step.
+9,Correct Transaction Time,"The time of the correct attempt toward the step, if there was one."
+10,Step End Time,The time of the last transaction toward the step.
+11,Step Duration (sec),"The elapsed time of the step in seconds, calculated by adding all of the                    durations for transactions that were attributed to the step. See the glossary entry for more detail. This column                    was previously labeled ""Assistance Time"". It differs from ""Assistance Time"" in that its                    values are derived by summing transaction durations, not finding the difference between                    only two points in time (step start time and the last correct attempt)."
+12,Correct Step Duration (sec),"The step duration if the first attempt for the step was correct. This might                    also be described as ""reaction time"" since it's the duration of time from the previous                    transaction or problem start event to the correct attempt. See the glossary entry for more detail.                    This column was previously labeled ""Correct Step Time (sec)""."
+13,Error Step Duration (sec),The step duration if the first attempt for the step was an error (incorrect                    attempt or hint request).
+14,First Attempt,"The tutor's response to the student's first attempt on the step. Example values                    are ""hint"", ""correct"", and ""incorrect""."
+15,Incorrects,Total number of incorrect attempts by the student on the step.
+16,Hints,Total number of hints requested by the student for the step.
+17,Corrects,Total correct attempts by the student for the step. (Only increases if the step                    is encountered more than once.)
+18,Condition,"The name and type of the condition the student is assigned to. In the case of a                    student assigned to multiple conditions (factors in a factorial design), condition names                    are separated by a comma and space. This differs from the transaction format, which                    optionally has ""Condition Name"" and ""Condition Type"" columns."
+19,KC (model_name),"(Only shown when the ""Knowledge Components"" option is selected.) Knowledge                    component(s) associated with the correct performance of this step. In the case of                     multiple KCs assigned to a single step, KC names are separated by two tildes (""~~"")."
+20,Opportunity (model_name),"(Only shown when the ""Knowledge Components"" option is selected.) An opportunity                    is the first chance on a step for a student to demonstrate whether he or she has learned                    the associated knowledge component. Opportunity number is therefore a count that                    increases by one each time the student encounters a step with the listed knowledge                    component. In the case of multiple KCs assigned to a single step, opportunity                    number values are separated by two tildes (""~~"") and are given in the same order as                     the KC names. Check here to see how opportunity count                    is computed when Event Type column is present in transaction data."
+21,Predicted Error Rate (model_name),"A hypothetical error rate based on the Additive Factor Model (AFM)                    algorithm. A value of ""1"" is a prediction that a student's first attempt will be an                    error (incorrect attempt or hint request); a value of ""0"" is a prediction that the                    student's first attempt will be correct. For specifics, see below ""Predicted Error Rate"" and how it's calculated.                     In the case of multiple KCs assigned to a single step, Datashop implements a compensatory sum across all of the KCs,                    thus a single value of predicted error rate is provided (i.e., the same predicted error rate for each KC assigned to a step).                     For more detail on Datashop's implementation for multi-skilled step, see                      Model Values page."

help_table3.csv

@@ -0,0 +1,22 @@
+,Field,Annotation
+0,Row,A row counter.
+1,Sample,"The sample that includes this problem. If you select more than one sample to export,                    problems that occur in more than one sample will be duplicated in the export.                    "
+2,Anon Student ID,The student that worked on the problem.
+3,Problem Hierarchy,The location in the curriculum hierarchy where this problem occurs.
+4,Problem Name,The name of the problem.
+5,Problem View,"The number of times the student encountered the problem so far. This counter                        increases with each instance of the same problem. See ""Problem View"" in the ""By                        Student-Step"" table above."
+6,Problem Start Time,"If the problem start time is not given in the original log data, then it is set                    to the time of the last transaction of the prior problem. If there is no prior problem                    for the session, the time of the earliest transaction is used. Earliest transaction time                    is equivalent to the minimum transaction time for the earliest step of the problem.                    For more detail on how problem start time is determined, see Determining                    Problem Start Time."
+7,Problem End Time,Derived from the maximum transaction time of the latest step of the problem.
+8,Latency (sec),"The amount of time the student spent on this problem. Specifically, the                        difference between the problem start time and the last transaction on this                        problem."
+9,Steps Missing Start Times,"The number of steps (from the student-step table) with ""Step Start Time""                        values of ""null"". "
+10,Hints,Total number of hints the student requested for this problem.
+11,Incorrects,Total number of incorrect attempts the student made on this problem.
+12,Corrects,Total number of correct attempts the student made for this problem.
+13,Avg Corrects,The total number of correct attempts / total number of steps in the problem.
+14,Steps,Total number of steps the student took while working on the problem.
+15,Avg Assistance Score,Calculated as (total hints requested + total incorrect attempts) / total steps.                    
+16,Correct First Attempts,Total number of correct first attempts made by the student for this problem.
+17,Condition,"The name and type of the condition the student is assigned to. In the case of a student                    assigned to multiple conditions (factors in a factorial design), condition names are                    separated by a comma and space. This differs from the transaction format, which optionally                    has ""Condition Name"" and ""Condition Type"" columns."
+18,KCs,Total number of KCs practiced by the student for this problem.
+19,Steps without KCs,Total number of steps in this problem (performed by the student) without an assigned KC.
+20,KC List,Comma-delimited list of KCs practiced by the student for this problem.