You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+98-7Lines changed: 98 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,21 +73,112 @@ Utilize the capability and the corresponding subject LLM score to select or gene
73
73
```bash
74
74
python -m src.run_lbo
75
75
```
76
-
77
76
### Agentic Generation Scripts
78
77
79
-
Generate areas, capabilities, and tasks using multi-agent debate systems. Configure parameters in `src/cfg/agentic_config.yaml`.
78
+
These scripts implement the multi-agent debate workflow for automated generation of areas, capabilities, tasks, and solutions.
79
+
All configurable parameters are defined in `src/cfg/agentic_config.yaml`.
80
+
81
+
#### Understanding Pipeline Tags
82
+
83
+
The pipeline uses **auto-generated tags** to organize outputs from each step. Understanding how tags work is essential for running the pipeline:
84
+
85
+
-**Tag Format**: Tags are automatically generated timestamps in the format `_YYYYMMDD_HHMMSS` (e.g., `_20251104_143022`)
86
+
-**Auto-Generation**: When you run a step (e.g., Generate Areas), the script automatically creates a tag and includes it in the output path
87
+
-**Finding Tags**: After running a step, check the console output or the output directory to see the generated tag. The tag appears in the file path where outputs are saved
88
+
-**Using Tags**: To run the next step in the pipeline, you need to specify the tag from the previous step's output:
89
+
- Step 2 (Generate Capabilities) needs `areas_tag` from Step 1
90
+
- Step 3 (Generate Tasks) needs `capabilities_tag` from Step 2
91
+
- Step 4 (Generate Solutions) needs `tasks_tag` from Step 3
80
92
93
+
**Example Workflow**:
94
+
1. Run `python -m src.agentic_area_generator` → outputs to `.../areas/_20251104_143022/areas.json`
95
+
2. Use the tag `_20251104_143022` in the next step:
-`pipeline_tags.areas_tag` specifies which set of areas to use when generating capabilities. This should be the `<areas_tag>` from the output of Step 1 (Generate Areas).
131
+
-`pipeline_tags.resume_capabilities_tag` (optional) resumes a previous capability generation run.
132
+
133
+
This step auto-generates a new tag for the capabilities output.
-`pipeline_tags.capabilities_tag` specifies which set of capabilities to use when generating tasks. This should be the `<capabilities_tag>` from the output of Step 2 (Generate Capabilities).
152
+
-`pipeline_tags.resume_tasks_tag` (optional) resumes a previous task generation run.
153
+
154
+
This step auto-generates a new tag for the tasks output.
0 commit comments