Telescope network collaborative observation planning system for target sky areas

By designing a telescope network collaborative observation planning system and rationally scheduling the observation targets in the telescope network, the problem of poor positioning of gravitational wave detector networks was solved, and the observation efficiency and the probability of discovering electromagnetic counterparts of gravitational waves were improved.

CN117706649BActive Publication Date: 2026-11-17NAT ASTRONOMICAL OBSERVATORIES CHINESE ACAD OF SCI
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311559490.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-21
Publication Date
2026-11-17
Estimated Expiration
2043-11-21

AI Technical Summary

Technical Problem

In existing technologies, the positioning accuracy of gravitational wave detector networks is poor, making it difficult to plan collaborative observations with large sky telescopes and thus hindering the discovery of electromagnetic counterparts of gravitational waves.

Method used

A telescope network collaborative observation planning system for a target sky area is provided, including a client, a processing module and a server. By running a telescope network collaborative observation planning algorithm, the system can rationally schedule the observation targets of different telescopes in the telescope network and optimize the observation capabilities.

Benefits of technology

This improved the observation efficiency of the telescope network, increased the probability of discovering electromagnetic counterparts of gravitational waves, and optimized the observation planning of the telescope network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117706649B_ABST
    Figure CN117706649B_ABST
Patent Text Reader

Abstract

This disclosure provides a collaborative observation planning system for a telescope network targeting a specific sky region. The system includes: a client, a processing module, and a server; the client is used to display first data information on a user interface, the first data information including one or more of the following: location information of a gravitational wave event, target host galaxy information, and observation information from each telescope matched with the telescope network; the processing module is used to receive the gravitational wave event, acquire alarm information corresponding to the gravitational wave event, and process the alarm information to obtain an observation planning result, the observation planning result including the observation information from each telescope; the server is used to store second data information, the second data information including the observation planning result generated by the processing module, the observation planning result being used to obtain the first data information. This disclosure also provides a data processing method, apparatus, device, and storage medium.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of telescope observation technology, and more specifically to a telescope network collaborative observation planning system, data processing method, apparatus, electronic equipment, and storage medium for a target sky region. Background Technology

[0002] Currently, the LIGO / Virgo Collaboration (LVC), consisting of the Advanced Laser Interferometer Gravitational-Wave Observatory (aLIGO) and the Virgo interferometer, is conducting a new round of gravitational wave signal searches. After detecting a gravitational wave signal, timely follow-up observations in the electromagnetic band to find its electromagnetic counterpart are crucial for studying gravitational wave events and their physical properties. However, the current gravitational wave detector network has poor localization accuracy, with the obtained probabilistic localization areas often ranging from hundreds to thousands of square degrees. How to plan coordinated telescope observations over large areas to improve the probability of discovering gravitational wave electromagnetic counterparts is a significant problem to be solved in gravitational wave follow-up observations. Besides gravitational wave events, the localization error of some gamma-ray burst event alarms can also reach hundreds of square degrees. Observing the afterglow of these gamma-ray burst events also requires coordinated observation planning through telescope networks.

[0003] Currently, the search methods for electromagnetic counterparts following gravitational waves are mainly divided into sky survey strategies for telescopes with wide field of view (greater than 1 square degree) and galaxy-targeting observations for telescopes with narrow field of view. The sky survey strategy divides the gravitational wave location area into observation grids identical to the telescope's field of view, and then surveys these grids in order to discover electromagnetic counterparts. The basic idea of ​​the galaxy-targeting observation strategy is that gravitational wave events occur in or near galaxies. The basic method is based on Bayesian inference, which involves matching the three-dimensional gravitational wave cumulative probability location area with known catalogs of nearby galaxies to calculate the probability that each galaxy is the host galaxy of the gravitational wave event, and then sorting them according to probability to obtain a list of galaxies to be observed.

[0004] Due to the limited observation capabilities of a single telescope, the current mainstream observation method involves multiple telescopes forming a telescope network, with each telescope observing a specific portion of the sky. How to rationally allocate the observation targets of different telescopes within the network to maximize their observational capabilities is a problem that needs to be solved. Summary of the Invention

