Magnetic resonance imaging method, device and system

Abstract

The embodiment of the invention provides a magnetic resonance imaging method, device and system. The device includes at least one storage medium including a set of instructions; and one or more processors in communication with the at least one storage medium. Wherein, when the instruction is executed, the one or more processors are configured to: read an intermediate translation file associated with a sequence, the intermediate translation file being obtained in a first development environment; converting the intermediate translation file into a component which can be identified by a second development environment, and generating a hardware instruction which can be executed by a hardware module; checking whether the hardware instruction can be executed in the magnetic resonance system or not and whether the corresponding sequence file is consistent with the requirement of the first development environment or not in the second development environment; and if yes, issuing the hardware instruction to each hardware module, so that the hardware module executes based on the hardware instruction to obtain a magnetic resonance signal matched with the sequence.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a magnetic resonance imaging method, device and system. Background Art

[0002] Nuclear magnetic resonance technology has been widely used in many fields with the help of rich and colorful experimental methods. In magnetic resonance systems, the main difference between various experimental methods lies in the sequence timing diagrams used. Generally, the development environment of magnetic resonance systems is based on the code framework, hardware modules and implementation logic of each manufacturer and cannot be shared. For users, magnetic resonance systems from different manufacturers correspond to completely different development environments, and all have the problem of too high thresholds for development languages ​​and development models, which greatly limits users' expansion and exploration of magnetic resonance applications, and also limits the promotion of magnetic resonance applications.

[0003] Therefore, it is hoped to provide a magnetic resonance imaging system to reduce the difficulty of magnetic resonance application development and improve the efficiency of magnetic resonance application development. Summary of the invention

[0004] In one aspect, the present specification provides a magnetic resonance imaging device, comprising: at least one storage medium, including a set of instructions; and one or more processing devices communicating with the at least one storage medium. Wherein, when executing the instructions, the one or more processors are used to: read an intermediate translation file related to a sequence, the intermediate translation file being obtained in a first development environment; convert the intermediate translation file into a component recognizable by a second development environment, and generate hardware instructions executable by a hardware module; check in the second development environment whether the hardware instructions can be executed in a magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; if so, send the hardware instructions to each hardware module, so that the hardware module executes based on the hardware instructions to obtain a magnetic resonance signal matching the sequence.

[0005] In some embodiments, the second development environment is a development environment of the magnetic resonance system, and the second development environment is different from the first development environment.

[0006] In some embodiments, the intermediate translation file includes gradient information, radio frequency information, and ADC information of the sequence.

[0007] In some embodiments, the format of the intermediate conversion file is configured to be readable and recognizable in the second development environment.

[0008] In some embodiments, the intermediate translation file includes a sequence file obtained in the first development environment, or the intermediate translation file is converted based on a sequence file obtained in the first development environment.

[0009] In some embodiments, in order to convert the intermediate translation file into a component recognizable by the second development environment and generate hardware instructions executable by the hardware module, the one or more processing devices are used to: convert the intermediate translation file into a component recognizable by the second development environment and generate an executable module, the executable module including at least one of a data acquisition module, a gradient module and a radio frequency module; and generate hardware instructions executable by the hardware module based on the executable module.

[0010] In some embodiments, if so, sending the hardware instruction to each hardware module includes: in response to the hardware instruction being able to run normally and output a sequence timing diagram matching the sequence, sending the hardware instruction to each hardware module.

[0011] In some embodiments, checking whether the corresponding sequence file is consistent with the requirements of the first development environment includes: under the second development environment, compiling based on the executable module and outputting a sequence timing diagram; obtaining user feedback information on the sequence timing diagram, and determining whether the sequence timing diagram is correct based on the feedback information, so as to determine whether the corresponding sequence file is consistent with the requirements of the first development environment.

[0012] In some embodiments, the one or more processors are further configured to: obtain update information of the sequence in the first development environment; and update the hardware instructions in real time in the second development environment based on the update information.

[0013] In one aspect, the present specification provides a magnetic resonance imaging method, comprising: reading an intermediate translation file related to a sequence, the intermediate translation file being obtained in a first development environment; converting the intermediate translation file into a component recognizable by a second development environment, and generating hardware instructions executable by a hardware module; checking in the second development environment whether the hardware instructions can be executed in a magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; if so, issuing the hardware instructions to each hardware module, so that the hardware module executes based on the hardware instructions to obtain a magnetic resonance signal matching the sequence.

[0014] In one aspect, the present specification provides a magnetic resonance imaging method, comprising: generating a sequence file related to a sequence in a first development environment; determining an intermediate translation file based on the sequence file in the first development environment; and sending the intermediate translation file to a second development environment where a magnetic resonance imaging device is located, so that the magnetic resonance imaging device performs a magnetic resonance scan matching the sequence design based on the intermediate translation file in the second development environment.

[0015] Another aspect of the present specification provides a magnetic resonance imaging system, comprising: a reading module, used to read an intermediate translation file related to a sequence, the intermediate translation file being obtained in a first development environment; a conversion module, used to convert the intermediate translation file into a component recognizable by a second development environment, and generate software instructions executable by a hardware module; a checking module, used to check in the second development environment whether the hardware instructions can be executed in a magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; and a sending module, used to send the hardware instructions to each hardware module, so that the hardware module executes based on the hardware instructions to obtain a magnetic resonance signal matching the sequence. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] This specification will be further described in the form of exemplary embodiments, which will be described in detail by the accompanying drawings. These embodiments are not restrictive, and in these embodiments, the same number represents the same structure, wherein:

[0017] Figure 1 is a schematic diagram of an application scenario of an exemplary magnetic resonance imaging device according to some embodiments of this specification;

[0018] Figure 2 is a schematic diagram of a module of an exemplary magnetic resonance imaging system according to some embodiments of the present specification;

[0019] Figure 3 is a flowchart of an exemplary magnetic resonance imaging method according to some embodiments of the present specification;

[0020] Figure 4 is a schematic diagram of an exemplary user-defined sequence timing diagram according to some embodiments of the present specification;

[0021] Figure 5 is a schematic diagram of an exemplary system output sequence timing diagram according to some embodiments of the present specification;

[0022] Figure 6 is a schematic diagram of an exemplary magnetic resonance system driving according to some embodiments of the present specification;

[0023] Figure 7 It is a flowchart of an exemplary magnetic resonance imaging method shown in other embodiments of the present specification. DETAILED DESCRIPTION

[0024] In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of this specification. For ordinary technicians in this field, this specification can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0025] It should be understood that the "system", "device", "unit" and / or "module" used herein are a method for distinguishing different components, elements, parts, portions or assemblies at different levels. However, if other words can achieve the same purpose, the words can be replaced by other expressions.

[0026] As shown in this specification and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "comprise" and "include" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0027] Flowcharts are used in this specification to illustrate the operations performed by the system according to the embodiments of this specification, and the relevant description is to help better understand the control method and / or system. It should be understood that the previous or subsequent operations are not necessarily performed accurately in order. On the contrary, the steps can be processed in reverse order or simultaneously. At the same time, other operations can also be added to these processes, or one or more operations can be removed from these processes.

[0028] A medical imaging system (e.g., an MRI system) may include a user interface that allows an operator to obtain a preset image, a data acquisition device that uses a certain imaging mode to acquire data from a target object, an image reconstruction processor that reconstructs an image using the acquired data, and a storage device for storing the image and related patient information. Generally, the hardware modules of the medical imaging system are designed to implement the above functions, and the system software (e.g., the execution instructions corresponding to the sequence timing diagram) is designed and written for each hardware module.

[0029] The existing magnetic resonance system development systems are generally based on the code framework, hardware modules and implementation logic of each manufacturer and cannot be shared. For users, magnetic resonance systems from different manufacturers correspond to completely different development environments, and all have the problem of too high thresholds for development languages ​​and development models. When users need to design their own sequences, they need to first learn the code framework, implementation logic and other knowledge corresponding to a manufacturer's magnetic resonance system development environment, or seek support from the manufacturer's engineers, which greatly limits users' expansion and exploration of magnetic resonance applications.

[0030] In the embodiments of the present specification, a magnetic resonance imaging method, device and system are provided, in which the intermediate translation file related to the sequence obtained in the first development environment is read in the magnetic resonance system development environment (second development environment), the intermediate translation file is converted into a component recognizable by the second development environment, and software instructions executable by the hardware module are generated. In this way, it is only necessary to agree with the magnetic resonance system on the format of the intermediate translation file, and the application developed by the user in any environment, even if it is different from the existing development language and development mode of the current magnetic resonance system, the magnetic resonance development system can convert the application provided by the user into the logic supported by the magnetic resonance system without the need for the development language of the magnetic resonance system, thereby opening up the driving mode of the magnetic resonance system and improving the development efficiency of the magnetic resonance application.

[0031] Figure 1 It is a schematic diagram of an application scenario of an exemplary magnetic resonance imaging method according to some embodiments of the present specification.

[0032] like Figure 1 As shown, in some embodiments, the magnetic resonance system 100 may include an imaging device 110, a processing device 120, a terminal device 130, a storage device 140, and a network 150. The connections between the components in the magnetic resonance system 100 may be variable. Figure 1 As shown, in some embodiments, the imaging device 110 may be connected to the processing device 120 via the network 150. For another example, the imaging device 110 may be directly connected to the processing device 120, as indicated by the dashed double-headed arrow connecting the imaging device 110 and the processing device 120. For another example, the storage device 140 may be connected to the processing device 120 directly or via the network 150. As an example, the terminal device 130 may be directly connected to the processing device 120 (as indicated by the dashed arrow connecting the terminal device 130 and the processing device 120), or may be connected to the processing device 120 via the network 150.

[0033] The imaging device 110 can be used to scan a target object or a portion thereof located within its detection area and generate an image related to the target object or a portion thereof. In some embodiments, the target object can be biological or non-biological. For example, the target object can include a patient, an animal, a man-made object, etc. In some embodiments, the target object can include a specific part of the body, such as the head, chest, abdomen, etc., or any combination thereof. In some embodiments, the target object can include a specific organ, such as the heart, esophagus, trachea, bronchus, stomach, gallbladder, small intestine, colon, bladder, ureter, uterus, fallopian tube, etc., or any combination thereof. In some embodiments, the target object can include a region of interest (ROI), such as a tumor, a nodule, etc.

[0034] In some embodiments, the imaging device 110 may include one or a combination of X-ray equipment, a computed tomography (CT) device, a three-dimensional (3D) CT, a four-dimensional (4D) CT, an ultrasound imaging component, a fluoroscopic imaging component, a magnetic resonance imaging (MRI) device, a single photon emission computed tomography (SPECT) device, a positron emission tomography (PET) device, etc.

[0035] In some embodiments, imaging device 110 can be an MRI device. MRI devices use strong magnetic fields, gradient magnetic fields and radio waves to generate magnetic resonance images of target objects to be scanned. In some embodiments, MRI devices can include a magnet assembly, a gradient coil assembly and a radio frequency (RF) coil assembly. The magnet assembly can generate a first magnetic field (also referred to as a main magnetic field) for polarizing the target object. The gradient coil assembly can be used to generate a second magnetic field (also referred to as a gradient magnetic field).

[0036] In some embodiments, the gradient coil assembly may generate one or more magnetic field gradient pulses for the main magnetic field in the X direction (Gx), Y direction (Gy), and Z direction (Gz) to encode the spatial information of the target object. In some embodiments, the X direction may be designated as a frequency encoding direction, and the Y direction may be designated as a phase encoding direction. In some embodiments, Gx may be used for frequency encoding or signal readout, which is generally referred to as a frequency encoding gradient or a readout (RO) gradient. In some embodiments, Gy may be used for phase encoding, which is generally referred to as a phase encoding (PE, Phase-Encoding) gradient. In some embodiments, Gz may be used for slice selection to obtain two-dimensional k-space data, which is generally referred to as a slice selection (SS) gradient. In some embodiments, Gz may be used for phase encoding to obtain three-dimensional k-space data.

[0037] In some embodiments, the RF coil may include one or more transmitting coils and / or one or more receiving coils. The RF transmitting coil may transmit RF pulses to the target object. Under the synergistic effect of the main magnetic field / gradient magnetic field and the RF pulse, a magnetic resonance signal related to the target object may be generated according to a pulse sequence. The RF receiving coil may acquire a magnetic resonance signal from the object according to the pulse sequence. The magnetic resonance signal may also be referred to as an echo signal. A transform operation (e.g., Fourier transform) may be used to process the magnetic resonance signal to fill the k-space to acquire k-space data, thereby generating a magnetic resonance image of the target object.

[0038] In some embodiments, the MRI device may include an analog-to-digital converter (ADC). The analog-to-digital converter may convert magnetic resonance signals received by one or more RF receiving coils into magnetic resonance imaging data. The analog-to-digital converter may be a direct conversion ADC, a successive approximation ADC, a ramp comparison ADC, a Wilkinson ADC, an integral ADC, an incremental coding ADC, a pipeline ADC, a sigma-delta ADC, etc., or any combination thereof.

[0039] The processing device 120 may process data and / or information obtained from the imaging device 110, the terminal device 130, the storage device 140, or other components of the magnetic resonance system 100. For example, the processing device 120 may read an intermediate translation file related to the sequence through the terminal device 130 or the storage device 140, convert the intermediate translation file into a component recognizable by the second development environment, and generate software instructions executable by the hardware module; check whether the hardware instruction is executable in the magnetic resonance system in the second development environment, and whether the corresponding sequence file is consistent with the requirements of the first development environment; if so, send the hardware instruction to each hardware module of the imaging device 110, so that the hardware module executes based on the hardware instruction to obtain a magnetic resonance signal matching the sequence.

[0040] In some embodiments, the processing device 120 and the imaging device 110 may be integrated into one. For example, the processing device 120 may be integrated into the imaging device 110, and the processing device 120 and the imaging device 110 may work together to implement the methods and / or functions described in this specification.

[0041] In some embodiments, the processing device 120 may include an input device and / or an output device. Interaction with a user (e.g., displaying a reconstructed image, etc.) may be achieved through the input device and / or the output device. In some embodiments, the input device and / or the output device may include a display screen, a keyboard, a mouse, a microphone, etc., or any combination thereof.

[0042] The terminal device 130 may be connected and / or communicate with the imaging device 110, the processing device 120, and / or the storage device 140. For example, the terminal device 130 may obtain and display an output sequence timing diagram from the processing device 120. In some embodiments, the terminal device 130 may include a mobile device 131, a tablet computer 132, a laptop computer 133, etc., or any combination thereof. In some embodiments, the terminal device 130 (or all or part of its functions) may be integrated into the processing device 120.

[0043] The storage device 140 may store data, instructions and / or any other information. In some embodiments, the storage device 140 may store data (e.g., intermediate translation files, software instructions, etc.) acquired from the imaging device 110, the processing device 120, or the terminal device 130. In some embodiments, the storage device 140 may store computer instructions for implementing a magnetic resonance system driving method, etc.

[0044] In some embodiments, the storage device 140 may include one or more storage components, each of which may be an independent device or part of another device. In some embodiments, the storage device 140 may include a random access memory (RAM), a read-only memory (ROM), a mass storage, a removable memory, a volatile read-write memory, or the like, or any combination thereof. Exemplarily, the mass storage may include a magnetic disk, an optical disk, a solid-state disk, or the like. RAM may include dynamic RAM (DRAM), double rate synchronous dynamic RAM (DDR SDRAM), static RAM (SRAM), thyristor RAM (T-RAM), and zero capacitance (Z-RAM), or the like. ROM may include mask ROM (MROM), programmable ROM (PROM), erasable programmable ROM (PEROM), electrically erasable programmable ROM (EEPROM), optical disk ROM (CD-ROM), and digital versatile disk ROM, or the like. In some embodiments, the storage device 140 may be implemented on a cloud platform.

[0045] The network 150 may include any suitable network capable of facilitating information and / or data exchange. In some embodiments, at least one component of the magnetic resonance system 100 (e.g., the imaging device 110, the processing device 120, the terminal device 130, the storage device 140) may exchange information and / or data with at least one other component in the magnetic resonance system 100 via the network 150.

[0046] It should be noted that the magnetic resonance system 100 is provided for illustrative purposes only and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various modifications or variations can be made based on the description of this specification. For example, the magnetic resonance system 100 can implement similar or different functions on other devices. However, these variations and modifications will not deviate from the scope of this specification.

[0047] Figure 2 is a schematic block diagram of an exemplary magnetic resonance imaging system according to some embodiments of the present specification.

[0048] like Figure 2 As shown, in some embodiments, the magnetic resonance imaging system 200 may include a reading module 210 , a conversion module 220 , a checking module 230 and a sending module 240 .

[0049] The reading module 210 can be used to read an intermediate translation file related to the sequence, wherein the intermediate translation file is obtained in the first development environment. For example, the reading module 210 can read the intermediate translation file stored in a mobile disk.

[0050] The conversion module 220 can be used to convert the intermediate translation file into a component recognizable by the second development environment and generate hardware instructions executable by the hardware module. In some embodiments, the conversion module 220 can convert the intermediate translation file into a component recognizable by the second development environment and generate an executable module; based on the executable module, generate hardware instructions executable by the hardware module.

[0051] The checking module 230 may be used to check in the second development environment whether the hardware instructions are executable in the magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment.

[0052] The sending module 240 can be used to send the hardware instructions to each hardware module so that the hardware module executes based on the hardware instructions to obtain a magnetic resonance signal matching the sequence. In some embodiments, the sending module 240 can respond to the instruction to run normally and output a sequence timing diagram matching the sequence, and send the hardware instructions to each hardware module.

[0053] For more information about the reading module 210, the conversion module 220, the checking module 230, and the sending module 240, see Figure 3 , I will not go into details here.

[0054] It should be noted that the above description of the magnetic resonance imaging system 200 and its modules is provided for illustrative purposes only and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various changes and modifications can be made according to the description of this specification. However, these changes and modifications do not depart from the scope of this specification.

[0055] Figure 3 is a flowchart of an exemplary magnetic resonance imaging method according to some embodiments of the present specification.

[0056] In some embodiments, the process 300 may be performed by the processing device 120 or the magnetic resonance imaging system 200. The operational diagram of the process 300 presented below is illustrative. In some embodiments, the process may be completed using one or more additional operations not described and / or one or more operations not discussed. In addition, Figure 3 The order in which the operations of flow 300 are illustrated and described below is not intended to be limiting.

[0057] Step 310 , reading an intermediate translation file related to the sequence, wherein the intermediate translation file is obtained in a first development environment. In some embodiments, step 310 may be performed by the processing device 120 or the reading module 210 .

[0058] The sequence file may reflect the relevant parameters of the sequence used to acquire data during the magnetic resonance imaging process. Exemplary sequences may include a spin echo sequence, a gradient echo sequence, a planar echo sequence, etc., or other sequences corresponding to specific applications. For example, a spin echo sequence may include a spin echo sequence, a fast spin echo (FSE), etc.

[0059] In some embodiments, the sequence file may include module information necessary for the sequence, such as gradient, RF, and ADC. For example, the gradient may include a readout gradient (RO gradient, also called a frequency encoding gradient), a phase encoding gradient (PE gradient), or a slice selection gradient (SS gradient). In some embodiments, the sequence may be determined in real time by the user based on actual conditions. For example, the user may customize the RF pulse (RF), gradient sequence, and other information and their parameters used in performing magnetic resonance scanning on the target object based on the target object's basic information, historical case information, and other information. Please refer to Figure 4 The figure shows the user-defined sequence timing diagram, including radio frequency pulse (corresponding to RF pulse in the figure), slice selection gradient (corresponding to G SS ), phase encoding gradient (corresponding to G in the figure PE ), read out the gradient (corresponding to G in the figure RO ) and data acquisition module ADC (corresponding to ADC in the figure).

[0060] The intermediate translation file may be obtained in a first development environment, such as MATLAB. The development environment may include a software development environment and an integrated development environment.

[0061] Software development environment refers to a set of software used to support the engineering development and maintenance of system software and application software. The basis for software implementation is computer language, such as algorithm language, database language, intelligent simulation language, etc. Different development environments may correspond to different development languages.

[0062] An integrated development environment is an application that provides a program development environment, generally including a code editor, compiler, debugger, and graphical user interface tools. It is an integrated development software service suite that integrates code writing, analysis, compilation, debugging, and other functions. All software or software suites (groups) with this feature can be called an integrated development environment, such as Visual Studio, C++Builder, Delphi, etc.

[0063] In some embodiments, the intermediate translation file may include gradient information, radio frequency information, ADC information, etc. of the sequence.

[0064] The gradient information may reflect the parameter information of the gradient. In some embodiments, the gradient information may include the gradient name, the coordinate axis of the gradient action (e.g., SS axis, PE axis, RO axis), the gradient amplitude, the gradient start time, the gradient climbing time, the gradient plateau time, the gradient descent time, the gradient size, etc. For example, gradient 1, name: layer selection gradient; start time: 0ms; climbing time: 0.2ms; plateau time: 3ms; descent time: 0.2ms; gradient size: 20mT / m.

[0065] The radio frequency information may reflect parameter information of the radio frequency pulse. In some embodiments, the radio frequency information may include at least one of the radio frequency name, radio frequency angle, radio frequency waveform, radio frequency start time, radio frequency duration, radio frequency center frequency, etc. For example, radio frequency pulse, name: refocusing pulse; angle: 150°; waveform: 4 tbw sinc pulse; start time: 0.2 ms; duration: 3 ms.

[0066] The ADC information may reflect the sampling parameters of the data acquisition module corresponding to the sequence. In some embodiments, the ADC information may include at least one of the sampling start time, sampling time interval, sampling point number, etc. For example, ADC1, name: ADC; start time: 3.8 ms; sampling time interval: 1000 ns; sampling point number: determined by the user according to the imaging size and voxel size.

[0067] In some embodiments, the file format of the intermediate translation file can be in any form (e.g., XML format, etc.), and this specification does not limit this. In some embodiments, the format of the intermediate translation file is configured to be able to be read in the second development environment to identify the parameters corresponding to the sequence (e.g., the coordinate axis of the gradient effect, the amplitude of the gradient, the size of the gradient, the radio frequency duration, the radio frequency angle, the sampling start time, the sampling time interval, etc.).

[0068] As an example, taking the intermediate translation file in text form as an example, the translation file can include template nodes such as Circle and Block. Circle is used to control the number of loops, and Block is used as a functional block. Block contains basic module information such as RF pulse, gradient, ADC, etc. in the functional module. The information of each basic module of RF pulse, gradient, and ADC can be filled in according to the template. Taking the gradient module as an example, the user's information about the module in the intermediate translation file can be expressed as "<Grad Trap> SS_RefSliceSelection:20_0_0.2_3_0.2< / Grad Trap> ", where Grad Trap indicates that this is a gradient module, SS indicates that the gradient acts on the SS axis, RefSliceSelection is the gradient name, 20_0_0.2_3_0.2 indicates that the amplitude of this gradient is 20mT / m, the start time is 0ms, the climb time is 0.2ms, the platform time is 3ms, and the descending time is 0.2ms.

[0069] In some embodiments, the second development environment is a magnetic resonance system development environment, and the second development environment is different from the first development environment. For example, the first development environment can be a MATLAB or python development environment that is familiar to the user. The first development environment and the second development environment are different from the development language. The first development environment and the second development environment can use the same or different development languages. For example, both the first development environment and the second development environment use C++ language, but correspond to different development environments.

[0070] In some embodiments, the user can obtain the sequence file in the first development environment. For example, the user can edit and form the sequence file in any development environment different from the magnetic resonance system development environment through any development language and / or application program. In some embodiments, the sequence file can be in any form, such as image form, text form, and this specification does not limit this.

[0071] In some embodiments, the intermediate translation file includes a sequence file obtained in the first development environment. In this case, the sequence file satisfies the preset format. For example, if the first development environment is MATLAB, the user can use MATLAB to generate a sequence file containing five arrays, corresponding to the RF pulse, SS axis gradient, PE axis gradient, RO axis gradient, and ADC acquisition module, respectively, wherein each point in the RF pulse array represents the amplitude of the RF pulse, each point in the SS axis gradient array represents the amplitude of the layer selection gradient, each point in the PE axis gradient array represents the amplitude of the phase encoding gradient, each point in the RO axis gradient array represents the amplitude of the readout gradient, and each point in the ADC array represents the sampling time of the ADC, based on which the module parameters in the sequence file can be directly read in the second development environment.

[0072] In some embodiments, the intermediate translation file can be converted based on the sequence file obtained in the first development environment, for example, automatically generated by a script, or manually edited by a user. Exemplarily, the user can translate the sequence file obtained in the first development environment (for example, MATLAB) into the intermediate translation file required by the second development environment by writing a script, so that the second development environment can translate it into executable software instructions. For example, the sequence file obtained in the first development environment already contains the type of each module (for example, gradient, radio frequency, ADC, etc.), parameters (for example, radio frequency duration, gradient size, coordinate axis of gradient action, etc.), after converting it into an intermediate translation file, the magnetic resonance development environment can translate the intermediate translation file into each component that can be recognized by the system, thereby generating hardware instructions. For another example, the user can directly fill in the information such as the parameters of the designed sequence into the intermediate translation file template of the predetermined format to form an intermediate translation file.

[0073] In some embodiments, the reading module 210 can read the intermediate translation file through any one of a cloud disk, a network disk, a local disk, a removable disk, a TCP / IP protocol, etc. For example, after the user edits the intermediate translation file corresponding to the sequence, the file can be copied to a removable disk, the removable disk is connected to the magnetic resonance system, and the magnetic resonance system reads the intermediate translation file in the removable disk. In some embodiments, the storage location of the intermediate translation file can be preset. For example, the user can set in advance to put the intermediate translation file on a network cloud disk, and the magnetic resonance system can read the intermediate translation file from the network cloud disk.

[0074] Step 320 , converting the intermediate translation file into a component recognizable by the second development environment, and generating hardware instructions executable by the hardware module. In some embodiments, step 320 may be performed by the processing device 120 or the conversion module 220 .

[0075] In some embodiments, the conversion module 220 can convert the intermediate translation file into a component recognizable by the second development environment and generate an executable module. The executable module refers to a module that can be run by the second development environment, and may include a gradient module, a radio frequency module and / or a data acquisition module (ADC module), etc.

[0076] In some embodiments, the conversion module 220 can read and parse the content contained in each template node of the intermediate translation file to convert it into a component recognizable by the second development environment and generate an executable module. For example, in combination with the above, the development environment of the magnetic resonance system reads the intermediate translation file from the specified path, and when the Circle node is read, the content in the Circle node is parsed through the Assemble Circle function developed by the second development environment, and then the Block node is read and the content in the Block is parsed through the Assemble Task Block function developed by the second development environment, and finally the content of each basic module node (such as gradient, radio frequency pulse, ADC, etc.) in the Block is read and parsed, and then the parsed information is set to the basic modules such as gradient, radio frequency pulse, ADC, etc. corresponding to the second development environment of the magnetic resonance system.

[0077] In some embodiments, the conversion module 220 can generate hardware instructions executable by the hardware module based on the executable module in the second development environment. The hardware module can refer to the hardware module of the magnetic resonance system, and the hardware instruction can refer to the program instruction of the development language corresponding to the magnetic resonance system development environment. For example, the magnetic resonance system development environment can compile based on the content set in the basic module to generate hardware instructions executable by the hardware module corresponding to the magnetic resonance system development environment.

[0078] Step 330 is to check in the second development environment whether the hardware instructions are executable in the magnetic resonance system and whether the corresponding sequence files are consistent with the requirements of the first development environment. In some embodiments, step 330 may be performed by the processing device 120 or the checking module 230 .

[0079] In some embodiments, the checking module 230 can compile based on the executable module to confirm whether the compiling module can run on the magnetic resonance hardware system. If not, the sequence design is modified in the first development environment; if it is, the sequence timing diagram corresponding to the current sequence is output. For example, when the compiling module cannot run on the magnetic resonance hardware system, the user can adjust the sequence design (such as the sequence timing diagram) in the first development environment so that the corresponding compiling module can run on the magnetic resonance hardware system.

[0080] In some embodiments, the checking module 230 can compile and output a sequence timing diagram based on the executable module under the second development environment; obtain user feedback information on the output sequence timing diagram, and determine whether the output sequence timing diagram is correct based on the feedback information to determine whether the corresponding sequence file is consistent with the requirements of the first development environment. For example, the checking module 230 can send the output sequence timing diagram to the user's terminal device 130 after confirming that the compiling module can run in the magnetic resonance hardware system, and the user's terminal device 130 displays the sequence timing diagram to the user (such as Figure 5 The user can input "correct" or "wrong" feedback information in the user interface of the terminal device 130, and whether the sequence timing diagram is correct can be determined based on the feedback information. If the user feedback is "correct", it is determined that the corresponding sequence file is consistent with the requirements of the first development environment, otherwise, it is considered inconsistent.

[0081] In some embodiments, the system can determine whether the output sequence timing diagram is correct by comparing the user-defined sequence timing diagram with the output timing diagram. In some embodiments, the inspection module 230 can determine whether the output sequence timing diagram is correct by any feasible method, such as determining whether the output timing diagram is correct based on sequence parameters, or comparing the image information of the output timing diagram and the sequence timing diagram, which is not limited in this specification.

[0082] In some embodiments, the system can obtain update information of the sequence timing diagram in the first development environment. For example, the user can update the gradient information, radio frequency information, and ADC information of the sequence through the display interface of the terminal device 130 or the imaging device 110. In some embodiments, the processing device can update the hardware instructions in real time in the second development environment based on the update information. For example, the processing device 120 can translate and update the corresponding hardware instructions in real time in the second development environment based on the user's update information of the sequence in the first development environment, so that the hardware module performs magnetic resonance scanning based on the updated hardware instructions.

[0083] Step 340 , if yes, the hardware instruction is sent to each hardware module, so that the hardware module executes based on the hardware instruction to obtain a magnetic resonance signal matching the sequence. In some embodiments, step 340 may be performed by the processing device 120 or the sending module 240 .

[0084] In some embodiments, the sending module 240 can send the hardware instructions corresponding to the generated second development environment to each hardware module, so that the hardware module executes based on the hardware instructions to obtain a magnetic resonance signal matching the sequence. In some embodiments, the sending module 240 can respond to the hardware instructions being able to run normally and output a sequence timing diagram matching the sequence, and send the hardware instructions to each hardware module. For example, the magnetic resonance system development environment can be compiled based on the executable module. If the compiled file can run normally in the magnetic resonance system development environment and the output sequence timing diagram is correct (i.e., matching the user-defined sequence timing diagram), the relevant compiled file and the intermediate translation file are loaded into the magnetic resonance system to perform a magnetic resonance scan matching the sequence.

[0085] It should be noted that the above description of process 300 is provided for illustrative purposes only and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various changes and modifications can be made according to the description of this specification. However, these changes and modifications do not depart from the scope of this specification.

[0086] Figure 6 FIG. 1 is a schematic diagram of an exemplary magnetic resonance system driving according to some embodiments of the present specification. Figure 6 As shown in, in some embodiments, the user designs a sequence in the first development environment 610, and then forms an intermediate translation file 620 related to the sequence module and timing design according to a preset format agreed upon with the magnetic resonance system development environment (for example, the user manually fills in and generates based on a template file, or automatically converts and generates based on the sequence file through a script). In some embodiments, the user can copy the intermediate translation file 620 to a mobile disk, or import the intermediate translation file 620 into the second development environment 630 (magnetic resonance system development environment) through a network. The second development environment 630 can read the intermediate translation file 620 and convert it into an executable module, such as a gradient module, a radio frequency module, an ADC module, etc. Further, the second development environment 630 can compile and output a sequence timing diagram. When it is determined that the intermediate translation file 620 of the sequence can run normally in the second development environment and the output sequence timing diagram is correct, the corresponding software instructions are sent to each hardware module of the magnetic resonance system 640 to perform a scan matching the sequence.

[0087] Figure 7 700 is a flowchart of an exemplary magnetic resonance imaging method according to other embodiments of the present specification. In some embodiments, process 700 can be performed by terminal device 130. The operation diagram of process 700 presented below is illustrative. In some embodiments, the process can be completed using one or more additional operations not described and / or one or more operations not discussed. In addition, Figure 7The order in which the operations of flow 700 are illustrated and described below is not intended to be limiting.

[0088] Step 710: Generate a sequence file related to the sequence in the first development environment.

[0089] In combination with the above, the user can generate a sequence file related to the sequence module and the timing in the first development environment. For example, the user can edit and form a sequence file in any development environment different from the magnetic resonance system development environment through any development language and / or application program. In some embodiments, the sequence file can be in any form, such as image form, text form, and this specification does not limit this.

[0090] Step 720: Under the first development environment, determine an intermediate translation file based on the sequence file. The sequence file may also be directly used as the intermediate translation file.

[0091] As described above, in some embodiments, the intermediate translation file can be automatically generated by a script or manually edited by a user based on the sequence file. Figure 3 Described in.

[0092] Step 730: Send the intermediate translation file to the second development environment where the magnetic resonance imaging device is located.

[0093] In some embodiments, the intermediate translation file can be sent to the second development environment where the magnetic resonance imaging device is located by means of data transmission. For example, the terminal device 130 can send the intermediate translation file to the magnetic resonance imaging device 110 through the network 150. For another example, after the user has edited the intermediate translation file corresponding to the sequence timing diagram, the user can copy the file to a mobile disk, connect the mobile disk to the magnetic resonance system, and the magnetic resonance system reads the intermediate translation file in the mobile disk. In some embodiments, the magnetic resonance system can convert the intermediate translation file into a component recognizable by the second development environment, and generate software instructions executable by the hardware module; the software instructions are sent to each hardware module, so that the hardware module performs a magnetic resonance scan that matches the sequence based on the software instructions. For more details, see Figure 3 Described in.

[0094] It should be noted that the above description of process 700 is provided for illustrative purposes only and is not intended to limit the scope of this specification. For those of ordinary skill in the art, various changes and modifications can be made according to the description of this specification. However, these changes and modifications do not depart from the scope of this specification.

[0095] In some embodiments of the present specification, a computer device is also provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the aforementioned method (e.g., processes 300, 700) when executing the computer program.

[0096] Another aspect of the present specification provides a computer-readable storage medium, wherein the storage medium stores computer instructions. When a computer reads the computer instructions in the storage medium, the computer executes the method described above (eg, processes 300 and 700).

[0097] The beneficial effects that may be brought about by the embodiments of this specification include but are not limited to: (1) Through the intermediate translation file of the agreed format, the hardware module of the magnetic resonance system does not need to rely on a fixed development framework, and the magnetic resonance sequences implemented in different development environments and using different development languages ​​can all support the scanning operation of the magnetic resonance system, effectively improving the development efficiency of magnetic resonance applications; (2) The sequences developed by the user in any environment, even if they are different from the existing development language and development mode of the current magnetic resonance system, can be converted into the logic supported by the system without being based on the development language of this magnetic resonance system, thereby opening up the driving method of the system; (3) The method of developing the sequence of the magnetic resonance system by means of the agreed intermediate translation file fully reduces the user's dependence on the magnetic resonance system development environment and reduces the learning cost. At the same time, it can realize the sharing of magnetic resonance sequences in different development environments and improve the utilization efficiency of magnetic resonance technology.

[0098] The basic concepts have been described above. Obviously, for those skilled in the art, the above detailed disclosure is only for example and does not constitute a limitation of this specification. Although not explicitly stated here, those skilled in the art may make various modifications, improvements and corrections to this specification. Such modifications, improvements and corrections are suggested in this specification, so such modifications, improvements and corrections still belong to the spirit and scope of the exemplary embodiments of this specification.

[0099] At the same time, this specification uses specific words to describe the embodiments of this specification. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, certain features, structures or characteristics in one or more embodiments of this specification can be appropriately combined.

[0100] In addition, unless explicitly stated in the claims, the order of the processing elements and sequences described in this specification, the use of alphanumeric characters, or the use of other names are not intended to limit the order of the processes and methods of this specification. Although the above disclosure discusses some invention embodiments that are currently considered useful through various examples, it should be understood that such details are only for illustrative purposes, and the attached claims are not limited to the disclosed embodiments. On the contrary, the claims are intended to cover all modifications and equivalent combinations that are consistent with the essence and scope of the embodiments of this specification. For example, although the system components described above can be implemented by hardware devices, they can also be implemented only by software solutions, such as installing the described system on an existing server or mobile device.

[0101] Similarly, it should be noted that in order to simplify the description disclosed in this specification and thus help understand one or more embodiments of the invention, in the above description of the embodiments of this specification, multiple features are sometimes combined into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the subject matter of this specification are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0102] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of this specification are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0103] Each patent, patent application, patent application publication, and other materials, such as articles, books, specifications, publications, documents, etc., cited in this specification are hereby incorporated by reference in their entirety. Except for application history documents that are inconsistent with or conflicting with the contents of this specification, documents that limit the broadest scope of the claims of this specification (currently or later attached to this specification) are also excluded. It should be noted that if the descriptions, definitions, and / or use of terms in the materials attached to this specification are inconsistent or conflicting with the contents described in this specification, the descriptions, definitions, and / or use of terms in this specification shall prevail.

