DNA MOVABLE TYPE STORAGE SYSTEM AND METHOD

Information

  • Patent Application
  • 20230274793
  • Publication Number
    20230274793
  • Date Filed
    June 07, 2021
    3 years ago
  • Date Published
    August 31, 2023
    a year ago
Abstract
A DNA movable type storage system and method based on movable type printing including: (1) construct a physical DNA movable type library of data payloads and a physical DNA movable type library of indexes based on “DNA movable type codebook”, which consist of a variety of DNA oligonucleotides corresponding to all “DNA payload movable type elements” and “DNA index movable type elements” in the two libraries, respectively; (2) transcode from the storage binary data into corresponding “DNA movable type units”, each of which contains corresponding DNA payload movable type elements and related DNA index movable type elements; (3) link the abovementioned DNA payload and index movable type elements to form a physical “DNA movable type unit”, and put all generated DNA movable type units together for DNA storage, which cover all data information of the target file.
Description

This application claims the benefit of Chinese Patent Application No.202010688281.X, filed on Jul. 16, 2020, the entire contents of which are hereby incorporated by reference in this application.


TECHNICAL FIELD

The disclosure relates to the field of DNA storage, in particular to a storage system and method based on the concept of DNA movable type.


BACKGROUND ART

As an emerging big data storage technology, DNA storage technology breaks through the limitation of the existing storage medium of silica-based materials, such as hard disks, optical disks and removable disks. Taking advantage of the inherent information storage capacity of DNA, DNA storage technology, according to certain encoding methods/rules, converts the 0-1 binary codes encoding various data files (text, image, audio, video, etc.) to corresponding DNA quaternary codes (i.e., combinations of A, T, C, and G), and the corresponding DNAs are then synthesized to store the data information into the DNA oligonucleotides with specific sequences. Conversely, based on corresponding decoding methods/rules, the stored DNAs can be sequenced to obtain DNA quaternary codes, further restoring to the data files with 0-1 binary codes. In short, DNA storage technology can achieve the data encoding, storage and reading using the synthesized DNAs with specific sequences based on certain encoding and decoding methods (i.e., codebook). Compared with the existing data and information storage technologies, DNA storage technology has the advantages of high data density, long storage time, low energy consumption, convenience for carrying, concealed transportation, and multiple encryptions


The idea of storing data and information using DNA was proposed early, however, the DNA storage technology did not have a substantial progress until 2005, with the rapid development of high-throughput DNA synthesis technologies and sequencing technologies. In 2007, Nozomu Yachie et al. for the first time, succeeded to realize the DNA storage for the text data of Einstein's “E=mc{circumflex over ( )}2 1905!” using a hexadecimal transcoding technology, incorporated herein by reference. In August 2012, George Church's research group published a milestone research on DNA storage in the journal Science, for the first time, they used a DNA chip as data storage medium, and successfully stored a variety of media files (including a HTML text file with 53,400 words, 11 JPG images and 1 JavaScript program) into 10-12 gram (1 picogram) of DNAs; and a new “bit-base” encoding method was also reported in this research for corresponding a bit (0-1 code) to a base, making it possible to store large multimedia files through DNA, however the error rate of this encoding method is relatively high, incorporated herein by reference. Almost at the same time, in 2013, Nick Goldman's research group from the European Bioinformatics Institute (EBI) reported their new research results of DNA storage in the journal Nature, and they succeeded to realize the DNA storage of ASCII, PDF, JPG and MP3 files, and first introduced a new error correction method for achieving 100% decoding and restoration of the above-mentioned files, incorporated herein by reference.


Since 2015, with the improvement of high-throughput DNA synthesis and sequencing technologies, the cost of DNA synthesis and sequencing was continued to decline, and the research on DNA storage also reached a new climax. In 2016, Blawat et al. cooperated with George Church's research group developed a new error correction method of DNA storage based on channel model, which can handle all types of errors during DNA synthesis, amplification and sequencing such as insertion, deletion, and recombination errors, and they successfully stored and retrieved 22M data with an accuracy rate of 100%, incorporated herein by reference. In 2017, in the journal Science, Yaniv Erlich's research group from Columbia University in the United States reported a novel DNA storage method based on the fountain code, which realized the storage of 2.15M multimedia files such as videos; compared with previous encoding methods, this method reduces the degree of redundancy through eliminating the overlaps for sequencing assembly, and increases the storage capacity by 60%, incorporated herein by reference.


In view of huge potential of DNA storage technology in future, the Microsoft Corporation of the United States had successively invested nearly 100 million U.S. dollars and cooperated with the James Bornholt's research group from the University of Washington to release a new DNA storage system that supports random-access reading of data in 2016. This system adopts a key-value mode addressing method, in which the storage address is divided into high and low parts, thereby increasing the flexibility of random-access reading. It succeed to realize the random-access reading of 42 kb subset data. Using the above-mentioned DNA storage system, the Microsoft Corporation had completed the DNA storage of about 200 MB of data by March 2018, including 100 classic literary works in the Gutenberg Project database, creating a new record in the field of DNA storage at the time.


Although DNA storage technology has many advantages over traditional data storage technologies, and relevant researches have made considerable progress in recent years, it has some disadvantages, mainly in two aspects. First, compared with traditional data storage technologies, its costing is very high, and the storage and reading are also very time-consuming, which greatly limit its practical application. Specifically, most design ideas of the above-mentioned DNA storage technologies are more similar to “engraving printing”: for each DNA stored file, it is necessary to synthesize all sequences of fragments encoding DNA storage file, but these synthesized DNA fragments cannot be reused, thereby leading to a main disadvantage of high cost for DNA storage technology. Secondly, since many current DNA storage technologies are prone to generate some errors during synthesizing and sequencing of DNA sequences, a large amount of redundant DNA fragments are required for error correction, thereby resulting in additionally costs.


SUMMARY

In order to solve or at least partially solve the above technical problems, the disclosure is based on the concept of “movable type printing”, one of the four great inventions of ancient China, and to one-to-one map a “DNA movable type unit” to corresponding data “payload movable type elements” (characters, pixels, audio amplitudes, etc.) and data “index movable type elements” (locations, file attributes, etc.), thereby realizing encoding, storage and precise decoding of quaternary DNA stored data (such as texts, pictures, audios, and videos). Specifically, the disclosure comprises the following aspects.


In a first aspect of the disclosure, provided herein is a method for DNA movable type storage, comprising:


(1) providing a physical library of data payload movable type elements and a physical library of index movable type elements, in which the payload movable type element library consists of a variety of oligonucleotides of data payload movable type elements (first oligonucleotides) that corresponds to various binary payload data information; the index movable type element library consists of a variety of oligonucleotides of index movable type elements (second oligonucleotides) that corresponds to various binary index data information;


(2) dividing the stored 0-1 binary data into corresponding data payload and index movable type elements; mapping the abovementioned data payload and index movable type elements to corresponding oligonucleotides from the physical libraries of data payload and index movable type elements, based on a codebook for encoding and decoding mapping rule between 0-1 binary codes and DNA A-T-C-G quaternary codes;


(3) linking the oligonucleotides of data payload movable type elements and the oligonucleotides of index movable type elements in step (2) to form a DNA movable type unit corresponding to a data element information, and all DNA movable type units form a DNA storage library that holds all the data element information of a stored file; and


(4) sequencing the oligonucleotides from the DNA storage library in step (3), and decoding the sequencing results into binary stored data according to a codebook of data payload and index movable types using a corresponding decoding software.


In some embodiments, the stored data are selected from at least one of text data, image data, audio data and video data.


In some embodiments, the data payload movable type element is selected from at least one of a character, a pixel, an audio amplitude and a video frame; the index movable type elements comprises location and attribute information for a data payload element.


In some embodiments, the location information of the data payload movable type element comprises information of page number, row and column.


In some embodiments, the attribute information comprises file type, file name, file size, and creation time for the data payload element.


In some embodiments, the linker sequences are comprised in the oligonucleotides of data payload and index movable type elements in the DNA movable type units.


In some embodiments, the linker sequence is an overlapping reverse complement sequence or an enzymatically cleavable sequence.


In the second aspect of the disclosure provided herein is a system for DNA movable type storage, comprising:


a. a physical library of data payload movable type elements and a physical oligonucleotide library of index movable type elements: the physical library of data payload movable type elements consists of a variety of oligonucleotides of data payload movable type elements, each of which corresponds to a only data payload movable type element for the DNA stored file; and the physical library of index movable type elements consists of a variety of oligonucleotides of index movable type elements, each of which corresponds to a only index element;


b. an encoding module/software first provides for dividing the binary targeted stored data file into corresponding data payload and index movable type elements; and for each data payload movable type element and its index movable type elements, encoding module/software can achieve the transcoding from 0-1 binary codes to DNA A-T-C-G quaternary codes based on certain codebook/mapping rule; these DNA A-T-C-G quaternary codes correspond to certain oligonucleotides from the physical libraries of payload and index movable type elements; and


c. a decoding module/software provides for the transcoding from DNA A-T-C-G quaternary codes to 0-1 binary codes based on certain codebook/mapping rule using the decoding sequencing data of the DNA oligonucleotide stored data file.


In some embodiments, the system for DNA movable type storage further comprises related system for DNA linkers and related system for DNA sequencing.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a schematic diagram of an exemplary system for DNA movable type storage.



FIG. 2 is a schematic diagram of the structure of an exemplary DNA movable type unit.



FIG. 3 is a schematic diagram of the structure of an exemplary DNA movable type unit of text file.



FIG. 4 is a design diagram of oligonucleotide sequences from an exemplary physical library of DNA movable types.



FIG. 5 is a mapping exemplary schematic diagram between 256 bytes and corresponding DNA sequences.



FIG. 6 is a flowchart of an exemplary encoding algorithm.



FIG. 7 is a flowchart of an exemplary decoding algorithm.



FIG. 8 shows all movable type units generated by PCR in an exemplary target text file.



FIG. 9 is a flowchart of an exemplary decoding algorithm of a text file.



FIG. 10 is a diagram showing an exemplary software decoding result.





DETAILED DESCRIPTION

Various exemplary implementations in the disclosure are now described in detail. The detailed description should not be considered as a limitation on the invention, but should be understood as a more detailed description of certain aspects, characteristics, and embodiments of the disclosure.


It should be understood that the terms described in the disclosure are only used to describe specific implementations, rather than to limit the invention. In addition, for the numerical ranges in the disclosure, it should be understood that the upper limit and the lower limit of the range and each intermediate value between them are specifically disclosed. Each smaller range between an intermediate value among any stated values or within any stated range and an intermediate value among any other stated values or within any other stated range is also encompassed in the disclosure. The upper and lower limits of these smaller ranges can be independently included or excluded from the range.


Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the disclosure belongs. Although the disclosure only describes some methods and materials, any methods and materials similar or equivalent to those described herein can also be used in the implementation or testing of the disclosure. All documents mentioned in this specification are incorporated by reference to disclose and describe methods and/or materials related to the documents. In the event of conflict with any incorporated document, the description in this specification shall prevail. Unless otherwise specified, “%” is a percentage based on weight.


Method for DNA Movable Type Storage

In the first aspect of the disclosure, provided herein is a method for DNA movable type storage. The concept of DNA movable type is core and focus for the method of the disclosure, which is based on the synthesis, usage of various DNA sequences and their combinations to achieve DNA data encoding, storage, and decoding/precise-interpretation, therefore, it can also be referred to as a “method for storing data using artificially synthesized DNAs”, or a “method for storing data using base sequences”.



FIG. 1 shows an example of a DNA movable type storage method and system. The storage method of the disclosure at least comprising:


(1) providing a physical library of data payload movable type elements and a physical library of index movable type elements, wherein the physical library of data payload movable type elements consists of a variety of oligonucleotides of data payload movable type elements which are stored separately, and each of them corresponds to different data payload elements for DNA data storage; and the physical library of index movable type consists of a variety of oligonucleotides of index movable type elements which are stored separately, and each of them corresponds to different index element;


(2) dividing the stored 0-1 binary data into corresponding data payload and index movable type elements; mapping the abovementioned data payload and index movable type elements to corresponding oligonucleotides from the physical libraries of data payload and index movable type elements, based on a codebook for encoding and decoding mapping rule between 0-1 binary codes and DNA A-T-C-G quaternary codes;


(3) linking the oligonucleotides of data payload movable type elements and the oligonucleotides of index movable type elements in step (2) to form a DNA movable type unit, and all DNA movable type units to form a DNA storage library that holds all the data element information of a stored file; and


(4) sequencing the oligonucleotides from the DNA storage file in step (3), and decoding the sequencing results into binary stored data according to a codebook of the data payload and index movable types using a corresponding decoding software.


Step (1)

