Skip to content

Vllm w load maybe ? - #9

Merged
apaz-cli merged 3 commits into
mainfrom
vllm-w-load
Feb 27, 2025
Merged

Vllm w load maybe ?#9
apaz-cli merged 3 commits into
mainfrom
vllm-w-load

Conversation

@samsja

@samsja samsja commented Feb 27, 2025

Copy link
Copy Markdown
Member

No description provided.

Signed-off-by: Sami Jaghouar <sami.jaghouar@gmail.com>
Signed-off-by: Sami Jaghouar <sami.jaghouar@gmail.com>
Signed-off-by: Sami Jaghouar <sami.jaghouar@gmail.com>
@apaz-cli
apaz-cli merged commit a7d4c22 into main Feb 27, 2025
samsja pushed a commit that referenced this pull request Nov 11, 2025
samsja pushed a commit that referenced this pull request Dec 4, 2025
samsja pushed a commit that referenced this pull request Mar 30, 2026
@joanvelja joanvelja mentioned this pull request Apr 17, 2026
seanbell added a commit to clouddatalabs/scalerl-prime-rl that referenced this pull request Apr 26, 2026
User's explicit stance from the snowflake_poc_critique PrimeIntellect-ai#9: "We should
always train on full batches. If some groups are dropped from low
variance, we should sample more groups until we have signal."

Prior behavior: scheduler.generate_batch retried up to 3 times only if
ALL rollouts were filtered (n_trainable == 0). A partial filter that
left, say, 32 of 256 rollouts surviving proceeded as-is; n_trainable >
0 was the success threshold.

New behavior (default mode): keep sampling and accumulating ADDITIONAL
groups until the surviving cohort reaches batch_size, up to 20 attempts.
compute_advantages is idempotent (it recomputes from `reward`),
apply_filters resets is_filtered/filters at function entry, and
apply_batch_advantage_normalization's scaling is keyed off
compute_advantages's fresh output — re-running them on the cumulative
rollout list each iteration is therefore correct.

Soft-fail on max_attempts exhausted: train on whatever survived if
n_trainable > 0 (don't crash). Only the truly-empty case (zero
surviving) is fatal — that signals env-level corruption rather than
just slow-start dynamics. Paper-faithful mode
(paper_faithful_empty_batch=True) preserved: one attempt, no refill,
all-filtered → raise (matches ScaleRL §3.4 "drop, don't refill").

Bumped MAX_EMPTY_BATCH_ATTEMPTS 3 -> 20 to give the dynamic-sampling
path enough budget to converge on full-trainable batches during
slow-start (TB cold-start: docker pulls + first-rollout images) and
late-training "everything is easy" plateaus.

Tests pass: 295/295 orchestrator + configs + environments.
snimu added a commit that referenced this pull request Jun 4, 2026
- enabled_losses=None now validated as the full term list, so >1 echo term per
  env is caught at config time instead of at rollout time. [review #6]
- loss_overrides keys validated against `losses`; non-echo overrides rejected. [#7]
- warn (don't fail) when prompt-role echo is configured with renderer=None
  (MITO), where prompt_attribution is unavailable so it would silently no-op. [#8]
- token_export: add echo_mask/echo_weight columns + export sequences trained
  only via echo (gate on loss_mask OR echo_mask). [#9]
- doc notes: echo CE uses the rollout temperature (scale alpha to compensate,
  kept as-is); negative alpha is intentional (suppresses tokens). [#1, #10]
- tests for the new config validators.

Deferred to a follow-up pass (per the review): full per-sample primary routing /
rl-disable [#2b] + the <=1-primary validation it enables [#5], and the multi-run
losses fingerprint [#3]. Not run locally; ruff + py_compile clean.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mikasenghaas
mikasenghaas deleted the vllm-w-load branch August 5, 2026 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants