Reservoir Simulation Storage Optimization via Hash Table
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Numerical reservoir simulations require significant high-performance computing and storage resources, leading to inefficiencies in storage and computation, particularly during the setup and initialization stages, where unnecessary input/output operations and resource usage are prevalent.
Innovation Solution
The technique involves hashing reservoir model structural and initialization data, using checksums to query a hash table for existing data, generating soft links instead of duplicating files, and updating the hash table with new entries when necessary, thereby optimizing storage and computation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If reservoir model structural data is stored in full for each simulation run, then data availability and accessibility are improved, but storage resource consumption increases significantly
Solution Approach 1:
The patent uses symbolic links (soft links) to create references to reservoir model structural data files instead of creating actual data copies. The hash table stores file path information that allows multiple simulation runs to access the same underlying data files through symbolic links, eliminating redundant storage while maintaining data accessibility.
Solution Approach 2:
The patent merges multiple simulation run data references into a single centralized hash table structure. Instead of duplicating data across multiple locations, the hash table consolidates all file path information in one place, allowing the system to manage and access shared reservoir model structural data efficiently across multiple simulation runs.
2Reliability
If reservoir model structural data is processed and initialized for each simulation run, then simulation accuracy is maintained, but computation time and I/O operations increase
Solution Approach 1:
The patent performs preliminary verification by calculating checksums of reservoir model structural data files and storing them in the hash table before simulation runs. This preliminary action allows the system to quickly verify data integrity and detect changes without re-processing the entire data set during each simulation initialization, reducing computation time while maintaining accuracy.
Solution Approach 2:
The patent implements a feedback mechanism where checksums are calculated and compared against stored values in the hash table. This feedback loop allows the system to determine whether data has changed since the last simulation run, enabling intelligent decisions about whether re-initialization is necessary, thus reducing unnecessary computation while ensuring simulation accuracy when data changes occur.
3Reliability
If checksum verification is performed for every data access, then data integrity is ensured, but processing overhead increases
Solution Approach 1:
The patent copies checksum values into a hash table structure that enables rapid lookup. Instead of performing complex verification calculations during each data access, the system stores pre-calculated checksums in the hash table with their corresponding file paths, allowing for efficient O(1) average-time complexity verification operations.
Solution Approach 2:
The hash table serves multiple functions: it stores file path information for accessing reservoir model structural data, stores checksum values for integrity verification, and provides a unified interface for both data location and verification operations. This multi-functionality reduces the need for separate verification processes and improves overall processing efficiency.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method and a system are provided for optimizing reservoir simulation runtime and storage by hashing reservoir model structural and initialization data. A checksum is calculated for model structural data produced from a reservoir simulation study. A hash table is queried for the checksum. A determination is made whether the checksum exists in the hash table. When a determination is made that the checksum exists in the hash table, soft links are generated to physical locations of reservoir structure files containing the model structural data. When a determination is made that the checksum does not exist in the hash table, the following occurs. New reservoir structure files are generated for the model structural data. A new hash table entry is generated containing record information identifying contents of the new reservoir structure files. The hash table is updated with the new hash table entry.