mirror of
https://github.com/NicolasBohn/NexQuant.git
synced 2026-07-28 16:07:46 +00:00
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
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -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:
|
||||
|
||||
Reference in New Issue
Block a user