[0104] Finally, it should be understood that the embodiments described in this specification are only used to illustrate the principles of the embodiments of this specification. Other variations may also fall within the scope of this specification. Therefore, as an example and not a limitation, alternative configurations of the embodiments of this specification may be considered consistent with the teachings of this specification. Accordingly, the embodiments of this specification are not limited to the embodiments explicitly introduced and described in this specification.

Claims

1. A magnetic resonance imaging device, comprising: at least one storage medium including a set of instructions; as well as One or more processing devices in communication with the at least one storage medium, wherein when executing the instructions, the one or more processing devices are configured to: reading an intermediate translation file associated with the sequence, wherein the intermediate translation file is obtained under a first development environment; Converting the intermediate translation file into a component recognizable by the second development environment, and generating hardware instructions executable by the hardware module; Checking in the second development environment whether the hardware instructions can be executed in the magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; If so, the hardware instruction is sent to each hardware module, so that the hardware module executes based on the hardware instruction to obtain a magnetic resonance signal matching the sequence.

2. The device according to claim 1, characterized in that The second development environment is a development environment of the magnetic resonance system, and the second development environment is different from the first development environment.

3. The device according to claim 1, characterized in that The intermediate translation file includes the gradient information, radio frequency information and ADC information of the sequence.

4. The device according to claim 1, characterized in that The format of the intermediate conversion file is configured to be readable and recognizable in the second development environment.

