# PRBench Task Configuration
# Each paper has one task.yaml that contains ALL task-specific information.
# Agent code is fully generic and reads everything from this file.

task_id: task_kolb_2003

# --- Paper Info ---
paper:
  title: "Hydrodynamic description of ultrarelativistic heavy-ion collisions"
  author: "Peter F. Kolb and Ulrich Heinz"
  doi: "nucl-th/0305084v2"
  year: 2003
  paper_file: "P.Kolb2003IdealHydro.md"           # relative to task dir

# --- Files ---
instruction_file: "instruction.md"       # what the white agent receives
metadata_file: "metadata.md"             # ground truth formulas + methodology (for grading)
ground_truth_data_dir: "data"            # directory with reference CSV files
ground_truth_code_dir: "reproduction"

# --- Input Files (copied to workspace for the white agent) ---
input_files:
  - "eosq.dat"                           # Equation of state table needed for simulation

# --- Expected Outputs (what the white agent must produce) ---
expected_outputs:
  analysis:
    - "reproduction/ANALYSIS.md"
  code:
    - "reproduction/hydro_core.py"
    - "reproduction/eos.py"
    - "reproduction/glauber.py"
    - "reproduction/fig2_glauber.py"
    - "reproduction/fig4_entropy_temp.py"
    - "reproduction/fig9_eccentricity.py"
  data:
    - "data/fig2_glauber.csv"
    - "data/fig4_R0fm.csv"
    - "data/fig4_R3fm.csv"
    - "data/fig4_R5fm.csv"
    - "data/fig9_eosi.csv"
    - "data/fig9_eosq.csv"

# --- Docker Environment ---
docker:
  image: "python:3.11-slim"
  memory_limit: "4g"
  timeout: 10800                         # 3 hours max
  pip_install:
    - numpy
    - scipy
    - matplotlib

# --- Grading Rubric (for model-judge) ---
grading:
  dimensions:
    - name: "methodology_understanding"
      weight: 0.20
      description: >
        Does the agent's ANALYSIS.md correctly describe the hydrodynamics methodology,
        Glauber model initialization, equation of state, and conservation equations?
        Compare against the ground truth in metadata.md.
    - name: "code_correctness"
      weight: 0.15
      description: >
        Are all required code files present? Does the code implement the core
        hydrodynamics simulation correctly (finite volume/difference schemes,
        Glauber initialization, EOS handling, conservation equations)?
    - name: "data_accuracy"
      weight: 0.50
      description: >
        How well do the generated data files match the ground truth reference data?
        Compare numerical values with ~20% relative tolerance for hydrodynamic quantities.
        Check column names, row counts, and value ranges.
    - name: "completeness"
      weight: 0.15
      description: >
        Are all 6 data files, all 6 code files, and the ANALYSIS.md present?
        Are the files non-trivial (not empty/placeholder)?

# --- Code-Only Evaluation Mode ---
code_only:
  instruction_suffix: |
    ## IMPORTANT: Code-Only Mode

    In this task you are in **code-only mode**. You must:
    1. Read and analyze the paper
    2. Write `reproduction/ANALYSIS.md` with your methodology analysis
    3. Implement ALL code files under `reproduction/`
    4. **DO NOT** run the simulation scripts or generate data files
    5. Focus on writing correct, complete, and well-structured code

    Your deliverables are ONLY the analysis document and code files.
    Do NOT produce any data files.

  expected_outputs:
    analysis:
      - "reproduction/ANALYSIS.md"
    code:
      - "reproduction/hydro_core.py"
      - "reproduction/eos.py"
      - "reproduction/glauber.py"
      - "reproduction/fig2_glauber.py"
      - "reproduction/fig4_entropy_temp.py"
      - "reproduction/fig9_eccentricity.py"

  grading:
    dimensions:
      - name: "methodology_understanding"
        weight: 0.25
        description: >
          Does ANALYSIS.md correctly describe the hydrodynamics methodology,
          Glauber model, EOS, and conservation equations?
      - name: "code_correctness"
        weight: 0.50
        description: >
          Read every code file carefully. Check whether the implementation is
          physically and algorithmically correct:
          - Finite volume/difference discretization
          - Glauber model for initial conditions
          - Equation of state implementation (ideal and tabulated)
          - Conservation equations and time evolution
          Compare against ground truth formulas in metadata.
      - name: "code_quality"
        weight: 0.10
        description: >
          Is the code well-structured, readable, and does it follow the
          expected file organization?
      - name: "completeness"
        weight: 0.15
        description: >
          Are all 6 code files and the ANALYSIS.md present and non-trivial?