[0005] In view of the above problems, this disclosure provides a telescope network collaborative observation planning system, data processing method, apparatus, electronic equipment and storage medium for a target sky area.

[0006] According to a first aspect of this disclosure, a telescope network collaborative observation planning system for a target sky region is provided. The system includes: a client, a processing module, and a server. The client is configured to display first data information on a user interface, the first data information including one or more of the following: location sky region information of a gravitational wave event, target host galaxy information, and observation information of each telescope matched with the telescope network; wherein the telescope network consists of multiple telescopes, each of which is used to observe a portion of the sky region located within the target sky region; the processing module is configured to receive a gravitational wave event, acquire alarm information corresponding to the gravitational wave event, and process the alarm information to obtain an observation planning result, the observation planning result including the observation information of each telescope; the server is configured to store second data information, the second data information including the observation planning result generated by the processing module, the observation planning result being used to obtain the first data information.

[0007] According to embodiments of this disclosure, the client is also used to display third data information on the user interface, the third data information including star catalog data and celestial position information.

[0008] According to an embodiment of this disclosure, the client is further configured to send a request to the server; and after sending the request, receive fourth data information returned according to the request, the fourth data information being used to obtain the first data information or the third data information; wherein, the fourth data information includes one or more of the location data of the gravitational wave event, the observation planning result, and the galaxy list data, the galaxy list data being used to obtain the target host galaxy information.

[0009] According to embodiments of this disclosure, the second data information stored on the server further includes: alarm information for the gravitational wave event, location sky area information, host galaxy information, and parameter information for each telescope.

[0010] According to embodiments of this disclosure, the processing module is further configured to send the observation planning results to the receiving end corresponding to each telescope.

[0011] According to a second aspect of this disclosure, a data processing method is provided, applied to a processing module of a telescope network collaborative observation planning system for a target sky region. The method includes: in response to receiving a gravitational wave event, acquiring alarm information corresponding to the gravitational wave event; running a telescope network collaborative observation planning algorithm based on the location sky region information in the alarm information to obtain observation information of each telescope; and determining the observation planning result based on the observation information of each telescope.

[0012] According to embodiments of this disclosure, the step of running a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain the observation information of each telescope includes: running a single telescope observation planning algorithm sequentially for each telescope according to the pre-configured priority of each telescope to obtain the observation information corresponding to each telescope, until all telescopes in each telescope have finished running, and obtaining the observation information of each telescope; wherein, the single telescope observation planning algorithm includes: calculating the visibility of the telescope target grid, initializing the candidate grid list as a visible grid list; selecting a grid located in the gravitational wave event location sky area as a target grid according to the visible grid list; determining an usable observation time period for each observation grid in the target grid within the observable time period, so as to perform telescope observations according to the usable observation time period.

[0013] A third aspect of this disclosure provides a data processing apparatus, comprising: a first acquisition module, configured to acquire alarm information corresponding to a gravitational wave event in response to receiving such an event; a second acquisition module, configured to run a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain observation information of each telescope; and a determination module, configured to determine the observation planning result based on the observation information of each telescope.

[0014] A fourth aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the methods disclosed above.

[0015] A fifth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the methods disclosed above. Attached Figure Description

[0016] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 This illustration schematically shows a telescope network collaborative observation planning system for a target sky area according to an embodiment of the present disclosure;

[0018] Figure 2 A flowchart illustrating a data processing method according to an embodiment of the present disclosure is shown schematically.

[0019] Figure 3 A schematic block diagram of a data processing apparatus according to embodiments of the present disclosure is shown; and

[0020] Figure 4 A block diagram schematically illustrates an electronic device suitable for implementing a data processing method according to an embodiment of the present disclosure. Detailed Implementation

[0021] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0022] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0023] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0024] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0025] Figure 1 A schematic diagram illustrates a telescope network collaborative observation planning system for a target sky region according to an embodiment of the present disclosure, such as... Figure 1 As shown, the system 100 of this embodiment includes a client 110, a processing module 120, and a server 130.