5. The device according to claim 4, characterized in that The intermediate translation file includes a sequence file obtained in the first development environment, or the intermediate translation file is converted based on a sequence file obtained in the first development environment.

6. The device according to claim 1, characterized in that In order to convert the intermediate translation file into a component recognizable by the second development environment and generate hardware instructions executable by the hardware module, the one or more processing devices are used to: Converting the intermediate translation file into a component recognizable by the second development environment and generating an executable module, wherein the executable module includes at least one of a data acquisition module, a gradient module and a radio frequency module; A hardware instruction executable by the hardware module is generated based on the executable module.

7. The device according to claim 6, characterized in that If so, sending the hardware instruction to each hardware module includes: In response to the hardware instruction being able to run normally and output a sequence timing diagram matching the sequence, the hardware instruction is issued to each of the hardware modules.

8. The device according to claim 1, characterized in that Checking whether the corresponding sequence file is consistent with the requirements of the first development environment includes: Under the second development environment, compiling based on the executable module and outputting a sequence timing diagram; Acquire user feedback information on the sequence timing diagram, and determine whether the sequence timing diagram is correct based on the feedback information to determine whether the corresponding sequence file is consistent with the requirements of the first development environment.

9. The device according to claim 1, characterized in that The one or more processing devices are also used to: Acquire update information of the sequence in the first development environment; Based on the update information, the hardware instructions are updated in real time in the second development environment.

10. A magnetic resonance imaging method, characterized in that: The method comprises: reading an intermediate translation file associated with the sequence, wherein the intermediate translation file is obtained under a first development environment; Converting the intermediate translation file into a component recognizable by the second development environment, and generating hardware instructions executable by the hardware module; Checking in the second development environment whether the hardware instructions can be executed in the magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; If so, the hardware instruction is sent to each hardware module, so that the hardware module executes based on the hardware instruction to obtain the sequence-matched magnetic resonance signal.

11. The method according to claim 10, characterized in that The second development environment is a development environment of a magnetic resonance system, and the second development environment is different from the first development environment.

12. The method according to claim 10, characterized in that The format of the intermediate conversion file is configured to be readable and recognizable in the second development environment.

13. The method according to claim 12, characterized in that The intermediate translation file includes a sequence file obtained in the first development environment, or the intermediate translation file is converted based on a sequence file obtained in the first development environment.

14. The method according to claim 10, characterized in that The step of converting the intermediate translation file into a component recognizable by the second development environment and generating hardware instructions executable by the hardware module includes: Converting the intermediate translation file into a component recognizable by the second development environment and generating an executable module, wherein the executable module includes at least one of a data acquisition module, a gradient module and a radio frequency module; generating hardware instructions executable by the hardware module based on the executable module; The sending of the hardware instruction to each hardware module comprises: In response to the hardware instruction being able to run normally and output a sequence timing diagram matching the sequence, the hardware instruction is issued to each hardware module.

15. The method according to claim 14, characterized in that Checking whether the corresponding sequence file is consistent with the requirements of the first development environment includes: Under the second development environment, compiling based on the executable module and outputting a sequence timing diagram; Acquire user feedback information on the sequence timing diagram, and determine whether the sequence timing diagram is correct based on the feedback information to determine whether the corresponding sequence file is consistent with the requirements of the first development environment.

16. A magnetic resonance imaging method, characterized in that: The method comprises: In the first development environment, a sequence file associated with the sequence is generated; In the first development environment, determining an intermediate translation file based on the sequence file; The intermediate translation file is sent to a second development environment where the magnetic resonance imaging device is located, so that the magnetic resonance imaging device performs a magnetic resonance scan matching the sequence based on the intermediate translation file in the second development environment.

17. A magnetic resonance imaging system, characterized in that: The system comprises: A reading module, used for reading an intermediate translation file related to the sequence, wherein the intermediate translation file is obtained under a first development environment; A conversion module, used to convert the intermediate translation file into a component recognizable by the second development environment, and generate hardware instructions executable by the hardware module; A checking module, used for checking in the second development environment whether the hardware instruction can be executed in the magnetic resonance system, and whether the corresponding sequence file is consistent with the requirements of the first development environment; The sending module is used to send the hardware instruction to each hardware module, so that the hardware module executes based on the hardware instruction to obtain a magnetic resonance signal matching the sequence.

Images