Update README.md
Browse files
README.md
CHANGED
|
@@ -3,69 +3,28 @@ task_categories:
|
|
| 3 |
- text-classification
|
| 4 |
|
| 5 |
---
|
| 6 |
-
# AutoTrain Dataset for project: github-emotion-
|
| 7 |
|
| 8 |
## Dataset Description
|
| 9 |
|
| 10 |
Dataset used in the paper: Imran et al., ["Data Augmentation for Improving Emotion Recognition in Software Engineering Communication"](https://arxiv.org/abs/2208.05573), ASE-2022.
|
| 11 |
|
| 12 |
-
|
| 13 |
-
|
| 14 |
-
The BCP-47 code for the dataset's language is unk.
|
| 15 |
|
| 16 |
## Dataset Structure
|
| 17 |
|
| 18 |
-
|
| 19 |
-
|
| 20 |
-
A sample from this dataset looks as follows:
|
| 21 |
-
|
| 22 |
-
```json
|
| 23 |
-
[
|
| 24 |
-
{
|
| 25 |
-
"feat_id": 704844644,
|
| 26 |
-
"text": "This change doesn't affect anything but makes the code more clear. If you look at the line about, `currentUrlTree` is set to `urlAfterRedirects`.",
|
| 27 |
-
"feat_Anger": 0,
|
| 28 |
-
"feat_Love": 0,
|
| 29 |
-
"feat_Fear": 0,
|
| 30 |
-
"feat_Joy": 1,
|
| 31 |
-
"feat_Sadness": 0,
|
| 32 |
-
"target": 0
|
| 33 |
-
},
|
| 34 |
-
{
|
| 35 |
-
"feat_id": 886568180,
|
| 36 |
-
"text": "Thanks very much for your feedback [USER] Your point is totally fair. My intention was to highlight that camelCase or dash-case class names are perfectly fine to use in Angular templates. Most people, especially beginners, do not know that and end up using the `ngClass` directive. Do you think that rewording the alert towards that direction would make sense?",
|
| 37 |
-
"feat_Anger": 0,
|
| 38 |
-
"feat_Love": 1,
|
| 39 |
-
"feat_Fear": 0,
|
| 40 |
-
"feat_Joy": 0,
|
| 41 |
-
"feat_Sadness": 0,
|
| 42 |
-
"target": 0
|
| 43 |
-
}
|
| 44 |
-
]
|
| 45 |
-
```
|
| 46 |
|
| 47 |
-
|
| 48 |
|
| 49 |
-
|
| 50 |
|
| 51 |
-
```json
|
| 52 |
-
{
|
| 53 |
-
"feat_id": "Value(dtype='int64', id=None)",
|
| 54 |
-
"text": "Value(dtype='string', id=None)",
|
| 55 |
-
"feat_Anger": "Value(dtype='int64', id=None)",
|
| 56 |
-
"feat_Love": "Value(dtype='int64', id=None)",
|
| 57 |
-
"feat_Fear": "Value(dtype='int64', id=None)",
|
| 58 |
-
"feat_Joy": "Value(dtype='int64', id=None)",
|
| 59 |
-
"feat_Sadness": "Value(dtype='int64', id=None)",
|
| 60 |
-
"target": "ClassLabel(num_classes=2, names=['0', '1'], id=None)"
|
| 61 |
-
}
|
| 62 |
-
```
|
| 63 |
|
| 64 |
### Dataset Splits
|
| 65 |
|
| 66 |
-
This dataset is split into a train and
|
| 67 |
|
| 68 |
| Split name | Num samples |
|
| 69 |
| ------------ | ------------------- |
|
| 70 |
| train | 1600 |
|
| 71 |
-
|
|
|
|
|
| 3 |
- text-classification
|
| 4 |
|
| 5 |
---
|
| 6 |
+
# AutoTrain Dataset for project: github-emotion-love
|
| 7 |
|
| 8 |
## Dataset Description
|
| 9 |
|
| 10 |
Dataset used in the paper: Imran et al., ["Data Augmentation for Improving Emotion Recognition in Software Engineering Communication"](https://arxiv.org/abs/2208.05573), ASE-2022.
|
| 11 |
|
| 12 |
+
This is an annotated dataset of 2000 GitHub comments. Six basic emotions are annotated. They are Anger, Love, Fear, Joy, Sadness and Surprise. This repository contains annotations of all emotions.
|
|
|
|
|
|
|
| 13 |
|
| 14 |
## Dataset Structure
|
| 15 |
|
| 16 |
+
Dataset is in CSV format. The columns are:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 17 |
|
| 18 |
+
```id, modified_comment, Anger, Love, Fear, Joy, Sadness, Surprise```
|
| 19 |
|
| 20 |
+
Here, `id` is a unique id for each comment. Each emotion is marked as 1 or 0.
|
| 21 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 22 |
|
| 23 |
### Dataset Splits
|
| 24 |
|
| 25 |
+
This dataset is split into a train and test split. The split sizes are as follows:
|
| 26 |
|
| 27 |
| Split name | Num samples |
|
| 28 |
| ------------ | ------------------- |
|
| 29 |
| train | 1600 |
|
| 30 |
+
| test | 400 |
|