From 21dfcdabf8930ca57ad6a2faa68a1cc14b0087b8 Mon Sep 17 00:00:00 2001
From: Yuante Li <104308117+WinstonLiyt@users.noreply.github.com>
Date: Wed, 26 Feb 2025 17:52:30 +0800
Subject: [PATCH] fix: clarify cross_validation (#644)

---
 .../coder/data_science/raw_data_loader/prompts.yaml          | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

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 0a952cd8..21629690 100644
--- a/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml
+++ b/rdagent/components/coder/data_science/raw_data_loader/prompts.yaml
@@ -262,8 +262,9 @@ spec:
           - It should be called before dataset splitting.
 
         3. Dataset Splitting
-          - The dataset returned by `load_data` is not split into training and testing sets, so the dataset splitting should happen after calling `feat_eng`.
-          - Use cross-validation if possible, as it provides a more robust evaluation of the model's performance.
+          - The dataset returned by `load_data` is not pre-split. After calling `feat_eng`, split the data into training and test sets.
+          - If feasible, apply cross-validation on the training set (`X_transformed`, `y_transformed`) to ensure a reliable assessment of model performance.
+          - Keep the test set (`X_test_transformed`) unchanged, as it is only used for generating the final predictions.
 
         4. Submission File:
           - Save the final predictions as `submission.csv`, ensuring the format matches the competition requirements (refer to `sample_submission` in the Folder Description for the correct structure).