Development system, method, storage medium for magnetic resonance sequences

Abstract

The present disclosure provides a development system, method and storage medium of a magnetic resonance sequence. The development system comprises a client and a server connected in communication with the client; the client displays a front-end page for development of the magnetic resonance sequence, and the server is deployed with a service for development of the magnetic resonance sequence; the client determines a target service matched with a development task of a sequence development request generated through the front-end page, and sends a calling request of the target service to the server in response to the sequence development request; the server feeds back the target service to the client in response to the calling request; and the client is further used for calling the target service to execute the development task. The present disclosure does not require the user to build a development environment by himself, simplifies the development operation of the magnetic resonance sequence, and can ensure the consistency of the development environment, and has the advantages of facilitating the development personnel of the development system to uniformly maintain the development environment, and avoiding the core technology of the development system from being leaked.

Description

Technical Field

[0001] This disclosure relates to the field of scientific instruments, and in particular to a system, method, and storage medium for developing magnetic resonance sequences. Background Technology

[0002] Magnetic resonance imaging (MRI) sequences are used to control the coordinated operation of various components in a scanning device, defining the timing and logic for completing a scan. Different MRI sequences need to be developed for different diseases and scanning requirements. Currently, platforms used for developing MRI sequences require users to install and set up a development environment on their local computers, which is inconvenient and hinders the unified maintenance of the development environment. Furthermore, there is a risk of core platform technology being leaked. Summary of the Invention

[0003] The technical problem to be solved by this disclosure is to overcome the above-mentioned defects in the prior art and provide a magnetic resonance sequence development system, method, storage medium, and computer program product.

[0004] This disclosure solves the above-mentioned technical problems through the following technical solution:

[0005] In a first aspect, a magnetic resonance imaging (MRI) sequence development system is provided, comprising: a client and a server communicatively connected to the client; the client displays a front-end page for MRI sequence development, and the server deploys services for MRI sequence development;

[0006] The client, in response to the sequence development request generated through the front-end page, determines the target service that matches the development task of the sequence development request, and sends a call request for the target service to the server;

[0007] The server, in response to the call request, sends the target service back to the client;

[0008] The client is also used to invoke the target service to perform the development task.

[0009] Optionally, the development task includes a code editing task for the magnetic resonance sequence; the client is specifically used to call the target service that performs the code editing task, so as to provide a text editor or integrated development environment for the code development of the magnetic resonance sequence through the front-end page;

[0010] And / or, the development task includes a code compilation task for the magnetic resonance sequence; the client is specifically used to call the target service that executes the code compilation task to generate a prototype file of the magnetic resonance sequence, and to display the prototype file through the front-end page;

[0011] And / or, the development task includes a sequence execution task for magnetic resonance imaging (MRI) sequences; the client is specifically used to call the target service that executes the sequence execution task to trigger the execution of the prototype file of the MRI sequence, and to display the execution results through the front-end page;

[0012] And / or, the development task includes a sequence translation task of a magnetic resonance sequence; the client is specifically used to call the target service that performs the sequence translation task to translate the prototype file of the magnetic resonance sequence into a prototype file that can be recognized by the scanning device, package the translated prototype file into an installation package, and display the installation package through the front-end page.

[0013] Optionally, the front-end page includes a file import control for importing the prototype file; the client, in response to the file import control being triggered, obtains the prototype file through the front-end page;

[0014] And / or, the front-end page includes a sharing control for sharing the prototype file; in response to the sharing control being triggered, the client shares the selected prototype file to the target area through the front-end page;

[0015] And / or, the front-end page includes a function extension control for function expansion; in response to the function extension control being triggered, the client sends the function service requirements obtained through the function extension control to the server, so that the server can send the function service requirements to the development end; or, the client sends the user development service obtained through the function extension control to the server.

[0016] Optionally, when the client calls the target service to execute the code compilation task, the client is also used to display compilation logs through the front-end page;

[0017] And / or, if the client calls the target service to execute the sequence running task, the client is also used to display the running log through the front-end page.

[0018] Optionally, the call request carries the login account information of the front-end page; if the server successfully authenticates the login account information, it sends the target service back to the client.

[0019] And / or, the front-end page is a web page;

[0020] And / or, the service used for developing the magnetic resonance sequence adopts a microservice architecture.

[0021] Secondly, a method for developing magnetic resonance imaging (MRI) sequences is provided, applied to a client-side application, wherein the client displays a front-end page for developing the MRI sequences; the development method includes:

[0022] In response to a sequence development request generated through the front-end page, a target service matching the development task of the sequence development request is determined;

[0023] Send the request to invoke the target service to the server;

[0024] The target service reported by the server is invoked to execute the development task.

[0025] Optionally, the development task includes a code editing task for the magnetic resonance sequence; invoking the target service fed back by the server to implement the development task includes: invoking the target service that executes the code editing task to provide a text editor or integrated development environment for the code development of the magnetic resonance sequence through the front-end page;

[0026] And / or, the development task includes a code compilation task for the magnetic resonance sequence; invoking the target service fed back by the server to implement the development task, including: invoking the target service that executes the code compilation task to generate a prototype file of the magnetic resonance sequence, and displaying the prototype file through the front-end page;

[0027] And / or, the development task includes a sequence execution task of a magnetic resonance sequence; invoking the target service fed back by the server to realize the development task includes: invoking the target service that executes the sequence execution task to trigger the execution of the prototype file of the magnetic resonance sequence, and displaying the execution result through the front-end page;

[0028] And / or, the development task includes a sequence translation task of a magnetic resonance sequence; invoking the target service fed back by the server to implement the development task includes: invoking the target service that executes the sequence translation task to translate the prototype file of the magnetic resonance sequence into a prototype file that can be recognized by the scanning device, packaging the translated prototype file into an installation package, and displaying the installation package through the front-end page.

[0029] Thirdly, a method for developing magnetic resonance imaging (MRI) sequences is provided, applied to a server, wherein the server is deployed with services for developing the MRI sequences; the development method includes:

[0030] In response to a request to invoke a target service sent by the client, the target service is fed back to the client so that the client can invoke the target service; wherein, the target service is a service that matches the development task of the sequence development request generated through the front-end page.

[0031] Optionally, the call request carries the login account information of the front-end page; the return of the target service to the client includes:

[0032] Authenticate the login account information;

[0033] Upon successful authentication, the target service is returned to the client.

[0034] Thirdly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method for developing magnetic resonance sequences as described in any one of the second or third aspects.

[0035] Based on common knowledge in the field, the above-mentioned preferred conditions can be combined arbitrarily to obtain various preferred embodiments of this disclosure.

[0036] The positive and progressive effects of this disclosure are as follows: In this disclosure, users develop magnetic resonance imaging (MRI) sequences by calling services on the server from the client side, eliminating the need for users to set up their own development environment and simplifying the development process. Furthermore, the service call method ensures consistency of the development environment, preventing situations where the MRI sequence runs correctly on one client but malfunctions on other clients. This disclosure also offers advantages such as facilitating unified maintenance of the development environment by developers and preventing the leakage of core technologies. Attached Figure Description

[0037] Figure 1 A schematic diagram of the architecture of a magnetic resonance sequence development system provided as an exemplary embodiment of this disclosure;

[0038] Figure 2 A flowchart illustrating a method for developing a magnetic resonance sequence as provided in an exemplary embodiment of this disclosure;

[0039] Figure 3 A flowchart illustrating another method for developing a magnetic resonance sequence provided as an exemplary embodiment of this disclosure;

[0040] Figure 4 This is a schematic diagram of the structure of an electronic device provided as an exemplary embodiment of the present disclosure. Detailed Implementation

[0041] The present disclosure is further illustrated below by way of embodiments, but the present disclosure is not limited to the scope of the embodiments described herein.

[0042] The prefixes such as "first" and "second" used in this disclosure are merely for distinguishing different descriptive objects and do not limit the position, order, priority, quantity, or content of the described objects. The use of ordinal numbers and other prefixes used to distinguish descriptive objects in this disclosure does not constitute a limitation on the described objects. The description of the described objects is given in the claims or the context of the embodiments, and should not be construed as an unnecessary limitation. Furthermore, in the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0043] Figure 1 This is a schematic diagram of the architecture of a magnetic resonance imaging (MRI) sequence development system provided as an exemplary embodiment of the present disclosure. The development system includes a client 11 and a server 12 communicatively connected to the client 11. The client can be software running on a terminal device, such as a desktop application or mobile application. The client 11 communicates with the server 12 via a wired or wireless network through the terminal device. The client can also be a hardware entity, such as any type of device capable of enabling front-end page interaction with the user, such as a mobile phone, tablet, laptop, PDA (Personal Digital Assistants), or wearable device (such as smart glasses or smartwatches). The client directly communicates with the server 12 via a wired or wireless network.

[0044] It should be noted that server 12 can establish connections with multiple clients 11 simultaneously, and is not limited to... Figure 1 One of them is shown.

[0045] Client 11 displays a front-end page for developing magnetic resonance imaging (MRI) sequences. The front-end page includes various controls to meet users' MRI sequence development needs. Users can trigger various development tasks for MRI sequence development through these controls. Development tasks may include, but are not limited to, MRI sequence code editing, code compilation, sequence execution, and sequence translation tasks.

[0046] Server 12 is deployed with services for magnetic resonance sequence development. Corresponding to the development tasks, server 12 is deployed with services for implementing various development tasks, such as editing services for code editing tasks, compilation services for code compilation tasks, sequence execution services for sequence execution tasks, and sequence translation services for sequence translation tasks. Server 12 provides magnetic resonance sequence development services to clients 11. The server for magnetic resonance sequence development can communicate and connect with multiple clients 11 simultaneously, allowing multiple clients 11 to call services and implement magnetic resonance sequence development. Server 12 can be a physical server containing a single host, or it can be a virtual server hosted in a host cluster.

[0047] Client 11 develops magnetic resonance imaging (MRI) sequences by calling services deployed on server 12. Because MRI sequence development is achieved through service calls, users do not need to install and maintain heavy components such as editors and databases on client 11. This reduces the hardware requirements of client 11, lowers overall hardware costs, and enables lightweight MRI sequence development.

[0048] The following section provides a further explanation of the system development process.

[0049] When developing magnetic resonance sequences, users generate sequence development requests through controls on the user page.

[0050] In response to the sequence development request generated by the front-end page, client 11 determines the target service that matches the development task of the sequence development request and sends a call request for the target service to server 12.

[0051] In response to the call request, server 12 sends the target service back to client 11, so that client 11 can call the target service to complete the development task.

[0052] In this embodiment, the user develops the magnetic resonance sequence by calling services in the server 12 through the client 11. The user does not need to build their own development environment, simplifying the development process. Furthermore, the service call method ensures the consistency of the development environment, preventing situations where the magnetic resonance sequence runs correctly on one client 11 but malfunctions on other clients 11. This disclosure also has advantages such as facilitating unified maintenance of the development environment by developers and preventing the leakage of core technologies. Moreover, since there is no concern about core technology leakage, services used to implement various functions / development tasks can be made available to users, meeting their diverse needs and thus improving the user experience.

[0053] In one embodiment, the development task includes a code editing task for the magnetic resonance sequence; the client 11 is specifically used to call the target service that performs the code editing task to provide a text editor or integrated development environment for the code development of the magnetic resonance sequence through a front-end page.

[0054] For example, if a user needs to edit the code of an MRI sequence, the code editing control on the user's page is triggered. The client 11 then sends a request to the server 12 to invoke the editing service (target service). The server 12 sends the editing service back to the client 11, which then invokes the editing service to provide a text editor or integrated development environment for editing the MRI sequence code.