In the disclosure, step (1) is a step of providing a physical library of data payload movable type elements and a physical library of index movable type elements. This step comprises constructing such physical libraries or using existing physical library. The physical library refers to a library composed of many different types of oligonucleotides, and usually each type of oligonucleotide is stored separately or independently. For the convenience of illustration, these oligonucleotides that constitute the physical library of data payload movable type elements are referred to as the oligonucleotides of data payload movable type elements (first oligonucleotides). The oligonucleotides that constitute the physical library of index movable type elements are referred to as the oligonucleotides of index movable type (second oligonucleotides). Either the oligonucleotides of data payload and index movable type elements can be single-stranded or double-stranded DNAs.


In the disclosure, the oligonucleotides of data payload movable type elements are of multiple different types, each type is stored separately, and each type of DNA sequences uniquely correspond to the data payload elements of the stored data file. Similarly, there are also many different types of oligonucleotides for index movable type elements, and each type is also stored separately. Each index movable type of DNA sequences corresponds to different levels of index information respectively. The oligonucleotide sequences are generated from permutations and combinations of four different bases (A, T, C, and G). The longer the sequence, the more permutations and combinations are obtained, and thus the more oligonucleotide types are obtained. Therefore, the desired oligonucleotide types/classes can be obtained by manipulating the length of oligonucleotides, thereby achieving the one-to-one correspondence between the oligonucleotides of data payload movable type elements and numerous data elements, or the one-to-one correspondence between the oligonucleotides of index movable type and a large amount of different index information.


In the case of no available physical library, step (1) of the disclosure also comprises reconstructing a physical library of data payload movable type elements and a physical library of index movable type elements. In an exemplary construction method, the quaternary encoding method using specific permutations and combinations of four kinds of bases (A, T, C and G) is used to create the libraries for the indicated data payload and index movable type elements. As shown in FIG. 4, the method comprises the following steps:


A set of DNA sequence combination is obtained by randomly permuting and combining the “A, T, C and G”, and then the dirty sequences in the set are cleaned up to obtain a library of candidate sequences. In some embodiments, the dirty sequences mainly comprise some sequences that can affect the sequencing and PCR effects, such as repeat sequences, palindrome sequences, higher structure-forming sequences, high GC content (>65%) sequences, and single continuous repeat bases (>3nt)-containing sequences. The oligonucleotides in the library of candidate sequences are then synthesized, used as the physical libraries (comprising a library of data payload movable type and a library of index movable type elements), and stored at −80° C. in a refrigerator.



FIG. 5 shows an example, in which the library of data payload of movable type elements is composed of 256 DNA sequences, and each sequence represents one byte data payload in a binary file.


Step (2)

In the disclosure, the step (2) is an encoding step, comprising dividing and annotating of the stored data, and generating a one-to-one correspondence between the binary data and the quaternary oligonucleotides in the physical libraries. Specifically, the binary data of the stored target file is first divided into a plurality of data payload movable type elements, and each data payload movable type element is then annotated with corresponding index movable type element information; for the data payload and index movable type elements in each data movable type unit, the encoding module/software can achieve the transcoding from 0-1 binary codes to DNA A-T-C-G quaternary codes based on certain mapping rule/codebook; corresponding oligonucleotides are finally obtained from the physical libraries of data payload and index movable type elements.


In the disclosure, the stored data is any known type of data, which includes, but is not limited to, text data, image data, audio data, and video data. The stored data in the disclosure may be at least one of the above-mentioned data. In a specific embodiment, the stored data is text data.


In the disclosure, a data payload or index movable type element is generally a minimum/repeat element of stored file, examples of which include, but are not limited to, characters, pixels, audio amplitudes, and video frames. At least one of the above-mentioned examples can be used in the disclosure. Preferably, the data element is a element repeated multiple times in the stored data. For example, in Chinese text data, the data element may be either individual Chinese character, such as custom-character, and custom-character, or expression or phrase composed of Chinese characters, such as custom-character, custom-character, and custom-character. The data element may also comprise punctuation marks, such as comma, full stop, space, and the like. As another example, in English text data, the data elements can be either English words, such as “hello” and “world”, or may be single English letters, such as “A”, “a”, “Y”, etc. When the data element is phrase, the commonly used phrases with higher repetitions are preferred.


In the disclosure, the index elements comprise location and attribute information of a data payload movable type element in the stored file. For example, the location information of the data payload element comprises information of page number, row and column. As another example, the attribute information of a file comprises file type, file name, file size, creation time and the like. Generally, each data payload movable type element needs to be annotated with multiple levels of or multiple index element information.


In the step (2) of the disclosure, the one-to-one correspondence between the data payload movable type element and oligonucleotide is realized through an association table (codebook) of data payload movable type, and the one-to-one correspondence between the index movable type information and oligonucleotide is realized through an association table of index movable type.


In exemplary embodiments, the encoding in step (2) is based on a codebook/association table (comprising a codebook/association table of data payload movable type and a codebook/association table of index movable type), and using an encoding software to convert each binary data element in a target file to corresponding oligonucleotide combination or a data payload movable type element and relate index movable type elements. As for the encoding software, it is for example written in a programming language such as Python, Java, so as to achieve the purpose of dividing and encoding the DNA movable type unit of the target file. An algorithm process of encoding software is shown in FIG. 6, and the details are as follows: dividing each movable type unit of a target file into corresponding data payload movable type and index movable type elements, according to an association table/codebook of the data payload movable type and an association table of the index movable type, thereby achieving the coding of data payload movable type and index movable type elements for the target file. It provides a guidance for the subsequent formation of each DNA movable type unit of the target file through linkage or PCR experiments.


Step (3)

The step (3) of the disclosure is a step for DNA movable type storage, which specifically comprises the linkage of oligonucleotides of the data payload and index movable type elements in step (2) to form a DNA movable type unit corresponding to each data element, and allowing a plurality of DNA movable type units to form a storage library that holds all the stored data.


In the disclosure, the storage library comprises a large number of DNA movable type units, each DNA movable type unit is a oligonucleotide, and each oligonucleotide is a linked sequence of a plurality of single-stranded or double-stranded DNA sequences composed of specific permutations and combinations of four bases (A, T, C and G), which corresponds or maps to data payload and index movable type elements. Such multiple mapping relationship forms a two-way correspondence between a codebook/association table of data payload movable type and a codebook/association table of index movable type. In some embodiments, a library of DNA movable type storage file in the disclosure comprises a plurality of DNA movable type units, and each DNA movable type unit comprises a oligonucleotide with data payload and index movable type elements (as shown in FIG. 2 and FIG. 3). The number of the index movable type elements is not particularly limited, and for example, it is an even number, such as 2, 4, 6, 8 and other even number of sequences of index movable type elements.


