Beam line station synchronous data acquisition device and method

Abstract

The invention discloses a beam line station synchronous data acquisition device and method, and belongs to the technical field of beam line station control, and the device comprises an equipment control layer and an application layer. The equipment control layer comprises a plurality of acquisition cases, an upper computer and a time service unit, the plurality of acquisition cases are respectively connected to the upper computer, and the time service unit is respectively connected to the timing module in each acquisition case; the application layer comprises an equipment abstraction module, a process abstraction module, a queue server module, a data storage module and a data visualization module. Unified abstract packaging is carried out on beam line station equipment and an experimental process, so that the same set of software framework is universal in all experimental modes and methodology, and a unified architecture for controlling a spectroscopy, imaging and diffraction experimental process is realized; experiments can be executed autonomously according to the queue sequence, automation of the experimental process is achieved, data acquisition efficiency is improved, and then the problems that in a beam line station, multi-device synchronization efficiency is low, and synchronization signal lines are prone to interference are solved.

Description

Technical Field

[0001] The present invention relates to the field of beam line station control technology, and in particular to a beam line station synchronous data acquisition device and method. Background Art

[0002] As the quality of synchrotron radiation sources becomes higher and higher, in order to better explore matter, various experimental methods have an increasing demand for high-precision synchronization and high-efficiency data acquisition. Especially for multi-modal detection experiments, the synchronization between detectors and energy scanning devices is particularly critical.

[0003] Existing beamline station data acquisition synchronization technologies are all based on hardware synchronization, involving hard-wired connections between various detection devices. However, in the synchrotron radiation environment, the poor electromagnetic environment will inevitably lead to false triggering, resulting in synchronization failures between devices. To this end, the present invention proposes a beamline station synchronization data acquisition device and method. Summary of the invention

[0004] The technical problem to be solved by the present invention is: how to solve the problems of low synchronization efficiency of multiple devices in a beam line station and susceptibility to interference of synchronization signal lines. A beam line station synchronization data acquisition device is provided, which abstractly integrates the experimental equipment and experimental processes controlled by step scanning, flying scanning and other experiments into a software framework, and realizes a unified architecture for spectroscopy, imaging and diffraction experiment process control and data acquisition.

[0005] The present invention solves the above technical problems through the following technical solutions. The present invention includes a device control layer and an application layer;

[0006] The device control layer includes multiple acquisition boxes, a host computer, and a timing unit. The multiple acquisition boxes are respectively connected to the host computer, and the timing units are respectively connected to the timing modules in each acquisition box;

[0007] The application layer includes a device abstraction module, a process abstraction module, a queue server module, a data storage module and a data visualization module; the device abstraction module is used to abstract the EPICS process variable information of the experimental equipment into a Python object, and multiple Python object signals form a device, which is configured and used as a unit, and after assigning names to the signals and devices, they are stored in the experimental metadata; the process abstraction module is used to abstract the experimental process into a plan; the queue server module is used for users to create and manage plan queues and plan execution environments, and autonomously execute plans according to the order of experimental queues in the plan queues; the data storage module is used to extract experimental metadata from the run start document, and cache the event documents of the entire experiment process, that is, to obtain the original data of the experiment, and then run the end document to trigger the data export and storage function; the data visualization module is used to manage the running engine environment of the queue server module, manage the plan queue, monitor the status of the EPICS process variable information, and display the data curve in real time;

[0008] The device control layer is a distributed architecture based on EPICS, using Ethernet as the communication means between the input / output controller IOC and the controlled experimental equipment. According to the Channel Access network protocol provided by EPICS, the communication between the host computer and the computer module in the acquisition chassis is carried out in Client / Server mode to realize the application layer's control of the experimental equipment parameters and the transmission of the detector experimental data.

[0009] Furthermore, the input / output controller IOC application includes a detector IOC application, a motor IOC application, and an energy / wavelength-position conversion IOC application.

[0010] Furthermore, the acquisition chassis is provided with a power module, a computer module, a timing module, a data acquisition module and an interface module. The power module, the computer module, the timing module, the data acquisition module and the interface module are all arranged on the 3U chassis backplane through VPX slots and are interconnected through a backplane bus.

[0011] Furthermore, the interface module includes a first voltage conversion circuit, an SRIO switch, a first FPGA controller and a first FLASH memory; the SRIO switch and the first FLASH memory are both connected to the first FPGA controller, and the first voltage conversion circuit is used to power the SRIO switch, the first FPGA controller and the first FLASH memory.

[0012] Furthermore, the data acquisition module includes a second voltage conversion circuit, a second FPGA controller, a second FLASH memory, an A / D conversion circuit and a pulse acquisition unit; the second FLASH memory and the A / D conversion circuit are both connected to the second FPGA controller, the pulse acquisition unit provides a DB15 male connector and a DB15 female connector to the outside for inputting and outputting 5V TTL signals to the outside, the A / D conversion circuit is installed on the data acquisition module to provide 4-way SMA input, and the second voltage conversion circuit is used to power the second FPGA controller, the second FLASH memory, the A / D conversion circuit and the pulse acquisition unit.

[0013] Furthermore, the timing module includes a third voltage conversion circuit, an SFP optical module, a third FPGA controller and a third FLASH memory; the third FLASH memory and the SFP optical module are both connected to the FPGA controller, and the third voltage conversion circuit is used to power the SFP optical module, the third FPGA controller and the third FLASH memory.

[0014] Furthermore, in the data storage module, the experimental metadata is exported into JSON format, and the experimental raw data is exported into HDF5 and CSV formats.

[0015] The present invention also provides a beam line station synchronous data acquisition method, which is used to realize the beam line station data acquisition synchronization work by using the above-mentioned beam line station synchronous data acquisition device, and comprises the following steps:

[0016] Step S1: Power on and time synchronization

[0017] Power on the power modules of each acquisition chassis. After the computer module self-checks, it starts the EPICS IOC to receive control instructions from the host computer. After the timing module is powered on, it communicates with the timing unit to complete the time synchronization.

[0018] Step S2: Initialization of acquisition parameters

[0019] The host computer sends the acquisition control parameters to the computer modules in each acquisition chassis through the network, and then the computer modules send them to the interface module through the PCIE bus, and then forward them to the FPGA controller in the data acquisition module through the SRIO switch to complete the initialization of the acquisition parameters;

[0020] Step S3: Prepare the operating environment

[0021] Prepare the host computer EPICS operating environment, including detector IOC application, motor IOC application and energy / wavelength-position conversion IOC application, and monitor the status of detectors and motors required for beamline station experiments under the EPICS architecture;

[0022] Step S4: Run the engine management service to start

[0023] Configure the queue server module runtime engine startup script and start the runtime engine management service;

[0024] Step S5: User Authentication

[0025] During the experiment, the user enters the card number and name for identity authentication, obtains the user and experiment proposal information from the user management system through the card number, sends a metadata request to the experiment data management system, and constructs user information and roles;

[0026] Step S6: Data visualization module executes the experimental process

[0027] Submit the experimental plan to the queue server module through the user interface, and each acquisition module starts working to package the collected experimental data and timestamps. The packaged experimental data is extracted through a data flow branch and published to the data real-time display callback function through ZeroMQ. The data real-time display callback function obtains real-time data from it to trigger drawing and progress bar refresh; another data flow branch writes the experimental original data and metadata in the experimental data into the data cache, and the running end document triggers the data export and storage function.

[0028] Furthermore, in step S3, EPICS process variable conversion is provided according to the energy / wavelength-position correspondence, and when assigning a value to the energy / wavelength process variable, it is directly converted into setting the corresponding motor position process variable, and when reading the motor position process variable, it is converted into the corresponding energy / wavelength process variable in real time.

[0029] Furthermore, in step S4, when the runtime engine management service is started, the Python object signals and devices provided by the device abstraction module and the plan provided by the process abstraction module are loaded.

[0030] Compared with the prior art, the present invention has the following advantages:

[0031] 1. Solve the problems of low synchronization efficiency of multiple devices in the beamline station and susceptibility to interference of synchronization signal lines, and avoid false triggering in the electromagnetic environment with poor synchrotron radiation, which leads to synchronization failure between devices; and the acquisition chassis adopts a modular design, which is highly versatile and easy to expand.

[0032] 2. Unified abstract encapsulation of beamline equipment and experimental processes makes the same software framework universal for all experimental modes and methodologies, realizing a unified architecture for spectroscopy, imaging, and diffraction experimental process control; experiments can be executed autonomously in queue order to automate the experimental process and improve data collection efficiency.

[0033] 3. Experimental metadata and raw data are stored in standard JSON, CSV and HDF5 formats respectively; recording detailed experimental information and experimental users in the experimental metadata not only explains how the data is generated, but also facilitates the reuse, identification, tracking and sharing of data, which will play an important role in downstream data mining and data analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a schematic structural diagram of a beamline station synchronous data acquisition device in an embodiment of the present invention;

[0035] Figure 2 1 is a schematic diagram of the structure of the equipment control layer of the beamline station synchronous data acquisition device in an embodiment of the present invention;

[0036] Figure 3 is a schematic diagram of the structure of a collection chassis in an embodiment of the present invention;

[0037] Figure 4 It is an abstract flow chart of the step-by-step scanning experiment process in an embodiment of the present invention;

[0038] Figure 5 This is a diagram of a login interface of a beamline station synchronous data acquisition device according to an embodiment of the present invention;

[0039] Figure 6 This is a diagram of the operating interface of the beamline station synchronous data acquisition device in an embodiment of the present invention. DETAILED DESCRIPTION

[0040] The following is a detailed description of an embodiment of the present invention. This embodiment is implemented on the premise of the technical solution of the present invention, and a detailed implementation method and a specific operation process are given, but the protection scope of the present invention is not limited to the following embodiment.

[0041] Embodiment 1

[0042] This embodiment provides a technical solution: a beamline station synchronous data acquisition device, including a device control layer and an application layer;

[0043] The equipment control layer includes N acquisition chassis, a host computer, and a timing unit, where N ≥ 2.

[0044] The acquisition chassis are connected to the host computer through a Gigabit Ethernet switch, and the timing unit is connected to the timing module in each acquisition chassis through a single-mode optical fiber. The equipment control layer is a distributed architecture based on EPICS (Experimental Physics and Industrial Control System), using Ethernet as the communication means between the input / output controller IOC and the controlled experimental equipment. According to the ChannelAccess network protocol provided by EPICS, the communication between the host computer and the computer module is carried out in Client / Server mode to realize the control of the experimental equipment parameters and the transmission of the detector experimental data by the application layer. The input / output controller IOC application includes the detector IOC application, the motor IOC application and the energy / wavelength-position conversion IOC application, which provides the EPICS process variables required by all application layers and is the basis for experimental process control and data acquisition.

[0045] The acquisition chassis is equipped with a power module, a computer module, a timing module, a data acquisition module and an interface module. The power module, the computer module, the timing module, the data acquisition module and the interface module are all placed on the 3U chassis backplane through VPX slots and interconnected through the backplane bus.

[0046] The power module converts the 220V AC power input from the outside of the acquisition chassis into 12V, 5V, and 3.3V DC power, and supplies power to the computer module, timing module, data acquisition module, and interface module through the 3U chassis backplane.

[0047] The computer module and the interface module are connected by a 4x PCIE 2.0 bus with a maximum rate of 20Gbps.

[0048] The interface module is connected to the data acquisition module and the timing module using RapidIO gen2 1x bus, with a maximum transmission rate of 3.125 Gbps.

[0049] The interface module includes a voltage conversion circuit, an SRIO switch, an FPGA controller, a FLASH memory, a debugging interface and an indicator light. The SRIO switch, the FLASH memory, the debugging interface and the indicator light are all connected to the FPGA controller. The voltage conversion circuit converts the 12V power provided by the power module into 5V, 3.3V, and 1.8V power within the module to power the remaining components in the interface module. The indicator lights are two green LEDs for providing work and communication indications. The FPGA controller is connected to the computer module through a 4x pcie 2.0 bus via a 3U chassis backplane.

[0050] The data acquisition module includes a voltage conversion circuit, an FPGA controller, a FLASH memory, an A / D conversion circuit, a pulse acquisition unit, a debugging interface and an indicator light. The FLASH memory, the A / D conversion circuit, the pulse acquisition unit, the debugging interface and the indicator light are connected to the FPGA controller. The pulse acquisition unit provides a DB15 male connector and a DB15 female connector to the outside for inputting and outputting 5V TTL signals to the outside. The A / D conversion circuit is installed on the data acquisition module with an FMC socket to provide 4-way SMA input. The voltage conversion circuit converts the 12V power provided by the power module into +5V, -5V, +3.3V, and 1.8V power supplies in the module to power the remaining components in the data acquisition module. The indicator lights are two green LEDs for providing work and communication indications.

[0051] The timing module includes a voltage conversion circuit, an SFP optical module, an FPGA controller, a FLASH memory, a debugging interface and an indicator light. The SFP optical module, the FLASH memory, the debugging interface and the indicator light are connected to the FPGA controller. The voltage conversion circuit converts the 12V power provided by the power module into 3.3V and 1.8V power in the module to power the remaining components in the interface module. The indicator light is two green LEDs for providing work and communication indications.

[0052] The application layer includes device abstraction module, process abstraction module, queue server module, data storage module and data visualization module.

[0053] The device abstraction module abstracts the experimental device EPICS process variable information into Python objects with common methods such as read() and set(). Multiple separate Python object signals form a "device" and are configured and used as a unit. Easy-to-understand names are assigned to signals and devices and stored in the experimental metadata.

[0054] The process abstraction module abstracts the experimental process into a plan, specifically calling the experimental signals and devices provided by the device abstraction module to perform a series of atomic operations according to the experimental process to complete the entire experiment.

[0055] The queue server module allows users to create and manage schedule queues and schedule execution environments. It can execute plans autonomously according to the order of experimental queues in the schedule queue to automate the experimental process. The core component of the queue server module is the runtime manager, which is responsible for maintaining and executing schedule queues. Plans are executed in a separate process of the runtime engine working environment. The data visualization module can use the ZeroMQ API to request access to the runtime manager. The document stream created by the runtime engine is published to the data storage module and the data visualization module through ZeroMQ. The runtime engine realizes multi-device linkage to complete the set experiment through the execution plan. In this process, the experimental raw data and metadata are read out and converted into a document stream output in a unified format. During data collection, the runtime engine dispatches the document stream to one or more callback functions in real time for real-time data processing, display and storage.

[0056] The data storage module extracts experimental metadata from the run start document and caches the event documents of the entire experiment process, that is, to obtain the original experimental data, and then runs the end document to trigger the data export and storage function. According to the standards set by the experimental data management system and the beamline station, after the experimental metadata is exported to JSON format, a request is sent to the experimental data management system, and the experimental raw data is exported to HDF5 and CSV formats and stored in the local data server. After the experimental data is collected and stored locally, it will be synchronously uploaded to the central server at the end of the plan execution, the file integrity will be verified and stored centrally, and Web data access services will be provided to users through the experimental data management system.

[0057] In this embodiment, the experimental data includes experimental raw data and experimental metadata.

[0058] The data visualization module mainly includes: the running engine environment management module for implementing the running engine environment management of the queue server module; the planned queue management module for implementing the planned queue management; the process variable monitoring module for implementing the EPICS process variable status monitoring; and the real-time curve module for realizing the real-time display of data curves. During the experiment, the user enters the card number and name for identity authentication, obtains the user and proposal information from the user management system through the card number, sends a metadata request to the experimental data management system, and constructs user information and roles. The data visualization module submits the plan to the queue server module through ZeroMQ and obtains the document stream. At the beginning of the plan, the experiment name, collection points and serial number are extracted from the run start document. As the plan is executed, the detector reading and current serial number are extracted from the event document, triggering the user interface drawing and progress bar refresh.

[0059] This embodiment also provides a beam line station synchronous data acquisition method, which is used to use the above-mentioned beam line station synchronous data acquisition device to realize beam line station data acquisition synchronization work, including the following steps:

[0060] Step 1: Power on the power modules of each acquisition chassis. After the computer module self-checks, it starts the EPICS IOC to receive control instructions from the host computer. After the timing module is powered on, it communicates with the timing unit to complete the time synchronization.

[0061] Step 2: The host computer sends the acquisition control parameters to the computer modules in each acquisition chassis through the network. After the computer module sends it to the interface module through the PCIE bus, it is forwarded to the FPGA controller in the data acquisition module through the SRIO switch to complete the initialization of the acquisition parameters.

[0062] Step 3: Prepare the host computer EPICS operating environment, including detector IOC application, motor IOC application and energy / wavelength-position conversion IOC application, and monitor the status of detectors and motors required for beamline station experiments under the EPICS architecture;

[0063] In the third step, EPICS process variable conversion is provided according to the energy / wavelength-position correspondence. When assigning a value to the energy / wavelength process variable, it is directly converted to set the corresponding motor position process variable. When reading the motor position process variable, it is converted into the corresponding energy / wavelength process variable in real time.

[0064] Step 4: Configure the queue server module runtime engine startup script to start the runtime engine management service. When the runtime engine manager starts, it loads the signals and devices provided by the device abstraction module and the plan provided by the process abstraction module.

[0065] Step 5: User authentication. During the experiment, the user enters the card number and name for identity authentication. The user and experiment proposal information (beamline station name, experiment proposal number, experiment proposal name, experiment start and end time, etc.) are obtained from the user management system through the card number, and a metadata request is sent to the experiment data management system to build user information and roles.

[0066] Step 6: The data visualization module executes the experimental process. Submit the experimental plan to the queue server module through the user interface, and each acquisition module starts working to package the collected experimental data and timestamps. The packaged experimental data is extracted through a data flow branch on the network and published to the data real-time display callback function through ZeroMQ. The data real-time display callback function obtains real-time data from it to trigger drawing and progress bar refresh; another data flow branch writes the experimental raw data and metadata in the experimental data into the data cache, and the running end document triggers the data export and storage function.

[0067] Embodiment 2

[0068] like Figure 1 , which is a schematic diagram of the structure of the beamline station synchronous data acquisition device of the present invention, including a device control layer and an application layer.

[0069] like Figure 2 As shown, the equipment control layer of the beamline station synchronous data acquisition device includes N acquisition chassis, a host computer, and a timing unit.

[0070] The acquisition chassis are connected to the host computer through a Gigabit Ethernet switch, and the timing unit is connected to the timing module in each acquisition chassis through a single-mode optical fiber. The device control layer is a distributed architecture based on EPICS, using Ethernet as the communication means between the input / output controller IOC and the controlled experimental equipment. According to the Channel Access network protocol provided by EPICS, the communication between the host computer and the computer module in the acquisition chassis is carried out in Client / Server mode to realize the control of the experimental equipment parameters and the transmission of the detector experimental data by the application layer. The input / output controller IOC application includes the detector IOC application, the motor IOC application and the energy / wavelength-position conversion IOC application, which provides the EPICS process variables required by all application layers and is the basis for experimental process control and data acquisition.

[0071] like Figure 3 As shown, the acquisition chassis includes a power module, a computer module, a timing module, a data acquisition module, and an interface module. The power module, the computer module, the timing module, the data acquisition module, and the interface module are all placed on the 3U chassis backplane through VPX slots and interconnected through the backplane bus.

[0072] The power module converts the 220V AC power input from the outside of the chassis into 12V, 5V, and 3.3V DC power, and supplies power to the computer module, timing module, position acquisition module, signal acquisition module, and interface module through the backplane.

[0073] The computer module and the interface module are connected by a 4x PCIE 2.0 bus with a maximum rate of 20Gbps.

[0074] The interface module is connected to the data acquisition module and the timing module using RapidIO gen2 1x bus, with a maximum transmission rate of 3.125 Gbps.

[0075] The interface module includes a voltage conversion circuit, an SRIO switch, an FPGA controller, a FLASH memory, a debugging interface and an indicator light. The SRIO switch, the FLASH memory, the debugging interface and the indicator light are connected to the FPGA controller. The voltage conversion circuit converts the 12V power provided by the power module into 5V, 3.3V, and 1.8V power within the module to power the remaining components in the interface module. The indicator lights are two green LEDs for providing work and communication indications. The FPGA is connected to the computer module through a 4x pcie 2.0 bus via the chassis backplane.

[0076] The data acquisition module includes a voltage conversion circuit, an FPGA controller, a FLASH memory, an A / D conversion circuit, a pulse acquisition unit, a debugging interface and an indicator light. The FLASH memory, the A / D conversion circuit, the debugging interface and the indicator light are connected to the FPGA controller. The pulse acquisition unit provides a DB15 male connector and a DB15 female connector for external input and output of 5V TTL signals. The A / D conversion circuit is installed on the data acquisition module with an FMC socket to provide 4 SMA inputs. The voltage conversion circuit converts the 12V power provided by the power module into +5V, -5V, +3.3V, and 1.8V power supplies in the module to power the remaining components in the data acquisition module. The indicator lights are two green LEDs for providing work and communication indications.

[0077] The timing module includes a voltage conversion circuit, an SFP optical module, an FPGA controller, a FLASH memory, a debugging interface and an indicator light. The SFP optical module, the FLASH memory, the debugging interface and the indicator light are connected to the FPGA controller. The voltage conversion circuit converts the 12V power provided by the power module into 3.3V and 1.8V power in the module to power the remaining components in the interface module. The indicator light is two green LEDs for providing work and communication indications.

[0078] The application layer includes device abstraction module, process abstraction module, queue server module, data storage module and data visualization module.

[0079] The device abstraction module abstracts the experimental equipment EPICS process variable information into Python objects with common methods such as read() and set(). The motor, detector and other status monitoring EPICS process variables are abstracted into Python object signals, and multiple individual motor control Python object signals are combined into a "motor" to be configured and used as a unit. Easy-to-understand names are assigned to signals and devices and stored in the experimental metadata.

[0080] The process abstraction module abstracts the experimental process into a plan, which is to call the experimental signals and equipment provided by the device abstraction module to perform a series of atomic operations according to the experimental process to complete the entire experiment. The plan of the fly scan is defined as three steps: start, finish, and collect. The start is to complete the scan and the parameter settings related to the detector and then start the scan. The finish is to wait for the scan to be completed and finally execute. The collection completes the acquisition and processing of the detector data. Figure 4 As shown in the figure, the step-scan experiment process abstractly needs to define the input parameters of the plan, including the detector, motor, energy at the start and end of the scan, and the number of acquisition points. At the beginning of the plan, the current number of acquisition points is judged. If the acquisition is completed, it ends. If the current number of acquisition points does not reach the total number of acquisition points, the energy setting value is calculated, and then the motor is moved to the position corresponding to the set energy. The detector data is collected multiple times to calculate the average value and the data is recorded in an event file. The cycle is repeated until the entire acquisition process is completed.

[0081] The queue server module allows users to create and manage schedule queues and schedule execution environments. It can execute plans autonomously according to the order of experimental queues in the schedule queue to automate the experimental process. The core component of the queue server module is the runtime manager, which is responsible for maintaining and executing schedule queues. Plans are executed in a separate process of the runtime engine working environment. The data visualization module can use the ZeroMQ API to request access to the runtime manager. The document stream created by the runtime engine is published to the data storage module and the data visualization module through ZeroMQ. The runtime engine realizes multi-device linkage to complete specific experiments through the execution plan. In this process, the raw data and metadata of the experiment are read out and converted into a document stream in a unified format for throwing. During data collection, the runtime engine dispatches the document stream to one or more callback functions in real time for real-time data processing, display and storage.

[0082] The data storage module extracts the experimental metadata from the run start document and caches the event documents of the entire experiment process, that is, the original experimental data is obtained, and then the run end document triggers the data export and storage function. According to the standards set by the experimental data management system and the beamline station, the experimental metadata is exported to the JSON format and a request is sent to the experimental data management system. The experimental raw data is exported to HDF5 and CSV formats and stored in the local data server. After the experimental data is collected and stored locally, it will be synchronously uploaded to the central server at the end of the plan execution, the file integrity will be verified and stored centrally, and Web data access services will be provided to users through the experimental data management system.

[0083] The data visualization module mainly includes: the runtime engine environment management module for implementing the runtime engine environment management of the queue server module; the plan queue management module for implementing the plan queue management; the process variable monitoring module for implementing the EPICS process variable status monitoring; and the real-time curve module for implementing the real-time display of the data curve. Figure 5 As shown in the figure, during the experiment, the user enters the card number and name for identity authentication, obtains the user and experiment proposal information from the user management system through the card number, sends a metadata request to the experiment data management system, and constructs user information and roles. Figure 6 As shown, the data visualization module submits a plan to the queue server module through ZeroMQ and obtains the document stream. At the beginning of the plan, the experiment name, collection points and serial number are extracted from the run start document. As the plan is executed, the detector readings and current serial number are extracted from the event document, triggering the user interface drawing and progress bar refresh.

[0084] The beam line station synchronous data acquisition method of the present invention comprises the following steps:

[0085] Step 1: Power on the power modules of each acquisition chassis. After the computer module self-checks, it starts the EPICS IOC to receive control instructions from the host computer. After the timing module is powered on, it communicates with the timing unit to complete the time synchronization.

[0086] Step 2: The host computer sends the acquisition control parameters to the computer modules in each acquisition chassis through the network. After the computer module sends it to the interface module through the PCIE bus, it is forwarded to the FPGA controller in the data acquisition module through the SRIO switch to complete the initialization of the acquisition parameters.

[0087] Step 3: Prepare the host computer EPICS operating environment, including detector IOC application, motor IOC application and energy / wavelength-position conversion IOC application, and monitor the status of detectors and motors required for beamline station experiments under the EPICS architecture;

[0088] In this step, EPICS process variable conversion is provided according to the energy / wavelength-position correspondence. When assigning a value to the energy / wavelength process variable, it is directly converted to set the corresponding motor position process variable. When reading the motor position process variable, it is converted into the corresponding energy / wavelength process variable in real time.

[0089] Step 4: Configure the queue server module runtime engine startup script to start the runtime engine management service. When the runtime engine manager starts, it loads the signals and devices provided by the device abstraction module and the plan provided by the process abstraction module.

[0090] Step 5: User authentication. During the experiment, the user enters the card number and name for identity authentication. The user and experiment proposal information are obtained from the user management system through the card number, and a metadata request is sent to the experiment data management system to build user information and roles.

[0091] Step 6: The data visualization module executes the experimental process. Submit the experimental plan to the queue server module through the user interface, and each acquisition module starts working to package the collected experimental data and timestamps. The packaged experimental data is extracted through a data flow branch on the network and published to the data real-time display callback function through ZeroMQ. The data real-time display callback function obtains real-time data from it to trigger drawing and progress bar refresh; another data flow branch writes the experimental raw data and metadata in the experimental data into the data cache, and the running end document triggers the data export and storage function.

[0092] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.

Claims

1. A beamline station synchronous data acquisition device, characterized in that: Includes device control layer and application layer; The device control layer includes multiple acquisition boxes, a host computer, and a timing unit. The multiple acquisition boxes are respectively connected to the host computer, and the timing units are respectively connected to the timing modules in each acquisition box; The application layer includes a device abstraction module, a process abstraction module, a queue server module, a data storage module and a data visualization module; the device abstraction module is used to abstract the EPICS process variable information of the experimental device into a Python object, and multiple Python object signals form a device, which is configured and used as a unit, and after assigning names to the signals and devices, they are stored in the experimental metadata; The process abstraction module is used to abstract the experimental process into a plan; the queue server module is used for users to create and manage the plan queue and the plan execution environment, and autonomously execute the plan according to the experiment queue sequence in the plan queue; the data storage module is used to extract the experimental metadata from the run start document, and cache the event document of the entire experiment process, that is, to obtain the original data of the experiment, and then run the end document to trigger the data export and storage function; the data visualization module is used to manage the running engine environment of the queue server module, manage the plan queue, monitor the status of the EPICS process variable information, and display the data curve in real time.

2. A beamline station synchronous data acquisition device according to claim 1, characterized in that: The input / output controller IOC application includes a detector IOC application, a motor IOC application, and an energy / wavelength-position conversion IOC application.

3. A beamline station synchronous data acquisition device according to claim 2, characterized in that: The acquisition chassis is provided with a power module, a computer module, a timing module, a data acquisition module and an interface module. The power module, the computer module, the timing module, the data acquisition module and the interface module are all arranged on the 3U chassis backplane through VPX slots and are interconnected through a backplane bus.

4. A beamline station synchronous data acquisition device according to claim 3, characterized in that: The interface module includes a first voltage conversion circuit, an SRIO switch, a first FPGA controller and a first FLASH memory; the SRIO switch and the first FLASH memory are both connected to the first FPGA controller, and the first voltage conversion circuit is used to power the SRIO switch, the first FPGA controller and the first FLASH memory.

5. The beamline station synchronous data acquisition device according to claim 3, characterized in that: The data acquisition module includes a second voltage conversion circuit, a second FPGA controller, a second FLASH memory, an A / D conversion circuit and a pulse acquisition unit; the second FLASH memory and the A / D conversion circuit are both connected to the second FPGA controller, the pulse acquisition unit provides a DB15 male connector and a DB15 female connector to the outside for external input and output of 5V TTL signals, the A / D conversion circuit is installed on the data acquisition module to provide 4-way SMA input, and the second voltage conversion circuit is used to power the second FPGA controller, the second FLASH memory, the A / D conversion circuit and the pulse acquisition unit.

6. The beamline station synchronous data acquisition device according to claim 3, characterized in that: The timing module includes a third voltage conversion circuit, an SFP optical module, a third FPGA controller and a third FLASH memory; The third FLASH memory and the SFP optical module are both connected to the FPGA controller, and the third voltage conversion circuit is used to supply power to the SFP optical module, the third FPGA controller and the third FLASH memory.

7. The beamline station synchronous data acquisition device according to claim 1, characterized in that: In the data storage module, the experimental metadata is exported in JSON format, and the experimental raw data is exported in HDF5 and CSV formats.

8. A beamline station synchronous data acquisition method, characterized in that: The method is used to realize the data acquisition synchronization of a beam line station by using the beam line station synchronization data acquisition device as described in any one of claims 3 to 7, comprising the following steps: Step S1: Power on and time synchronization Power on the power modules of each acquisition chassis. After the computer module self-checks, it starts the EPICS IOC to receive control instructions from the host computer. After the timing module is powered on, it communicates with the timing unit to complete the time synchronization. Step S2: Initialization of acquisition parameters The host computer sends the acquisition control parameters to the computer modules in each acquisition chassis through the network, and then the computer modules send them to the interface module through the PCIE bus, and then forward them to the FPGA controller in the data acquisition module through the SRIO switch to complete the initialization of the acquisition parameters; Step S3: Prepare the operating environment Prepare the host computer EPICS operating environment, including detector IOC application, motor IOC application and energy / wavelength-position conversion IOC application, and monitor the status of detectors and motors required for beamline station experiments under the EPICS architecture; Step S4: Run the engine management service to start Configure the queue server module runtime engine startup script and start the runtime engine management service; Step S5: User Authentication During the experiment, the user enters the card number and name for identity authentication, obtains the user and experiment proposal information from the user management system through the card number, sends a metadata request to the experiment data management system, and constructs user information and roles; Step S6: Data visualization module executes the experimental process Submit the experimental plan to the queue server module through the user interface, and each acquisition module starts working to package the collected experimental data and timestamps. The packaged experimental data is extracted through a data flow branch and published to the data real-time display callback function through ZeroMQ. The data real-time display callback function obtains real-time data from it to trigger drawing and progress bar refresh; another data flow branch writes the experimental original data and metadata in the experimental data into the data cache, and the running end document triggers the data export and storage function.

9. A beamline station synchronous data acquisition method according to claim 8, characterized in that: In step S3, EPICS process variable conversion is provided according to the energy / wavelength-position correspondence, and when assigning a value to the energy / wavelength process variable, it is directly converted into setting the corresponding motor position process variable, and when reading the motor position process variable, it is converted into the corresponding energy / wavelength process variable in real time.

10. A beamline station synchronous data acquisition method according to claim 8, characterized in that: In step S4, when the runtime engine management service is started, the Python object signals and devices provided by the device abstraction module and the plan provided by the process abstraction module are loaded.

Images