[0055] In this embodiment, the editing of magnetic resonance sequences can be achieved by calling the service. Users do not need to set up their own development environment or understand the code logic of the editing service. The workflow is simple, easy to learn, has a low learning threshold, and is easy to use, thereby improving the efficiency of users in editing magnetic resonance sequences.

[0056] In one embodiment, the user page provides a code editing window where users can write, view, and modify the code for the magnetic resonance imaging (MRI) sequence. This window supports partitioned display, allowing users to write different code blocks in different partitions according to their needs, such as import statements and main logic, thus enabling flexible and free code segmentation.

[0057] The code editing language can include, but is not limited to, Python, MATLAB, C, etc. The development system in this embodiment supports various development languages.

[0058] In one embodiment, the user page also provides code templates. Users can select the desired code template through the corresponding controls on the user page and modify the code template to simplify the editing of magnetic resonance sequences and improve the efficiency of magnetic resonance sequence editing and development.

[0059] In one embodiment, the development task includes compiling code for the magnetic resonance sequence; the client 11 is specifically used to call the target service that executes the code compilation task to generate a prototype file for the magnetic resonance sequence, and to display the prototype file through a front-end page for users to view, download, and use. The prototype file for the magnetic resonance sequence is also known as a .Seq file.

[0060] For example, if a user requests to compile the code for a magnetic resonance imaging (MRI) sequence, the code compilation control on the user's page is triggered. Client 11 then sends a request to the server 12 to invoke the compilation service (target service). Server 12 sends the compilation service back to client 11, which then invokes the compilation service to compile the MRI sequence code. The user page also supports interactive running and breakpoint debugging, allowing users to easily view the compilation results and variable values.

[0061] In this embodiment, the compilation of magnetic resonance sequences can be achieved simply by calling the service. Users do not need to set up their own development environment or understand the code logic of the compilation service. The workflow is simple, easy to learn, and has a low learning threshold, making it highly usable and thus improving the efficiency of compiling magnetic resonance sequences. Furthermore, since the development system in this embodiment provides a consistent development environment for each client 11, it avoids the situation where a magnetic resonance sequence can be compiled normally on one client 11 but fails to compile on other clients 11, thereby improving the compilation efficiency of magnetic resonance sequences.

[0062] In one embodiment, during the process of client 11 calling the compilation service, client 11 also displays compilation logs through a front-end page. The compilation logs may include, but are not limited to, at least one of the following: compilation time, error messages, and suggested modifications, so that users can understand the code compilation status.

[0063] In one embodiment, the development task includes a sequence execution task for a magnetic resonance sequence; the client 11 is specifically used to call the target service that executes the sequence execution task to trigger the execution of the prototype file of the magnetic resonance sequence, and to display the execution results through a front-end page.

[0064] For example, when a user needs to run the prototype file of a magnetic resonance sequence, the sequence run control on the user page is triggered. Client 11 then sends a request to the sequence run service (target service) to server 12. Server 12 sends the sequence run service back to client 11, and client 11 calls the sequence run service to run the prototype file of the magnetic resonance sequence. The user page also supports viewing the waveforms obtained after the prototype file is run (representing the physical properties of the magnetic resonance sequence). Users can identify whether the code logic of the magnetic resonance sequence is correct based on the waveforms, providing a reference for code modification.

[0065] In this embodiment, the magnetic resonance sequence can be run simply by calling the service. Users do not need to build their own development environment or understand the code logic of the sequence running service. The workflow is simple, easy to learn, and has a low learning curve, thus improving the efficiency of running magnetic resonance sequences. Furthermore, since the development system in this embodiment provides a consistent development environment for each client 11, it avoids the situation where the magnetic resonance sequence runs normally on one client 11 but encounters errors on other clients 11, thereby improving the running efficiency of the magnetic resonance sequence.