In the DNA movable type unit of the disclosure, a linker sequence exists among the oligonucleotides of data payload and index movable type elements. The linker sequence is located at one/both end of an oligonucleotide sequence, for example, forming a combination of linker-payload-index oligonucleotide sequences. The purpose of the linker sequence is to realize the linking and assembling of the data payload movable type and the index movable type elements into a DNA movable type unit. The number of linker sequences is not particularly limited, and for example it is a natural number such as 1, 2, 3, 4, 5, 6, 7 and 8 linker sequences. In some embodiments, these linker sequences are PCR primer sequences or enzymatically cleavable linkers. In some specific embodiments, the linkage of these linker sequences for the abovementioned oligonucleotides are achieved by polymerase chain reaction.


In some exemplary embodiments, the method of the disclosure comprises converting the binary data in the target file to a A-T-C-G quaternary file composed of DNA movable type units by encoding software, and then obtaining the corresponding DNA movable type elements from physical libraries of data payload movable type and index movable type elements. In some specific embodiments, PCR, linkage and other reactions can be used to link the data and index payload movable type elements to form each DNA movable type unit of the target file, and finally the various DNA movable type units are collected and cryopreserved to complete the DNA movable type storage of a target file. In order to store each movable type unit for a long time and used repeatedly for many times, preferably, each movable type unit may be cloned into a plasmid and introduced into Escherichia coli for preservation to achieve this purpose. The plasmid and Escherichia coli are not particularly limited. In some specific embodiments, each movable type unit is cloned into a PUC19 plasmid and introduced into Escherichia coli DH5α for preservation.


Step (4)

The step (4) is a decoding step, which is an optional step in the method for DNA movable type storage. The decoding step generally comprises the step of sequencing the oligonucleotides in the storage library. In some embodiments, firstly, using for example a high-throughput sequencing platform to sequence the DNA sequences of a DNA movable type storage file to obtain all the sequence information of the DNA oligonucleotides of the target file at one time; then using a decoding software to decode the DNA sequences of the binary target file, and output a readable target file to realize information decoding and precise interpretation of the DNA movable type oligonucleotides. The decoding step can decode the sequencing result into the binary data of stored file, based on the association table/codebook of data payload and index movable type elements.


System for DNA Movable Type Storage

In a second aspect of the disclosure, provided herein is a system for DNA movable type storage, at least comprising the following items (a˜c):


a. physical libraries of oligonucleotides comprise a physical library of data payload movable type elements and a physical library of index movable type elements, wherein the physical library of data payload movable type elements consists of a variety of oligonucleotides of data payload movable type elements which stored separately, and each oligonucleotide sequence corresponds to one data payload element in the targeted data file; and the physical library of index movable type elements consists of a variety of oligonucleotides of index movable type elements which stored separately, and each oligonucleotide base sequence corresponds to different index movable type element respectively;


b. an encoding module/software which provided for dividing the stored data of a target file into a plurality of data movable type units, which contained certain data payload movable type elements with annotating index data movable type elements; based on an encoding software from association table/codebook, the binary data of movable type units were transcoded into corresponding oligonucleotide base sequences in the physical libraries of data payload and index movable type elements; and


c. a decoding module/software which provided for decoding the sequencing data of the oligonucleotides in the storage library into the binary stored data in a target file according to an association table of the data payload/index movable type elements and a corresponding decoding software.


The physical library of data payload movable type elements and the physical library of index movable type elements in the disclosure contains series of different oligonucleotides which stored separately. In certain embodiments, the physical library data payload movable type elements is stored in a series of containers (e.g., test tubes, EP tubes): one sequence of oligonucleotide of data payload movable type element is stored in a container, and one sequence of oligonucleotide uniquely corresponds to one data payload movable type element. Similarly, the physical library of index movable type elements is also stored in a series of containers (e.g., test tubes, EP tubes): one sequence of oligonucleotide of index movable type element is stored in a container, and the sequence of oligonucleotide uniquely corresponds to one data index movable type element. The oligonucleotides in different containers are quantitatively added into the DNA linking reaction system according to the encoding result.


The oligonucleotide physical libraries of the disclosure (comprising the physical library of data payload movable type elements, the physical library of index movable type elements and the physical library of linkers) are in a solution or dry powder state in which a specified amount of oligonucleotides are comprised. Typically, the oligonucleotide physical libraries are stored at a low temperature such as −80° C. Different physical libraries are used in solution state, which can be called by, for example, automatic machine manipulation.


The encoding module and decoding module of the disclosure are typically implemented by software(s). As an exemplary software, it specifically implements the task of converting binary data files of various formats into quaternary DNA sequence information. In some embodiments, the encoding software is written in program languages such as Python and Java, to achieve the goal of dividing and encoding a binary data target file into DNA movable type units, with an algorithm process as shown in FIG. 6. In the decoding module, it typically implements the task of converting the DNA movable type sequence data obtained through high-throughput sequencing into a readable binary data target file, wherein the target file here may be texts, images, audios, videos. In some embodiments, the decoding software typically comprises multiple sub-modules such as a sub-module for controlling DNA sequence quality, a sub-module for decoding data payload movable type elements, a sub-module for decoding index movable type elements, and a sub-module for outputting binary data target file, which are integrated into a data decoding module (as shown in FIG. 7), to achieve the decoding and precise interpretation of the DNA oligonucleotide sequences into the binary data target file.


Optionally, the system for DNA movable type storage of the disclosure further comprises at least one of a system for linking DNA, a system for sequencing DNA, and a system for DNA cryogenic storage.


The system for linking DNAs of the disclosure refers to a system for linking at least two oligonucleotides, and generally speaking, it comprises a reaction container, various reaction reagents and a controller. There may be one or more reaction container. For example, the reaction container is an EP tube. The various reaction reagents of the disclosure comprise a buffer and DNA ligase. Known commercial reaction reagents can be used in the disclosure. The controller of the disclosure is an instrument for controlling reaction conditions such as 37° C.


The system for DNA sequencing of the disclosure can be any known commercial system, for example, a second-generation sequencing system (i.e., the next-generation sequencing technology) including Illumina sequencers. The DNA sequencing system of the disclosure can also be a third-generation sequencing system (i.e., a single-molecule sequencing system), such as Pacbio or Oxford nanopore sequencing platforms.


The system for DNA cryogenic storage of the disclosure refers to a system for long-term storage of oligonucleotides. Known commercial systems can be used. Generally speaking, DNA can be stored at a low temperature for at least 50 years, preferably at least 100 years, and more preferably not less than 200 years. The cryogenic storage system comprises a cryogenic refrigerator.


In the system for DNA movable type storage of the disclosure, each subsystem or component can either be a separated part, which can be combined into a complete system when in use, or be integrated into a whole; and each subsystem or component can be controlled by a controller as a whole to achieve coordinated operation, thereby realizing the automatic encoding, storage or decoding of DNA stored data.


EXAMPLES

DNA movable type storage of a classical Chinese poem by Li Bai, custom-charactercustom-charactercustom-character” was used as an example of the disclosure, and the PCR method was used for linking.


1. Encoding and Synthesis of DNA Sequences of DNA Movable Type Units

According to the method of the disclosure, a file composed of movable type units was designed and used to generate for custom-charactercustom-character as shown in Table 1. According to this file, with the help of the encoding software, the DNA sequences of 12 bp data payload movable type elements as shown in Table 2 and the sequences of 8 bp index movable type elements as shown in Table 3 were generated, and the corresponding DNA sequences were synthesized.









TABLE 1







File composed of movable type units















Movable type





File name
Row
element
Column
Page








custom-character

8

custom-character

 1
1




custom-character

8

custom-character

 2
1




custom-character

8

custom-character

 3
1




custom-character

8

custom-character

 4
1




custom-character

8

custom-character

 5
1




custom-character

8

custom-character

 6
1




custom-character

8

custom-character

 7
1




custom-character

8
,
 8
1




custom-character

8

custom-character

 9
1




custom-character

8

custom-character

10
1




custom-character

8

custom-character

11
1




custom-character

8

custom-character

12
1




custom-character

8

custom-character

13
1




custom-character

8

custom-character

14
1




custom-character

8

custom-character

15
1




custom-character

8
°
16
1

















TABLE 2







Sequences of data payload movable type elements of the target file











Linker sequence
Payload
Linker sequence


Payload
on the
movable type
on the


information
left side
element
right side






custom-character

ATAAGCCTCGAGTAG
GCGTAGCTGTAC
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
GCAGGACACTGT
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
GACGGTCAAGTG
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TGCGCATGACAG
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
ACTAATACGTCG
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
CTACCGACTCTG
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TCTCACAGTAGC
TGATAGTACCAGAGC





,
ATAAGCCTCGAGTAG
CACGGTCTCGAT
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TCACCACTTCTA
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
AGCTCACAGCGT
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
CGAGGATCACAC
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
AGCTTGACGTAT
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TGAGTCAGACAT
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TAGTACTGTCGC
TGATAGTACCAGAGC






custom-character

ATAAGCCTCGAGTAG
TGTGCTATCACT
TGATAGTACCAGAGC






ATAAGCCTCGAGTAG
CACACATCTAGT
TGATAGTACCAGAGC
















TABLE 3







Sequences of index movable type elements of the target file












Index




Linker sequence
movable
Linker sequence


Index
on the left
type
on the


information
side
element
right side






custom-character

AGCTATACGGAGCAT
CGTGAGAT
TAGTCAACTAGCCTC





Page 1
CTACATGTCCAGGCA
ATGCCGTA
GCTTGTGACAGCATA





Row 8
TAGTCAACTAGCCTC
GTCATCGT
ATAAGCCTCGAGTAG





Column 1
TGATAGTACCAGAGC
CAGAACGA
CTACATGTCCAGGCA





Column 2
TGATAGTACCAGAGC
AGCATCGA
CTACATGTCCAGGCA





Column 3
TGATAGTACCAGAGC
TGATGCTG
CTACATGTCCAGGCA





Column 4
TGATAGTACCAGAGC
GATCCTGA
CTACATGTCCAGGCA





Column 5
TGATAGTACCAGAGC
ACATCGCT
CTACATGTCCAGGCA





Column 6
TGATAGTACCAGAGC
GATGAGTG
CTACATGTCCAGGCA





Column 7
TGATAGTACCAGAGC
AGCTTCAG
CTACATGTCCAGGCA





Column 8
TGATAGTACCAGAGC
CTAGCTCA
CTACATGTCCAGGCA





Column 9
TGATAGTACCAGAGC
CTACACAG
CTACATGTCCAGGCA





Column 10
TGATAGTACCAGAGC
TAGCCACT
CTACATGTCCAGGCA





Column 11
TGATAGTACCAGAGC
AGTGATGC
CTACATGTCCAGGCA





Column 12
TGATAGTACCAGAGC
CATCATGC
CTACATGTCCAGGCA





Column 13
TGATAGTACCAGAGC
TGCAACGT
CTACATGTCCAGGCA





Column 14
TGATAGTACCAGAGC
ACGCATCA
CTACATGTCCAGGCA





Column 15
TGATAGTACCAGAGC
GTGATGCT
CTACATGTCCAGGCA





Column 16
TGATAGTACCAGAGC
TGACCTAG
CTACATGTCCAGGCA









The synthesized DNA sequences of data payload movable type elements were diluted to 0.01 μM, and the synthesized sequences of row, column and page index movable type elements were diluted to 5 μM.


2. Assembly of the Data Payload Movable Type Elements and the Corresponding Index Movable Type Elements by PCR to Form DNA Movable Type Units

According to the guidance file of Table 2, each movable type unit was formed by PCR linking as per the structure of “file name-row-data payload movable type-column-page”, and the components therein were assembled together by PCR using linker sequences between two components. The specific process was as follows:


2.1 Assembly of the Movable Type Unit with the Structure of “File Name-Row-Data Payload Movable Type-Column-Page”

The first step of assembly: a unit of “row-data payload movable type-column” was assembled. PCR reaction system: 5 μl of 2×Es Taq MasterMix, 1 μl of each of the diluted movable type, row and column oligos, and 2 μl of sterile water. Pre-denaturation at 94° C. for 2 min; then denaturation at 94° C. for 30 s, annealing at 62° C. for 30 s, and extension at 72° C. for 30 s, 30 cycles; and finally, extension at 72° C. for 2 min.


The second step of assembly: the unit of “row-data payload movable type-column” formed in the first step was secondly assembled with the file name and page number to form a DNA movable type unit of “file name-row-data payload movable type-column-page”. PCR reaction system: 25 μl of 2×Es Taq MasterMix, 1 μl of unit of “row-movable type-column”, 10 μl of each of diluted file name and page number oligos, and 4 μl of sterile water. Pre-denaturation at 94° C. for 2 min; then denaturation at 94° C. for 30 s, annealing at 62° C. for 30 s, and extension at 72° C. for 30 s, 30 cycles; and final extension at 72° C. for 2 min.


2.2 Purification of the Complete DNA Movable Type Unit of “File Name-Row-Data Payload Movable Type-Column-Page”

The movable type units assembled in the second step were separated by 2% agarose gel electrophoresis (electrophoresis was run at a voltage of 90 V for 35 minutes), and the target fragments were cut off, recovered and purified using Zymoclean Gel DNA Recovery Kit. Each of the movable type units of “file name-row-data payload movable type-column-page” was shown by the arrow in FIG. 8.



3. DNA Movable Type Storage of a Target Text File

In order to store each movable type unit for a long time and use it repeatedly, we cloned each movable type unit into PUC19 plasmid and introduced it into E. coli DH5α for storage. The specific process was as follows:


3.1 Enzymatic Digestion

Each purified movable type unit and pUC19 plasmid were quantified with Nanodrop, and digested with enzymes EcoRI and XbaI. Enzymatic digestion system: 1 μl of 10×NEB 2.1 buffer, 0.5 μl of EcoRI (NEB), 0.5 μl of XbaI (NEB), 500 ng of pUC19 and 200 ng of movable type units, ddH2O complemented to 10 μl, digestion at 37° C. for 1 h.


3.2 Enzymatic Ligation

Each movable type unit and plasmid which had been subjected to the enzymatic digestion in the previous step were quantified with Nanodrop, and mixed in a ratio of 1:2, 10 μl mixture was taken out, 2 μl of 10×T4 DNA ligase buffer, 1 μl of T4 DNA ligase and 7 μl of ddH2O were added, and ligated overnight at 16° C.


3.3 Transformation

The enzymatic ligation product from the previous step was added to 100 μl of DH5α, placed on ice for 30 min, heat shocked at 42° C. for 90 s, quickly placed on ice for 3 min, added to 500 μl of LB medium and cultured at 37° C. at 200 rpm for 1 h, and 100 μl of the resultant was taken and spread on an ampicillin resistant LB plate, and cultured overnight at 37° C. The colonies on the plate were picked up for Sanger sequencing verification. The validated successful clone for each Chinese character was selected, cultured in an LB medium to the logarithmic phase, and stored in 30% glycerol at −80° C. for a long time.


4. Decoding

The storage files with 16 DNA movable type unit for custom-charactercustom-charactercustom-character were taken out from the refrigerator, thawed, and amplified. The decoding libraries for second-generation sequencing were then constructed, sequenced using illumina Hiseq4000 sequencing platform, and decoded with the decoding software. The specific text file decoding algorithm process was shown in FIG. 9, where the index movable type elements were ranked according to the priority order of file name>page number>row>column. The output target file is as shown in FIG. 10.


Similarly, the full text of custom-character by Li Bai can be encoded. For details, please refer to the whole poem and the position encoding table.



custom-character



custom-character
custom-character



custom-character
custom-character



custom-character
custom-character



custom-character
custom-character



custom-character
custom-character



custom-character
custom-character



custom-character
custom-character
















1

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



row 1 page 1 custom-character .txt
AGCCTCGAGTAGCGACGAGCCATATGATAGTACCAGAGCCAGAACGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





2

custom-character

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



column 2
AGCCTCGAGTAGCTCAGATGGCATTGATAGTACCAGAGCAGCATCGAC



row 1 page custom-character .txt
TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





3

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



row 1 page 1
AGCCTCGAGTAGACTCTAGTGTGATGATAGTACCAGAGCTGATGCTGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





4

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



Row 1 page 1
AGCCTCGAGTAGGATGGCGTGAGATGATAGTACCAGAGCGATCCTGAC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





5

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



row 1 page 1
AGCCTCGAGTAGACAGCGACCTGATGATAGTACCAGAGCACATCGCTC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





6

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



row 1 page 1 
AGCCTCGAGTAGGTATCACGTGCGTGATAGTACCAGAGCGATGAGTGC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





7
\n column 7 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACATGCATA



1 page 1 custom-character
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCAGCTTCAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





8

custom-character column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 
AGCCTCGAGTAGAGAGGTGACTCATGATAGTACCAGAGCCAGAACGAC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





9

custom-character  column

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 2
AGCCTCGAGTAGAGAGACACCATCTGATAGTACCAGAGCAGCATCGAC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





10

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1
AGCCTCGAGTAGTCTGATCGAGCATGATAGTACCAGAGCTGATGCTGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





11

custom-character  column 4 

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character
AGCCTCGAGTAGTATGGATCCGTATGATAGTACCAGAGCGATCCTGACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





12

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1
AGCCTCGAGTAGGACGTACGGAGATGATAGTACCAGAGCACATCGCTC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





13

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1
AGCCTCGAGTAGGTACCACTATGTTGATAGTACCAGAGCGATGAGTGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





14
\0 column 7 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



2 page 1 custom-character
AGCCTCGAGTAGCTGCCACTCTACTGATAGTACCAGAGCAGCTTCAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





15

custom-character  column 8

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGAGAGGTGACTCATGATAGTACCAGAGCCTAGCTCAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





16

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGACACATGACAGATGATAGTACCAGAGCCTACACAGC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





17

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGTGAGCTCGATGTTGATAGTACCAGAGCTAGCCACTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





18

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGTATGGATCCGTATGATAGTACCAGAGCAGTGATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





19

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGGTGCACTGTCACTGATAGTACCAGAGCCATCATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





20
\n column 13
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCATGTGTATA



row 2 page 1 custom-character .txt
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





21

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGGTCTATGACTCATGATAGTACCAGAGCCAGAACGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





22

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGCTAGCAGATCACTGATAGTACCAGAGCAGCATCGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





23

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTCTAGTAGGATCTGATAGTACCAGAGCTGATGCTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





24

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGGATAAGCAGAGTTGATAGTACCAGAGCGATCCTGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





25

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGAGCACACACACTTGATAGTACCAGAGCACATCGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





26

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTCGTGTCGGCTATGATAGTACCAGAGCGATGAGTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





27

custom-character  column 7

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTATGAGTGGTGCTGATAGTACCAGAGCAGCTTCAGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





28
, column 8 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



3 page 1 custom-character
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





29

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 
AGCCTCGAGTAGGCTATCAGGATATGATAGTACCAGAGCCTACACAGC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





30

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGATGTACTCCACGTGATAGTACCAGAGCTAGCCACTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





31

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTAGACTGAACGTTGATAGTACCAGAGCAGTGATGCC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





32

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGGAGCTCTGCTGATGATAGTACCAGAGCCATCATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





33

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTCACCACTTCTATGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





34

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGCGCACTCAATAGTGATAGTACCAGAGCACGCATCAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





