Fix local LIBERO rollout device on CUDA - #346
Open
rylinjames wants to merge 1 commit into
Open
rylinjames wants to merge 1 commit into
rylinjames wants to merge 1 commit into
Conversation
rylinjames
marked this pull request as ready for review
September 22, 2026 19:44
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change
Pass
verification_device="cuda"from the local LIBERO runner to the shared rollout. The policy and processors already run on CUDA; the rollout's default was CPU, which sent CPU bfloat16 image inputs into CUDA bfloat16 weights.Evidence
execution_target="linux-gpu"andruntime="local": appap-1VsOqQ03QMDKS2FWAPPUlM, LIBERO-10 task 0, seed 9301, one episode per arm.f1bb83de60fb4ed956ed6e25d528d037f09ecac11f7051141e6587e3d06c49e2; candidate report SHA-256:4c3f41f33c6832e43a69362fe156f199415d09ea812483393e92d4715b14cf18.7 passed), including an assertion that the local runner selects CUDA.This demonstrates the execution path and evidence generation; it does not claim that the policy passed LIBERO task success criteria.