[0066] In one embodiment, during the process of client 11 calling the sequence execution service, client 11 also displays the execution log through a front-end page. The execution log may include, but is not limited to, at least one of the following information: execution time, error messages, modification suggestions, etc., so that users can understand the sequence execution status.

[0067] In one embodiment, the development task includes a sequence translation task of a magnetic resonance imaging (MRI) sequence. The client 11 is specifically used to invoke the target service that performs the sequence translation task to translate the prototype file of the MRI sequence into a prototype file recognizable by the scanning device, package the translated prototype file into an installation package, and display the installation package through a front-end page for users to view, download, and use. The installation package includes instructions recognizable by the scanning device; installing the installation package on the scanning device enables control of the various components of the scanning device to work together.

[0068] For example, when a user requests to translate a prototype file of an MRI sequence, the sequence translation control on the user's page is triggered. Client 11 then sends a request to the server 12 to invoke the sequence translation service (target service). Server 12 sends the sequence translation service back to client 11, which then invokes the sequence translation service to translate the prototype file of the MRI sequence into a prototype file that the scanning device can recognize, and packages the translated prototype file into an installation package that the scanning device can recognize.

[0069] In this embodiment, the translation and packaging of magnetic resonance sequences can be achieved by calling the service. Users do not need to understand the code logic of the sequence running service. The workflow is simple, easy to learn, has a low learning threshold, and is easy to use, thereby improving the efficiency of users running magnetic resonance sequences.

[0070] In one embodiment, users can mark relevant information about the installation package on the user page, which may include, but is not limited to, the name of the sequence corresponding to the installation package, the time the installation package was generated, the author, the attributes of the applicable scanning device, the applicable objects, the version number, etc., so as to facilitate users to trace back and compare the developed magnetic resonance sequences.

[0071] In one embodiment, a user can provide the attributes of the scanning device (model, type, etc.) through a user page. The client 11 calls a sequence translation service to package the prototype file of the magnetic resonance sequence into an installation package that matches the attributes of the scanning device, so that the scanning device can recognize the installation package.

[0072] In one embodiment, the user page also includes a composite control that can invoke multiple services simultaneously when triggered.

[0073] For example, function control A is pre-associated with sequence execution service and sequence translation service. When function control A is triggered, client 11 sends call requests for sequence execution service and sequence translation service to server 12. Server 12 returns sequence execution service and sequence translation service to client 11. Client 11 sequentially calls sequence execution service and sequence translation service to run the prototype file of magnetic resonance sequence. If no errors occur during the run, the prototype file of magnetic resonance sequence is translated and packaged into an installation package that can be recognized by the scanning device.

[0074] It should be noted that functional controls can be combined according to actual needs. For example, in other implementations, functional control B can be associated with the code compilation service, sequence execution service, and sequence translation service. When functional control B is triggered, client 11 sends call requests for the code compilation service, sequence execution service, and sequence translation service to server 12.

[0075] In one embodiment, the front-end page includes a file import control for importing prototype files; the client 11 obtains the prototype files through the front-end page in response to the file import control being triggered.

[0076] In one embodiment, the front-end page includes a sharing control for sharing code and / or prototype files of magnetic resonance sequences; in response to the sharing control being triggered, the client 11 shares the selected code and / or prototype files to the target area via the front-end page.

[0077] The target area is open to any user, who can view and use the code and / or prototype files of the target area, thereby facilitating the co-construction and sharing of the scientific research ecosystem.

[0078] In one embodiment, the front-end page includes a function extension control for function expansion; in response to the function extension control being triggered, the client 11 sends the function service requirements (provided by the user) obtained through the function extension control to the server 12, so that the server 12 sends the function service requirements to the development end, so that the development end can develop corresponding services according to the function service requirements for the user to use.

[0079] In this embodiment, the development system can be optimized based on user feedback, the functions of the development system can be enriched, and the user experience can be further improved.

[0080] In one embodiment, a user can develop their own service and send it to server 12 via a feature extension control. Server 12 verifies the service or sends it to the development team for verification, and runs client 11 to invoke the service upon successful verification.

