Fix DM21 functionals incorrectly defaulting to DM21M (#589)#647
Open
nsrawat0333 wants to merge 3 commits intogoogle-deepmind:masterfrom
Open
Fix DM21 functionals incorrectly defaulting to DM21M (#589)#647nsrawat0333 wants to merge 3 commits intogoogle-deepmind:masterfrom
nsrawat0333 wants to merge 3 commits intogoogle-deepmind:masterfrom
Conversation
- Update aiohttp to address potential security vulnerabilities - Maintains compatibility with existing codebase - Addresses dependency security recommendations
…ation - Created comprehensive solution for convenient processed WikiText-103 dataset access - Added two complementary tools: * setup_wikitext103_dataset.py: Lightweight, dependency-free solution * create_processed_wikitext103_dataset.py: Full-featured with WikiGraphs integration - Features: * One-command dataset download and processing * Automatic vocabulary creation with configurable thresholds * Comprehensive validation and integrity checks * Ready-to-use examples and documentation * Cross-platform compatibility - Created WIKITEXT103_SETUP_GUIDE.md with detailed usage instructions - Updated main README.md with quick start section - Addresses 4+ year old Issue google-deepmind#40 from @cp-pc Files added: - wikigraphs/scripts/setup_wikitext103_dataset.py (400+ lines) - wikigraphs/scripts/create_processed_wikitext103_dataset.py (600+ lines) - wikigraphs/WIKITEXT103_SETUP_GUIDE.md (comprehensive guide) - ISSUE_40_SOLUTION.md (GitHub issue response) This solution transforms WikiText-103 setup from complex multi-step process to simple one-command operation, significantly improving researcher productivity.
- Enhanced TensorFlow session isolation between different DM21 functionals - Fixed graph context issues causing all functionals to default to DM21M - Added proper cleanup methods to prevent resource leaks - Added error handling and validation for model loading - Includes comprehensive test suite and documentation Technical changes: - Modified NeuralNumInt.__init__ to explicitly bind sessions to graphs - Added __del__ and close() methods for proper resource management - Enhanced _build_graph with better error handling and validation - Added test script to validate fix and demonstrate correct usage Fixes: google-deepmind#589
|
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-11T06:13:49
* Subject :
[google-deepmind/deepmind-research] Fix DM21 functionals incorrectly defaulting to DM21M (#589) (PR #647)
* 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.
Summary
Fixes Issue #589 where all DM21 functionals (DM21, DM21MC, DM21MU) were incorrectly defaulting to DM21M regardless of which functional was specified by users.
Problem
Users reported that when attempting to use different DM21 functionals in their neural network research, all functionals would run as DM21M instead of the requested functional (DM21, DM21MC, or DM21MU). This prevented researchers from accessing the full suite of DM21 density functionals.
Root Cause
The issue was caused by improper TensorFlow session and graph isolation between different
NeuralNumIntinstances:Solution
1. Enhanced Session Isolation
2. Added Resource Management
close()method for explicit session cleanup__del__()method for automatic resource management3. Improved Error Handling
Testing
Usage Impact