35

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 custom-character .txt
AGCCTCGAGTAGTATCTACGACTGTGATAGTACCAGAGCGTGATGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





36
○ column 16
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1
AGCCTCGAGTAGCACACATCTAGTTGATAGTACCAGAGCTGACCTAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





37
\n column 17
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACACCTCTATA



row 3 page 1 
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGTCACACCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





38

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGTATGTATCGCTCTGATAGTACCAGAGCCAGAACGACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





39

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGTGACCTCGTGTCTGATAGTACCAGAGCAGCATCGACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





40

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGCGTGGTACGTACTGATAGTACCAGAGCTGATGCTGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





41

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGACTGCTCTCGTGTGATAGTACCAGAGCGATCCTGACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





42

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGTCTCGCACAGCATGATAGTACCAGAGCACATCGCTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





43

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page
AGCCTCGAGTAGGCGTACTAGAGTTGATAGTACCAGAGCGATGAGTGC



1 custom-character .txt
TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





44

custom-character  column 7

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page
AGCCTCGAGTAGTATGCAGTGACATGATAGTACCAGAGCAGCTTCAGCT



1 custom-character .txt
ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





45
, column 8 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



4 page 1 custom-character
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





46

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1 custom-character .txt
AGCCTCGAGTAGAGTCACAGTGATTGATAGTACCAGAGCCTACACAGC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





47

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1 
AGCCTCGAGTAGGATGACGATCTATGATAGTACCAGAGCTAGCCACTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





48

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGATGCGTAGCGTATGATAGTACCAGAGCAGTGATGCC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





49

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGAGCTGCAGGATCTGATAGTACCAGAGCCATCATGCCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





50

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGTGAGTATACGACTGATAGTACCAGAGCTGCAACGTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





51

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1 custom-character .txt
AGCCTCGAGTAGGTGCATGCGTCTTGATAGTACCAGAGCACGCATCACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





52

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGCTCACACTACATTGATAGTACCAGAGCGTGATGCTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





53
○ column 16
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGCACACATCTAGTTGATAGTACCAGAGCTGACCTAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





54
\n column 17
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCAGAGTACATA



row 4 page 1
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGTCACACCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





55

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGTGTAGCGTGATATGATAGTACCAGAGCCAGAACGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





56

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGCTCGAGTGTATATGATAGTACCAGAGCAGCATCGACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





57

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGTACTACTGCGTCTGATAGTACCAGAGCTGATGCTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





58

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGTGTGGTGTGTACTGATAGTACCAGAGCGATCCTGACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





59

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGGCGACACTGATATGATAGTACCAGAGCACATCGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





60

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGGCGAGATATAGATGATAGTACCAGAGCGATGAGTGC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





61

custom-character  column 7

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1
AGCCTCGAGTAGCTGTGCTGCACATGATAGTACCAGAGCAGCTTCAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





62
, column 8 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



5 page 1 custom-character
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





63

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGTGACACTCACAGTGATAGTACCAGAGCCTACACAGC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





64

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGTATGTAGCTGCGTGATAGTACCAGAGCTAGCCACTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





65

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGCATCCATGCTGATGATAGTACCAGAGCAGTGATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





66

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGCGACGAGCCATATGATAGTACCAGAGCCATCATGCC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





67

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGCGATGTGTTACTTGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





68

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1 custom-character .txt
AGCCTCGAGTAGACATCTCGTCACTGATAGTACCAGAGCACGCATCACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





69

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1
AGCCTCGAGTAGGTGCTACATAGTTGATAGTACCAGAGCGTGATGCTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





70
○ column 16
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1
AGCCTCGAGTAGCACACATCTAGTTGATAGTACCAGAGCTGACCTAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





71
\n column 17
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCACTGAGTCATA



row 5 page 1
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGTCACACCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





72

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGATAGGCATCGACTGATAGTACCAGAGCCAGAACGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





73

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGAGATCACGGCAGTGATAGTACCAGAGCAGCATCGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





74

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGAGTCGAGAATCTTGATAGTACCAGAGCTGATGCTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





75

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGTAGCGAGCTCATTGATAGTACCAGAGCGATCCTGACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





76

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1
AGCCTCGAGTAGGCGACAGTTACATGATAGTACCAGAGCACATCGCTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





77

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGATCGATCTTCTCTGATAGTACCAGAGCGATGAGTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





78

custom-character  column 7

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1
AGCCTCGAGTAGAGCACAGAACTGTGATAGTACCAGAGCAGCTTCAGC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





79
, column 8 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



6 page 1 custom-character .txt
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





80

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1
AGCCTCGAGTAGCAGCTGACTCACTGATAGTACCAGAGCCTACACAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





81

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1
AGCCTCGAGTAGCAGCCTGACATGTGATAGTACCAGAGCTAGCCACTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





82

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGACTCTGCATCATTGATAGTACCAGAGCAGTGATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





83

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGTCATAGCGATCTTGATAGTACCAGAGCCATCATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





84

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGTATCGCTGTGTGTGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





85

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGGTGACGCGTGTATGATAGTACCAGAGCACGCATCAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





86

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGCGCACTGCATGATGATAGTACCAGAGCGTGATGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





87

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



column 16
AGCCTCGAGTAGCACACATCTAGTTGATAGTACCAGAGCTGACCTAGCT



row 6 page 1 custom-character .txt
ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





88
\n column 17
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCCTACGATGATA



row 6 page 1 custom-character .txt
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGTCACACCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





89

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGCGACGAGCCATATGATAGTACCAGAGCCAGAACGAC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





90

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGCTCAGATGGCATTGATAGTACCAGAGCAGCATCGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





91

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGACTCTAGTGTGATGATAGTACCAGAGCTGATGCTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





92
! column 4
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 
AGCCTCGAGTAGATATGTGCGTGTTGATAGTACCAGAGCGATCCTGACT




custom-character
custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





93

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGCGACGAGCCATATGATAGTACCAGAGCACATCGCTC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





94

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGCTCAGATGGCATTGATAGTACCAGAGCGATGAGTGC




custom-character .txt

TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





95

custom-character  column 7

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page
AGCCTCGAGTAGACTCTAGTGTGATGATAGTACCAGAGCAGCTTCAGCT



1 custom-character .txt
ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





96

custom-character  column 8

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



Row 7 page 1
AGCCTCGAGTAGATATGTGCGTGTTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





97

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGCTCGCTGTACTATGATAGTACCAGAGCCTACACAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





98

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGACAGGCTGAGCTTGATAGTACCAGAGCTAGCCACTCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