[0081] In one embodiment, the call request carries the login account information of the front-end page; if the login account information is successfully authenticated, the server 12 sends the target service back to the client 11.

[0082] In this embodiment, users need to register when using the development system provided for the first time. After registration, they can log in to the front-end page from any client 11 using the login account information used during registration to conduct magnetic resonance sequence development. By adding an authentication mechanism, access by unregistered / unauthorized users can be prevented, thereby protecting the system and data from malicious attacks. Adding an authentication mechanism can also implement access control, allowing the development system to restrict service calls based on the user's identity and permission level.

[0083] In one embodiment, the service for developing magnetic resonance sequences adopts a microservices architecture.

[0084] In this embodiment, the service used for magnetic resonance sequence development adopts a microservice architecture, which improves the scalability and fault tolerance of the service, while also improving the agility and maintainability of the service.

[0085] Corresponding to the aforementioned embodiments of the magnetic resonance sequence development system, this disclosure also provides embodiments of the magnetic resonance sequence development method.

[0086] Figure 2 A flowchart illustrating an exemplary embodiment of this disclosure provides a method for developing a magnetic resonance imaging (MRI) sequence. The method is applied to a client, which displays a front-end page for developing the MRI sequence. The development method includes:

[0087] Step 200: In response to the sequence development request generated through the front-end page, determine the target service that matches the development task of the sequence development request;

[0088] Step 202: Send the request to invoke the target service to the server;

[0089] Step 204: Invoke the target service returned by the server to execute the development task.

[0090] Optionally, the development task includes a code editing task for the magnetic resonance sequence; invoking the target service fed back by the server to implement the development task includes: invoking the target service that executes the code editing task to provide a text editor or integrated development environment for the code development of the magnetic resonance sequence through the front-end page;

[0091] And / or, the development task includes a code compilation task for the magnetic resonance sequence; invoking the target service fed back by the server to implement the development task, including: invoking the target service that executes the code compilation task to generate a prototype file of the magnetic resonance sequence, and displaying the prototype file through the front-end page;

[0092] And / or, the development task includes a sequence execution task of a magnetic resonance sequence; invoking the target service fed back by the server to realize the development task includes: invoking the target service that executes the sequence execution task to trigger the execution of the prototype file of the magnetic resonance sequence, and displaying the execution result through the front-end page;

[0093] And / or, the development task includes a sequence translation task of a magnetic resonance sequence; invoking the target service fed back by the server to implement the development task includes: invoking the target service that executes the sequence translation task to translate the prototype file of the magnetic resonance sequence into a prototype file that can be recognized by the scanning device, packaging the translated prototype file into an installation package, and displaying the installation package through the front-end page.

[0094] The front-end page includes a file import control for importing the prototype file; the client, in response to the file import control being triggered, obtains the prototype file through the front-end page.

[0095] And / or, the front-end page includes a sharing control for sharing the prototype file; in response to the sharing control being triggered, the client shares the selected prototype file to the target area through the front-end page;

[0096] And / or, the front-end page includes a function extension control for function expansion; in response to the function extension control being triggered, the client sends the function service requirements obtained through the function extension control to the server, so that the server can send the function service requirements to the development end; or, the client sends the user development service obtained through the function extension control to the server.

[0097] Optionally, after the step of invoking the target service to execute the code compilation task, the method further includes: displaying compilation logs through the front-end page;

[0098] And / or, after the step of calling the target service to execute the sequence running task, the method further includes: displaying the running log through the front-end page.

[0099] And / or, the front-end page is a web page;

[0100] And / or, the service used for developing the magnetic resonance sequence adopts a microservice architecture.

[0101] Figure 3 A flowchart illustrating another method for developing a magnetic resonance sequence provided as an exemplary embodiment of this disclosure. Figure 3 The server's operation process is further explained through the interaction between the server and the client. The server deploys services for the development of the magnetic resonance sequence; the development method includes:

