feat(reward):api reward - #244
Conversation
Expose actor concurrency in the shared pool while keeping GPU rewards serial by default. Reuse the API client across concurrent calls and retry transient provider failures twice. Update existing tests and reward documentation.
Method1: Direct prompt, paper: https://arxiv.org/html/2510.18263v1#A3.SS1Batch / Reward ConfigBatch size=16 API rubric System PromptResult: API with little gain in reward,HPS with decent gain
Matches the result in the paper
ConclusionTry method 2 |
Method2: RubricRL, paper: https://arxiv.org/html/2511.20651v2Batch / Reward ConfigBatch size=16 API rubric System PromptGenerate and select 10 criteria per prompt. Score each criterion separately as 0/1, then average the 10 scores. Result: API and HPS both little gainCompleted 100 rollouts: https://wandb.ai/jig040-uc-san-diego/miles-diffusion-grpo/runs/q7uwzp0p First 20 vs. last 20 rollouts:
ConclusionNo clear evidence yet that rubric scoring outperforms direct scoring. NoteOne dataset prompt consistently triggered
Temporarily excluded this single prompt. All 1,600 training prompts passed rubric-generation preflight before this run. |





No description provided.