Update README.md
Browse files
README.md
CHANGED
|
@@ -18,8 +18,8 @@ This dataset consists of raw terminal recording logs in XML format, paired with
|
|
| 18 |
|
| 19 |
# Model 0: Terminal Boundary Extractor
|
| 20 |
|
| 21 |
-
Terminal recordings are
|
| 22 |
-
**Model 0** is specifically designed for this segmentation task.
|
| 23 |
|
| 24 |
## Generation Logic & Sliding Windows (Important)
|
| 25 |
|
|
@@ -45,4 +45,4 @@ Assume a recording has three sequential boundaries: `0.007194`, `21.987222`, and
|
|
| 45 |
2. **The Content:** This window actually covers two distinct events:
|
| 46 |
* **Event A:** Context between `0.007194` and `21.987222`.
|
| 47 |
* **Event B:** Context between `21.987222` and `37.178971`.
|
| 48 |
-
3. **The Target Output:** `21.987222` (the dividing boundary).
|
|
|
|
| 18 |
|
| 19 |
# Model 0: Terminal Boundary Extractor
|
| 20 |
|
| 21 |
+
Terminal recordings are long, continuous streams of text data. To make this data useful for downstream tasks, we must first break this stream into logical "events" (e.g., a single command execution and its resulting output).
|
| 22 |
+
**Model 0** is specifically designed for this segmentation task. The model is trained to identify the precise timestamp boundary where one event ends and the next begins.
|
| 23 |
|
| 24 |
## Generation Logic & Sliding Windows (Important)
|
| 25 |
|
|
|
|
| 45 |
2. **The Content:** This window actually covers two distinct events:
|
| 46 |
* **Event A:** Context between `0.007194` and `21.987222`.
|
| 47 |
* **Event B:** Context between `21.987222` and `37.178971`.
|
| 48 |
+
3. **The Target Output:** `21.987222` (the dividing boundary between Event 1 and Event 2).
|