Skip to content

Fix block dimensions consistency#4

Draft
igor-holt wants to merge 1 commit intomainfrom
fix-block-dims-consistency-10423846750295347954
Draft

Fix block dimensions consistency#4
igor-holt wants to merge 1 commit intomainfrom
fix-block-dims-consistency-10423846750295347954

Conversation

@igor-holt
Copy link
Owner

Fixed inconsistency where single-block scalar states were not expanded to have a leading dimension. Removed special handling for len(collected) == 1 to always use _stack. Added regression test.


PR created automatically by Jules for task 10423846750295347954 started by @igor-holt

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules
Copy link

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link

Summary of Changes

Hello @igor-holt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an inconsistency in how block dimensions were handled, specifically for scalar states within single blocks. By standardizing the dimension expansion, it ensures that all states, regardless of the number of blocks, maintain a consistent shape, thereby improving the robustness and predictability of the block_management system.

Highlights

  • Dimension Consistency: Ensured that single-block scalar states are consistently expanded to have a leading dimension (e.g., () to (1,)) to match multi-block states.
  • Simplified Logic: Removed special conditional handling for single-block collections in block_state_to_global, now always using jax.tree.map(_stack, *collected).
  • Regression Test: Added a new test file (tests/test_block_management_scalar.py) to verify the correct shape expansion for scalar states in both single and multi-block scenarios.
Changelog
  • tests/test_block_management_scalar.py
    • Added a new test file test_block_management_scalar.py to validate the shape of scalar states in single and multi-block configurations.
  • thrml/block_management.py
    • Modified the block_state_to_global function to remove special handling for single-element collected lists, ensuring jax.tree.map(_stack, *collected) is always used.
Activity
  • PR created automatically by Jules for task 10423846750295347954, started by @igor-holt.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses an inconsistency in how scalar states are handled for single blocks. By removing the special case for a single collected state in block_state_to_global and always using jax.tree.map with _stack, the code now correctly expands scalar states to have a leading dimension, making their shape (1,) instead of (). This improves consistency with multi-block states which are stacked into shapes like (N,). The change simplifies the code and removes a TODO comment. A new regression test has been added to verify this fix, covering both single and multi-block scenarios. The implementation is clean and the test is comprehensive. This is a great improvement.

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