docs

README.md

@@ -96,19 +96,19 @@ dataset_info:
 
 # About the Dataset
 
-The source code used to generate the dataset can be found on 
+The source code used to generate the dataset can be found on
 [GitHub](https://github.com/alexjercan/bug-detection/tree/master/bugnet)
 
-The dataset is based on the [CodeNet project](https://github.com/IBM/Project_CodeNet) 
-and contains Python and C++ code submissions for online coding competitions. The data 
-is obtained by selecting consecutive attempts of a single user that resulted in fixing a 
-buggy submission. Thus the data is represented by code pairs and annotated by the diff 
-and error of each changed instruction. We have already tokenized all the source code 
+The dataset is based on the [CodeNet project](https://github.com/IBM/Project_CodeNet)
+and contains Python and C++ code submissions for online coding competitions. The data
+is obtained by selecting consecutive attempts of a single user that resulted in fixing a
+buggy submission. Thus the data is represented by code pairs and annotated by the diff
+and error of each changed instruction. We have already tokenized all the source code
 files and kept the same format as in the original dataset.
 
-The upgrade made compared to CodeNetPy is that we only keep one line errors. 
-This means that the task of bug detection and repair will be easier to manage. 
-We also removed all the files that fail on linters, so that we are focusing only 
+The upgrade made compared to CodeNetPy is that we only keep one line errors.
+This means that the task of bug detection and repair will be easier to manage.
+We also removed all the files that fail on linters, so that we are focusing only
 on bugs that cannot be identified easily.
 
 The resulting dataset file will be a csv with the following columns:
@@ -124,6 +124,7 @@ The resulting dataset file will be a csv with the following columns:
 - `j2`: End of the change in the accepted source (not inclusive; for `delete` we have `j1 == j2`)
 - `error`: The error that was obtained running the buggy source code on the input/output examples
 - `stderr`: The full output of stderr of running the buggy source code on the input/output examples
+- `stdout`: The full output of stdout of running the buggy source code on the input/output examples
 - `description`: The problem statement in html format
 - `input`: The input for the test case
-- `output`: The output for the test case
+- `output`: The output for the test case