> For the complete documentation index, see [llms.txt](https://docs.projectassessment.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectassessment.app/data-and-estimation.md).
# Data and Estimation
### Introduction and Data Files
In education, we often grade artifacts using a rubric. Rubrics are made up of a series of rows grading some aspect of the artifact's quality. For instance, consider the following rubric row grading the quality of a literature review.
| k=0 | k=1 | k=2 | k=3 |
| ------------------------------------ | ---------------------------------------------------------------------------- | ------------------------------------------------------- | ----------- |
| Did not meet any of the requirements | The chosen topic was on-topic for the course, but the literature was lacking | The literature review was complete but contained errors | Full credit |
In this example there are four possible boxes starting with no credit and ending with full credit. One can think of each one of these boxes as a *trial.* That is, if a student's paper was scored in the second box from the left, that means the paper *survived* one trial. If they scored in the third box from the left, they *survived* two trials. The final box indicates they survived at least three trials. However, they could have survived more; some students will perform (or could perform) substantially better than others who earned full credit (in essence, the top box is censored).
The number of successful trials (indicated with the "k" values in the header), translates to the data you can provide this web application. Here is an example table:
| k | bound | student | rubric |
| - | ----- | ------- | ------ |
| 3 | 3 | s1 | 1 |
| 3 | 3 | s1 | 2 |
| 2 | 3 | s1 | 3 |
| 2 | 3 | s2 | 1 |
| 2 | 3 | s2 | 2 |
| 1 | 3 | s2 | 3 |
Here "k" is the number of trials, or the student's score, on a given rubric row. "Bound" is the maximum number of observed trials or maximum possible score on a given rubric row. "Student" and "rubric" are identifiers for the students and rubric rows. In the example above numbers are used to identify students and rubric rows. However, that is not necessary. The identifiers simply need to be unique to each student/rubric.
### Example Data Files
To get you started, there are three sample data files available: [small.csv](https://projectassessment.app/data/small.csv) (5 students, 3 rubric rows), [medium.csv](https://projectassessment.app/data/medium.csv) (24 students, 3 rubric rows), [large.csv](https://projectassessment.app/data/large.csv) (62 students, 8 rubric rows). A [zip file](https://projectassessment.app/data/data.zip) containing all three CSV files is also available. To start exploring the program, drag one of these files to the empty box on the [ProjectAssessment.App](https://projectassessment.app). When you start making your own files, make sure to save them as a [CSV -- a format available to all spreadsheet applications](https://en.wikipedia.org/wiki/Comma-separated_values).
If your institution uses Canvas, you might be able to create this file automatically. [Read more about this possibility.](/canvas-and-converter-app.md)
### Mapping Data File Columns for Analysis
In the above image, the application is asking for a mapping between the columns in the provided file and their meaning. If you use the columns "k", "bound", "student", and "rubric" these will be mapped for you. Once the mapping is correct, click "Save mapping." This will start the estimation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.projectassessment.app/data-and-estimation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.