[0102] Step 203: In response to the target service invocation request sent by the client, the target service is fed back to the client so that the client can invoke the target service; wherein, the target service is a service that matches the development task of the sequence development request generated through the front-end page.

[0103] Optionally, the call request carries the login account information of the front-end page; the return of the target service to the client includes:

[0104] Authenticate the login account information;

[0105] Upon successful authentication, the target service is returned to the client.

[0106] In response to a request to invoke a target service sent by the client, the target service is fed back to the client so that the client can invoke the target service; wherein, the target service is a service that matches the development task of the sequence development request generated through the front-end page.

[0107] For the method embodiments, since they basically correspond to the system embodiments, the relevant parts can be referred to in the description of the method embodiments.

[0108] Figure 4 This is a schematic diagram of the structure of an electronic device according to 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. When the processor executes the computer program, it implements the method for developing magnetic resonance sequences as described in any of the above embodiments. Figure 4 The electronic device 40 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0109] like Figure 4 As shown, the electronic device 40 can be manifested as a general-purpose computing device, such as a server device. The components of the electronic device 40 may include, but are not limited to: at least one processor 41, at least one memory 42, and a bus 43 connecting different system components (including memory 42 and processor 41).

[0110] Bus 43 includes a data bus, an address bus, and a control bus.

[0111] The memory 42 may include volatile memory, such as random access memory (RAM) 421 and / or cache memory 422, and may further include read-only memory (ROM) 423.

[0112] The memory 42 may also include a program tool 425 (or utility) having a set (at least one) program module 424, such program module 424 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0113] The processor 41 executes various functional applications and data processing by running computer programs stored in the memory 42, such as the magnetic resonance sequence development method provided in any of the above embodiments.

[0114] Electronic device 40 can also communicate with one or more external devices 44 (e.g., keyboard, pointing device, etc.). This communication can be performed via input / output (I / O) interface 45. Furthermore, electronic device 40 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public network, such as the Internet) via network adapter 46. As shown, network adapter 46 communicates with other modules of electronic device 40 via bus 43. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with electronic device 40, 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.

[0115] It should be noted that although several units / modules or sub-units / modules of the electronic device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this 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 and embodied by multiple units / modules.

[0116] This disclosure also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method for developing magnetic resonance sequences provided in any of the above embodiments.

[0117] The readable storage medium may be more specifically adopted, including but not limited to: portable disk, hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical storage device, magnetic storage device, or any suitable combination thereof.

[0118] This disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the method for developing magnetic resonance sequences as described above.

[0119] The program code for executing the computer program product of this disclosure can be written in any combination of one or more programming languages, and the program code can be executed entirely on a user device, partially on a user device, as a stand-alone software package, partially on a user device and partially on a remote device, or entirely on a remote device.

[0120] While specific embodiments of this disclosure have been described above, those skilled in the art should understand that these are merely illustrative examples, and the scope of protection of this disclosure is defined by the appended claims. Those skilled in the art can make various changes or modifications to these embodiments without departing from the principles and essence of this disclosure, but all such changes and modifications fall within the scope of protection of this disclosure.

Claims

1. A system for developing magnetic resonance sequences, characterized in that, include: The client and the server that communicates with the client; The client displays a front-end page for the development of the magnetic resonance sequence, and the server deploys services for the development of the magnetic resonance sequence. The client, in response to the sequence development request generated through the front-end page, determines the target service that matches the development task of the sequence development request, and sends a call request for the target service to the server; The server, in response to the call request, sends the target service back to the client; The client is also used to invoke the target service to perform the development task.

