Skip to content

fix(block_balance): sequential stages and success only for a free-standing balanced beam - #10

Merged
juelg merged 2 commits into
masterfrom
fix/block-balance-success-check
Oct 30, 2026
Merged

juelg merged 2 commits into
masterfrom
fix/block-balance-success-check

Conversation

@juelg

@juelg juelg commented Oct 27, 2026

Copy link
Copy Markdown
Contributor
  • Stages advance strictly in order (n -> n+1); later predicates can no longer skip stages
  • beam_on_cube is checked at the current step instead of being latched
  • Success requires the beam and both rectangles to touch only task bodies (no table/robot support)
  • Previously a beam lying flat on the table with both rectangles on it counted as success
  • Calibrated on 93 sim demos: 54/54 successful demos still reach stage 5
  • Adds src/tests/test_block_balance_stage.py (old code fails 3/4 tests)

juelg added 2 commits October 29, 2026 23:30
…nding balanced beam

Stages advance one at a time, so a stage can no longer be reached without the
ones before it. beam_on_cube is evaluated at the current step instead of being
latched, and success requires the beam and both rectangles to touch only each
other and the cube (not the table or a robot). Previously a beam that touched the
cube once and then lay flat on the table with both rectangles on it counted as
balanced. All 54 successful sim demos still reach the final stage.
@juelg
juelg force-pushed the fix/block-balance-success-check branch from 4e9c077 to 1d7a33b Compare October 30, 2026 06:30
@juelg
juelg merged commit e5f7a49 into master Oct 30, 2026
1 check passed
@juelg
juelg deleted the fix/block-balance-success-check branch October 30, 2026 06:35
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.

1 participant