[0026] Client 110 is used to display first data information on a user interface. The first data information includes one or more of the following: the location sky region information of the gravitational wave event, the target host galaxy information, and the observation information of each telescope matched with the telescope network. The telescope network consists of multiple telescopes, and each of the multiple telescopes is used to observe a portion of the sky region located within the target sky region. Processing module 120 is used to receive the gravitational wave event, obtain the alarm information corresponding to the gravitational wave event, and process the alarm information to obtain the observation planning result. The observation planning result includes the observation information of each telescope. Server 130 is used to store second data information, which includes the observation planning result generated by processing module 120. The observation planning result is used to obtain the first data information.

[0027] In some embodiments, the client 110 is also used to display third data information on the user interface, the third data information including star catalog data and celestial position information.

[0028] In some embodiments, the client 110 is further configured to send a request to the server 130; and after sending the request, to receive fourth data information returned according to the request, the fourth data information being used to obtain the first data information or the third data information; wherein the fourth data information includes one or more of the location data of the gravitational wave event, the observation planning results, and the galaxy list data, the galaxy list data being used to obtain the target host galaxy information.

[0029] For example, client 110 can use a single-page web application built with Vue.js and Aladin Lite to intuitively display one or more of the following: the location of the gravitational wave event, the target host galaxy, and observation information from various telescopes matched with the telescope network. For instance, it can display the location of the gravitational wave event, candidate host galaxies, and observation plans from different telescopes. Vue.js is a JavaScript framework for building user interfaces, providing a declarative, component-based programming model for efficient user interface development. Aladin Lite, developed by the Centre de Données astronomiques de Strasbourg (CDS), is an astronomical data visualization tool based on WebGL (Web Graphics Library). WebGL is a web graphics technology based on JavaScript and graphics processing units (GPUs) that can render complex 3D graphics and visual effects on web pages in real time. Aladin Lite utilizes WebGL technology to load and display sky images (i.e., the location of the gravitational wave event), star catalog data, and celestial object positions, allowing users to zoom, pan, and select specific celestial objects. Aladin Lite supports various astronomical data formats and protocols, such as FITS and VO, and also provides APIs for developers to perform advanced customization functions such as custom visualization targets, custom visualization content, and custom interactive operations. For example, client 110 can request the API provided by server 130 to obtain the location data of gravitational wave events, the planning result data obtained from the observation planning algorithm of the wide-field telescope, and the galaxy list data sorted by priority obtained from the galaxy screening method. Through Aladin Lite, the location of gravitational wave events on the celestial sphere and the location information for observation planning can be intuitively visualized, and the observation time, exposure time, number of exposures, and cumulative coverage probability of the observed sky area can be displayed in a table.

[0030] In some embodiments, the second data information stored by the server 130 further includes: alarm information for gravitational wave events, location information for the sky region, host galaxy information, and parameter information for each telescope.

[0031] For example, the database backend could be an application programming interface (API) service built using the Flask framework. Flask is a lightweight web framework written in Python that provides a series of modules and third-party plugins for rapid web application development. It is understood that server 130 includes a database. The database backend service in this disclosure provides a series of application programming interfaces (APIs) based on the Hypertext Transfer Protocol (HTTP) and uses JavaScript Object Notation (JSON) as the data format for data transmission, reducing the coupling between the frontend and backend services. This system can use a PostgreSQL database to store data such as the observation planning results generated by the processing module 120, information about the gravitational wave alarm itself (e.g., alarm information for gravitational wave events), the given location sky map (e.g., location sky information), the list of candidate galaxies within the location sky region of the gravitational wave event obtained by the galaxy screening method (e.g., host galaxy information), and parameter information of each telescope.

[0032] It is understandable that the processing module 120 is primarily responsible for obtaining alarm information corresponding to the detected gravitational wave events. It then calculates the observation planning results from the alarm information and uploads these results to the database of the server 130 for archiving. The observation planning algorithms for wide-field telescopes and the joint observation planning algorithm for wide-field telescope networks both run in the processing module 120.