2. The magnetic resonance sequence development system according to claim 1, characterized in that, The development task includes a code editing task for magnetic resonance sequences; the client is specifically used to call the target service to execute the code editing task, so as to provide a text editor or integrated development environment for the code development of the magnetic resonance sequences through the front-end page; And / or, the development task includes a code compilation task for the magnetic resonance sequence; the client is specifically used to call the target service that executes the code compilation task to generate a prototype file of the magnetic resonance sequence, and to display the prototype file through the front-end page; And / or, the development task includes a sequence running task of magnetic resonance sequences; The client is specifically used to call the target service that executes the sequence running task to trigger the execution of the prototype file of the magnetic resonance sequence, and to display the running results through the front-end page; And / or, the development task includes sequence translation of magnetic resonance sequences; The client is specifically used to call the target service that performs the sequence translation task to translate the prototype file of the magnetic resonance sequence into a prototype file that can be recognized by the scanning device, package the translated prototype file into an installation package, and display the installation package through the front-end page.

3. The magnetic resonance sequence development system according to claim 2, characterized in that, The front-end page includes a file import control for importing the prototype file; the client, in response to the file import control being triggered, obtains the prototype file through the front-end page. And / or, the front-end page includes a sharing control for sharing the prototype file; in response to the sharing control being triggered, the client shares the selected prototype file to the target area through the front-end page; And / or, the front-end page includes a function extension control for function expansion; in response to the function extension control being triggered, the client sends the function service requirements obtained through the function extension control to the server, so that the server can send the function service requirements to the development end; or, the client sends the user development service obtained through the function extension control to the server.

4. The magnetic resonance sequence development system according to claim 2, characterized in that, When the client calls the target service to execute the code compilation task, the client is also used to display compilation logs through the front-end page; And / or, if the client calls the target service to execute the sequence running task, the client is also used to display the running log through the front-end page.

5. The development system according to any one of claims 1-4, characterized in that, The call request carries the login account information of the front-end page; if the server successfully authenticates the login account information, it sends the target service back to the client. And / or, the front-end page is a web page; And / or, the service used for developing the magnetic resonance sequence adopts a microservice architecture.

6. A method for developing a magnetic resonance sequence, characterized in that, The application is to a client, which displays a front-end page for developing the magnetic resonance sequence; the development method includes: In response to a sequence development request generated through the front-end page, a target service matching the development task of the sequence development request is determined; Send the request to invoke the target service to the server; The target service reported by the server is invoked to execute the development task.

7. The method for developing a magnetic resonance sequence according to claim 6, characterized in that, The development tasks include code editing tasks for magnetic resonance sequences; Calling the target service fed back by the server to realize the development task includes: calling the target service that executes the code editing task to provide a text editor or integrated development environment for the code development of the magnetic resonance sequence through the front-end page; And / or, the development task includes a code compilation task for the magnetic resonance sequence; invoking the target service fed back by the server to implement the development task, including: invoking the target service that executes the code compilation task to generate a prototype file of the magnetic resonance sequence, and displaying the prototype file through the front-end page; And / or, the development task includes a sequence execution task of a magnetic resonance sequence; invoking the target service fed back by the server to realize the development task includes: invoking the target service that executes the sequence execution task to trigger the execution of the prototype file of the magnetic resonance sequence, and displaying the execution result through the front-end page; And / or, the development task includes a sequence translation task of a magnetic resonance sequence; invoking the target service fed back by the server to implement the development task includes: invoking the target service that executes the sequence translation task to translate the prototype file of the magnetic resonance sequence into a prototype file that can be recognized by the scanning device, packaging the translated prototype file into an installation package, and displaying the installation package through the front-end page.

8. A method for developing a magnetic resonance sequence, characterized in that, The application is to a server, which is deployed with services for the development of the magnetic resonance sequence; The development method includes: In response to a request to invoke a target service sent by a client, the target service is fed back to the client so that the client can invoke the target service; wherein, the target service is a service that matches the development task of the sequence development request generated through the front-end page.

9. The method for developing a magnetic resonance sequence according to claim 8, characterized in that, The call request carries the login account information of the front-end page; Feedback of the target service to the client includes: Authenticate the login account information; Upon successful authentication, the target service is returned to the client.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method for developing magnetic resonance sequences according to any one of claims 6 to 9.

Images