From 34e143cd66860479c8284bd54e2ffa5618960b7b Mon Sep 17 00:00:00 2001 From: XianBW <36835909+XianBW@users.noreply.github.com> Date: Tue, 25 Feb 2025 23:06:41 +0800 Subject: [PATCH] fix: avoid try-except in ensemble eval prompts (#637) * avoid try-except in prompts * remove try-except limit from coder prompt * add no try-except criteria in ensemble eval --- rdagent/components/coder/data_science/ensemble/prompts.yaml | 3 ++- .../components/coder/data_science/raw_data_loader/prompts.yaml | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/rdagent/components/coder/data_science/ensemble/prompts.yaml b/rdagent/components/coder/data_science/ensemble/prompts.yaml index c9dacadd..544fcaab 100644 --- a/rdagent/components/coder/data_science/ensemble/prompts.yaml +++ b/rdagent/components/coder/data_science/ensemble/prompts.yaml @@ -90,7 +90,8 @@ ensemble_eval: {% endif %} ## Evaluation Criteria - You will be given the standard output (`stdout`) from the ensemble test and, if applicable, the workflow test. + - You will be given the standard output (`stdout`) from the ensemble test and, if applicable, the workflow test. + - Code should have no try-except blocks because they can hide errors. Please respond with your feedback in the following JSON format and order ```json diff --git a/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml b/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml index 2c88601d..b56ec586 100644 --- a/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml +++ b/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml @@ -329,6 +329,7 @@ data_loader_coder: ## Guidelines 1. Ensure that the dataset is loaded strictly from `/kaggle/input/`, following the exact folder structure described in the **Data Folder Description**, and do not attempt to load data from the current directory (`./`). + 3. You should avoid using logging module to output information in your generated code, and instead use the print() function. ## Output Format Please response the code in the following json format. Here is an example structure for the JSON output: