KR20130064195A - Visual pulse sequence edit system and the method thereof - Google Patents

Abstract

PURPOSE: A visual pulse sequence editing system and a method thereof are provided to easily generate a visual pulse sequence code by supplying various editing functions and pulse components. CONSTITUTION: A visual pulse sequence program editor(100) generates and edits a pulse sequence component on a graphic screen. A pulse sequence editor complier(200) parses a pulse sequence graph screen generated through the visual pulse sequence program editor into a pulse sequence program code. The visual pulse sequence program editor includes a central lookup module. If a user adds or edits pulse components to the screen, the central lookup module shares attribute values to update and synchronize the pulse sequence graph screen according to the change of pulses.

Description

Visual pulse sequence edit system and the method

The present invention relates to a visual pulse sequence editing system and a method thereof, and more particularly to visual pulse sequence editing that provides an intuitive and efficient method for visualizing a pulse sequence programming by providing a variety of graphically edited pulse component configurations and graphic editing functions. System and method thereof.

As shown in FIG. 1, in the conventional general pulse sequence program form, in order to visualize the pulse data onto the program, a pulse program needs to be created as shown in the center of FIG.

Most commercially available pulse sequence programming tools now support text formats. Of course, you can write complex fMRI pulse sequences.

However, writing detailed pulse sequence program code for a pulse sequence programming language can be a daunting task for fMRI scientists who are not familiar with pulse programming languages.

Therefore, it is necessary to implement a GUI platform that can create a pulse sequence program or modify an existing pulse sequence program without learning a pulse programming language.

SUMMARY OF THE INVENTION In order to solve the above problems, an object of the present invention is to provide a visual pulse sequence editing system and method for providing an intuitive and efficient method for visualizing a pulse sequence programming by providing a figured pulse component configuration and various graphical editing functions. There is this.

The present invention provides a visual pulse sequence program editor for creating and editing a pulse sequence component on a graphic screen, and a pulse sequence graph scene generated through the visual pulse sequence program editor. It consists of a pulse sequence editor compiler that parses into pulse sequence program code.

The visual pulse sequence program editor further includes a central lookup module, wherein when the user adds or edits pulse components in the pulse sequence screen, the central lookup module shares attribute values in real time according to a change in the height or width of the pulse. Update and synchronize the pulse sequence graph screen.

The visual pulse sequence program editor is displayed on the screen as top components, and the top component displayed on the screen includes a parameter module for editing a property value list such as pulse, delay, gradient, and the like. Palette module showing a list of pulse components, Pulse Scene graph display module showing a pulse sequence program, Inspector module showing a list of pulse widgets, and properties for the selected pulse widget. And a property window module for editing an index and a project module for managing a pulse sequence program project.

In the visual pulse sequence program editor, a pulse parameter input table is added to a pulse parameter top component. The pulse parameter top component configures a tap for each pulse type including pulse, delay, and gradient, and the width of the pulse in the tap ( attribute values, including duration, power, amplitude, are displayed as tabs, and one of the tabs constituting the parameter table includes a parameter table model class, a table panel class, and parameters The parameter table model (AbstractParameterTableModel) class manages the data inputted to the rows and columns of the pulse table, detects the event of the property value change, and the TablePanel class displays the parameter table model The Parameter class is By sharing attribute values of a table model with other modules, storing the attribute values of all table models in an array, registering them in the central lookup, and synchronizing the parameter attribute values of the parameter module with another module registered in the central lookup. When entering or modifying the parameter property value, the changed property value is applied to the screen and property window of the pulse scene sequence graph so that the parameter can be modified through the integrated input window and the parameter can be modified during the pulse sequence program.

The present invention provides a method of generating and editing a pulse sequence component on a graphic screen through a visual pulse sequence program editor, and a pulse sequence graph scene generated through the visual pulse sequence program editor through a pulse sequence editor compiler. Parsing into pulse sequence program code, and through the central lookup module included in the visual pulse sequence program editor, when the user adds or edits pulse components in the pulse sequence screen, the attribute values are shared. The method may further include updating and synchronizing the pulse sequence graph screen in real time according to a change in the height or width of the pulse.

According to the present invention, it provides an intuitive and efficient method by providing a variety of editing functions graphically and graphically.

According to the present invention, it is possible to easily generate a visualized pulse sequence program code.

1 is a diagram comparing the prior invention.
2 is a conceptual diagram showing the overall concept of the present invention.
Figure 3 is a diagram showing in detail the configuration of a visual pulse sequence editing system according to the present invention.
4 shows a pulse bean designed according to the visual pulse sequence editing system of the present invention.
5 is a conceptual view of a central lookup of a visual pulse sequence editing system according to the present invention;
6 is a schematic representation of a visual pulse sequence program editor in accordance with the present invention.
Figure 7 shows a visual pulse sequence program editor of the visual pulse sequence editing system according to the present invention.
8 illustrates a parameter input method according to the present invention.
9 illustrates a pulse component in accordance with the present invention.
10 shows a module for generating a pulse component in accordance with the present invention.
11 is a class diagram of a pulse sequence graph screen according to the present invention;
Figure 12 shows a pulse sequence screen according to the present invention.
Figure 13 illustrates a Popup Menu Provider (WidgetPopupMenuProvider) class in accordance with the present invention.
14 illustrates a method of selecting and sorting widgets in a row in accordance with the present invention.
15 shows a pulse scene graph screen according to the present invention;
Figure 16 shows the structure of a project module according to the present invention.
Figure 17 shows a Pulse Program Data Object (PulseProgramDataObject) and a Pulse Program Data Node (PulseProgramDataNode) in accordance with the present invention.
18 is a diagram showing providing a sample project for guiding project templates according to the present invention.
19 illustrates a compiler function in accordance with the present invention.
20 is a pulse sequence program in accordance with the present invention showing a text editor.
21 is a view showing a UI that can be switched with the text edit window in accordance with the present invention.
22 and 23 are diagrams compared with the pulse programming language of Bruker.
Figure 24 shows an example of a pulse sequence program according to the present invention.
FIG. 25 is a diagram illustrating the release of spectrometer control, data processing, simulation, and visualization according to the present invention; FIG.
Figure 26 illustrates hardware instructions (pulses, gradient pulses, timings) needed in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the drawings.

3 is a view showing in detail the configuration of a visual pulse sequence editing system according to the present invention, the pulse sequence programming generator framework is largely composed of three according to an embodiment of the present invention.

The visual pulse sequence program editor 100 allows a pulse sequence component to be created and edited on a graphic screen.

The compiler 200 parses a pulse sequence graph scene drawn in the visual pulse sequence program editor into pulse sequence program code.

And it consists of graph structure and data structure of pulse sequence component type and parameter values necessary for pulse sequence program code generation.

FIG. 4 is a diagram illustrating a pulse bean designed according to the visual pulse sequence editing system of the present invention. The aforementioned framework is based on a netbeans platform. Is designed.

The pulse bin is a module suites structure containing submodules. The module suite includes a pulse scene module and a central lookup object.

The pulse scene module consists of the packages that make up the visual editor and compiler.

The central lookup acts as a global class that manages instances shared between these packages.

5 is a conceptual diagram of a central lookup of a visual pulse sequence editing system according to the present invention, wherein the central lookup is configured to share attribute values when a user adds or edits pulse components in a pulse sequence screen according to a change in height or width of a pulse. Update the pulse sequence graph screen in real time and synchronize it with other modules.

Conventional lookup is a programming technique that selects data items from an array or table whose items are identified by their key. The lookup of the NetBeans platform applied in the existing lookup is a concept generally used to manage object instances. It is mainly used to communicate modules with each other in an application. It is the central lookup that aligns the lookup described above with the framework presented in this patent.

A conceptual diagram of such a central lookup is as shown in FIG. 5. When a class object is registered from each module in the module suite, it is kept in the central lookup. When a class object is requested from another module, the corresponding lookup result is returned.

6 is a schematic diagram of a visual pulse sequence program editor according to the present invention, which aims to enable a fMRI-related person to graphically design a pulse sequence without learning about pulse sequence programming. .

This allows the user to infer a use case diagram for generating pulse sequence program code using the Visual Pulse Sequence Program Editor.

FIG. 7 is a diagram illustrating a visual pulse sequence program editor of the visual pulse sequence editing system according to the present invention. The visual pulse sequence program editor proposed in the present invention is displayed on the screen with top components adapted to the characteristics of each module. The top components displayed on the screen are as follows.

Parameter: Edit the list of property values such as Pulse, Delay, Gradient, etc.

* Palette: Displays a list of pulse components such as Pulse, Delay, Gradient, etc.

Pulse sequence graph: shows the pulse sequence program

Inspector: displays a list of pulse widgets

Properties window: Edits properties and indexes for the selected pulse widget.

Project: manages pulse sequence program project

8 is a view showing a parameter input method according to the present invention, the existing Bruker program requires a separate input according to the parameter type, but the parameter input method proposed in this patent has improved the existing method by implementing an integrated input window . In addition, the PulseParameterTopComponent is placed at the bottom of the platform to enable parameter modification during pulse sequence program work.

8 is a class diagram of a parameter module, and shows a structure in which a pulse parameter input table is added to a pulse parameter top component. The pulse parameter top component configures taps by pulse types such as Pulse, Delay, and Gradient, and displays attribute values such as pulse width and power in them.

In other words, the following three classes are required for one tab of the parameter table.

AbstractParameterTableModel :: AbstractTableModel

TablePanel :: JPanel

* Parameters

First of all, the ParameterParameterModelModel class manages data entered into rows and columns of a pulse table and detects events about attribute value changes. The TablePanel class displays the parameter table model, and the Parameter class shares the attribute values of the table model with other modules.

The parameter class stores the attribute values of all table models in an array and is registered in the aforementioned central lookup. This is to synchronize the parameter attribute values of the parameter module and other modules registered in the central lookup. That is, when the user enters or modifies the parameter property value, the changed property value is applied to the screen and property window of the pulse scene sequence graph.

FIG. 9 is a diagram illustrating a pulse component according to the present invention. The pulse component includes a pulse widget, a pulse node, and a pulse model class as shown in FIG. 9. To create a new pulse component, you must implement the following three classes and add them to the palette.

Pulse widget: Implements the PaintProvider interface to draw a pulse component on the screen.

* Pulse Node: Node shown in the Palette Top component

* Pulse model: This model contains information for converting pulse widgets and pulse nodes.

The pulse component that the user selects from the pallet top component consists of pulse nodes. The pulse node has index information of each property and creates a property window. The selected pulse node creates a pulse model during drag and drop. When dropped, the pulse model converts the pulse node into a pulse widget, which draws the pulse component on the pulse sequence graph screen according to the shape, height, and width of the pulse component.

10 is a view showing a module for generating a pulse component according to the present invention, the pallet proposed in the present invention is a module for generating a new pulse component. The pulse components are shown in tree form according to their types, and can be dragged and dropped onto the pulse sequence graph screen.

In order to implement such a pallet function, the pallet module provided by the existing NetBeans was implemented according to the present patent. By default, the Netbeans IDE consists of a palette module that allows you to drag and drop the displayed components into the Netbeans editor. Palette data is managed by the PaletteController.

By registering the palette controller in the lookup of the top component, the palette is automatically opened when the top component is activated.

However, the Palettes of the Netbeans IDE do not allow modification. Therefore, using the existing NetBeans palette API, we implemented a palette that displays pulse components. When the top component of the pulse sequence graph screen is activated, a palette is created. In order to create a palette, the palette controller must be registered in the lookup of the top component.

In order to reconfigure the provided pallet controller according to the patent, the PaletteUtils class is implemented to support the pallet. This class supports palette data, actions, drag and drop handlers, and more. In particular, to create a node hierarchy that provides data to the palette, the following four classes are implemented:

* PaletteCategoryNodeContainer

  : Container containing all category nodes in the palette

* PaletteCategoryNode

  : One category node, creating a new pallet pulse node container

* PaletteNodeContainer

  : Container containing all pulse nodes belonging to one category

PaletteStructure: Registers a new category or new pulse component. Manages a list of all categories and pulse nodes in the palette

FIG. 11 is a diagram showing a class diagram of a pulse sequence graph screen according to the present invention. The class diagram of the pulse sequence graph screen is largely composed of a pulse scene component, a pulse scene and a pulse scene layout. It was.

In addition, the pulse scene tower component converts and displays a pulse scene and a pulse sequence program code. To do this, a tool bar was configured on top of the pulse tower component, including a source and a design button. According to the action event, the source button shows the pulse sequence program code in the text area, and the design button shows the pulse scene.

The pulse scene is the most important part of the pulse sequence graph. To show the visual pulse sequence graph screen, we inherited the scene class of the NetBeans Visual Library API and implemented it for the pulse scene. The scene is itself a widget and the root element for the current hierarchy of displayed widgets.

Thus, the pulse scene becomes the root element of the tree structure, displaying and managing all subordinate widgets. In addition, several layer widgets were used to manage the various widgets independently in the order and role they are drawn. Layer widgets are widgets that are not drawn on the screen and are used as layers to organize other types of widgets. The types of layer widgets included in the pulse scene are as follows.

Main layer: manages pulse widgets via pulse scene layout

Filler layer: Manages the Filler widget and Sort Display widget for sorting between pulse widgets

Loop layer: Managed loop widget for displaying the border of repeating statements

Interaction layer: adds and manages widgets that connect the boundaries of repeating statements

Background layer: manages selection pulse widget and selection display widget when dragging

Guidelines layer: displays rows of the pulse sequence graph

Table 1 below shows the main functions of the visual pulse sequence program editor.

12 is a diagram showing a pulse sequence screen according to the present invention, in which selection and movement functions are used to select and move a pulse widget on a pulse sequence screen. There are two cases of selecting a pulse widget: single selection and continuous selection. Single selection is when the left mouse button is clicked on the pulse widget of the pulse scene. Continuous selection is when you click the left mouse button while holding down the control keys on the keyboard or drag and drop the mouse to select a rectangular area.

FIG. 13 is a diagram illustrating a popup menu provider (WidgetPopupMenuProvider) class according to the present invention. Basically, a top component is updated in an inspector and an attribute window for a selected node among nodes displayed on a screen. However, in the pulse scene, the pulse widget is selected, so we need to change the widget to a node known from the top component. Therefore, the selected pulse widgets were changed to pulse nodes and stored in the pulse node container. The created pulse node container is registered in the pulse tower component so that the selected pulse widget can be known globally.

And in order to move the pulse widget, we store the position when the mouse is first clicked and the pulse widget to be moved. After that, update the position of the pulse widget to the position when the mouse is released. The location update consists of changing the order of the pulse widgets included in the main layer widget, and uses the indexes of the moving pulse widget and the target pulse widget.

The pop-up menu is also used to select events for editing, looping, sorting, etc. other than selection and movement. Select the pulse widget and right-click to create a popup menu. The pop-up menu is generated by the pop-up menu provider (WidgetPopupMenuProvider) class of FIG. 13 mentioned above. The widget popup menu provider class creates a popup menu and executes events according to action commands defined through action listeners.

The function to edit the selected pulse widget is used to copy, paste and delete the pulse widget in the pulse sequence screen. When copying and pasting selected widgets, paste them into the corresponding row of each selection pulse widget.

FIG. 14 is a diagram illustrating a method of selecting and sorting widgets in a row according to the present invention, wherein the sorting function is used to align pulse sequences in the same time zone, and allows the time (horizontal) axis of the selected widgets to be aligned on the GUI.

You can also create a new filler widget by selecting the widget in each row and right-clicking on it to select the 'Align' menu. The selected widgets are then aligned with the center coordinates of the rightmost widget.

Table 2. Key functions of the filler layer widget

FIG. 15 is a diagram illustrating a pulse scene graph screen according to the present invention, wherein a loop function is used to generate a repetitive phrase, and is represented by a line connecting a start pulse widget and an end pulse widget on a pulse scene graph screen.

In addition, as shown in FIG. 15, after selecting two widgets, clicking the right mouse button and selecting 'Loop' from the pop-up menu, a new loop is drawn.

Adding a new loop is indicated by a curved arrow at the bottom of the bottom row, with the start coordinates of the widget on the left and the end coordinates of the widget on the right of the two selected widgets. One route is implemented as the LoopWidget class, and consists of two LoopBoundaryWidget classes that draw the loop boundaries. These loop widget classes are added as child nodes of the loop layer widget.

When a widget is inserted into a loop, it is either when the widget outside the loop is inserted inside or when a new widget is added into the loop from the palette. If the inserted widget is inside a loop, make sure that the loop's width is as wide as the inserted widget.

When the widgets in the loop move, you need to handle the following two cases: First, if the widget in the loop moves to the left of the left border, remove the loop. And if the widget in the loop moves to the right of the right border, the right border of the loop will stretch that much.

Also, the user can delete the loop. Click on a specific loop with the mouse to select it and change the color of the selected loop. Right-clicking on the selected loop brings up a pop-up menu, and clicking the 'Remove' menu deletes the loop.

For the functions of the aforementioned loop, the main classes implemented are shown in Table 3.3.

Table 3 Loop Main Classes

16 is a view showing the structure of a project module according to the present invention, in which a pulse project factory serving as a project factory checks whether a project exists and creates a new pulse project or loads an existing pulse project. do. It also saves properties and files for the loaded project.

17 is a diagram showing a pulse program data object (PulseProgramDataObject) and a pulse program data node (PulseProgramDataNode) according to the present invention. In order to open or recognize each .ppg file in the visual pulse sequence program editor, a pulse program data object (PulseProgramDataObject) is shown. ) And a pulse program data node (PulseProgramDataNode).

Create a pulse program data object through NetBeans' DataLoader, a factory for registering file extensions and MIME types specific to the project. The generated pulse program data object causes all files in the .ppg to appear under the project folder when the project window and the file window are opened.

Each file in the project is assigned a specific icon or action by a pulse program data node. For each action, the main file designation, pulse scene graph screen opening and saving are designated.

FIG. 18 is a diagram showing providing a sample project for guiding project templates according to the present invention. When the user newly creates a project, FIG. 18 provides a sample project for guiding project templates. do. The sample project consists of a sample and an empty package.

The sample package provides a project template with the default pulse sequence code entered, and the empty package provides only an empty .ppg file with no default project code. You can also create a new project from the menu, or create a project directly from the project window.

19 is a view showing a compiler function according to the present invention, the compiler has two functions. The first one parses the pulse sequence graph screen created by the user and creates a pulse sequence program file (.ppg).

The second one parses a textual pulse sequence program file, draws it on the pulse sequence graph screen, and puts the parameter value.

The aforementioned pulse sequence graph screen is a screen that draws pulse components and loops such as Pulse, Delay, and Gradient as a picture. A separate data structure was designed to parse this pulse sequence graph screen into a pulse sequence program file.

The pulse sequence graph screen stores each pulse component in a tree structure. Each pulse component also has its own label, type, width, height, attributes, and information needed for parsing. This information can be obtained as a string and used like a tag.

First, the token component list stored in the pulse sequence graph screen is sequentially tokenized for each row. The visual keyword is examined in a symbol table consisting of pulses, delays, gradients, and loops. If a visual keyword is present, the attribute value is taken from a string tag that contains the width, height, attributes, and index of the pulse component. Finally, input the attribute value of the index in the parameter table and generate the pulse sequence program code. If the visual keyword does not exist, try token analysis again.

20 is a diagram showing a pulse sequence program in accordance with the present invention, a text editor, the existing text-based Bruker pulse sequence program editor, as shown in Figure 20 fMRI scientists of the user needs training in the pulse programming language, pulse sequence The program uses a text editor and saves it as a text file.

In order to evaluate the performance of the proposed visual pulse sequence programming generator, this patent is evaluated through three diagnostic criteria. The first consists of evaluating the accuracy of the generated code, the second evaluating the efficiency of the average work time, and finally the user's convenience.

Therefore, according to the present invention, the accuracy of the proposed method was first evaluated, and the test version was distributed to the pulse signal processing experts in the medical field for about one month for evaluation of efficiency and convenience. That is, the method of processing accuracy evaluation by comparing the generated code is shown.

Table 4. Accuracy test results by code comparison

FIG. 21 is a diagram illustrating a UI capable of switching with a text edit window according to the present invention. The visual pulse sequence editor provides a UI capable of switching with a text edit window as shown in FIG. 21. This results in inaccurate results after creating the pulse sequence graph screen, or allows the user to directly modify the text if more complex pulse sequence programming is required.

22 and 23 are diagrams comparing the pulse programming language of Bruker, which is compared to the pulse programming language of Bruker through the experiment, and visualizes the pulse-based text-based pulse sequence program without training for the pulse programming language. It was possible to edit and provide intuitive information to the user.

24 is a view showing an example of a pulse sequence program according to the present invention, Bruker pulse sequence program is typically used in the conventional pulse sequence program, in addition to 40 various pulse sequence programs such as MatNMR, AMBER, MRIcro Are present. These pulse sequence programs have been activated since the early 90's, and even the same pulse sequence programs are released in different types according to data processing purposes.

As a representative example, Bruker pulse sequence program has been active since '95 and launched various pulse program packages for different pulse analysis purposes such as WINNMR 1D, WINNMR 2D, WIN-SpecEdit, WIN-DAIZY, and WIN-Xpert. . This is one of Bruker's greatest strengths in the NMR analysis program. However, the need for parameter information for separate NMR measurements lies in the Bruker program. Next, FIG. 24 shows a text-based parameter input window which is commonly used for each package as a Bruker program sample.

In general, in the case of Bruker programs, separate text-based parameters are entered for NMR analysis for each module. This part can be a disadvantage for the user. The problem is that all the information must be known for each NMR analysis, and additional information coding requires additional knowledge.

FIG. 25 is a diagram illustrating the release of spectrometer control, data processing, simulation, and visualization in accordance with the present invention. It has been released as a separate single package.

In general, it means that it is released for analysis purposes. It means that the pulse analysis is mainly classified into spectrometer control, data processing, simulation, and visualization. This represents representative programs that have been released for analysis purposes in FIG. 25.

Among them, DAMARIS, a program developed by Achim G, developed a framework for NMR Spectrometer Controls. However, due to the lack of performance in the part of the visualization or simulation, it was released in an unsuitable form for data processing in the pulse program. Another example is MathWorks' matNMR. matNMR is a representative data processing program through Matlab, which uses Matlab-based NMR and EPR spectrum toolboxes, and is characterized by high flexibility and compatibility. However, the use of various toolboxes is not a small burden on the system.

Among the simulation packages, AMBER is a representative simulation package that can simulate the relationship diagram of NMR structure by various cases. In particular, more intuitive and faster processing speed is considered to be an advantage over other simulation packages. Finally, MRIcro, developed by Chris Rorden, is one of the visualization packages that focuses on the conversion and visualization of various medical data formats, including DICOM, ECAT, NEMA, GE Signa & LX, Interfile, Picker CT, Siemens Magnetom, and others. The advantage is that it handles various raw data formats.

However, most commercially available pulse sequence programming tools now support text formats. Of course, you can write complex MRI pulse sequences. However, writing detailed pulse sequence program code for a pulse sequence programming language can be a daunting task for those unfamiliar with the pulse programming language.

Therefore, the present invention proposes a visual pulse sequence programming generator based on fMRI to visualize a pulse sequence so that a pulse sequence program code can be easily generated. A new pulse sequence program or an existing pulse sequence can be created without learning a pulse programming language. Implemented a GUI platform different from the existing one to modify the program.

FIG. 26 is a diagram illustrating hardware commands (pulses, gradient pulses, timings) required according to the present invention, and the pulse sequence is based on the acquired MR image, and refers to a technique for measuring the same. The pulse sequence also includes the hardware instructions (pulses, gradient pulses, timings) needed to obtain the data in the desired format, and sets the pulse sequence program format to the appropriate pulse sequence program instructions sequentially.

The pulse sequence program is ASCII text consisting of numbers on a line. A simple Brucker pulse sequence program example is programmed as shown in FIG. 26, where each line may contain one or more pulse sequence program statements that specify certain actions to be performed by hardware or software.

100: visual pulse sequence program editor
200: compiler

Claims (5)

A visual pulse sequence program editor for creating and editing a pulse sequence component on a graphic screen;
A pulse sequence editor compiler for parsing a pulse sequence graph scene generated by the visual pulse sequence program editor into pulse sequence program code;
Visual pulse sequence editing system, characterized in that consisting of. The method of claim 1,
The visual pulse sequence program editor,
Further includes a central lookup module,
When the user adds or edits pulse components in the pulse sequence screen, the central lookup module updates and synchronizes the pulse sequence graph screen in real time according to a change in the height or width of the pulse by sharing property values. Pulse sequence editing system. The method of claim 1,
The visual pulse sequence program editor,
The top components displayed on the screen are displayed on the screen, and the top component displayed on the screen includes a parameter module for editing a property value list such as pulse, delay, and gradient, and a palette representing a list of pulse components such as pulse, delay, and gradient. Palette module, Pulse Scene Graph module showing pulse sequence program, Inspector module showing pulse widget list, and properties and indexes for selected pulse widgets. A visual pulse sequence editing system comprising: a Properties window module, and a Project module for managing a pulse sequence program project. The method according to claim 1 or 2,
The visual pulse sequence program editor,
A pulse parameter input table is added to the pulse parameter top component, wherein the pulse parameter top component configures taps by pulse types including pulses, delays, and gradients, and the widths, amplitudes, the attribute value including amplitude is displayed as a tab, and the one tab constituting the parameter table includes a parameter table model class, a table panel class, and a parameter class.
The parameter table model class manages data input to rows and columns of a pulse table, detects an event about a change in an attribute value, and the table panel class displays a parameter table model, and the parameter ( Parameters class shares the property values of the table model with other modules, stores the property values of all table models in an array, and registers them in the central lookup.
Synchronize the parameter attribute values of the parameter module with other modules registered in the central lookup so that when the user enters or modifies the parameter attribute values, the changed attribute values are applied to the screen and the attribute window of the pulse scene sequence graph. Visual pulse sequence editing system, characterized in that the parameter input method through the input window, and the parameters can be modified during the pulse sequence program operation. Creating and editing a pulse sequence component on a graphic screen through a visual pulse sequence program editor;
Parsing a pulse sequence graph scene generated by the visual pulse sequence program editor through a pulse sequence editor compiler into pulse sequence program code;
Through the central lookup module included in the visual pulse sequence program editor, when the user adds or edits pulse components in the pulse sequence screen, the attribute values are shared to display the pulse sequence graph screen in real time according to the change of the height or width of the pulse. And updating and synchronizing.

Images