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: rdagent/scenarios/data_science/proposal/exp_gen/prompts_v2.yaml
+13-2Lines changed: 13 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -265,6 +265,7 @@ hypothesis_select:
265
265
system: |-
266
266
You are a Kaggle Grandmaster with deep expertise in model evaluation and decision making. Based on the given example, please select the most appropriate hypothesis from the candidates.
267
267
These hypotheses are sourced from `model/data/feature/workflow`. Choose the one that best matches the intent or logic of the prompt.
268
+
Alternatively, if you determine that ensemble is the best option, you may propose a **ensemble hypothesis** (not present in the candidates), as long as it aligns with the runtime and training constraints.
268
269
You are given the following hypothesis candidates:
269
270
{{ hypothesis_candidates }}
270
271
If multiple hypotheses seem reasonable, select the one that is most robust or consistent with Previous Experiments and Feedbacks, pay attention to the runtime of each loop.
@@ -274,9 +275,19 @@ hypothesis_select:
274
275
### 1. Ensemble Core Principle
275
276
Your goal is not just to tune individual models, but to build an **effective ensemble**. Make design decisions that lead to **strong overall ensemble performance**, not just strong base models.
276
277
Please note: you are operating under a time budget dedicated to ensemble training of {{res_time}} seconds, and the maximum allowed time is {{ensemble_timeout}} seconds.
277
-
{{use_ratio}}% of the total ensemble time has been used. As this surpasses the 70% threshold, you are advised to shift focus toward optimizing the ensemble component rather than continuing with model, data, feature, or workflow exploration.
278
-
Please take the remaining {{res_time}} seconds to carefully consider and design the most reasonable and optimal ensemble hypothesis based on your current progress.
278
+
{{use_ratio}}% of the total ensemble time has been used.
279
+
Please note: you are operating under a time budget dedicated to ensemble training of {{res_time}} seconds, and the maximum allowed time is {{ensemble_timeout}} seconds.
280
+
{{use_ratio}}% of the total ensemble time has been used.
281
+
282
+
{% if use_ratio >= 70 %}
283
+
As this exceeds the 70% threshold, you are advised to **stop exploring individual model/feature/workflow hypotheses**.
284
+
Instead, please focus on **designing a final ensemble hypothesis** that effectively leverages and combines the most promising components based on the historical performance of your previous trials.
285
+
Use insights from earlier experiments (including successful models, valuable features, and workflows) to create a robust ensemble that captures their collective strength.
286
+
{% else %}
287
+
Please continue selecting the most promising hypothesis from the candidates to enhance your current code.
288
+
{% endif %}
279
289
290
+
Please take the remaining {{res_time}} seconds to carefully consider and design the most reasonable and optimal ensemble hypothesis based on your current progress.
280
291
Assume training a single model takes about 1 hour. For example, if you have roughly twice that time left, you can try training multiple models with different random seeds or data splits to reuse time effectively.
281
292
If you have more time, you might consider training a multi-fold ensemble. Use your judgment to decide how many folds or seeds fit within your remaining time budget.
0 commit comments