Datasets:
Record the duplicate rows upstream leaves in the fs training split
Browse files
README.md
CHANGED
|
@@ -162,6 +162,13 @@ pinned revisions. It needs `rdkit` and `pandas`.
|
|
| 162 |
- Reaction subtasks are keyed on the reaction the question names, not on every
|
| 163 |
molecule it mentions. Common solvents and reagents recur throughout both
|
| 164 |
splits and keying on them would empty the training set for no gain.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 165 |
- Removal is reported, never silent. If a subtask's training split is too small
|
| 166 |
after removal to be useful, the table above says so before you train on it.
|
| 167 |
|
|
|
|
| 162 |
- Reaction subtasks are keyed on the reaction the question names, not on every
|
| 163 |
molecule it mentions. Common solvents and reagents recur throughout both
|
| 164 |
splits and keying on them would empty the training set for no gain.
|
| 165 |
+
- Duplicates *inside* the training split are left alone, because the rule here
|
| 166 |
+
is about the test split. One place has many: upstream `fs_major_product.json`
|
| 167 |
+
holds 2,788 rows but only 1,164 distinct ones, so 1,624 rows of the `fs`
|
| 168 |
+
training split are byte-identical copies of another row, and `id` is not
|
| 169 |
+
unique there. Every other file is clean. Drop them with
|
| 170 |
+
`train.to_pandas().drop_duplicates()` if repeated rows would skew your
|
| 171 |
+
training mixture.
|
| 172 |
- Removal is reported, never silent. If a subtask's training split is too small
|
| 173 |
after removal to be useful, the table above says so before you train on it.
|
| 174 |
|