Aptlantis commited on
Commit
b77b42b
·
verified ·
1 Parent(s): d5076d1

Upload 3 files

Browse files
Files changed (4) hide show
  1. .gitattributes +1 -0
  2. README.md +59 -3
  3. train.jsonl +3 -0
  4. validation.jsonl +0 -0
.gitattributes CHANGED
@@ -57,3 +57,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
57
  # Video files - compressed
58
  *.mp4 filter=lfs diff=lfs merge=lfs -text
59
  *.webm filter=lfs diff=lfs merge=lfs -text
 
 
57
  # Video files - compressed
58
  *.mp4 filter=lfs diff=lfs merge=lfs -text
59
  *.webm filter=lfs diff=lfs merge=lfs -text
60
+ train.jsonl filter=lfs diff=lfs merge=lfs -text
README.md CHANGED
@@ -1,3 +1,59 @@
1
- ---
2
- license: mit
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # HolyC Dataset (TempleOS)
2
+
3
+ > **Source**: TempleOS Source Code & Terry Davis Explanations
4
+ > **Task**: Code Generation / Language Modeling
5
+
6
+ ## Overview
7
+ This dataset is a collection of **HolyC** code snippets paired with mock "Assistant" conversations, designed to train Large Language Models (LLMs) on the unique syntax and style of Terry Davis's HolyC programming language (used in TempleOS).
8
+
9
+ The dataset was constructed by matching Terry Davis's video explanations (transcribed or contextually linked) with the original source code modules from the TempleOS codebase.
10
+
11
+ ## Dataset Structure
12
+ The dataset consists of two JSONL files located in `datasets/HolyC/` (or the root `HolyC` directory depending on your setup).
13
+
14
+ ### Files
15
+ - `train.jsonl`: Training set (~10MB)
16
+ - `validation.jsonl`: Validation set (~2MB)
17
+
18
+ ### Schema
19
+ Each line is a JSON object representing a "training example" in a ChatML-like format.
20
+
21
+ | Field | Type | Description |
22
+ |-------|------|-------------|
23
+ | `text` | string | The raw HolyC source code block. |
24
+ | `formatted` | json-object | A structured conversation object containing `messages`. |
25
+
26
+ #### `formatted` Object Structure
27
+ The `formatted` field is designed for fine-tuning chat models. It typically follows this pattern:
28
+
29
+ ```json
30
+ {
31
+ "messages": [
32
+ {
33
+ "role": "system",
34
+ "content": "You are Terry Davis, the creator of TempleOS. Write HolyC code in your unique style."
35
+ },
36
+ {
37
+ "role": "user",
38
+ "content": "Please write some HolyC code."
39
+ },
40
+ {
41
+ "role": "assistant",
42
+ "content": "<ACTUAL_HOLYC_SOURCE_CODE>"
43
+ }
44
+ ]
45
+ }
46
+ ```
47
+
48
+ ## Provenance
49
+ - **Original Author**: Terry A. Davis
50
+ - **Collection Method**: Matching ~103 technical explanation videos with their corresponding 120,933 lines of TempleOS source code.
51
+ - **Goal**: To capture the specific dialect (HolyC) which includes features like:
52
+ - `U0` (Void)
53
+ - `I64` (64-bit Integer)
54
+ - Unparenthesized function calls
55
+ - JIT compilation directives (e.g., `#help_index`)
56
+ - DolDoc syntax integration
57
+
58
+ ## Future Work (Planned)
59
+ - **Revision History**: Extracting keystroke-level revisions from the `TempoSpage.org` and `Sheikhs Place` HTML archives to model the *process* of writing HolyC, not just the final output.
train.jsonl ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:e75746e9934ef42330f5f3aa2480b56e1b50ac6a4c708e162c69fae851ef81ef
3
+ size 20138090
validation.jsonl ADDED
The diff for this file is too large to render. See raw diff