Knowledge pushing method and system, electronic equipment, storage medium and program product
By collecting operational data on the ship design platform, matching knowledge application scenarios, and optimizing knowledge push using historical behavior data, the problem of low knowledge acquisition efficiency in the design process is solved, fast and accurate knowledge acquisition is achieved, and design efficiency is improved.
Patent Information
- Application Number
- CN202411124427.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-16
- Publication Date
- 2024-11-15
AI Technical Summary
During the ship design process, designers need to search for various knowledge from multiple systems and folders, resulting in low knowledge acquisition efficiency and increasing design time cost.
By collecting the current operation data of the design platform, determining the design stage, and matching the corresponding knowledge application scenarios, using hierarchical classification method and correlation classification method to divide the knowledge into the corresponding scenarios, obtaining historical behavior data to arrange knowledge in reverse order, and through the socket interface Push matching knowledge to the design platform, provide regional, model, keyword and tag knowledge acquisition interfaces to improve knowledge acquisition efficiency.
It effectively reduces the time cost of designers for searching knowledge, improves the efficiency of knowledge acquisition, and improves the degree of design automation and work efficiency.
Smart Images

Figure CN118964696A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a knowledge push method, system, electronic device, storage medium and program product. Background Art
[0002] When using the design platform for ship design, it is necessary to go through multiple design stages, such as building a database, modeling, drawing, and data. In the actual design process, designers will need various types of knowledge, such as design drawings, equipment information, design standards, design specifications, design experience, etc., and these knowledge are scattered in various systems and folders. When using, designers need to search in various folders to obtain the required knowledge, resulting in poor efficiency in knowledge acquisition. Summary of the invention
[0003] The technical problem to be solved by the present disclosure is to overcome the defect of poor efficiency of knowledge acquisition in the design process in the prior art, and to provide a knowledge push method, system, electronic device, storage medium and program product.
[0004] The present invention solves the above technical problems through the following technical solutions:
[0005] In a first aspect, a knowledge push method is provided, which is applied to a design platform for shipbuilding, and the knowledge push method comprises:
[0006] Collecting current operation data on the design platform and determining the design stage of the current operation data;
[0007] Determine the knowledge in the knowledge application scenario that matches the design stage of the current operation data as the knowledge to be pushed;
[0008] Among them, at least one of the knowledge application scenarios matches the design stage, and the knowledge application scenario includes at least one knowledge.
[0009] Optionally, the establishment of the knowledge application scenario includes:
[0010] extracting attribute information of the knowledge;
[0011] According to the relationship between the attribute information and the design stage, the knowledge is classified into knowledge application scenarios corresponding to the design stage using a hierarchical classification method and / or a correlation classification method.
[0012] Optionally, after the step of determining the knowledge in the knowledge application scenario matching the design stage of the current operation data as the knowledge to be pushed, the knowledge pushing method includes:
[0013] Acquire historical behavior data on the design platform; wherein the historical behavior data includes at least one of the following: the number of clicks on the knowledge, the number of views on the knowledge, and the number of searches on the knowledge;
[0014] Obtaining knowledge reference requirements based on the historical behavior data;
[0015] Arrange the knowledge in the knowledge application scenario in reverse order according to the knowledge search requirements.
[0016] Optionally, the current operation data includes: a selected area on the design platform, a used model, and executed commands.
[0017] Optionally, the design platform is provided with an interface, the interface comprising at least one of the following: a region knowledge acquisition interface, a model knowledge acquisition interface, a keyword knowledge acquisition interface, and a tag knowledge acquisition interface;
[0018] The regional knowledge acquisition interface is used to acquire knowledge related to the region selected on the design platform;
[0019] The model class knowledge acquisition interface is used to acquire knowledge related to the model used on the design platform;
[0020] The keyword knowledge acquisition interface is used to acquire knowledge containing target keywords;
[0021] The tag knowledge acquisition interface is used to acquire knowledge containing target tags.
[0022] Optionally, the knowledge is stored in a knowledge push platform, and the knowledge push method further includes:
[0023] By means of a socket (socket interface), an association is established between the knowledge push platform and the design platform;
[0024] The knowledge to be pushed on the knowledge pushing platform is pushed to the design platform.
[0025] In a second aspect, a knowledge push system is provided, which is applied to a design platform for shipbuilding, and the knowledge push system includes:
[0026] An operation data collection module, used to collect current operation data on the design platform and determine the design stage of the current operation data;
[0027] A module for determining knowledge to be pushed, used for determining knowledge in a knowledge application scenario matching the design stage of the current operation data as knowledge to be pushed;
[0028] Among them, at least one of the knowledge application scenarios matches the design stage, and the knowledge application scenario includes at least one knowledge.
[0029] Optionally, the knowledge push system further includes:
[0030] An extraction module, used for extracting attribute information of the knowledge;
[0031] A classification module is used to classify the knowledge into knowledge application scenarios corresponding to the design stage by using a hierarchical classification method and / or a correlation classification method according to the relationship between the attribute information and the design stage.
[0032] Optionally, the knowledge push system further includes:
[0033] A behavior data acquisition module, used to acquire historical behavior data on the design platform; wherein the historical behavior data includes at least one of the following: the number of clicks on the knowledge, the number of views on the knowledge, and the number of searches on the knowledge;
[0034] A reference requirement determination module, used to obtain knowledge reference requirements based on the historical behavior data;
[0035] The arrangement module is used to arrange the knowledge in the knowledge application scenario in reverse order according to the knowledge search requirements.
[0036] Optionally, the current operation data includes: a selected area on the design platform, a used model, and executed commands.
[0037] Optionally, the design platform is provided with an interface, the interface comprising at least one of the following: a region knowledge acquisition interface, a model knowledge acquisition interface, a keyword knowledge acquisition interface, and a tag knowledge acquisition interface;
[0038] The regional knowledge acquisition interface is used to acquire knowledge related to the region selected on the design platform;
[0039] The model class knowledge acquisition interface is used to acquire knowledge related to the model used on the design platform;
[0040] The keyword knowledge acquisition interface is used to acquire knowledge containing target keywords;
[0041] The tag knowledge acquisition interface is used to acquire knowledge containing target tags.
[0042] Optionally, the knowledge is stored in a knowledge push platform, and the knowledge push system further includes:
[0043] A connection module, used to establish the association between the knowledge push platform and the design platform by means of a socket;
[0044] A push module is used to push the knowledge to be pushed on the knowledge push platform to the design platform.
[0045] According to a third aspect, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and used to run on the processor, wherein the processor implements any of the above-mentioned knowledge push methods when executing the computer program.
[0046] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored, characterized in that when the computer program is executed by a processor, it implements any of the above-mentioned knowledge push methods.
[0047] In a fifth aspect, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the knowledge push method described in any one of the above items is implemented.
[0048] On the basis of being in accordance with the common sense in the art, the above-mentioned preferred conditions can be arbitrarily combined to obtain the preferred embodiments of the present disclosure.
[0049] The positive progressive effect of the present disclosure is that the present disclosure has at least one knowledge application scenario that matches the design stage. During the design process, the knowledge to be pushed can be determined based on the designer's current operating data, effectively reducing the designer's time cost for searching for knowledge, improving the efficiency of knowledge acquisition, and increasing the degree of automation, thereby improving the designer's work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] Figure 1 A flowchart of a knowledge push method provided for an exemplary embodiment of the present disclosure;
[0051] Figure 2 A schematic diagram of a module of a knowledge push system provided by an exemplary embodiment of the present disclosure;
[0052] Figure 3 The present invention provides a schematic structural diagram of an electronic device according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION
[0053] The present disclosure is further described below by way of examples, but the present disclosure is not limited to the scope of the examples.
[0054] Prefixes such as "first" and "second" are used in the embodiments of the present disclosure only to distinguish different description objects, and have no limiting effect on the position, order, priority, quantity or content of the described objects. The use of prefixes such as ordinal numbers to distinguish description objects in the embodiments of the present disclosure does not constitute a limitation on the described objects. For the statement of the described objects, please refer to the description in the context of the claims or embodiments, and no unnecessary limitation should be constituted due to the use of such prefixes. In addition, in the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.
[0055] Example 1
[0056] Figure 1 A flowchart of a knowledge push method provided by an exemplary embodiment of the present disclosure is applied to a design platform for shipbuilding. The design platform includes but is not limited to Smart3D (Soarscape Smart3D3D real scene modeling system, real scene 3D modeling software), which can be selected according to actual conditions and is not particularly limited here.
[0057] Taking the use of Smart3D for shipbuilding design as an example, the design stage includes but is not limited to database building, modeling, drawing and data output, which can be added or deleted according to the actual situation and are not specifically limited here. Designers will need various types of knowledge to complete the design at different design stages. Knowledge includes but is not limited to design drawings, equipment information, design standards, technical protocols, design specifications and design experience, etc., which can be set according to the actual situation and are not specifically limited here. The knowledge push method provided in this embodiment can avoid designers searching for the required knowledge in various systems and folders, and improve the efficiency of knowledge acquisition.
[0058] The knowledge push method includes:
[0059] Step S101: collect current operation data on the design platform and determine the design stage of the current operation data.
[0060] Step S102: determine the knowledge in the knowledge application scenario that matches the design stage of the current operation data as the knowledge to be pushed.
[0061] Among them, at least one knowledge application scenario matches the design stage, and the knowledge application scenario includes at least one knowledge. The number of knowledge can be set according to actual conditions and is not particularly limited here.
[0062] Specifically, the number of knowledge application scenarios is at least one, and each design stage has at least one knowledge application scenario matching the design stage. For example, the design stage is a modeling stage, and the corresponding knowledge application scenario includes: at least one knowledge used in the modeling stage.
[0063] When in use, the corresponding knowledge application scenario is determined according to the current design stage, and the knowledge required for the current design stage is pushed to the designer.
[0064] In this embodiment, there is at least one knowledge application scenario that matches the design stage. During the design process, the knowledge to be pushed can be determined based on the designer's current operation data, effectively reducing the designer's time cost for searching for knowledge, improving the efficiency of knowledge acquisition, and increasing the degree of automation, thereby improving the designer's work efficiency.
[0065] In one embodiment, establishing the knowledge application scenario includes: extracting the attribute information of the knowledge, and classifying the knowledge into the knowledge application scenario corresponding to the design stage by using the hierarchical classification method and / or the correlation classification method according to the relationship between the attribute information and the design stage.
[0066] Knowledge includes but is not limited to design drawings, equipment information, design standards, technical agreements, design specifications and design experience. As the types of knowledge are complex and diverse, it is necessary to classify the knowledge and include it in the knowledge push platform for unified management. The categories of knowledge include but are not limited to design drawings, equipment information, design standards, technical agreements, design specifications, design experience, relevant patents, operating manuals, design guidance, quality cases, review points, common opinions, design practices, accident management, design safety general rules and other design rules, which can be set according to actual conditions and are not specifically limited here.
[0067] The attribute information includes but is not limited to the project name, description, model object, region information, standard number, etc., which can be selected according to the actual situation and is not particularly limited here. According to the relationship between the attribute information and the design stage, the design stage corresponding to the knowledge is determined, and the corresponding design stage is added to the attribute information.
[0068] Specifically, the attribute information of the knowledge is sorted out, and the relationship between the attribute information and the design stage is determined. This can be determined by the designer. The specific determination method can be selected according to the actual situation and is not particularly limited here. Determining the relationship between the attribute information and the design stage is to determine the requirements of knowledge in different design stages. For example, the design stage is the modeling stage, and the knowledge attributes of the required knowledge may include model objects.
[0069] The knowledge is classified into the knowledge application scenarios corresponding to the design stage by using the hierarchical classification method and / or the correlation classification method. The specific implementation can refer to the relevant technical description, which will not be repeated here. It should be noted that other classification methods can be used to classify the knowledge as needed, which is not particularly limited here.
[0070] In this embodiment, a knowledge application scenario that matches the design stage is established, and knowledge is divided into knowledge application scenarios corresponding to the design stage using a hierarchical classification method and / or a correlation classification method, thereby effectively reducing the time cost of designers searching for knowledge, improving the efficiency of knowledge acquisition, and increasing the degree of automation, thereby improving the work efficiency of designers.
[0071] In one embodiment, after step S102, the knowledge push method includes: obtaining historical behavior data on the design platform, obtaining knowledge search requirements according to the historical behavior data, and arranging the knowledge in the knowledge application scenario in reverse order according to the knowledge search requirements.
[0072] The historical behavior data includes at least one of the following: the number of clicks on the knowledge, the number of views on the knowledge, and the number of searches on the knowledge.
[0073] Specifically, the TF-IDF (Term Frequency-Inverse Document Frequency) similarity algorithm is used to obtain the knowledge reference requirements based on the frequency, inverse document rate and field length of the designer's search terms on the knowledge push platform, and then the requirements are sorted in reverse order. The greater the knowledge reference requirements, the higher the designer's knowledge requirements for the knowledge. Conversely, the smaller the knowledge reference requirements, the lower the designer's knowledge requirements for the knowledge.
[0074] In this embodiment, the order of knowledge in the knowledge application scenario is determined according to the knowledge retrieval requirements, which can help designers quickly acquire the required knowledge, effectively reduce the time cost of designers searching for knowledge, improve the efficiency of knowledge acquisition, increase the degree of automation, and thus improve the work efficiency of designers.
[0075] In one embodiment, the current operation data includes: a selected area on the design platform, a used model, and executed commands.
[0076] The design stage of the current operation data can be determined based on the current operation data. Specifically, when the collected current operation data includes the target operation, that is, the designer triggers the target operation, the design stage can be determined, thereby determining the knowledge in the knowledge application scenario that matches the design stage as the knowledge to be pushed.
[0077] The target operation can be set according to the actual situation and is not limited here. For example, if the target operation includes selecting a deck on the design platform, when the designer selects the deck on the design platform, it is considered to trigger the target operation, the design stage is the deck design stage, and the matching knowledge application scenarios include: at least one knowledge for the deck design stage. If the target operation includes clicking on model A, when the designer clicks on model A on the design platform, it is considered to trigger the target operation, the design stage is the modeling stage, and the matching knowledge application scenarios include: at least one knowledge for model A.
[0078] In this embodiment, during the design process, the knowledge to be pushed can be determined based on the selected area, the model used and the executed commands on the design platform, effectively reducing the time cost of designers searching for knowledge, improving the efficiency of knowledge acquisition, and increasing the degree of automation, thereby improving the work efficiency of designers.
[0079] In one embodiment, an interface is provided on the design platform, and the interface includes at least one of the following: a region knowledge acquisition interface, a model knowledge acquisition interface, a keyword knowledge acquisition interface, and a tag knowledge acquisition interface.
[0080] The category of the interface is determined according to the category of knowledge, the attribute information of the knowledge and the characteristics of the design platform. It can be set according to actual conditions and is not particularly limited here.
[0081] The regional knowledge acquisition interface is used to obtain knowledge related to the region selected on the design platform.
[0082] Region refers to the current design area, and the attribute information of knowledge includes region information. Taking the deck area as an example, users can retrieve knowledge related to the deck area design through the region knowledge acquisition interface, that is, the region information is the knowledge of the deck area.
[0083] When in use, based on the correspondence between the region and the drawing, the correspondence between the drawing number and the drawing, and the correspondence between the model and the drawing, the required drawings can be obtained through the interface. The correspondence between the region and the drawing, the correspondence between the drawing number and the drawing, and the correspondence between the model and the drawing can be obtained through statistics, and the specific implementation method is not particularly limited here.
[0084] The model class knowledge acquisition interface is used to obtain knowledge related to the model used on the design platform. It mainly obtains knowledge related to the model used through model attributes. Model attributes include but are not limited to model object type and model object attributes. The specific selection can be based on actual conditions and is not specifically limited here.
[0085] The keyword knowledge acquisition interface is used to acquire knowledge containing target keywords, mainly through keywords such as drawing number, file name, standard number, system number, drawing number, etc. to acquire knowledge containing corresponding target keywords.
[0086] When in use, you can enter the target keyword, such as the standard number, identification number or words contained in the description of the attribute information, through the keyword knowledge acquisition interface, and perform fuzzy search to obtain knowledge containing the target keyword. Among them, the type of target keyword can be adjusted according to the type of knowledge, and the number of input target keywords can be selected according to the actual situation. The specific setting can be based on the actual situation and is not particularly limited here.
[0087] When in use, the drawing number of the drawing required in the current design stage is obtained based on the equipment list relationship table, and the knowledge corresponding to the drawing number is accurately searched through the keyword knowledge acquisition interface to obtain the knowledge corresponding to the drawing number, such as the equipment information corresponding to the drawing number. Among them, the equipment list relationship table is pre-recorded and stored by the designer, and can also be obtained by other means, which is not particularly limited here.
[0088] The tag knowledge acquisition interface is used to acquire knowledge containing target tags, mainly by combining various target tags to comprehensively acquire knowledge containing corresponding target tags. Tags include but are not limited to ship types and drawing types, which can be adjusted according to the knowledge type and are not specifically limited here. Among them, the number of input target tags can be selected according to the actual situation and can be set according to the actual situation and are not specifically limited here.
[0089] The knowledge can be labeled by the designer according to the content of the knowledge, or the knowledge can be labeled using relevant algorithms such as annotation algorithms. For relevant algorithms for labeling, please refer to the relevant technical description, which will not be repeated here.
[0090] When in use, matching is performed based on the knowledge tags to obtain knowledge containing target tags, such as design conventions and design guidelines. Knowledge tags include but are not limited to professions, component types, drawing types, etc., which can be set according to actual conditions and are not specifically limited here.
[0091] The type and number of interfaces can be set according to the actual situation and are not specifically limited here. It is understandable that if there are too few types of interfaces, it is impossible to ensure that all knowledge can be searched. If there are too many types of interfaces, the complexity of the algorithm will increase. Therefore, in actual situations, the appropriate type and number of interfaces can be determined in combination with the category and attribute information of the knowledge.
[0092] Combined with the knowledge classification and knowledge attribute information, the platform element attributes of the design platform are analyzed to determine the integration scheme of the interface and the design platform. The integration scheme can be selected according to the actual situation and is not specifically limited here. The platform element attributes include, but are not limited to: design platform folders, design platform models, and design platform drawings. Among them, the design platform folder includes regional attributes, the design platform model includes the model name, design standard and model type, and the design platform drawings include the drawing catalog name and drawing name. The specific details can be adjusted according to the actual situation and are not specifically limited here. For the specific integration method, please refer to the relevant technical description and will not be repeated here.
[0093] In this embodiment, through the region knowledge acquisition interface, model knowledge acquisition interface, keyword knowledge acquisition interface and tag knowledge acquisition interface, it is ensured that all knowledge can be searched, helping designers to quickly acquire the required knowledge.
[0094] In one embodiment, the knowledge is stored in a knowledge push platform, and the knowledge push method further includes: establishing a relationship between the knowledge push platform and the design platform by means of a socket, and pushing the knowledge to be pushed on the knowledge push platform to the design platform.
[0095] Through the socket, the current operation data on the design platform is collected in real time, and the current operation data is analyzed to determine the design stage of the current operation data, and the knowledge in the knowledge application scenario that matches the design stage of the current operation data is determined as the knowledge to be pushed, so as to push different knowledge in different design stages.
[0096] In this embodiment, the knowledge push platform is used to uniformly manage knowledge, ensure the unique data source and data integrity of knowledge, facilitate subsequent maintenance of knowledge, efficiently assist design work, and establish a relationship between the knowledge push platform and the design platform, so as to push different knowledge at different design stages and present knowledge such as drawings required by designers.
[0097] Example 2
[0098] Corresponding to the aforementioned knowledge push method embodiment, the present disclosure also provides an embodiment of a knowledge push system.
[0099] Figure 2 A schematic diagram of a module of a knowledge push system provided by an exemplary embodiment of the present disclosure, which is applied to a design platform for shipbuilding, includes:
[0100] The operation data collection module 21 is used to collect the current operation data on the design platform and determine the design stage of the current operation data;
[0101] The knowledge to be pushed determining module 22 is used to determine the knowledge in the knowledge application scenario matching the design stage of the current operation data as the knowledge to be pushed;
[0102] Among them, at least one knowledge application scenario matches the design stage, and the knowledge application scenario includes at least one knowledge.
[0103] Optionally, the knowledge push system further includes:
[0104] Extraction module, used to extract attribute information of knowledge;
[0105] The classification module is used to classify the knowledge into knowledge application scenarios corresponding to the design stage by using a hierarchical classification method and / or a correlation classification method according to the relationship between the attribute information and the design stage.
[0106] Optionally, the knowledge push system further includes:
[0107] A behavior data acquisition module is used to acquire historical behavior data on the design platform; wherein the historical behavior data includes at least one of the following: the number of clicks on the knowledge, the number of views on the knowledge, and the number of searches on the knowledge;
[0108] A reference demand determination module is used to obtain knowledge reference needs based on historical behavior data;
[0109] The arrangement module is used to arrange the knowledge in the knowledge application scenario in reverse order according to the knowledge reference requirements.
[0110] Optionally, the current operation data includes: a selected area on the design platform, a used model, and executed commands.
[0111] Optionally, an interface is provided on the design platform, and the interface includes at least one of the following: a region knowledge acquisition interface, a model knowledge acquisition interface, a keyword knowledge acquisition interface, and a tag knowledge acquisition interface;
[0112] The regional knowledge acquisition interface is used to obtain knowledge related to the region selected on the design platform;
[0113] The model class knowledge acquisition interface is used to obtain knowledge related to the models used on the design platform;
[0114] The keyword knowledge acquisition interface is used to acquire knowledge containing target keywords;
[0115] The tag knowledge acquisition interface is used to obtain knowledge containing target tags.
[0116] Optionally, the knowledge is stored in a knowledge push platform, and the knowledge push system further includes:
[0117] The connection module is used to establish the association between the knowledge push platform and the design platform through the socket;
[0118] The push module is used to push the knowledge to be pushed on the knowledge push platform to the design platform.
[0119] As for the system embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The system embodiment described above is only illustrative, wherein the units described as separate components may or may not be physically separated, and the components as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the disclosed solution.
[0120] Example 3
[0121] Figure 3 This is a structural diagram of an electronic device shown in an example embodiment of the present disclosure, the electronic device includes a memory, a processor, and a computer program stored in the memory and used to run on the processor, and when the processor executes the computer program, the knowledge push method described in any of the above embodiments is implemented. Figure 3 The electronic device 30 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0122] like Figure 3 As shown, the electronic device 30 may be in the form of a general-purpose computing device, for example, it may be a server device. The components of the electronic device 30 may include, but are not limited to: at least one processor 31, at least one memory 32, and a bus 33 connecting different system components (including the memory 32 and the processor 31).
[0123] The bus 33 includes a data bus, an address bus, and a control bus.
[0124] The memory 32 may include a volatile memory, such as a random access memory (RAM) 321 and / or a cache memory 322 , and may further include a read-only memory (ROM) 323 .
[0125] The memory 32 may also include a program tool 325 (or utility) having a set (at least one) of program modules 324, such program modules 324 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include an implementation of a network environment.
[0126] The processor 31 executes various functional applications and data processing by running the computer program stored in the memory 32, such as the knowledge push method provided in any of the above embodiments.
[0127] The electronic device 30 may also communicate with one or more external devices 34 (e.g., keyboards, pointing devices, etc.). Such communication may be performed via an input / output (I / O) interface 35. Furthermore, the electronic device 30 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 36. As shown, the network adapter 36 communicates with other modules of the electronic device 30 via a bus 33. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 30, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.
[0128] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided into multiple units / modules to be embodied.
[0129] Example 4
[0130] The embodiments of the present disclosure also provide a computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the knowledge push method provided in any of the above embodiments is implemented.
[0131] The readable storage medium may include but is not limited to: a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device or any suitable combination of the above.
[0132] Example 5
[0133] The present disclosure also provides a computer program product, including a computer program, which implements any of the above-mentioned knowledge push methods when executed by a processor.
[0134] Among them, the program code for executing the computer program product of the present disclosure can be written in any combination of one or more programming languages, and the program code can be executed completely on the user device, partially on the user device, as an independent software package, partially on the user device and partially on a remote device, or completely on the remote device.
[0135] Although the specific embodiments of the present disclosure are described above, those skilled in the art should understand that this is only an example, and the protection scope of the present disclosure is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present disclosure, but these changes and modifications all fall within the protection scope of the present disclosure.
Claims
1. A knowledge push method, characterized in that: The knowledge push method for the design platform applied to shipbuilding includes: Collecting current operation data on the design platform and determining the design stage of the current operation data; Determine the knowledge in the knowledge application scenario that matches the design stage of the current operation data as the knowledge to be pushed; Among them, at least one of the knowledge application scenarios matches the design stage, and the knowledge application scenario includes at least one knowledge.
2. The knowledge push method according to claim 1, characterized in that: The establishment of the knowledge application scenario includes: extracting attribute information of the knowledge; According to the relationship between the attribute information and the design stage, the knowledge is classified into knowledge application scenarios corresponding to the design stage using a hierarchical classification method and / or a correlation classification method.
3. The knowledge push method according to claim 2, characterized in that: After the step of determining the knowledge in the knowledge application scenario matching the design stage of the current operation data as the knowledge to be pushed, the knowledge pushing method includes: Acquire historical behavior data on the design platform; wherein the historical behavior data includes at least one of the following: the number of clicks on the knowledge, the number of views on the knowledge, and the number of searches on the knowledge; Obtaining knowledge reference requirements based on the historical behavior data; Arrange the knowledge in the knowledge application scenario in reverse order according to the knowledge search requirements.
4. The knowledge push method according to claim 1, characterized in that: The current operation data includes: the selected area on the design platform, the used model and the executed commands.
5. The knowledge push method according to claim 4, characterized in that: The design platform is provided with an interface, and the interface includes at least one of the following: a region knowledge acquisition interface, a model knowledge acquisition interface, a keyword knowledge acquisition interface, and a tag knowledge acquisition interface; The regional knowledge acquisition interface is used to acquire knowledge related to the region selected on the design platform; The model class knowledge acquisition interface is used to acquire knowledge related to the model used on the design platform; The keyword knowledge acquisition interface is used to acquire knowledge containing target keywords; The tag knowledge acquisition interface is used to acquire knowledge containing target tags.
6. The knowledge push method according to any one of claims 1 to 5, characterized in that: The knowledge is stored in a knowledge push platform, and the knowledge push method further includes: Establishing the association between the knowledge push platform and the design platform through socket; The knowledge to be pushed on the knowledge pushing platform is pushed to the design platform.
7. A knowledge push system, characterized in that: The design platform applied to shipbuilding, the knowledge push system includes: An operation data collection module, used to collect current operation data on the design platform and determine the design stage of the current operation data; A module for determining knowledge to be pushed, used for determining knowledge in a knowledge application scenario matching the design stage of the current operation data as knowledge to be pushed; Among them, at least one of the knowledge application scenarios matches the design stage, and the knowledge application scenario includes at least one knowledge.
8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and used to run on the processor, characterized in that: When the processor executes the computer program, the knowledge push method according to any one of claims 1 to 6 is implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the knowledge pushing method according to any one of claims 1 to 6 is implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the knowledge push method according to any one of claims 1 to 6 is implemented.
Citation Information
Patent Citations
Ship piping research and development design method, storage medium and computer equipment
CN115630441A
Simulation method for ship research, development and design and simulation research, development and design knowledge pushing system
CN115659513A
Knowledge pushing-based ship electrical research and development design method and ship
CN115675781A
