Computer system and program code conversion method

Abstract

This computer system is connected to a program for performing conversion between device experiment code and simulation code, receives a conversion request including device experiment code or simulation code as target code, and repeatedly executes processing for acquiring first converted code obtained by converting the target code into the other program code using the program, processing for acquiring second converted code obtained by converting the first converted code into the other program code using the program, processing for determining whether the target code and the second converted code are similar, and fourth processing for setting the second converted code as new target code when the target code and the second converted code are not similar, until the target code and the second converted code are similar.

Description

Computer System and Program Code Conversion Method ,

[0006] ,

[0005] Incorporation by Reference

[0001] This application claims the priority of Japanese Patent Application No. 2025-007928 filed on January 20, 2025, and incorporates its content by reference into this application.

[0002] The present invention relates to a technology for converting program codes.

[0003] Devices used in research such as quantum physics are limited in number and cannot be frequently experimented with, so research may not be able to be advanced. Also, it may be difficult to prepare the conditions for experiments. When it is difficult to execute an experiment using a device, a simulation using a simulator that mimics the device is useful. On the other hand, in order to obtain evidence showing the usefulness etc. of a system developed based on an experiment by simulation, it is desirable to actually operate the system using a device. [[ID=​​​​​​​In response to this, a method using program code conversion technology can be considered. For example, Patent Document 1 discloses "a configuration comprising: a source language specification data file 6 that describes the source language specification; a target language specification data file 7 that describes the target language specification; a conversion rule data file 8 that describes conversion rule data for converting from the source language to the target language; a language conversion processing generation means 3 that extracts necessary descriptive data from each of these file data, performs lexical conversion, syntactic conversion, and semantic conversion to generate source data for generating a target program 9 from a source program 5; and a language conversion processing means 4 that analyzes the source program using the source data of this language conversion processing generation means, converts it into intermediate data in the form of a syntax tree, and converts this intermediate data into a target language."

[0007] Japanese Patent Application Publication No. 5-197560

[0008] By using program code conversion technology, bidirectional conversion between simulation code and device experiment code becomes possible. However, program code obtained using program code conversion technology may contain errors. Therefore, verification of the obtained program code is necessary.

[0009] However, because system researchers are not familiar with the devices, it is difficult for them to identify errors in the device experiment code converted from the simulation code.

[0010] The present invention aims to provide a system and method for converting program code for conducting device experiments or simulation experiments with reduced errors.

[0011] A typical example of the invention disclosed in this application is as follows: A computer system comprising a processor, a storage device connected to the processor, and a network interface connected to the processor, which is accessiblely connected to a program that performs conversions between device experiment code for performing experiments using physical devices and simulation code for performing simulation experiments for simulating the experiments, wherein the processor receives a conversion request that includes the device experiment code or the simulation code as a target code, and uses the program to perform a first process of obtaining a first conversion code obtained by converting the target code to the other program code, a second process of obtaining a second conversion code obtained by converting the first conversion code to the other program code, a third process of determining whether the target code and the second conversion code are similar, and a fourth process of setting the second conversion code as a new target code if the target code and the second conversion code are not similar, which are repeatedly executed until the target code and the second conversion code are similar, and if it is determined that the target code and the second conversion code are similar, the first conversion code is output.

[0012] According to the present invention, it is possible to convert program code for performing device experiments or simulation experiments with reduced errors. Other problems, configurations, and effects will be clarified by the following description of the embodiments.

[0013] This figure shows an example of the system configuration of Example 1. This figure shows an example of the hardware configuration of the computer that constitutes the code conversion support system of Example 1. This figure shows an example of the user database of Example 1. This figure shows an example of the program code stored in the conversion history database of Example 1. This figure shows an example of the program code stored in the code database of Example 1. This figure shows an example of the program code stored in the code database of Example 1. This is a flowchart illustrating an example of the processing performed by the code conversion support system of Example 1. This figure shows an example of the screen presented by the code conversion support system of Example 1. This figure shows an image of the processing performed by the code conversion support system of Example 1. This is a flowchart illustrating an example of the similarity determination processing performed by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1. This figure shows a specific example of code conversion by the code conversion support system of Example 1.

[0014] The embodiments of the present invention will be described below with reference to the drawings. However, the present invention is not to be construed as being limited to the embodiments described below. It will be readily apparent to those skilled in the art that the specific configuration can be modified without departing from the spirit or intent of the present invention.

[0015] In the configuration of the invention described below, identical or similar components or functions are denoted by the same reference numerals, and redundant descriptions are omitted.

[0016] The designations "First," "Second," "Third," etc., used in this specification are for the purpose of identifying constituent elements and do not necessarily limit their number or order.

[0017] Figure 1 shows an example of the system configuration of Example 1. Figure 2 shows an example of the hardware configuration of the computer that constitutes the code conversion support system of Example 1.

[0018] The system consists of a code conversion support system 100, an experimental system 101, a simulation system 102, a large-scale language model system 103, and a terminal 104. The code conversion support system 100 connects to the experimental system 101, the simulation system 102, the large-scale language model system 103, and the terminal 104 via a network such as a LAN (Local Area Network).

[0019] Experimental system 101 is a system for conducting device experiments. Simulation system 102 is a system for conducting simulation experiments. Terminal 104 is a terminal operated by a device researcher or a system researcher.

[0020] The large-scale language model system 103 is a system that provides a large-scale language model (LLM). The large-scale language model system 103 receives input prompts containing the content of the task to be executed by the LLM, inputs prompts to the LLM, and responds with the output of the LLM.

[0021] The code conversion support system 100 assists in the conversion between simulation code and device experiment code. The code conversion support system 100 consists of a computer 200 as shown in Figure 2. The computer 200 has a processor 201, a main memory 202, a secondary memory 203, and a network interface 204. Each hardware element is connected to the others via a bus 205.

[0022] The processor 201 executes a program stored in the main memory 202. By executing processing according to the program, the processor 201 operates as a functional unit (module) that realizes a specific function. In the following description, when the processing is described with a functional unit as the subject, it indicates that the processor 201 is executing a program that realizes that functional unit.

[0023] The main memory 202 is a memory unit that stores the program executed by the processor 201 and the information used by the program. The main memory 202 is also used as a work area.

[0024] The secondary storage device 203 is a large-capacity storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive). The programs and information stored in the main memory 202 may also be stored in the secondary storage device 203. In this case, the processor 201 reads the programs and information from the secondary storage device 203 and loads them into the main memory 202.

[0025] The network interface 204 is an interface for connecting to a network.

[0026] The code conversion support system 100 includes a code conversion cycle control unit 110, a code comparison unit 111, a code management unit 112, and a user management unit 113, and also maintains a user database 120, a conversion history database 121, and a code database 122.

[0027] Furthermore, each module in the computer may be combined into a single module, or a single module may be divided into multiple modules according to its function.

[0028] Figure 3 shows an example of the user database 120 in Example 1.

[0029] The user database 120 is a database that stores information for managing users. The user database 120 stores, for example, a table 300 as shown in Figure 3. The table 300 stores entries that include user ID 301, username 302, type 303, group 304, and review count 305.

[0030] User ID 301 is a field that stores the user's ID. Username 302 is a field that stores the user's name. Type 303 is a field that stores the user's development type. Type 303 will store either a systems researcher or a device researcher. Group 304 is a field that stores the ID of the research group (research subject). Review count 305 is a field that stores the number of times the program code has been reviewed.

[0031] The user management unit 113 receives user registration requests from the terminal 104. When the user management unit 113 receives a registration request, it adds an entry to the table 300 and sets values ​​for user ID 301, username 302, type 303, and group 304. The group ID may be set in advance, or it may be determined by grouping users based on program code created by the user management unit 113.

[0032] Figure 4 shows an example of program code stored in the conversion history database 121 of Example 1.

[0033] The conversion history database 121 is a database that stores the conversion results of program code. The conversion history database 121 stores, for example, a table 400 as shown in Figure 4. The table 400 stores entries that include a history ID 401, a timestamp 402, a code before conversion 403, a code after conversion 404, a client 405, a reviewer 406, feedback 407, and an evaluation score 408.

[0034] History ID 401 is a field that stores the ID of the program code conversion result. Timestamp 402 is a field that stores the date and time the program code was converted. Pre-conversion code 403 is a field that stores the program code before conversion. Post-conversion code 404 is a field that stores the converted program code. Requester 405 is a field that stores the name of the user who requested the review of the converted program code. Reviewer 406 is a field that stores the name of the user who reviewed the converted program code. Feedback 407 is a field that stores the feedback in the review of the converted program code. Evaluation score 408 is a field that stores the requester's evaluation of the feedback.

[0035] Figures 5A and 5B show examples of program code stored in the code database 122 of Embodiment 1.

[0036] The code database 122 stores, for example, device experiment code as shown in Figure 5A and simulation code as shown in Figure 5B. The code database 122 also stores converted program code.

[0037] Figure 6 is a flowchart illustrating an example of the processing performed by the code conversion support system 100 of Example 1. Figure 7 is a diagram showing an example of a screen displayed by the code conversion support system 100 of Example 1. Figure 8 is a diagram showing an image of the processing performed by the code conversion support system 100 of Example 1.

[0038] A device researcher or system researcher uses terminal 104 to send a code conversion request, including the program code to be converted, to the code conversion support system 100. The code conversion request includes identification information such as the user's ID. Here, we will explain using the example of a system researcher sending a code conversion request that includes simulation code.

[0039] The code conversion support system 100 receives a code conversion request including a simulation code (target code) from the terminal 104 (step S101).

[0040] The code conversion loop control unit 110 acquires the conversion history related to the simulation code from the conversion history database 121 (step S102). Since there is no conversion history at the first time point, the process of step S102 may be omitted.

[0041] The code conversion loop control unit 110 acquires the device experiment code (first conversion code) into which the simulation code has been converted (step S103).

[0042] Specifically, the code conversion loop control unit 110 generates a prompt including the simulation code and instructing the conversion to the device experiment code, and transmits it to the large language model system 103. The conversion history is included in the prompt. Note that the conversion history may not be included. The effect of improving the accuracy of code conversion can be expected by including the conversion history.

[0043] The large language model system 103 inputs the prompt to the LLM and transmits the device experiment code, which is the output of the LLM, to the code conversion support system 100.

[0044] The code conversion loop control unit 110 identifies the device researcher (reviewer) who is requested to review the device experiment code, and requests the review of the device experiment code (step S104).

[0045] Specifically, the code conversion loop control unit 110 refers to the table 300 of the user database 120 and identifies the device researcher belonging to the same group as the system researcher who requested the code conversion. A list of groups for which review requests are possible may be separately held, and the reviewer may be identified based on the list. The code conversion loop control unit 110 presents a screen 700 as shown in FIG. 7 to the terminal 104 operated by the identified device researcher. An efficient review can be realized by requesting a review from a device researcher who may obtain useful feedback.

[0046] The screen 700 includes a request information area 701, a code area 702, and a review area 703.

[0047] The request information area 701 is an area for displaying the content of the review request and the like. In the request information area 701 of FIG. 7, information including the correction request ID, the requester, the performance of the request, and the like is presented. The information regarding the performance of the request can be generated by analyzing the conversion history.

[0048] The code area 702 is an area for displaying the program code to be reviewed. When the review request is accepted, the program code displayed in the code area 702 can be corrected.

[0049] The review area 703 is an area for inputting the review content.

[0050] If the specified reviewer rejects the review request, the code conversion loop control unit 110 identifies a new reviewer.

[0051] The code conversion loop control unit 110 may identify a plurality of reviewers at once and request a review from the plurality of reviewers.

[0052] The code conversion loop control unit 110 acquires the device experiment code corrected via the screen 700 (step S105). At this time, the code conversion loop control unit 110 also acquires feedback via the screen 700.

[0053] The code conversion loop control unit 110 acquires the simulation code (second conversion code) obtained by converting the corrected device experiment code (step S106).

[0054] Specifically, the code conversion loop control unit 110 generates a prompt including the corrected device experiment code and instructing conversion to the simulation code, and transmits it to the large language model system 103. The prompt may include the conversion history.

[0055] The large language model system 103 inputs the prompt to the LLM and transmits the simulation code, which is the output of the LLM, to the code conversion support system 100.

[0056] The code conversion cycle control unit 110 displays the review results to the terminal 104 operated by the system researcher who made the request, and accepts the evaluation score (step S107).

[0057] The code conversion cycle control unit 110 registers the conversion history in the conversion history database 121 (step S108). At this time, the code conversion cycle control unit 110 instructs the code management unit 112 to save the modified device experiment code.

[0058] Specifically, the code conversion cycle control unit 110 adds an entry to the table 400. The code conversion cycle control unit 110 sets the review request ID in history ID 401, sets the date and time the simulation code was converted in timestamp 402, sets the simulation code in pre-conversion code 403, sets the modified device experiment code in post-conversion code 404, and sets the feedback in feedback 407. The code conversion cycle control unit 110 sets the name of the system researcher in requester 405 and the name of the device researcher who performed the review in reviewer 406. The code conversion cycle control unit 110 sets the evaluation score in evaluation score 408.

[0059] In step S102, the code conversion cycle control unit 110 instructs the code comparison unit 111 to execute a similarity determination process in order to determine whether the simulation code to be converted (target code) and the simulation code (second conversion code) obtained in step S106 are similar (step S109). Details of the similarity determination process will be described later.

[0060] The code conversion cycle control unit 110 determines whether the two simulation codes are similar based on the output of the code comparison unit 111.

[0061] If the two simulation codes are not similar, the code conversion cycle control unit 110 presents the simulation code obtained in step S106 to the system researcher and accepts the modification of the simulation code (step S111).

[0062] The code conversion cycle control unit 110 sets the modified simulation code to the new simulation code to be converted (step S112), and then returns to step S102.

[0063] If the two simulation codes are similar, the code conversion cycle control unit 110 outputs the modified device experiment code (modified first conversion code) obtained in step S105 to the terminal 104 operated by the system researcher (step S113). After that, the code conversion support system 100 completes the series of processes.

[0064] For example, the code conversion cycle control unit 110 presents the modified device experiment code to the terminal 104. Alternatively, after presenting the modified device experiment code to the terminal 104, the code conversion cycle control unit 110 may input the device experiment code into the experiment system 101.

[0065] The present invention's method will now be described. Simulation code and device experiment code performing equivalent experiments are functionally identical. However, program code of different types differs in its data structure and class / module structure. In the following description, data structure and class / module structure will be referred to as program structure.

[0066] (Characteristic 1) The smaller the difference in program structure, the higher the probability that the program code can be converted correctly.

[0067] (Characteristic 2) Part of the program structure of the converted program code is influenced by the program structure of the target program code.

[0068] As shown in Figure 8, the code conversion support system 100 repeatedly performs conversions between simulation code and device experiment code using the large-scale language model system 103. By repeatedly performing code conversions, characteristic 2 results in program code that contains the program structures of both simulation code and device experiment code in roughly equal proportions. Since the program structures before and after conversion of program code that contains the program structures of both to roughly equal proportions are almost identical, characteristic 1 ensures that conversion from one program code to another is performed correctly.

[0069] This invention achieves efficient and highly accurate program code conversion by conducting reviews during the iterative conversion of program code and accepting revisions from researchers.

[0070] When a systems researcher requests a device researcher to review device experiment code and receives direct feedback, the device researcher can review the code but lacks an understanding of the simulation framework and the systems researcher's intentions, making it difficult for them to provide useful feedback for modifying the simulation code. Therefore, the code conversion support system 100 converts the modified device experiment code, based on the device researcher's feedback, into simulation code. If the two simulation codes are not similar, the system researcher presents the converted simulation code to the systems researcher. This allows the systems researcher to utilize their knowledge of the simulation framework to verify whether the intended feedback has been received and to make modifications. Furthermore, the device researcher does not need to possess knowledge of the simulation framework and can make modifications using their knowledge of the physical device, thus reducing the burden of the review process.

[0071] The LLM may perform the review. However, the review is not necessarily required. In this case, steps S104, S107, and S111 can be omitted.

[0072] Figure 9 is a flowchart illustrating an example of the similarity determination process performed by the code conversion support system 100 of Example 1.

[0073] The code comparison unit 111 divides the target code and the second conversion code into line units (step S201).

[0074] The code comparison unit 111 selects one line of the target code (step S202).

[0075] The code comparison unit 111 compares each line of the selected target code with each line of the second conversion code and searches for a line in the second conversion code that matches the line of the selected target code (step S203). If a line in the second conversion code that matches the line of the selected target code exists, the code comparison unit 111 associates the line of the selected target code with the matching line of the second conversion code and saves it.

[0076] The code comparison unit 111 determines whether processing has been completed for all lines of the target code (step S204).

[0077] If processing has not been completed for all lines of the target code, the code comparison unit 111 returns to step S202.

[0078] If processing is completed for all lines of the target code, the code comparison unit 111 determines whether the number of lines of the target code that do not match any line of the second converted code is greater than a threshold (step S205).

[0079] If the number of lines in the target code that do not match any line in the second conversion code is greater than the threshold, the code comparison unit 111 determines that the target code and the second conversion code are dissimilar (step S206).

[0080] If the number of lines in the target code that do not match any line in the second conversion code is less than or equal to a threshold, the code comparison unit 111 determines that the target code and the second conversion code are similar (step S207).

[0081] Note that the process shown in Figure 9 is just one example and is not limited thereto. For example, the code comparison unit 111 may calculate the similarity using the embedded representations of the two program codes and determine whether the two program codes are similar or not based on that similarity.

[0082] Next, a specific example of program code conversion in this embodiment will be described. Figures 10A, 10B, 10C, 10D, 10E, 10F, and 10G are diagrams showing specific examples of code conversion by the code conversion support system 100 of Embodiment 1.

[0083] The code conversion support system 100 receives a code conversion request including the simulation code 1000 shown in Figure 10A (step S101), and obtains the device experiment code 1001 shown in Figure 10B by inputting a prompt to instruct the large-scale language model system 103 to convert the simulation code 1000 (step S103).

[0084] Device experiment code 1001 contains the error shown in the shaded area. After review by the device researcher, the corrected device experiment code 1002 shown in Figure 10C is obtained (step S105). The underlined portion of device experiment code 1002 indicates the correction.

[0085] The code conversion support system 100 obtains the simulation code 1003 shown in Figure 10D by inputting a prompt to the large-scale language model system 103 instructing it to convert the device experiment code 1002 (step S106).

[0086] The code conversion support system 100 performs a similarity determination process on simulation code 1000 and simulation code 1003 (step S109), and determines that the two simulation codes are dissimilar (step S110 is NO).

[0087] Simulation code 1003 contains an error shown in the rectangular area. After review by the system researcher, the corrected simulation code 1004 shown in Figure 10E is obtained (step S111). The underlined portion of simulation code 1004 indicates the corrected part.

[0088] The code conversion support system 100 obtains the device experiment code 1005 shown in Figure 10F by inputting a prompt to instruct the large-scale language model system 103 to convert the simulation code 1004 (step S103).

[0089] Since device experiment code 1005 does not contain any errors, no corrections are made by the device researchers. Therefore, the code conversion support system 100 acquires device experiment code 1005 as a corrected code (step S105).

[0090] The code conversion support system 100 obtains the simulation code 1006 shown in Figure 10G by inputting a prompt to the large-scale language model system 103 instructing it to convert the device experiment code 1005 (step S106).

[0091] The code conversion support system 100 performs a similarity determination process on simulation code 1004 and simulation code 1006 (step S109), and determines that the two simulation codes are similar (step S110 is YES).

[0092] The code conversion support system 100 outputs the device experiment code 1005 (step S113).

[0093] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. Furthermore, for example, the embodiments described above are detailed explanations of the configuration in order to clearly illustrate the present invention, and are not necessarily limited to those having all the configurations described. In addition, some of the configurations in each embodiment can be added to, deleted from, or replaced with other configurations.

[0094] Furthermore, each of the above-mentioned configurations, functions, processing units, processing means, etc., may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. The present invention can also be implemented by software program code that realizes the functions of the embodiment. In this case, a storage medium on which the program code is recorded is provided to a computer, and the processor of that computer reads the program code stored in the storage medium. In this case, the program code read from the storage medium itself realizes the functions of the embodiment described above, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media used to supply such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, and the like.

[0095] Furthermore, the program code that implements the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, Perl, Shell, PHP, Python, and Java.

[0096] Furthermore, the program code for the software that implements the functions of the embodiment may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the computer's processor may read and execute the program code stored in the storage means or storage medium.

[0097] In the above-described embodiment, the control lines and information lines shown are those deemed necessary for explanation and do not necessarily represent all control lines and information lines in the actual product. All components may be interconnected.

Claims

1. A computer system comprising a processor, a storage device connected to the processor, and a network interface connected to the processor, and being accessiblely connected to a program that performs conversions between device experiment code for performing experiments using physical devices and simulation code for performing simulation experiments for simulating the experiments, wherein the processor receives a conversion request that includes the device experiment code or the simulation code as a target code, and using the program, performs a first process to obtain a first conversion code obtained by converting the target code to the other program code, a second process to obtain a second conversion code obtained by converting the first conversion code to the other program code, a third process to determine whether the target code and the second conversion code are similar, and a fourth process to set the second conversion code as a new target code if the target code and the second conversion code are not similar, and repeats these processes until the target code and the second conversion code are similar, and outputs the first conversion code if it is determined that the target code and the second conversion code are similar.

2. A computer system according to claim 1, wherein the program is a large-scale language model program, and in the first process, the processor generates a first prompt including an instruction to convert the target code to the other program code, inputs the first prompt to the program and obtains the first converted code, and in the second process, the processor generates a second prompt including an instruction to convert the first converted code to the other program code, inputs the second prompt to the program and obtains the second converted code.

3. A computer system according to claim 2, wherein the system is connected to a plurality of terminals operated by either a first user performing the experiment or a second user performing the simulation, wherein in the first process, the processor identifies the first user or the second user requesting a review of the first conversion code as a reviewer, sends a review request to the terminal operated by the reviewer, and obtains the result of modifying the first conversion code via the terminal, wherein in the second process, the processor generates the second prompt including an instruction to convert the modified first conversion code into the other program code, wherein in the fourth process, the processor presents the second conversion code to the terminal operated by the first user or the second user who input the conversion request, obtains the result of modifying the second conversion code via the terminal, and sets the modified second conversion code as the new target code.

4. A computer system according to claim 3, wherein it maintains a database for storing user data for managing the first user and the second user, the user data includes a group identifier set based on the research subject of the first user or the second user, the conversion request includes the group identifier, and in the first process, the processor refers to the database to identify the first user or the second user to whom the same group identifier as the group identifier included in the conversion request has been assigned.

5. A computer system according to claim 3, wherein the processor records a history of program code conversion in the first process and the second process, in the first process the processor generates the first prompt including the history, and in the second process the processor generates the second prompt including the history.

6. A computer system according to claim 5, wherein the history includes identification information of the first user or the second user who input the conversion request, and in the first process, the processor generates review request history information of the first user or the second user who sent the conversion request based on the history, and transmits the review request including the review request history information to the terminal operated by the reviewer.

7. A program code conversion method to be executed by a computer system, wherein the computer system has a processor, a storage device connected to the processor, and a network interface connected to the processor, and is accessiblely connected to a program that performs conversion between device experiment code for performing experiments using physical devices and simulation code for performing simulation experiments for simulating the experiments, and the program code conversion method is characterized by comprising: a step in which the processor receives a conversion request that includes the device experiment code or the simulation code as target code; a step in which the processor uses the program to obtain a first conversion code obtained by converting the target code to the other program code; a step in which the processor uses the program to obtain a second conversion code obtained by converting the first conversion code to the other program code; a step in which the processor repeatedly performs the following until the target code and the second conversion code are similar: a step in which the processor uses the program to determine whether the target code and the second conversion code are similar or not; a step in which, if the target code and the second conversion code are not similar, the processor sets the second conversion code as a new target code; and a step in which, if the target code and the second conversion code are determined to be similar, the processor outputs the first conversion code.

8. A program code conversion method according to claim 7, wherein the program is a large-scale language model program, and in the first process, the processor generates a first prompt including an instruction to convert the target code to the other program code, inputs the first prompt to the program and obtains the first conversion code, and in the second process, the processor generates a second prompt including an instruction to convert the first conversion code to the other program code, inputs the second prompt to the program and obtains the second conversion code.

9. A program code conversion method according to claim 8, comprising: connecting to a plurality of terminals operated by either a first user performing the experiment or a second user performing the simulation; in the first process, the processor identifies the first user or the second user requesting a review of the first conversion code as a reviewer, sends a review request to the terminal operated by the reviewer, and obtains the result of modifying the first conversion code via the terminal; in the second process, the processor generates the second prompt including an instruction to convert the modified first conversion code to the other program code; and in the fourth process, the processor presents the second conversion code to the terminal operated by the first user or the second user who input the conversion request, obtains the result of modifying the second conversion code via the terminal, and sets the modified second conversion code as the new target code.

Images