[0033] In some embodiments, the processing module 120 is further configured to send the observation planning results to the receiving end corresponding to each telescope.

[0034] For example, the processing module 120 can automatically send observation plans (such as observation planning results) to the telescope station and send email notifications to telescope staff via message queues and mail servers.

[0035] The telescope network collaborative observation planning system for the target sky region provided in this embodiment can obtain the observation planning results through the processing module, which is beneficial for each telescope to work according to the observation planning results. For example, it can observe a part of the sky region located in the target sky region based on the observation planning results, thereby realizing the reasonable scheduling of the target observed by different telescopes in the telescope network and optimizing its observation capabilities.

[0036] Embodiments of this disclosure also provide a data processing method and apparatus, which, in response to receiving a gravitational wave event, acquire alarm information corresponding to the gravitational wave event; run a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain the observation information of each telescope; and determine the observation planning result based on the observation information of each telescope.

[0037] The data processing method of this disclosure can be applied to the processing module of a telescope network collaborative observation planning system for a target sky region. Figure 2 The data processing method 200 of the disclosed embodiments will be described in detail.

[0038] Figure 2 A flowchart illustrating a data processing method according to an embodiment of this disclosure is shown schematically. Figure 2 As shown, this embodiment includes operations S210 to S230.

[0039] In operation S210, in response to receiving a gravitational wave event, alarm information corresponding to the gravitational wave event is acquired.

[0040] During operation S220, based on the location sky area information in the alarm message, the telescope network collaborative observation planning algorithm is run to obtain the observation information of each telescope.

[0041] In some embodiments, based on the location sky area information in the alarm information, a telescope network collaborative observation planning algorithm is run to obtain the observation information of each telescope. This includes: according to the pre-configured priority of each telescope, a single telescope observation planning algorithm is run sequentially for each telescope to obtain the observation information corresponding to each telescope, until all telescopes in each telescope have finished running, and the observation information of each telescope is obtained. The single telescope observation planning algorithm includes: calculating the visibility of the telescope target grid and initializing the candidate grid list as the visible grid list; selecting the grid located in the gravitational wave event location sky area as the target grid according to the visible grid list; and determining an usable observation time period for each observation grid in the target grid within the observable time period, so as to perform telescope observations according to the usable observation time period.

[0042] When operating S230, the observation planning results are determined based on the observation information from each telescope.

[0043] For example, the system continuously monitors gravitational wave event alerts sent by LVC through the General Coordinates Network (GCN) to obtain alert information. On one hand, the system can analyze the type of gravitational wave alert information and send alert emails to the observation team. On the other hand, it can run a telescope network collaborative observation planning algorithm based on the location sky area information in the alert information to obtain the observation information of each telescope.

[0044] It can be understood that the location sky region is the same as the target sky region. The location sky region is stored in the FITS file as a HEALPix (Hierarchical EqualArea isoLatitude Pixelation) all-sky image, consisting of the posterior probability distribution of candidate events on the celestial sphere and luminosity distance (only for CBC candidate events). HEALPix is ​​a widely used spherical uniform pixelation scheme in astronomy. HEALPix divides the spherical surface into a series of equal-area regions, called pixels, each with a unique number for easy indexing and processing. In the FITS file of the location sky region, each pixel corresponds to a posterior probability value, representing the posterior probability that a gravitational wave event occurs in the sky region corresponding to that pixel.

[0045] First, the system needs to obtain the telescope's survey template file in advance. For telescopes without a template file, the system generates a survey template file based on its field of view. After obtaining the telescope's survey template file, the system calculates the correspondence between the survey grid and HEALPix pixels to pre-calculate the sky region positions corresponding to the survey grid.

[0046] Due to the limitations of ground-based telescopes, the visibility of the telescope's target grid must be calculated to obtain the observable target grid under actual conditions. The system uses the astroplan package to calculate the visibility and observable time range of the target grid. astroplan is an open-source library developed in Python for astronomical observation planning and visibility prediction. By setting the telescope's longitude, latitude, and altitude, the visibility of a given celestial position at a given time at the telescope's location can be calculated. In this system, the observable time range can be set to the time range when the sun is 12 degrees below the horizon, with an altitude limit added by the telescope's configured minimum visible altitude angle. The system also dynamically adds distance limits between the observed target and the moon under different lunar phases, taking into account the impact of different lunar phases. Using the astroplan package, the system can calculate the visibility and observable time range of the current telescope's template grid for the next visible night. The next step is to select grids located within the celestial region for locating gravitational wave candidate events from the visible template grid for planned observations.

[0047] This system selects target grids by using cumulative probability layers to ensure that the selected target grids are clustered together. A cumulative probability layer is defined as follows: after sorting the posterior probabilities of the target sky region from high to low, a 5% cumulative posterior probability is calculated as one layer, and the HEALPix pixel indexes contained in each layer are obtained. Then, the system traverses layer by layer according to priority. For each layer's sky region, the system iterates through the grids in the unassigned grid list. Initially, the unassigned list contains all observable template grids for the current telescope. If the grid's center coordinates are within the sky region of that layer, the grid is added to the candidate observation grid list and removed from the unassigned grid list. If the grid's center coordinates are not within the sky region of that layer, but the corresponding sky region partially overlaps with that layer's sky region, the layer is added to the next layer's priority traversal grid list and removed from the unassigned grid list. When the current cumulative probability layer is traversed and preparation is made to traverse the next layer, the priority traversal grid list obtained from the current layer is added to the front of the unassigned grids, and the priority traversal grid list is cleared. After iterating through all the cumulative probability layers, the system obtains a list of telescope-visible observation grids sorted by priority from high to low.

[0048] After obtaining the observable priority observation grids, the next step is to select a usable observation time segment within the observable time period for each of the candidate observation grids. For each observation target, the telescope itself is configured with exposure time and exposure counts. This system can divide the entire visible night observation time into several equal time slices according to the telescope's configured exposure time and exposure counts, and configure all time slices as usable time slices. Next, the candidate observation grid list is traversed from high to low priority. When traversing to the current grid, the time slices within the visible time range of the current grid are calculated. The first unoccupied time slice is found, marked as occupied, and the observation time of that time slice is allocated to the current grid. If no unoccupied time slice is found, the grid is skipped.

[0049] To better understand the single-telescope observation planning algorithm of the present invention, the content of the single-telescope observation planning algorithm is further explained below with reference to the embodiments, but the present invention is not limited to the following embodiments.

[0050] For example, S1 calculates the visibility of the telescope template network and initializes the candidate network list as the visible network list.

[0051] S2. Traverse the location areas of gravitational wave events in layers from high to low probability.

[0052] S3. Determine whether to traverse all probability layers.

[0053] S4. If yes, return the list of time grids to be assigned.

[0054] S5. If not, iterate through the candidate grid list.

[0055] S6. Determine whether there are any untraversed grids among the candidate grids.

[0056] S7. If not, update the candidate grid to the priority traversal grid list + the normal traversal grid list, and return to S3.

[0057] S8. If yes, determine whether the entire area of ​​the current grid is located in the current cumulative probability layer.

[0058] S9. If so, add the current network to the list of time grids to be assigned.

[0059] S10. If not, determine whether the current grid is partially located in the current cumulative probability layer.

[0060] S11. If yes, add the current network to the priority traversal grid list and return to S6.

[0061] S12. If not, add the current network to the list of normal traversal grids and return to S6.

[0062] The above steps are for the observation planning algorithm of a single telescope. Compared with the single telescope observation planning algorithm, the telescope network collaborative observation planning algorithm can take into account the overlap of observations by different telescopes, and one telescope should try to avoid observing the area that another telescope has already planned to observe.

[0063] For example, firstly, the system determines the priority of telescope allocation based on their field of view, prioritizing those with larger fields of view for observation planning. Simultaneously, global variables are initialized to record the allocated sky areas, with initial values ​​of empty. Then, a single-telescope observation planning algorithm is performed on each telescope in the telescope network according to their priority. When calculating observable grids, in addition to the aforementioned observation restrictions, a comparison is added with the globally recorded allocated sky area variables. When 80% of a grid's sky area has been observed by other telescopes, that grid is added to the invisible list. The remaining steps are the same as the single-telescope observation planning algorithm. After obtaining the observation planning result for that telescope, the globally allocated sky area variables are updated, and the current telescope's observation planning result is recorded. After planning for all telescopes, the joint observation planning result for all telescopes in the telescope network is obtained.

[0064] To better understand the telescope network cooperative observation planning algorithm of the present invention, the content of the telescope network cooperative observation planning algorithm is further explained below with reference to the embodiments, but the present invention is not limited to the following embodiments.

[0065] For example, S1, prioritize the telescopes in the telescope network according to their field of view size.

[0066] S2. Initialize the global traversal of the observed sky area, with an initial value of empty.

[0067] S3. Traverse the telescopes according to priority and run the single telescope planning algorithm.

[0068] S4. Determine if there is another telescope that has not been planned for observation.

[0069] S5. If not, obtain the observation planning results for the telescope network.

[0070] S6. In the case of yes, calculate the telescope template network visibility by traversing the globally allocated sky regions and the current inherent telescope configuration.

[0071] S7. Continue running the single-telescope observation planning algorithm.

[0072] S8. Update the global planned sky area variables, record the current telescope planning results, and return to S4.

[0073] The data processing method provided in this embodiment can perform collaborative observation planning for various telescopes in the network after receiving a gravitational wave alarm event. The observation planning results make it easier for users to view the observation area and help increase the probability of observing the electromagnetic counterpart of gravitational waves.

[0074] Figure 3 A schematic block diagram of a data processing apparatus according to an embodiment of the present disclosure is shown.

[0075] like Figure 3 As shown, the data processing device 300 of this embodiment includes a first acquisition module 310, a second acquisition module 320, and a determination module 330.

[0076] The first acquisition module 310 is used to acquire alarm information corresponding to the gravitational wave event in response to receiving the gravitational wave event;

[0077] The second acquisition module 320 is used to run a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain the observation information of each telescope; and

[0078] The determination module 330 is used to determine the observation planning results based on the observation information of each telescope.

[0079] According to embodiments of this disclosure, any plurality of modules among the first obtaining module 310, the second obtaining module 320, and the determining module 330 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the first obtaining module 310, the second obtaining module 320, and the determining module 330 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the first obtaining module 310, the second obtaining module 320, and the determining module 330 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0080] Figure 4 A block diagram of an electronic device suitable for implementing a number of data processing methods according to embodiments of the present disclosure is shown schematically.

[0081] like Figure 4 As shown, an electronic device 400 according to an embodiment of the present disclosure includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage portion 408 into a random access memory (RAM) 403. The processor 401 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 401 may also include onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0082] RAM 403 stores various programs and data required for the operation of electronic device 400. Processor 401, ROM 402, and RAM 403 are interconnected via bus 404. Processor 401 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 402 and / or RAM 403. It should be noted that the programs may also be stored in one or more memories other than ROM 402 and RAM 403. Processor 401 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0083] According to embodiments of this disclosure, the electronic device 400 may further include an input / output (I / O) interface 405, which is also connected to a bus 404. The electronic device 400 may also include one or more of the following components connected to the I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 410 as needed so that computer programs read from it can be installed into the storage section 408 as needed.

[0084] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0085] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 402 and / or RAM 403 and / or one or more memories other than ROM 402 and RAM 403 described above.

[0086] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the data processing methods provided in the embodiments of this disclosure.

[0087] When the computer program is executed by the processor 401, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0088] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via communication section 409, and / or installed from removable medium 411. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0089] In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by processor 401, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0090] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0091] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0092] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0093] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A telescope network collaborative observation planning system for a target sky region, the system comprising: Client, processing module, and server; The client is used to display first data information on a user interface. The first data information includes one or more of the following: the location sky region information of the gravitational wave event, the target host galaxy information, and the observation information of each telescope matched with the telescope network; wherein, the telescope network consists of multiple telescopes, and each of the multiple telescopes is used to observe a portion of the sky region located within the target sky region. The processing module is used to receive gravitational wave events, obtain alarm information corresponding to the gravitational wave events, process the alarm information to obtain observation planning results, and the observation planning results include the observation information of each telescope. The server is used to store second data information, which includes the observation planning result generated by the processing module, and the observation planning result is used to obtain the first data information. The processing module is further configured to: Based on the pre-configured priority of each telescope, the single telescope observation planning algorithm is run sequentially for each telescope to obtain the observation information corresponding to each telescope, until all telescopes in each telescope have finished running, and the observation information of each telescope is obtained. The single-telescope observation planning algorithm includes: Calculate the visibility of the telescope target grid and initialize the candidate grid list as the visible grid list; Select the grid located within the sky region for locating the gravitational wave event from the visible grid list as the target grid; For each observation grid in the target grid, a usable observation period is determined within the observable time period, and telescope observations are performed based on the usable observation period.

2. The system according to claim 1, wherein, The client is also used to display third data information on the user interface, which includes star catalog data and celestial position information.

3. The system according to claim 2, wherein, The client is also used to send requests to the server; as well as After sending the request, receive fourth data information returned according to the request, the fourth data information being used to obtain the first data information or the third data information; The fourth data information includes one or more of the following: location data of the gravitational wave event, the observation planning results, and galaxy list data. The galaxy list data is used to obtain information about the target host galaxy.

4. The system according to claim 1, wherein, The second data information stored on the server also includes: alarm information for the gravitational wave event, location information for the sky region, host galaxy information, and parameter information for each telescope.

5. The system according to claim 1, wherein, The processing module is also used to send the observation planning results to the receiving end corresponding to each telescope.

6. A data processing method, said method being applied to the processing module of a telescope network collaborative observation planning system for a target sky region, said method comprising: In response to receiving a gravitational wave event, acquire alarm information corresponding to the gravitational wave event; Based on the location sky area information in the alarm information, run the telescope network collaborative observation planning algorithm to obtain the observation information of each telescope; as well as The observation planning results are determined based on the observation information of each telescope; wherein, the step of running a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain the observation information of each telescope includes: Based on the pre-configured priority of each telescope, the single telescope observation planning algorithm is run sequentially for each telescope to obtain the observation information corresponding to each telescope, until all telescopes in each telescope have finished running, and the observation information of each telescope is obtained. The single-telescope observation planning algorithm includes: Calculate the visibility of the telescope target grid and initialize the candidate grid list as the visible grid list; Select the grid located within the sky region for locating the gravitational wave event from the visible grid list as the target grid; For each observation grid in the target grid, a usable observation period is determined within the observable time period, and telescope observations are performed based on the usable observation period.

7. A data processing apparatus, comprising: The first acquisition module is used to acquire alarm information corresponding to the gravitational wave event in response to receiving the gravitational wave event; The second acquisition module is used to run a telescope network collaborative observation planning algorithm based on the location sky area information in the alarm information to obtain the observation information of each telescope; as well as The determination module is used to determine the observation planning results based on the observation information of each telescope; The second obtaining module is further configured to perform the following operations: Based on the pre-configured priority of each telescope, the single telescope observation planning algorithm is run sequentially for each telescope to obtain the observation information corresponding to each telescope, until all telescopes in each telescope have finished running, and the observation information of each telescope is obtained. The single-telescope observation planning algorithm includes: Calculate the visibility of the telescope target grid and initialize the candidate grid list as the visible grid list; Select the grid located within the sky region for locating the gravitational wave event from the visible grid list as the target grid; For each observation grid in the target grid, a usable observation period is determined within the observable time period, and telescope observations are performed based on the usable observation period.

8. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to claim 6.

9. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to claim 6.

Citation Information

Patent Citations

  • Astronomical telescope network collaborative observation method based on four-layer structure

    CN102571824A

  • Telescope control device, system and method, storage medium, program and application

    CN111538149A