Genome file data processing method and apparatus, device, and storage medium
By splitting the genome files into units of genetic units and writing them to the library, the problem of slow loading of gene editing software tools when processing large genome files is solved, and fast and efficient genome file loading and editing is achieved, avoiding system crashes. risk.
Patent Information
- Application Number
- PCT/CN2023/093816
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-21
AI Technical Summary
Traditional gene editing software tools are slow to load when processing larger genome files, which are prone to lag or system crashes.
The genome file is divided into genetic unit sequences in units specified by the designated genetic unit and written into the genetic unit library to load and display one or more genetic units as needed to avoid the same genetic unit being divided into different data blocks. This ensures the integrity of the genetic unit.
It improves the loading speed of genomic files, ensures that gene editing software tools can quickly and efficiently browse and edit smaller or larger genomic files, avoiding the risk of system crashes.
Smart Images

Figure CN2023093816_21112024_PF_FP_ABST
Abstract
Description
Data processing method, device, equipment and storage medium for genome files Technical Field
[0001] This specification relates to the field of synthetic biology research technology, and in particular to a data processing method, device, equipment and storage medium for genome files. Background Art
[0002] Synthetic biology is a field that combines the principles of molecular biology, systems biology, and engineering. It uses DNA synthesis, DNA assembly, gene editing, and other technical means to arrange and combine genetic elements in a building block-like manner (similar to integrated circuit design) to synthesize biological components (such as cells or organisms) with specific functions for use in biomedicine, agriculture, food, chemistry, and energy. Before conducting synthetic biology experiments on physical entities, it is generally necessary to use gene editing software tools for simulation design and simulation experiments. Currently, traditional gene editing software tools can perform visual editing of smaller genome files (such as microorganisms, yeast, etc.); however, when the genome files are large, the gene editing software tools load slowly, and are prone to freezes or even system crashes.
[0003] Summary of the Invention
[0004] The purpose of the embodiments of this specification is to provide a method, apparatus, device, and storage medium for processing genome file data to increase the speed of loading genome files.
[0005] To achieve the above objectives, on the one hand, embodiments of this specification provide a method for processing genome file data, comprising:
[0006] Split the genome file into genetic unit sequences based on the specified genetic unit and write them into the genetic unit library;
[0007] receiving a selection operation for one or more genetic units in the genetic unit sequence;
[0008] Reading corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence;
[0009] The genetic unit subsequences are displayed.
[0010] In the data processing method of the genome file of the embodiment of this specification, the designated genetic unit includes a chromosome.
[0011] In the data processing method of the genome file of the embodiment of this specification, the dividing of the genome file into genetic unit sequences based on designated genetic units includes:
[0012] Obtain the file name suffix of the genome file;
[0013] confirming whether the genome file is in a target format according to the file name suffix; and converting the genome file into a target format when the genome file is not in a target format;
[0014] Identify all target tags in the genome file content after conversion to the target format.
[0015] In the data processing method of the genome file of the embodiment of this specification, the target mark includes a double slash mark.
[0016] In the genome file data processing method of the embodiment of this specification, the identifying of all target markers in the genome file content includes:
[0017] confirming whether the genome file is in a target format; and converting the genome file into a target format when the genome file is not in a target format;
[0018] Identify all target tags in the genome file content after conversion to the target format.
[0019] In the data processing method of the genome file of the embodiment of this specification, the displaying of the genetic unit subsequence includes:
[0020] Based on the attributes and status of the object, determining whether the genetic unit subsequence has the same object as the currently displayed page;
[0021] If the same object exists, rendering the objects in the genetic unit subsequence except the same object;
[0022] If no identical objects exist, all objects in the genetic unit subsequence are rendered.
[0023] The data processing method of the genome file in the embodiment of this specification further includes:
[0024] receiving an editing operation for a currently displayed genetic unit subsequence;
[0025] The operation result of the editing operation is dynamically displayed, and the genetic unit library is updated according to the operation result.
[0026] The data processing method of the genome file in the embodiment of this specification further includes:
[0027] Receive genetic unit read requests sent by the downstream system through the corresponding interface;
[0028] Reading a target genetic unit from the genetic unit library;
[0029] The target genetic unit is converted into a target file suitable for processing by the downstream system, and provided to the downstream system for processing through the interface.
[0030] On the other hand, the embodiments of this specification further provide a data processing device for a genome file, comprising:
[0031] The segmentation module is used to segment the genome file into genetic unit sequences based on the specified genetic unit and write them into the genetic unit library;
[0032] A receiving module, configured to receive a selection operation for one or more genetic units in the genetic unit sequence;
[0033] a reading module, configured to read corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence;
[0034] A display module is used to display the genetic unit subsequence.
[0035] On the other hand, an embodiment of this specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, wherein the computer program executes instructions of the above method when executed by the processor.
[0036] On the other hand, an embodiment of this specification further provides a computer storage medium having a computer program stored thereon, wherein the computer program executes the instructions of the above method when executed by a processor of a computer device.
[0037] On the other hand, an embodiment of this specification further provides a computer program product, which includes a computer program. When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the above method.
[0038] As can be seen from the technical solutions provided in the embodiments of this specification, the embodiments of this specification can pre-segment a genome file into a sequence of genetic units based on specified genetic units and write them into a genetic unit library. When a selection operation is received for one or more genetic units in the genetic unit sequence, the corresponding genetic units can be read from the genetic unit library according to the selection operation and loaded for display. In this way, compared with loading the entire genome file, loading and displaying one or more genetic units on demand is faster and more efficient. Moreover, because the genome file is segmented by genetic unit, it can also prevent the same genetic unit from being segmented into different data blocks, thereby ensuring the integrity of the genetic units and facilitating subsequent browsing and editing. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some of the embodiments described in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:
[0040] FIG1 shows a schematic diagram of a data processing application scenario for genome files in some embodiments of this specification;
[0041] FIG2 shows a flow chart of a method for processing genome file data in some embodiments of this specification;
[0042] FIG3 shows a flow chart of segmenting genome files in the embodiment shown in FIG2 ;
[0043] FIG4 shows a flow chart of a method for processing genome file data in other embodiments of this specification;
[0044] FIG5 is a schematic diagram showing a data processing process of a genome file in an exemplary embodiment of this specification;
[0045] FIG6 shows a structural block diagram of a data processing device for group files in some embodiments of this specification;
[0046] FIG7 shows a structural block diagram of a computer device in some embodiments of this specification.
[0047] [Explanation of the accompanying drawings] 61. Slicing module; 62. Receiving module; 63. Reading module; 64. Display module; 702. Computer device; 704. Processor; 706. Memory; 708. Driving mechanism; 710. Input / output interface; 712. Input device; 714. Output device; 716. Presentation device; 718. Graphical user interface; 720. Network interface; 722. Communication link; 724. Communication bus. DETAILED DESCRIPTION
[0048] To help those skilled in the art better understand the technical solutions in this specification, the following will provide a clear and complete description of the technical solutions in the embodiments of this specification, in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. All other embodiments derived by those skilled in the art based on the embodiments in this specification without creative effort shall fall within the scope of protection of this specification.
[0049] In the field of synthetic biology research, a genome is the sum of the genetic material of a given organism, and a genome file is an electronic medium that records genome information; therefore, the amount of data in a genome file is generally relatively large. When the genome file is large, the gene editing software tool loads the genome file slowly, which can lead to problems such as long loading time, loading freeze, and even system crashes. In view of this, in order to increase the loading speed of the genome file, this specification embodiment provides a new data processing scheme for the genome file. Among them, loading can be initiated based on the user's browsing, editing, and other needs.
[0050] The embodiments of this specification provide a method for processing genome file data, which can be applied to a computer device or a system including a computer device, and more specifically, can be applied to software (e.g., a gene editing software tool) running on the computer device. Referring to FIG1 , in some embodiments, the method for processing genome file data can include the following steps:
[0051] Step 101: Split the genome file into genetic unit sequences based on designated genetic units, and write them into a genetic unit library.
[0052] Step 102: Receive a selection operation for one or more genetic units in the genetic unit sequence.
[0053] Step 103: Read corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence.
[0054] Step 104: display the genetic unit subsequence.
[0055] The embodiments of this specification can pre-split a genome file into a genetic unit sequence based on a specified genetic unit and write it into a genetic unit library; when a selection operation is received for one or more genetic units in the genetic unit sequence, the corresponding genetic unit can be read from the genetic unit library according to the selection operation and loaded for display; thus, compared with loading the entire genome file, loading and displaying one or more genetic units on demand is faster and more efficient; allowing gene editing software tools to not only quickly and efficiently browse and edit smaller genomes such as microorganisms and yeast, but also quickly and efficiently browse and edit larger genomes such as humans and mice. Moreover, since the genome file is segmented based on genetic units, it can also avoid the same genetic unit being segmented into different data blocks, thereby ensuring the integrity of the genetic unit and facilitating subsequent browsing and editing.
[0056] The designated genetic unit refers to a preset segmentation granularity, which can be customized according to actual needs. For example, in an exemplary embodiment, the designated genetic unit can be a chromosome. Since the number of chromosomes in most species is dozens (for example, the number of human chromosomes is 46), by segmenting the genome file in units of chromosomes, the amount of data per copy has been greatly reduced, so that the gene editing software tool can load and display quickly and smoothly; and for the user, the number of genetic unit options formed after segmenting the genome file in units of chromosomes is more appropriate, which is convenient for the user to select the operation. For example, as shown in Figure 5, with a single chromosome as the segmentation granularity, the genome file can be segmented into chromosomes 1 to chromosomes N, a total of N genetic unit sequences. In some embodiments, the segmentation of the genome file in units of chromosomes can mean that each chromosome in the genome file is segmented as a data block; for example, taking the human genome file as an example, the human genome file can be divided into 46 genetic units. Of course, in other embodiments, according to actual needs, the designated genetic unit can also be any other suitable segmentation granularity, and this specification embodiment is not limited to this; for example, in other embodiments, the designated genetic unit can be DNA or gene, etc.
[0057] 2 , in some embodiments, dividing a genome file into genetic unit sequences based on designated genetic units may include the following steps:
[0058] Step 201: Obtain the file name suffix of the genome file.
[0059] Currently, there are many formats of genome files (such as fasta, gff, gtf, gbk, etc.). The format of each genome file can be identified by its file name suffix, so you can get the file name suffix of the genome file (such as .fasta, .gff, .gtf, .gbk, etc.).
[0060] In some embodiments, taking a Java / JavaScript-based gene editing software tool as an example, the file name suffix of the genome file can be obtained using methods such as String.substring(), String.split(), regular expressions, commons.io.FilenameUtils class, util.StringUtils class, or java.nio.file.Paths class.
[0061] In some embodiments, the genome file can be obtained from a specified local storage path, or by accessing an external public genome database.
[0062] Step 202: confirm whether the genome file is in the target format based on the file name suffix; if the genome file is not in the target format, execute step 203; otherwise, execute step 204.
[0063] For a specific gene editing software tool, it may only support one or several specific data formats. In order to meet user needs or meet the input file format requirements of the gene editing software tool, the genome file can be converted to a unified format (i.e., converted to a target format) before segmentation. For example, taking the GBK format as the target format, genome files in formats such as FASTA, GFF, and GTF can be converted to genome files in the GBK format.
[0064] Step 203: Convert the genome file into a target format.
[0065] In some embodiments, a data conversion component may be integrated into the gene editing software tool, and the genome file may be converted to a target format by calling the data conversion component. For example, in an exemplary embodiment, the genome file may be converted to a target format using the PGDSpider component. The PGDSpider component is a powerful automatic data conversion tool that can be used for genome file format conversion in the field of synthetic biology research. In another exemplary embodiment, the genome file may also be converted to a target format according to a self-developed format conversion script (e.g., a python script).
[0066] Step 204: Identify all target tags in the genome file content after conversion to the target format.
[0067] In some embodiments, a target marker is used to identify the boundaries or start and end positions of information of each specified genetic unit (e.g., chromosome) in the content of a genome file (i.e., the data content of the genome file). For example, in one exemplary embodiment, a double slash (i.e., " / / ") can be used as a target marker.
[0068] If the target format genome file already contains a target tag, it can be directly identified to reduce implementation costs. If the target format genome file does not already contain a target tag, it can be added to the genome file content. It should be noted that when adding a target tag to the genome file content, the target tag can be customized; however, regardless of the target tag, it should be avoided from being confused with other symbolic tags in the genome file to avoid affecting the accuracy of file segmentation.
[0069] In some embodiments, target tags in the genome file content converted to the target format can be identified by regular expression matching or keyword matching.
[0070] Step 205: Divide the genome file into multiple genetic units using the target marker as a segmentation point.
[0071] Each genetic unit after segmentation has the same data format (i.e., all are in the target format); each genetic unit after segmentation can include a genetic unit identifier, annotation information, genetic feature location, and genetic features. Among them, the genetic unit identifier can be used to uniquely identify an individual genetic unit; the genetic unit identifier can also be used to represent the position of the genetic unit in the genome file. For example, in an exemplary embodiment, if the file name of the genome file is xxxgenome, the genetic unit identifiers of the genetic units segmented from the beginning to the end are xxxgenome-01, xxxgenome-02, xxxgenome-03, ..., xxxgenome-0n; then xxxgenome-02 is the second sort, the previous genetic unit of xxxgenome-02 is xxxgenome-01, and the next genetic unit is xxxgenome-03. Accordingly, {xxxgenome-01, xxxgenome-02, ..., xxxgenome-0n} forms a genetic unit sequence. Annotation information is basic descriptive information used to describe the corresponding chromosome, such as the species to which the chromosome belongs (i.e., which chromosome belongs to which species), chromosome position, etc. Genetic signatures are used to describe the genetic signature position of each gene on the corresponding chromosome. Genetic signatures are used to characterize the nucleotide sequence (base pair sequence) of each gene on the corresponding chromosome.
[0072] In some embodiments, the genetic unit library can be a local data warehouse for storing genetic unit sequences (e.g., local storage under a specified storage path) to facilitate faster loading and display of genome files. For scenarios involving multiple genome files, a separate genetic unit library can be set up for the genetic unit sequences corresponding to each genome file.
[0073] In some embodiments, the gene editing software tool may provide a slider function, and the user may select a genetic unit by dragging the slider on the user interface of the gene editing software tool (the dragging coverage range is the selection range), or use a preset key combination (such as a left and right flip key + a confirmation key) to select a genetic unit; or select a genetic unit by clicking a genetic unit option in a drop-down list. For example, as shown in FIG5 , based on the segmentation granularity of a single chromosome, the genome file may be segmented into chromosomes 1 to chromosome N, for a total of N genetic unit sequences; chromosome 2 may be selected as the target.
[0074] In addition, in some embodiments, the gene editing software tool can also provide the function of locating and searching genetic units from the genetic unit library based on sequence, gene name and / or sequence type (such as promoter, etc.) to shorten the time for users to locate genetic units.
[0075] In some embodiments, displaying the genetic unit subsequence may include: first, based on the attributes and status of the object, determining whether the genetic unit subsequence and the current display page have the same object; if the same object exists, rendering the objects in the genetic unit subsequence except for the same object (i.e., only rendering the objects that do not exist or have changed in the current display page); in this way, the rendering range and the response time of the page refresh can be greatly reduced, thereby further improving the speed of loading the genome file. For example, in the embodiment shown in Figure 5, if the current display page displays the DNA graphics corresponding to chromosomes 2 and chromosomes 3, if a gene in chromosome 2 needs to be modified, then when the page is refreshed after the modification, the DNA graphics of chromosome 3 and the DNA graphics of chromosome 2, except for the modified gene, do not need to be re-rendered. Of course, if the same object does not exist, all objects in the genetic unit subsequence need to be rendered.
[0076] Wherein, object refers to the object in the DNA graph corresponding to the genetic unit, and attribute refers to the visually perceptible attribute of the object (such as shape, structure, size, position, etc.). State refers to the display state of the object (i.e., whether the object has been rendered). Therefore, in the embodiments of this specification, the same object refers to the object with the same attribute and the same state.
[0077] In some embodiments, when judging whether the genetic unit subsequence and the current display page have the same object, it should be a comparison between the aligned objects (e.g., objects with the same object noun); for example, there is an object named ABCDE in the current display page, and there is also an object named ABCDE in the genetic unit subsequence, then it can be judged whether the two are the same. In some embodiments, taking a Java / JavaScript-based gene editing software tool as an example, the Object.values function can be called to obtain the properties of the object, etc.; then a judgment comparison is performed to determine the refresh range (i.e., the rendering range). In other embodiments, it can also be achieved by calling a component (e.g., PureComponent) that improves loading display performance.
[0078] In some embodiments, referring to FIG3 , another method for processing genome data is provided in this embodiment, which may include the following steps:
[0079] Step 301: Split the genome file into genetic unit sequences based on designated genetic units, and write them into a genetic unit library.
[0080] Step 302: Receive a selection operation for one or more genetic units in the genetic unit sequence.
[0081] Step 303: Read the corresponding genetic unit from the genetic unit library according to the selection operation to form a genetic unit subsequence.
[0082] Step 304: Display the genetic unit subsequence.
[0083] Step 305: Receive an editing operation for the currently displayed genetic unit subsequence.
[0084] Step 306: Dynamically display the operation result of the editing operation, and update the genetic unit library according to the operation result.
[0085] Compared with the data processing method of the genome file shown in Figure 1, the data processing method of the genome file shown in Figure 3 includes a processing step in which a gene editing software tool receives and responds to the user's editing operation on the currently displayed genetic unit subsequence. Wherein, the editing operation can be, for example, any one or more of the operations such as modification, deletion, increase, scaling, rotation, opening of a circular sequence, and splicing and reconnection of an opened circular sequence to a gene (sequence). Updating the genetic unit library according to the operation result refers to: for write operations (such as modification, deletion, increase, etc.), The modified genetic unit is stored in the genetic unit library, and for read operations (such as scaling, rotation, etc.), it is not necessary to update the genetic unit library according to the operation result. It should be pointed out that all editing operations (especially write operations) can be recorded in the editing operation record, and the user can record the historical records back through the editing operation record.
[0086] In some embodiments, referring to FIG4 , an embodiment of this specification provides another method for processing genome file data, which may include the following steps:
[0087] Step 401: Split the genome file into genetic unit sequences based on designated genetic units, and write them into a genetic unit library.
[0088] Step 402: Receive a selection operation for one or more genetic units in the genetic unit sequence.
[0089] Step 403: Read the corresponding genetic unit from the genetic unit library according to the selection operation to form a genetic unit subsequence.
[0090] Step 404: Display the genetic unit subsequence.
[0091] Step 405: Receive a genetic unit read request sent by a downstream system through a corresponding interface.
[0092] Step 406: Read the target genetic unit from the genetic unit library.
[0093] Step 407: Convert the target genetic unit into a target file suitable for processing by the downstream system, and provide the target file to the downstream system for processing through the interface.
[0094] Compared with the data processing method of the genome file shown in Figure 1, the data processing method of the genome file shown in Figure 4 includes an interactive processing step between the gene editing software tool and the downstream system (i.e., the system that relies on the gene editing software tool). The gene editing software tool is provided with an application program interface (API) that interacts with each downstream system, and the downstream system can perform data interaction through the corresponding interface between the gene editing software tools. Of course, the downstream system can also subscribe to the data push service of the gene editing software tool, and the gene editing software tool can actively push genetic units to the downstream system through event triggering (such as when there is a genetic unit update). Therefore, by the data interaction between the gene editing software tool and the downstream system, the user can save the import and export operations of data.
[0095] Although the process flows described above include multiple operations occurring in a particular order, it should be understood that these processes may include more or fewer operations, which may be performed sequentially or in parallel (eg, using parallel processors or a multi-threaded environment).
[0096] Corresponding to the above-mentioned genome file data processing method, embodiments of this specification further provide a genome file data processing device (i.e., a gene editing software tool), which can be configured on the above-mentioned computer device. Referring to FIG6 , in some embodiments, the genome file data processing device may include:
[0097] A segmentation module 61 is used to segment the genome file into genetic unit sequences based on the specified genetic unit and write them into the genetic unit library;
[0098] A receiving module 62 is configured to receive a selection operation for one or more genetic units in the genetic unit sequence;
[0099] a reading module 63, configured to read corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence;
[0100] The display module 64 is used to display the genetic unit subsequence.
[0101] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0102] It should be noted that in the embodiments of this specification, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user and fully authorized by all parties.
[0103] The embodiments of this specification also provide a computer device. As shown in Figure 7, in some embodiments of this specification, the computer device 702 may include one or more processors 704, such as one or more central processing units (CPUs) or graphics processing units (GPUs), and each processing unit may implement one or more hardware threads. The computer device 702 may also include any memory 706, which is used to store any type of information such as code, settings, data, etc. In a specific embodiment, the computer program on the memory 706 and that can run on the processor 704, when the computer program is run by the processor 704, can execute the instructions of the data processing method of the genome file described in any of the above embodiments. Non-restrictive, for example, the memory 706 may include any one or more combinations of: any type of RAM, any type of ROM, flash memory device, hard disk, optical disk, etc. More generally, any memory can use any technology to store information. Further, any memory can provide volatility or non-volatile retention of information. Further, any memory can represent a fixed or removable component of the computer device 702. In one embodiment, when the processor 704 executes the associated instructions stored in any memory or combination of memories, the computer device 702 can perform any operation of the associated instructions. The computer device 702 also includes one or more drive mechanisms 708 for interacting with any memory, such as a hard disk drive mechanism, an optical disk drive mechanism, etc.
[0104] The computer device 702 may also include an input / output interface 710 (I / O) for receiving various inputs (via input devices 712) and for providing various outputs (via output devices 714). A specific output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, the input / output interface 710 (I / O), input devices 712, and output devices 714 may not be included, and the computer device 702 may simply be a computer device in a network. The computer device 702 may also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the components described above together.
[0105] The communication link 722 can be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 722 can include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
[0106] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), computer-readable storage media, and computer program products of some embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processor to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processor produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0107] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processor to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0108] These computer program instructions can also be loaded onto a computer or other programmable data processor so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0109] In a typical configuration, a computer device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0110] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
[0111] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computer device. As defined in this specification, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0112] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0113] Embodiments of this specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, and the like that perform specific tasks or implement specific abstract data types. Embodiments of this specification may also be practiced in distributed computing environments where tasks are performed by remote processors connected via a communications network. In distributed computing environments, program modules may be located in local and remote computer storage media, including storage devices.
[0114] It should also be understood that in the embodiments of this specification, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.
[0115] The various embodiments in this specification are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiments are generally similar to the method embodiments, so the description is relatively simple. For relevant parts, refer to the description of the method embodiments.
[0116] In the description of this specification, the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiments of this specification. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art can combine and combine different embodiments or examples described in this specification and features of different embodiments or examples without contradiction.
[0117] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.
Claims
1. A method for processing genome file data, characterized in that: include: The genome file is divided into genetic unit sequences based on the specified genetic unit and written into the genetic unit library; receiving a selection operation for one or more genetic units in the genetic unit sequence; Reading corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence; The genetic unit subsequences are displayed.
2. The method for processing genome file data according to claim 1, characterized in that: The specified genetic unit includes a chromosome.
3. The method for processing genome files according to claim 2, characterized in that: The step of dividing the genome file into genetic unit sequences based on the specified genetic unit includes: Identifying all target markers in the genome file content; The genome file is divided into a plurality of genetic units using the target marker as a dividing position point; each of the genetic units comprises a genetic unit identifier, annotation information, a genetic feature position and a genetic feature.
4. The method for processing genome file data according to claim 3, characterized in that: The target mark includes a double slash mark.
5. The method for processing genome file data according to claim 3, characterized in that: The step of identifying all target markers in the genome file content includes: Obtain the file name suffix of the genome file; Confirming whether the genome file is in the target format according to the file name suffix; when the genome file is not in the target format, converting the genome file into the target format; Identify all target tags in the genome file content after conversion to the target format.
6. The method for processing genome file data according to claim 1, characterized in that: The display of the genetic unit subsequence comprises: Based on the attributes and status of the object, determining whether the genetic unit subsequence has the same object as the current display page; If the same object exists, rendering the objects in the genetic unit subsequence except the same object; If no identical objects exist, all objects in the genetic unit subsequence are rendered.
7. The method for processing genome file data according to claim 1, characterized in that: Also includes: receiving an edit operation for a currently displayed genetic unit subsequence; The operation result of the editing operation is dynamically displayed, and the genetic unit library is updated according to the operation result.
8. The method for processing genome file data according to claim 1, characterized in that: Also includes: receiving a genetic unit read request sent by a downstream system through a corresponding interface; Reading a target genetic unit from the genetic unit library; The target genetic unit is converted into a target file suitable for processing by the downstream system, and provided to the downstream system for processing through the interface.
9. A data processing device for genome files, characterized in that: include: A segmentation module is used to segment the genome file into genetic unit sequences based on the specified genetic unit and write them into the genetic unit library; A receiving module, used for receiving a selection operation for one or more genetic units in the genetic unit sequence; A reading module, used for reading corresponding genetic units from the genetic unit library according to the selection operation to form a genetic unit subsequence; A display module is used to display the genetic unit subsequence.
10. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the computer program is executed by the processor, the computer program executes the instructions of the method according to any one of claims 1 to 8.
11. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor of a computer device, the computer program executes the instructions of the method according to any one of claims 1 to 8.
12. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the instructions of the method according to any one of claims 1 to 8 are executed.
Citation Information
Patent Citations
Method for rapidly detecting human genome single base mutation and micro-insertion deletion
CN104762402A
Restriction-site associated DNA sequencing library construction method, restriction-site associated DNA sequencing data analysis method, detection equipment and storage medium
CN111524552A
Genome annotation method and device, visualization platform and storage medium
CN112885412A
Accelerated Processing of Genomic Data and Streamlined Visualization 0f Genomic Insights
US20210043285A1