99

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 
AGCCTCGAGTAGCTCAGATGGCATTGATAGTACCAGAGCAGTGATGCCT



1 custom-character .txt
ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





100
, column 12
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCATCATGCCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





101

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGGCATGTAGGCTCTGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





102

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGGTCTGAGATGATTGATAGTACCAGAGCACGCATCACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





103

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGACATGACTGCGTTGATAGTACCAGAGCGTGATGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





104
? column 16
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGATCACATGACTCTGATAGTACCAGAGCTGACCTAGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





105
\n column 17
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGCAGATGTATA



row 7 page 1 custom-character .txt
AGCCTCGAGTAGGTCAACGCTCATTGATAGTACCAGAGCTGTCACACCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





106

custom-character  column 1

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page
AGCCTCGAGTAGGCGTAGCTGTACTGATAGTACCAGAGCCAGAACGAC



1 custom-character .txt
TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





107

custom-character  column 2

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGGCAGGACACTGTTGATAGTACCAGAGCAGCATCGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





108

custom-character  column 3

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGGACGGTCAAGTGTGATAGTACCAGAGCTGATGCTGC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





109

custom-character  column 4

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGTGCGCATGACAGTGATAGTACCAGAGCGATCCTGAC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





110

custom-character  column 5

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGACTAATACGTCGTGATAGTACCAGAGCACATCGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





111

custom-character  column 6

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGCTACCGACTCTGTGATAGTACCAGAGCGATGAGTGCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





112
column 7
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1
AGCCTCGAGTAGTCTCACAGTAGCTGATAGTACCAGAGCAGCTTCAGCT




custom-character
custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





113
, column 8 row
AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



8 page 1 custom-character
AGCCTCGAGTAGCACGGTCTCGATTGATAGTACCAGAGCCTAGCTCACT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





114

custom-character  column 9

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1
AGCCTCGAGTAGTCACCACTTCTATGATAGTACCAGAGCCTACACAGCT




custom-character .txt

ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





115

custom-character  column 10

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGAGCTCACAGCGTTGATAGTACCAGAGCTAGCCACTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





116

custom-character  column 11

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGCGAGGATCACACTGATAGTACCAGAGCAGTGATGCC




TACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





117

custom-character  column 12

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGAGCTTGACGTATTGATAGTACCAGAGCCATCATGCCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





118

custom-character  column 13

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGTGAGTCAGACATTGATAGTACCAGAGCTGCAACGTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





119

custom-character  column 14

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGTAGTACTGTCGCTGATAGTACCAGAGCACGCATCACT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





120

custom-character  column 15

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



row 8 page 1 custom-character .txt
AGCCTCGAGTAGTGTGCTATCACTTGATAGTACCAGAGCGTGATGCTCT




ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA





121

AGCTATACGGAGCATCGTGAGATTAGTCAACTAGCCTCGTCATCGTATA



column 16
AGCCTCGAGTAGCACACATCTAGTTGATAGTACCAGAGCTGACCTAGCT



row 8 page 1 custom-character .txt
ACATGTCCAGGCAATGCCGTAGCTTGTGACAGCATA









Although the disclosure has been described with reference to the exemplary embodiments, it should be understood that the disclosure is not limited to the disclosed exemplary embodiments. Without departing from the scope or spirit of the disclosure, various adjustments or changes can be made to the exemplary embodiments of the present specification. The scope of the claims should be based on the broadest interpretation to cover all modifications and equivalent structures and functions.

Claims
  • 1. A method for DNA movable type storage mainly comprising: (1) construct a physical movable type library of payloads and a physical movable type library of indexes based on “DNA movable type codebook”, which consist of a variety of DNA oligonucleotides corresponding to all “DNA payload movable type elements” and “DNA index movable type elements” in the two libraries, respectively,(2) transcode from the binary data of the target storage file into a variety of DNA movable type units (containing DNA payload and index movable type elements), assign the corresponding “DNA index movable type elements” to each “DNA payload movable type element”, and map all of them to corresponding DNA oligonucleotides from the two abovementioned libraries based on DNA movable type encoding principle from “DNA movable type codebook”,(3) link the physical DNA payload movable type elements with their related physical DNA movable type index elements in step (2) to generate a physical “DNA movable type unit”, and then put all generated “DNA movable type units” together for DNA data storage, which cover all data information of the target file,(4) sequencing all oligonucleotides in the storage library in step (3), and decode the sequencing results based on “DNA movable type decoding principle” from “DNA movable type codebook”.
  • 2. The method for DNA movable type storage according to claim 1, wherein binary data of the target storage file are selected from at least one of text, image, audio and video.
  • 3. The method for DNA movable type storage according to claim 1, wherein the DNA payload movable type elements are selected from at least one of a character, a pixel, an audio amplitude and a video frame; and the DNA index movable type elements comprise location and attribute information of a DNA payload movable type element.
  • 4. The method for DNA movable type storage according to claim 3, wherein the location information of a DNA payload movable type elements comprises information of page number, row and column.
  • 5. The method for DNA movable type storage according to claim 3, wherein the attribute information of a DNA payload movable type element comprises file type, file name, file size, and creation time.
  • 6. The method for DNA movable type storage according to claim 1, wherein the linker sequences are comprised among the oligonucleotides of “DNA payload movable type elements” and the oligonucleotides of “DNA index movable type elements” in a DNA movable type unit.
  • 7. The method for DNA movable type storage according to claim 6, wherein the linker sequences are overlapping sequences or enzymatically cleavable linker sequences.
  • 8. A system for DNA movable type storage comprising: a. a library of DNA oligonucleotides corresponding to all “DNA payload movable type elements” and a library of DNA oligonucleotides corresponding to all “DNA index movable type elements”;b. an encoding module/software provides for splitting binary data of the target storage file to a variety of DNA payload movable type elements, assign related “DNA index movable type elements” to each “DNA payload movable type element”, map them to corresponding DNA oligonucleotides from the libraries based on “DNA movable type encoding principle” from “DNA movable type codebook”, andc. a decoding module/software provides for decoding the sequencing data from the oligonucleotides in a library for a DNA movable type storage file into corresponding binary data of target storage file, according to “DNA movable type encoding principle” from “DNA movable type codebook” using a corresponding decoding software.
  • 9. The system for DNA movable type storage according to claim 8, wherein the system further comprises a system for DNA linker design and a system for DNA sequencing.
Priority Claims (1)
Number Date Country Kind
202010688281.X Jul 2020 CN national
PCT Information
Filing Document Filing Date Country Kind
PCT/CN2021/098663 6/7/2021 WO