# 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_dimitrov_2000

# --- Paper Info ---
paper:
  title: "Chirality of Nuclear Rotation"
  author: "S. Dimitrov, T. Frauendorf, F. Dönau"
  doi: "10.1103/PhysRevLett.84.5732"
  year: 2000
  paper_file: "3-Dimitrov2000Phys.Rev.Lett.5732.md"

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

# --- Expected Outputs (what the white agent must produce) ---
expected_outputs:
  analysis:
    - "reproduce/ANALYSIS.md"
  code:
    - "reproduce/main.py"
    - "reproduce/tac3d_python.py"
    - "reproduce/ws_reference.py"
  data:
    - "data/pr134_final_reproduction_comparison.csv"
    - "data/pr134_final_reproduction_metrics.csv"
    - "data/pr134_table1_angles_j.csv"
    - "data/pr134_table1_transitions.csv"

# --- Docker Environment ---
docker:
  image: "python:3.11-slim"
  memory_limit: "4g"
  timeout: 21600                        # 6 hours (complex iterative TAC solver)
  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 TAC (Tilted Axis Cranking)
        methodology: hybrid spherical Woods-Saxon + Nilsson deformation coupling,
        fixed-gap pairing, branch-continuous theta/phi search, and explicit handling
        of the BC-crossing region to stay on the nu_h11/2 branch?
        Does it identify the Cwiok universal Woods-Saxon parameter set (V0=49.6 MeV,
        kappa=0.86, a=0.70 fm) and the final accepted parameters (eps2=0.182,
        gamma=27.0 deg, delta_p=1.10 MeV, delta_n=1.20 MeV)?
        Compare against metadata.md.
    - name: "code_correctness"
      weight: 0.25
      description: >
        Is the reproduction code physically and algorithmically correct? Check:
        Woods-Saxon single-particle spectrum uses the Cwiok universal parameter set
        (V0=49.6 MeV, kappa=0.86, a=0.70 fm, r0(P)=1.275 fm, r0(N)=1.347 fm,
        r0_so(P)=1.20 fm, r0_so(N)=1.310 fm, lambda_so(P)=36.0, lambda_so(N)=35.0),
        Nilsson deformation matrix elements correctly applied (eps2=0.182, gamma=27.0),
        fixed-gap pairing implemented (delta_p, delta_n), TAC self-consistency loop
        converges for each omega, branch continuity enforced across frequency chain,
        BC-crossing region handled explicitly. Penalize pure geometric toy models,
        wrong WS parameters, or independent point-by-point minimization with no
        branch tracking.
    - name: "data_accuracy"
      weight: 0.40
      description: >
        How well do the generated CSV files match the ground truth reference data?
        Key quantitative checks against data/pr134_final_reproduction_comparison.csv:
        RMS(J) <= 1.0 (accepted reference ~0.807), RMS(theta) <= 6 deg (reference
        ~5.016 deg), RMS(phi) <= 8 deg (reference ~6.782 deg). Physical trend checks:
        theta increases with omega, phi evolves from near-planar to large out-of-plane,
        J monotonically increasing. Worst-point check: omega=0.475 MeV should show
        the largest residual (dJ~+2.1 in accepted result). Non-monotonic J or phi
        collapsing to near-zero over multiple points indicates wrong branch.
    - name: "completeness"
      weight: 0.15
      description: >
        Are all expected CSV data files, the required code modules, and ANALYSIS.md
        present and non-trivial? Does `python main.py` run self-contained from
        reproduce/ without reading benchmark targets from data/?

# --- 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 `reproduce/ANALYSIS.md` with your methodology analysis
    3. Implement ALL code files under `reproduce/`
    4. **DO NOT** run the scripts or generate CSV 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 CSV data files.

  expected_outputs:
    analysis:
      - "reproduce/ANALYSIS.md"
    code:
      - "reproduce/main.py"
      - "reproduce/tac3d_python.py"
      - "reproduce/ws_reference.py"

  grading:
    dimensions:
      - name: "methodology_understanding"
        weight: 0.25
        description: >
          Does ANALYSIS.md correctly describe the hybrid WS+Nilsson TAC approach,
          fixed-gap pairing, branch-continuous angle search, and BC-crossing handling?
          Are the Cwiok universal WS parameters and final accepted parameters identified?
      - name: "code_correctness"
        weight: 0.50
        description: >
          Read every code file carefully. Check whether the implementation is
          physically and algorithmically correct:
          - Woods-Saxon potential with Cwiok universal parameters (V0=49.6 MeV, etc.)
          - Nilsson deformation coupling (eps2=0.182, gamma=27.0 deg)
          - Fixed-gap pairing (delta_p=1.10 MeV, delta_n=1.20 MeV)
          - TAC self-consistency: minimize Routhian over theta, phi for each omega
          - Branch-continuous search: track theta/phi solution across frequency chain
          - BC-crossing handled explicitly to stay on nu_h11/2 branch
          Compare against ground truth methodology in metadata.md. Flag any bugs.
      - name: "code_quality"
        weight: 0.10
        description: >
          Is the code well-structured, modular (WS solver, TAC solver, pairing,
          branch-tracking as separate concerns), and readable?
      - name: "completeness"
        weight: 0.15
        description: >
          Are the required code modules and ANALYSIS.md present and non-trivial?