|
1 | 1 | # Vert Ramp Affirmation |
2 | 2 |
|
| 3 | +## Background |
| 4 | +The Display Lab work is divided into two parts: User Centered Design and Feedback Production. |
| 5 | +User Centered Design produces: |
| 6 | +- Display Templates |
| 7 | +- Performance Data Annotations |
| 8 | +- ISRs (Intervention Situation Relations) |
| 9 | +- Performers |
| 10 | + |
| 11 | +Feedback Production consumes the above and produces: |
| 12 | +- Appropriate Performance Feedback Displays |
| 13 | + |
3 | 14 | ## Description |
4 | | -This project serves as the overview of the parts of the feedback summary pipeline. |
| 15 | +This project serves as the overview of the parts of the feedback production pipeline. |
5 | 16 | It contains stubs and mock ups to illustrate components of the intervention pipeline. |
6 | | -Specifically, the examples here demonstrate tailoring feedback for two recipients. |
| 17 | +Specifically, it has examples to demonstrate tailoring feedback for two recipients. |
7 | 18 |
|
8 | 19 | ## Outline |
9 | 20 | The steps (and associated projects) to the intervention generation pipeline: |
10 | | -1. Run data analyzer (bit-stomach) |
11 | | -1. Run candidate generator (candidate-smasher) |
12 | | -1. Run reasoner (think-pudding) |
13 | | -1. Generate performance summaries (relevant-fermenter) |
| 21 | +1. Data analsis for performance features |
| 22 | +1. Performance feedback candidate generation |
| 23 | +1. Reasoning about appropriateness of candidates |
| 24 | +1. Generate performance summaries using appropriate candidates |
14 | 25 |
|
15 | | -## Background |
16 | | -This work is a result of the persuit of building a feedback intervention generating system. |
17 | | -The project here attempts to construct a skeleton of the pipeline that will consider the performance data, |
18 | | -situation information, intervention situations, and intervention templates in order to produce appropriate performance feedback. |
| 26 | +## Definitions |
| 27 | +- Display Template: Code to generate plot or figure. |
| 28 | +- Annotations: Mathematical calculations to make assertions from performance data. |
| 29 | +- ISR: Computable representation of theory or domain expertise about what makes a performance display candidate appropriate. |
| 30 | +- Spek: top level data container for list of templates, list of ISRs, list of performers. |
19 | 31 |
|
20 | 32 | ## The Pipeline |
21 | | -### Data Analyzer |
| 33 | +### Data Analyzer (Bit Stomach) |
22 | 34 | - Inputs: |
23 | 35 | - Spek |
24 | 36 | - Performance Data |
25 | 37 | - Performance Data Analysis |
26 | 38 | - Outputs: |
27 | 39 | - Spek plus additional annotations |
28 | 40 |
|
29 | | -### Candidate Generator |
| 41 | +### Candidate Generator (Candidate Smasher) |
30 | 42 | - Inputs: |
31 | | - - Situation Plus |
| 43 | + - Spek Plus |
32 | 44 | - Templates |
33 | 45 | - Outputs: |
34 | 46 | - Candidates |
35 | 47 |
|
36 | | -### Reasoning Runner |
| 48 | +### Reasoning Runner (Think Pudding) |
37 | 49 | - Inputs: |
38 | 50 | - Candidates |
39 | 51 | - ISRs |
40 | 52 | - Outputs: |
41 | 53 | - Annotated Candidates |
42 | 54 |
|
43 | | -### Figure Generator |
| 55 | +### Figure Generator (Relevant Fermenter) |
44 | 56 | - Inputs: |
45 | 57 | - Annotated Candidates |
46 | 58 | - Performance Data |
47 | | - - Template Implementations |
| 59 | + - Templates |
48 | 60 | - Outputs: |
49 | 61 | - Performance Summary Figures |
50 | 62 |
|
51 | | - |
52 | | -## Example Data Description |
53 | | -The example data consists of five performers (a,b,c,d,e). |
54 | | -The first two, a & b, are used as the recipients of feedback. |
55 | | -Recipient 'a' has performance above the mastery threshold specified in the situation, and has decreasing recent performance. |
56 | | -Recipient 'b' has performance below the mastery level, and has increasing performance. |
57 | | - |
58 | | -## Machinery Explanation |
59 | | - |
60 | | -1. Data analyzer reads data & data annotation. |
61 | | -It makes inferences about each performer. |
62 | | -The result of these inferences are added to the situation. |
63 | | - ``` |
64 | | - performer_a has_mastery |
65 | | - performer_a has_decreasing_performance |
66 | | - performer_b has_increasing_performance |
67 | | - |
68 | | - performer_c has_mastery |
69 | | - ... |
70 | | - ``` |
71 | | -1. The candidate generator takes the situation and the performer specified as the recipient. |
72 | | -It creates intermediate constructs called candidate interventions by combining the situation with each intervention template. |
73 | | -1. The reasoner is loaded with the candidates and the intervention-situation-interaction. |
74 | | -The question posed to reasoner is essentially, "Which candidate interventions are acceptable interventions?" |
75 | | -From the linked data tripples that have been given, it will make inferences and return a result answering the question. |
76 | | - ``` |
77 | | - candidate_one acceptable_candidate |
78 | | - ``` |
79 | | -1. The figure geenrator takes the candidates, and passes the relevant data along to the matching template implementations. |
80 | | - |
81 | | -## Use |
82 | | - |
83 | | -1. Pass Situation, Performance Data, and Data Analyzer to Bit Stomach |
84 | | -2. Save & Examine resulting Situation Plus. |
85 | | - |
86 | | - |
87 | | - |
| 63 | +## Examples |
| 64 | +- [example one](ex_one.md) |
0 commit comments