Fix MMV axis name error and improve single-device support - Fixes #603#640
Open
nsrawat0333 wants to merge 2 commits intogoogle-deepmind:masterfrom
Open
Fix MMV axis name error and improve single-device support - Fixes #603#640nsrawat0333 wants to merge 2 commits intogoogle-deepmind:masterfrom
nsrawat0333 wants to merge 2 commits intogoogle-deepmind:masterfrom
Conversation
- Update aiohttp to address potential security vulnerabilities - Maintains compatibility with existing codebase - Addresses dependency security recommendations
…gle-deepmind#603 - Fix 'unbound axis name: i' error in cross-replica batch normalization - Update normalization.py to handle single-device vs multi-device contexts - Add run_mmv_eval.py wrapper script for robust evaluation - Update requirements.txt with compatible version specifications - Add comprehensive troubleshooting guide to README Addresses Issue google-deepmind#603: MMV's running problem - NameError: unbound axis name: i The error occurs because: 1. MMV uses cross-replica batch norm with axis name 'i' 2. This axis only exists in pmap (multi-device) contexts 3. Single-device runs don't have this axis defined Solutions provided: 1. Smart axis detection in normalization layer 2. Environment configuration script 3. Single-device mode forcing 4. Better dependency management 5. Comprehensive error handling Users can now run MMV on both single and multi-device setups without manual JAX configuration or code modifications.
|
Dooray! Failure Notice
Failure Notice
Your message sent to
***@***.***)
has failed to be delivered.
Please refer to the below for details.
* Recipient :
***@***.***)
* Sent time :
2025-08-11T04:16:03
* Subject :
[google-deepmind/deepmind-research] Fix MMV axis name error and improve single-device support - Fixes #603 (PR #640)
* Remote host said :
Your mail was denied from the receiver.
This message was sent from a notification-only address that cannot accept incoming email.
For more information, please contact ***@***.***
© Dooray!.
|
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
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.
Problem
Issue #603 reported
NameError: unbound axis name: iwhen running MMV (Self-Supervised MultiModal Versatile Networks). This error occurs because the model uses cross-replica batch normalization expecting a pmap axis named 'i', but this axis only exists in multi-device contexts, not single-device runs.Root Cause Analysis
The error happens in
normalization.pywhere:Solution
Implemented comprehensive fix for both single and multi-device scenarios:
🔧 Smart Normalization Layer (normalization.py)