Remove redundant evaluator-boundary prompt wording
Browse files- tasks/computing_math/dit_pipeline_cfg_alignment_fid_256_001/base/input/task_prompt.md +0 -2
- tasks/education_info/homework_grading_numerical_pdes_instance_02/base/input/TASK_PROMPT.md +0 -1
- tasks/life_sciences/spatial_transcriptomics_spatial_domain_identification/base/input/task_prompt.md +0 -2
- tasks/visual_media/compress_3dgs_scene_ply/base/input/task_prompt.md +0 -2
tasks/computing_math/dit_pipeline_cfg_alignment_fid_256_001/base/input/task_prompt.md
CHANGED
|
@@ -20,5 +20,3 @@ You are repairing a standalone `pipeline_dit.py` implementation for a Diffusers-
|
|
| 20 |
Write exactly one file:
|
| 21 |
|
| 22 |
`output/pipeline_dit.py`
|
| 23 |
-
|
| 24 |
-
Do not rely on hidden evaluator files while solving.
|
|
|
|
| 20 |
Write exactly one file:
|
| 21 |
|
| 22 |
`output/pipeline_dit.py`
|
|
|
|
|
|
tasks/education_info/homework_grading_numerical_pdes_instance_02/base/input/TASK_PROMPT.md
CHANGED
|
@@ -22,7 +22,6 @@ Your task:
|
|
| 22 |
|
| 23 |
Rules:
|
| 24 |
- Treat `input/` as read-only.
|
| 25 |
-
- Do not read or modify evaluator-only files under `reference/`.
|
| 26 |
- Keep student IDs stable across every output file.
|
| 27 |
- Use the task-local `/media/user/data/agenthle/education/homework_grading_numerical_pdes_instance_02/base/software/python` wrapper if you want to script the grading workflow (it `exec`s the preinstalled system Python).
|
| 28 |
- Write final deliverables only under `output/`.
|
|
|
|
| 22 |
|
| 23 |
Rules:
|
| 24 |
- Treat `input/` as read-only.
|
|
|
|
| 25 |
- Keep student IDs stable across every output file.
|
| 26 |
- Use the task-local `/media/user/data/agenthle/education/homework_grading_numerical_pdes_instance_02/base/software/python` wrapper if you want to script the grading workflow (it `exec`s the preinstalled system Python).
|
| 27 |
- Write final deliverables only under `output/`.
|
tasks/life_sciences/spatial_transcriptomics_spatial_domain_identification/base/input/task_prompt.md
CHANGED
|
@@ -12,8 +12,6 @@ Visible inputs:
|
|
| 12 |
- `software/uv`
|
| 13 |
- `software/python3.12`
|
| 14 |
|
| 15 |
-
The task is unsupervised. Manual layer annotations are evaluator-only and are not available as solve-time input.
|
| 16 |
-
|
| 17 |
Recommended setup:
|
| 18 |
1. Work on Linux.
|
| 19 |
2. If you need the spatial transcriptomics Python stack, install it with:
|
|
|
|
| 12 |
- `software/uv`
|
| 13 |
- `software/python3.12`
|
| 14 |
|
|
|
|
|
|
|
| 15 |
Recommended setup:
|
| 16 |
1. Work on Linux.
|
| 17 |
2. If you need the spatial transcriptomics Python stack, install it with:
|
tasks/visual_media/compress_3dgs_scene_ply/base/input/task_prompt.md
CHANGED
|
@@ -15,8 +15,6 @@ Visible files:
|
|
| 15 |
Important visibility rule:
|
| 16 |
- The filenames for the holdout views are public and listed in `input/scene_manifest.json`.
|
| 17 |
- The JPG files for those holdout names under visible `input/scene/images/` are placeholders only.
|
| 18 |
-
- Scoring uses hidden evaluator-only ground-truth images, not the visible placeholders.
|
| 19 |
-
|
| 20 |
What to produce:
|
| 21 |
- `output/point_cloud_30000_compressed.ply`
|
| 22 |
- `output/rendered_test_views/<holdout filename>.jpg` for every holdout name in the manifest
|
|
|
|
| 15 |
Important visibility rule:
|
| 16 |
- The filenames for the holdout views are public and listed in `input/scene_manifest.json`.
|
| 17 |
- The JPG files for those holdout names under visible `input/scene/images/` are placeholders only.
|
|
|
|
|
|
|
| 18 |
What to produce:
|
| 19 |
- `output/point_cloud_30000_compressed.ply`
|
| 20 |
- `output/rendered_test_views/<holdout filename>.jpg` for every holdout name in the manifest
|