Reservoir modeling parameter pushing system and method
Through the reservoir modeling parameter push system, the problem of interconnection between reservoir modeling software and geological knowledge base is solved, efficient parameter query and display are achieved, user learning costs are reduced, and query accuracy and utilization are improved.
Patent Information
- Application Number
- CN202410332057.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-03-22
- Publication Date
- 2025-09-26
Smart Images
Figure CN120705387A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of reservoir modeling knowledge push technology, and specifically to a reservoir modeling parameter push system and a reservoir modeling parameter push method. Background Art
[0002] The current mainstream reservoir modeling geological knowledge base integrates various types of geological knowledge in different forms and sources, roughly including three categories: professional terms, literature, and analogical cases. Among them, professional terms and literature are mainly stored in unstructured or semi-structured forms such as text and drawings. Analogous cases refer to the results of core, logging, and seismic data analysis from field outcrops, modern sedimentary surveys, sedimentary simulation experiments, or actual exploration and development areas. Its core is various quantitative parameter data about reservoir structure (stored in structured form).
[0003] At the same time, when using reservoir modeling client software, users often need to understand or learn the modeling process, methods, specifications, and experience. Furthermore, in actual operation, the data of the target modeling area is often incomplete. In this case, understanding the research results of analogous cases similar to the modeling target area is important for reducing the uncertainty of modeling decisions. Because reservoir modeling software and reservoir modeling geological knowledge bases are not currently interconnected, queries for relevant modeling data must be done manually, which is inefficient. Both software have certain entry barriers, which increases the cost of user learning. Summary of the Invention
[0004] The purpose of the embodiments of the present application is to provide a reservoir modeling parameter push system and method to solve the above problems.
[0005] In order to achieve the above-mentioned objectives, the present application provides, in a first aspect, a reservoir modeling parameter push system, comprising:
[0006] Query module, display module and reservoir modeling parameter knowledge base;
[0007] The query module is used to receive a query instruction from a user, the query instruction including at least a target keyword to be queried, and querying a target reservoir modeling parameter matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameter to the user through the display module;
[0008] The reservoir modeling parameter knowledge base is used to store different reservoir modeling parameters;
[0009] The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
[0010] Optionally, the query module includes at least one push control built based on a QT plug-in, and the push control includes at least a professional term push control, a literature push control, and an analogy case push control.
[0011] Optionally, the professional term parameters include at least the name of the professional term and the explanation content of the professional term, the literature parameters include at least the title, author, source, publication time and literature content index of the literature, and the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case.
[0012] Optionally, the display module is a browser built based on the QWebEngine kernel; displaying the queried target reservoir modeling parameters to the user through the display module includes:
[0013] The titles of the retrieved documents or the names of the professional terms are arranged in order and displayed in the first display area, and the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term is displayed in the second display area.
[0014] Optionally, the keyword of the analogy case includes at least a quantitative parameter name of the reservoir structure, a target genesis type, and a target chart type; when the target keyword is the keyword of the analogy case, querying the reservoir modeling parameter knowledge base for a target reservoir modeling parameter that matches the target keyword based on the target keyword includes:
[0015] According to the keyword of the analogy case, query the reservoir modeling parameter knowledge base for IDs of all analogy cases that match the keyword of the analogy case;
[0016] Determine whether the obtained ID of each comparison case belongs to a preset subset. If it is determined that the ID of each comparison case belongs to any preset subset, obtain the ID of each subset that matches the ID of each comparison case;
[0017] The causal type corresponding to each subset ID obtained by querying is determined, and if there is a causal type matching the target causal type among the obtained causal types, the subset ID corresponding to the obtained causal type is determined as the target subset ID;
[0018] Determine, in the subset corresponding to the target subset ID, analogy case parameters of the analogy case that match the quantitative parameter name, target genesis type, and target chart type of the reservoir structure as target reservoir modeling parameters that match the target keyword.
[0019] In a second aspect of the present application, a reservoir modeling parameter push method is provided, using the above-mentioned reservoir modeling parameter push system, the method comprising:
[0020] receiving a user's query instruction through a query module, the query instruction including at least a target keyword to be queried, and querying a target reservoir modeling parameter matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameter to the user through a display module;
[0021] Storing different reservoir modeling parameters through a reservoir modeling parameter knowledge base;
[0022] The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
[0023] Optionally, the query module includes at least one push control built based on a QT plug-in, and the push control includes at least a professional term push control, a literature push control, and an analogy case push control.
[0024] Optionally, the professional term parameters include at least the name of the professional term and the explanation content of the professional term, the literature parameters include at least the title, author, source, publication time and literature content index of the literature, and the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case.
[0025] Optionally, the display module is a browser built based on the QWebEngine kernel; displaying the queried target reservoir modeling parameters to the user through the display module includes:
[0026] The titles of the retrieved documents or the names of the professional terms are arranged in order and displayed in the first display area, and the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term is displayed in the second display area.
[0027] Optionally, the keyword of the analogy case includes at least a quantitative parameter name of the reservoir structure, a target genesis type, and a target chart type; when the target keyword is the keyword of the analogy case, querying the reservoir modeling parameter knowledge base for a target reservoir modeling parameter that matches the target keyword based on the target keyword includes:
[0028] According to the keyword of the analogy case, query the reservoir modeling parameter knowledge base for IDs of all analogy cases that match the keyword of the analogy case;
[0029] Determine whether the obtained ID of each comparison case belongs to a preset subset. If it is determined that the ID of each comparison case belongs to any preset subset, obtain the ID of each subset that matches the ID of each comparison case;
[0030] The causal type corresponding to each subset ID obtained by querying is determined, and if there is a causal type matching the target causal type among the obtained causal types, the subset ID corresponding to the obtained causal type is determined as the target subset ID;
[0031] Determine, in the subset corresponding to the target subset ID, analogy case parameters of the analogy case that match the quantitative parameter name, target genesis type, and target chart type of the reservoir structure as target reservoir modeling parameters that match the target keyword.
[0032] In a third aspect of the present application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, causes the processor to execute the reservoir modeling parameter pushing method as described above.
[0033] In a fourth aspect of the present application, a terminal device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned reservoir modeling parameter pushing method when executing the computer program.
[0034] The embodiments provided in this application have the following beneficial effects:
[0035] This application can push relevant content in the reservoir modeling geological knowledge base to users on the desktop client, including professional terms, literature and analogy cases. Users can obtain modeling processes, methods, specifications and experience through professional terms and literature, and make up for the lack of data in the target area by querying the research results data of analogy cases, reduce the uncertainty of modeling decisions, realize the interconnection between B / S and C / S ends, and improve the query accuracy and utilization rate of digital assets.
[0036] Other features and advantages of the embodiments or implementations of the present application will be described in detail in the subsequent detailed description. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] The accompanying drawings are used to provide a further understanding of the embodiments of the present application and constitute a part of the specification. Together with the following detailed description, they are used to explain the embodiments of the present application but do not constitute a limitation on the embodiments of the present application. In the accompanying drawings:
[0038] Figure 1 The following schematically shows the architecture of the reservoir modeling parameter push system according to the embodiment of the present application;
[0039] Figure 2The following schematically shows the appearance of the parameter push control in use according to an embodiment of the present application;
[0040] Figure 3 The following schematically shows the B / S side technical process framework diagram of the embodiment of the present application;
[0041] Figure 4 The following is a schematic diagram showing the communication process between the query module and the knowledge base parameter push interface in an embodiment of the present application;
[0042] Figure 5 The following schematically shows a request logic diagram for a professional term query according to an embodiment of the present application;
[0043] Figure 6 Schematically shows a request logic diagram for a document query according to an embodiment of the present application;
[0044] Figure 7 The following schematically shows a request logic diagram of an analogy case query according to an embodiment of the present application;
[0045] Figure 8 Schematically shows a statistical chart diagram corresponding to the width of an embodiment of the present application;
[0046] Figure 9 Schematic diagram of statistical charts corresponding to the trends of the embodiments of the present application;
[0047] Figure 10 A schematic diagram of the structure of a terminal device in an embodiment of the present application is shown schematically.
[0048] Description of Reference Numerals
[0049] 10-terminal device, 100-processor, 101-memory, 102-computer program. DETAILED DESCRIPTION
[0050] The following describes the specific implementation of the embodiment of the present application in detail with reference to the accompanying drawings. It should be understood that the specific implementation described herein is only used to illustrate and explain the embodiment of the present application and is not intended to limit the embodiment of the present application.
[0051] In order to solve the above problems, the first aspect of the present application provides a reservoir modeling parameter push system, comprising:
[0052] Query module, display module and reservoir modeling parameter knowledge base;
[0053] The query module is used to receive a user's query instruction, the query instruction at least including a target keyword to be queried, and querying the target reservoir modeling parameters matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameters to the user through the display module;
[0054] The reservoir modeling parameter knowledge base is used to store different reservoir modeling parameters;
[0055] The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
[0056] In this way, this application can push relevant content in the reservoir modeling geological knowledge base to users on the desktop client, including professional terms, literature and analogy cases. Users can obtain modeling processes, methods, specifications and experience through professional terms and literature, and make up for the lack of data in the target area by querying the research results data of analogy cases, reduce the uncertainty of modeling decisions, realize the interconnection between B / S and C / S ends, and improve the query accuracy and utilization rate of digital assets.
[0057] In this application, module 3, i.e., the display module, is a browser built on the QWebEngine kernel. Module 1, i.e., the query module, includes at least one push control built on a QT plug-in. The push control includes at least a professional term push control, a literature push control, and an analogy case push control. Module 2, i.e., the reservoir modeling parameter knowledge base, includes a knowledge base parameter push interface and a reservoir modeling parameter database, wherein the database uses MySQL. Figure 1 As shown, this application builds a reservoir modeling parameter push system based on QT plug-in and QWebEngine. This application organizes the modeling knowledge system according to the general process of geological modeling, constructs application scenarios for knowledge push, and provides corresponding knowledge push content and software functions according to application needs at different levels, including but not limited to the push of professional terms, literature and analogy cases. The reservoir modeling parameter push system of this application mainly includes the following modules:
[0058] The query module is based on a variety of custom push type controls based on the QT plug-in. The custom push controls in this application include at least professional entry push controls, literature push controls, and analogy case push controls. Each push control utilizes QT custom plug-in technology and is published as a C++ dynamic link library. This not only facilitates the dissemination of the plug-in, but also decouples it from the client software to facilitate subsequent plug-in upgrades. The QT plug-in is used to implement the appearance of each push control, basic push trigger logic, reading and writing push parameters, and the transmission of push parameters to the B / S end.
[0059] It is understandable that the basic structure of implementing a control includes storing push parameters, creating and linking signals and slot functions, and controlling the appearance of the control. In order to implement the parameter push function, the custom control must contain some new properties. For different push type controls, the stored push parameters are similar. The more important properties include: the control ID, which is the control's unique identifier; the control's prompt information, which will be displayed as floating information on the program interface; and the control's push parameters. The push parameters of the professional term push control are the names of the professional terms, the push parameters of the literature push control are the literature keywords, and the push parameters of the analogy case push control are a set of case-limited key-value pairs. For example, the key-value pair can be (quantitative parameter A of reservoir structure, genetic type A).
[0060] The creation of signals and slot functions involves defining appropriate trigger signals according to the usage scenarios of different controls, linking the program blocks that trigger the startup, that is, the corresponding slot functions. For example, the trigger signal can be a signal that the user selects the corresponding control. By exposing the pointer of the core appearance component in the control, linking the signal with the slot function, and designing the appearance of the control, the basic structure of the control is realized. Among them, the appearance of the parameter push control is as follows: Figure 2 shown.
[0061] In this application, an XML reading and writing class for each control is pre-designed. When the client software is started, it is checked whether there is a corresponding XML file. If an XML file exists, the setting items of each internal control are read according to the ID of each control, and the code setting items are overwritten; if the ID is not read, the control content is written into the XML file; if there is no XML file, the XML file is written out according to the setting content of the control in the program code.
[0062] This application is based on the B / S technical architecture, adopts the front-end and back-end separation mode, uses the Vue development framework for the front-end, uses the element-plus style library to optimize the structure page, and uses Canvas technology and extension packages such as Cesium.js and Echarts.js to achieve visual analysis of data. This application uses Axios technology for data exchange between the front-end and back-end, and the data exchange format is lightweight JSON format. The back-end development adopts the Springboot framework, which is divided into the control layer, business logic layer, and data persistence layer. The control layer is mainly responsible for the interface that interacts with the front-end, the business logic layer is responsible for processing the logical calculation of data, etc. The data persistence layer uses Mybatis to map the data in the MySQL database to the corresponding entity class in the back-end. The entire B / S end technical process framework is as follows: Figure 3 As shown, the B / S technical architecture is an existing technology and will not be described in detail here.
[0063] In this application, the B / S side implements data communication with the C / S side through QWebChannel. First, it receives the push parameters from the C / S side through QWebChannel, and then reads the JSON data written to the QWebChannel by the C / S side. For example, the process of the user side receiving the push data from the server through a browser built on the QWebEngine kernel is the process of the B / S side implementing data communication with the C / S side through QWebChannel.
[0064] This application builds a custom browser based on the QWebEngine kernel provided by QT to realize calling the browser on the client to display the parameter push results of the reservoir modeling geological knowledge base. In this way, this application does not need to call the user's local browser when executing the search result push, reducing the compatibility risk, and facilitating high customization of the browser to realize other special functions.
[0065] Specifically, first create a QWebEngine browser window. Wrap the browser window with a QWidget, set the QWidget's window size and title, enable HTTP caching and GPU rendering for the browser window, and expose the browser component pointer to facilitate subsequent customization of the browser outside of the plugin.
[0066] Get the QWebEnginePage class of the browser window and set the pre-packaged QWebChannel to it. At this time, the object generated by QWebChannel will be transmitted to the HTML / JavaScript client at runtime, waiting for the JS code to call. The JS code will obtain the data in the json object. At this point, the parameter data pushed by the C / S side has been obtained by the B / S side, such as Figure 4 At the same time, you can also create another QWebEngine browser window, set the url of the browser to the local debugging port number, and use it to open the browser developer debugging window. This will not be described here.
[0067] like Figure 5 As shown, when a user executes a professional term query through the professional term push control on the user side, for example, the user queries "deterministic modeling method" through the control, based on the parsed data read from the QWebChannel, the professional term interface will send a search request to the backend server based on the parsed term name. The backend receives the term name sent by the frontend, and then uses the term name as the search condition to send a query request to the database, i.e., the reservoir modeling parameter knowledge base, through the Mybatis SQL statement. The database returns the corresponding search results to the backend, and the backend returns the results to the frontend for display. For example, all relevant retrieved terms are displayed in a list format.
[0068] like Figure 6 As shown, when the user executes a document query through the document push control on the user side, for example, when the user queries for documents related to "braided river reservoirs" through the control, the document interface will send a search request to the backend based on the parsed document name keywords according to the data read from the QWebChannel. The backend receives the document name sent by the frontend, and then uses the document name keywords as search conditions, and sends a query request to the database through the Mybatis SQL statement. The database returns all retrieved documents related to braided river reservoirs as search results to the backend, and the backend then displays the results to the frontend.
[0069] Among them, the professional term parameters at least include the name of the professional term and the explanation content of the professional term, and the document parameters at least include the title, author, source, release time and document content index of the document.
[0070] The target reservoir modeling parameters retrieved are displayed to the user through the display module, including: arranging the titles of the retrieved documents or the names of the professional terms in order and displaying them in the first display area, and displaying the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term in the second display area. For example, when returning the search results of the professional terms or documents to the user end, the browser is divided into two different display areas, namely the first display area and the second display area. The term names or document names are displayed in the form of a list in the first display area for the user to browse and select, and the term explanation content and document details such as the title, author, source, release time and document content index of the document are displayed in the second display area, and the user browses the document content by clicking on the document content index.
[0071] In the present application, the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case, and the keywords of the analogy case include at least the quantitative parameter name of the reservoir structure, the target causal type and the target chart type; when the target keyword is the keyword of the analogy case, the target reservoir modeling parameters matching the target keyword are queried from the reservoir modeling parameter knowledge base based on the target keyword, including: querying the IDs of all analogy cases matching the keyword of the analogy case from the reservoir modeling parameter knowledge base based on the keyword of the analogy case; judging whether the IDs of each obtained analogy case belong to a preset subset, if it is determined that the IDs of each analogy case belong to any preset subset, obtaining each subset ID matching the ID of each comparison case; querying the causal type corresponding to each obtained subset ID, if there is a causal type matching the target causal type among the obtained causal types, determining the subset ID corresponding to the obtained causal type as the target subset ID; determining that in the subset corresponding to the target subset ID, the analogy case parameters of the analogy case matching the quantitative parameter name of the reservoir structure, the target causal type and the target chart type are the target reservoir modeling parameters matching the target keyword.
[0072] like Figure 7 As shown, when the user executes an analogy case query through the analogy case push control on the user side, for example, when the user queries the analogy case of quantitative parameters related to "cracks" through the control, based on the parsed data read from QWebChannel, the analogy case interface will send a case retrieval request to the backend according to the parsed boundary conditions, wherein the boundary conditions may include but are not limited to the quantitative parameter name, target cause type and target chart type; the backend server sends a query request to the database through the Mybatis SQL statement according to the boundary conditions, and the database returns all the corresponding analogy case ids to the backend. The backend then queries the database for the subset id corresponding to each case id according to the retrieved case id, and then queries the database for the corresponding cause type according to the subset id, and then determines whether the cause type requested by the user exists in the cause type obtained according to the subset id. If so, the parameters are requested from the database according to the subset id and the cause type, and it is determined whether the requested parameters exist in the valid parameters obtained, and then the chart type is determined according to the parameter type. For example, Figure 8 、 Figure 9As shown, the target chart type can be a statistical chart corresponding to the width or a statistical chart corresponding to the direction. Finally, the corresponding statistical chart data is obtained from the retrieved results according to the subset id, cause type, request parameters, chart type, etc., and the results are transmitted to the front end for display. At the same time, the present application can also transmit the statistical analysis results to the C / S end through QWebChannel. It is understandable that the analogy case parameters of the stored category cases may include statistical charts pre-constructed in the form of preset statistical charts, which can be directly read during retrieval. Alternatively, when performing analogy case parameter retrieval, the analogy case parameters of the retrieved category cases are calculated and counted in real time according to the requested statistical chart form to generate a statistical chart in the form of a corresponding statistical chart. It is understandable that the statistical calculation of the analogy case parameters can be implemented using existing technologies, and the present application does not limit this.
[0073] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other and are not used to limit the scope of protection of this application.
[0074] In a second aspect of the present application, a reservoir modeling parameter push method is provided, which uses the above-mentioned reservoir modeling parameter push system, and the method includes:
[0075] receiving a user's query instruction through the query module, the query instruction including at least a target keyword to be queried and querying a target reservoir modeling parameter matching the target keyword from a reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameter to the user through the display module;
[0076] Storing different reservoir modeling parameters through a reservoir modeling parameter knowledge base;
[0077] The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
[0078] Optionally, the query module includes at least one push control built based on a QT plug-in, and the push control includes at least a professional term push control, a literature push control, and an analogy case push control.
[0079] Optionally, the professional term parameters include at least the name of the professional term and the explanation content of the professional term, the literature parameters include at least the title, author, source, release time and literature content index of the literature, and the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case.
[0080] Optionally, the display module is a browser built based on the QWebEngine kernel; the queried target reservoir modeling parameters are displayed to the user through the display module, including:
[0081] The titles of the retrieved documents or the names of the professional terms are arranged in order and displayed in the first display area, and the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term is displayed in the second display area.
[0082] Optionally, the keyword of the analogy case includes at least the name of the quantitative parameter of the reservoir structure, the target genesis type, and the target chart type; when the target keyword is the keyword of the analogy case, querying the target reservoir modeling parameter matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword includes:
[0083] According to the keyword of the analogy case, query the reservoir modeling parameter knowledge base for the IDs of all analogy cases that match the keyword of the analogy case;
[0084] Determine whether the obtained ID of each comparison case belongs to a preset subset. If it is determined that the ID of each comparison case belongs to any preset subset, obtain the ID of each subset that matches the ID of each comparison case;
[0085] The causal type corresponding to each subset ID obtained by querying is determined. If there is a causal type among the obtained causal types that matches the target causal type, the subset ID corresponding to the obtained causal type is determined as the target subset ID;
[0086] Determine that in the subset corresponding to the target subset ID, analog case parameters of the analog case that match the quantitative parameter name of the reservoir structure, the target genesis type, and the target chart type are target reservoir modeling parameters that match the target keyword.
[0087] In a third aspect of the present application, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, causes the processor to execute the reservoir modeling parameter pushing method as described above.
[0088] In a fourth aspect of the present application, a terminal device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned reservoir modeling parameter pushing method when executing the computer program.
[0089] like Figure 10 The figure shows a schematic diagram of a terminal device provided by an embodiment of the present application. Figure 10 As shown, the terminal device 10 of this embodiment includes: a processor 100, a memory 101, and a computer program 102 stored in the memory 101 and executable on the processor 100. When the processor 100 executes the computer program 102, the steps of the above-described method embodiment are implemented. Alternatively, when the processor 100 executes the computer program 102, the functions of the modules / units in the above-described apparatus embodiments are implemented.
[0090] Exemplarily, the computer program 102 may be divided into one or more modules / units, one or more of which are stored in the memory 101 and executed by the processor 100 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 102 in the terminal device 10.
[0091] The terminal device 10 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal device 10 may include, but is not limited to, a processor 100 and a memory 101. Those skilled in the art will understand that Figure 10 It is only an example of the terminal device 10 and does not constitute a limitation of the terminal device 10. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal device may also include input and output devices, network access devices, buses, etc.
[0092] The processor 100 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0093] The memory 101 can be an internal storage unit of the terminal device 10, such as a hard disk or memory of the terminal device 10. The memory 101 can also be an external storage device of the terminal device 10, such as a plug-in hard disk equipped on the terminal device 10, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. Furthermore, the memory 101 can also include both the internal storage unit of the terminal device 10 and an external storage device. The memory 101 is used to store computer programs and other programs and data required by the terminal device 10. The memory 101 can also be used to temporarily store data that has been output or is about to be output.
[0094] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0095] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.
[0096] The above are merely embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.
Claims
1. A reservoir modeling parameter push system, characterized in that: include: Query module, display module and reservoir modeling parameter knowledge base; The query module is used to receive a query instruction from a user, the query instruction including at least a target keyword to be queried, and querying a target reservoir modeling parameter matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameter to the user through the display module; The reservoir modeling parameter knowledge base is used to store different reservoir modeling parameters; The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
2. The reservoir modeling parameter push system according to claim 1, characterized in that: The query module includes at least one push control built based on a QT plug-in, and the push control includes at least a professional term push control, a literature push control, and an analogy case push control.
3. The reservoir modeling parameter push system according to claim 1, characterized in that: The professional term parameters include at least the name of the professional term and the explanation content of the professional term, the literature parameters include at least the title, author, source, release time and literature content index of the literature, and the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case.
4. The reservoir modeling parameter push system according to claim 3, characterized in that: The display module is a browser built based on the QWebEngine kernel; The display module displays the queried target reservoir modeling parameters to the user, including: The titles of the retrieved documents or the names of the professional terms are arranged in order and displayed in the first display area, and the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term is displayed in the second display area.
5. The reservoir modeling parameter push system according to claim 3, characterized in that: The keyword of the analogy case includes at least the name of the quantitative parameter of the reservoir structure, the target genesis type, and the target chart type. When the target keyword is the keyword of the analogy case, querying the reservoir modeling parameter knowledge base for target reservoir modeling parameters that match the target keyword based on the target keyword includes: According to the keyword of the analogy case, query the reservoir modeling parameter knowledge base for IDs of all analogy cases that match the keyword of the analogy case; Determine whether the obtained ID of each comparison case belongs to a preset subset. If it is determined that the ID of each comparison case belongs to any preset subset, obtain the ID of each subset that matches the ID of each comparison case; The causal type corresponding to each subset ID obtained by querying is determined, and if there is a causal type matching the target causal type among the obtained causal types, the subset ID corresponding to the obtained causal type is determined as the target subset ID; Determine, in the subset corresponding to the target subset ID, analogy case parameters of the analogy case that match the quantitative parameter name, target genesis type, and target chart type of the reservoir structure as target reservoir modeling parameters that match the target keyword.
6. A reservoir modeling parameter pushing method, using the reservoir modeling parameter pushing system according to any one of claims 1 to 5, characterized in that: The method comprises: receiving a user's query instruction through a query module, the query instruction including at least a target keyword to be queried, and querying a target reservoir modeling parameter matching the target keyword from the reservoir modeling parameter knowledge base based on the target keyword, and displaying the queried target reservoir modeling parameter to the user through a display module; Storing different reservoir modeling parameters through a reservoir modeling parameter knowledge base; The target keywords include at least keywords of professional terms, keywords of literature materials and keywords of analogy cases, and the reservoir modeling parameters include at least parameters of professional terms, parameters of literature materials and parameters of analogy cases.
7. The reservoir modeling parameter pushing method according to claim 6, characterized in that: The query module includes at least one push control built based on a QT plug-in, and the push control includes at least a professional term push control, a literature push control, and an analogy case push control.
8. The reservoir modeling parameter pushing method according to claim 6, characterized in that: The professional term parameters include at least the name of the professional term and the explanation content of the professional term, the literature parameters include at least the title, author, source, release time and literature content index of the literature, and the analogy case parameters include at least the quantitative parameter data of the reservoir structure of the analogy case.
9. The reservoir modeling parameter pushing method according to claim 8, characterized in that: The display module is a browser built based on the QWebEngine kernel; The display module displays the queried target reservoir modeling parameters to the user, including: The titles of the retrieved documents or the names of the professional terms are arranged in order and displayed in the first display area, and the document content corresponding to the title of the selected document or the explanation content corresponding to the name of the professional term is displayed in the second display area.
10. The reservoir modeling parameter pushing method according to claim 8, characterized in that: The keyword of the analogy case includes at least the name of the quantitative parameter of the reservoir structure, the target genesis type, and the target chart type. When the target keyword is the keyword of the analogy case, querying the reservoir modeling parameter knowledge base for target reservoir modeling parameters that match the target keyword based on the target keyword includes: According to the keyword of the analogy case, query the reservoir modeling parameter knowledge base for IDs of all analogy cases that match the keyword of the analogy case; Determine whether the obtained ID of each comparison case belongs to a preset subset. If it is determined that the ID of each comparison case belongs to any preset subset, obtain the ID of each subset that matches the ID of each comparison case; The causal type corresponding to each subset ID obtained by querying is determined, and if there is a causal type matching the target causal type among the obtained causal types, the subset ID corresponding to the obtained causal type is determined as the target subset ID; Determine, in the subset corresponding to the target subset ID, analogy case parameters of the analogy case that match the quantitative parameter name, target genesis type, and target chart type of the reservoir structure as target reservoir modeling parameters that match the target keyword.