Splice variant caller for RNA

The processor-based nucleic acid sequence processing system effectively identifies and characterizes splice variants in RNA sequences by mapping and aligning reads to a reference sequence, addressing the challenge of processing variations in unspliced DNA transcripts and enhancing genetic and disease-related analysis.

WO2026235974A1PCT designated stage Publication Date: 2026-11-12ILLUMINA INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/025790
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-11-18
Filing Date
2026-04-29
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing methods struggle to accurately identify and characterize splice variants in RNA sequences, particularly due to variations in how unspliced DNA transcripts are processed into functional forms, which are crucial for understanding genetic and disease-related characteristics.

Method used

A processor-based nucleic acid sequence processing system that receives nucleic acid sequence reads, maps and aligns them to a reference sequence, and processes alignment outputs to generate splice variant outputs, utilizing processor-executable code and memory structures to facilitate accurate identification of splice variants.

Benefits of technology

Enables efficient and accurate detection of splice variants and gene fusions in RNA sequences, providing comprehensive insights into genetic and disease-related characteristics.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026025790_12112026_PF_FP_ABST
    Figure US2026025790_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates in general to a processor-based nucleic acid sequence processing system. In accordance with certain implementations, the processor-based nucleic acid sequence processing system may comprise: one or more processing circuits configured to access and execute processor-executable code and one or more memory structures configured to store the processor executable code. In such an implementation, the processor executable code, when accessed and executed by the one or more processing circuits, causes acts to be performed comprising: receiving as an input a plurality of nucleic acid sequence reads; mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.
Need to check novelty before this filing date? Find Prior Art

Description

SPLICE VARIANT CALLER FOR RNABACKGROUND

[0001] Aspects of the present disclosure relate generally to devices, systems, and methods providing biological or chemical analysis. Various protocols in biological or chemical research involve performing a large number of controlled reactions on local support surfaces or within predefined reaction chambers. The designated reactions may then be observed or detected, and subsequent analysis may help identify or reveal properties of chemicals involved in the reaction. For example, in some multiplex assays, an unknown analyte having an identifiable label (e.g., fluorescent label) may be exposed to thousands of known probes under controlled conditions. Each known probe may be deposited into a corresponding well of a flow cell channel. Observing any chemical reactions that occur between the known probes and the unknown analyte within the wells may help identify or reveal properties of the analyte. Other examples of such protocols include known DNA and / or RNA sequencing processes, such as sequencing-by-synthesis (SBS) or cyclic-array sequencing.

[0002] While a variety of devices, systems, and methods have been made and used to perform biological or chemical analysis, it is believed that no one prior to the inventor(s) has made or used the devices and techniques described herein.

[0003] With the preceding in mind, it may be appreciated that factors in addition to the genetic sequence alone influence characteristics (e.g., development, disease states, and more) that are of interest to researchers and clinicians. Correspondingly, researchers and clinicians have turned to multiomics approaches for looking at the transcriptome, epigenome, and proteome, in addition to the genome. By looking into these additional research areas that extend beyond genetic sequence alone, researchers hope to find comprehensive answers to developmental and / or disease state questions of interest.

[0004] By way of example, RNA sequencing offers a technique for analyzing gene expression across the transcriptome, illuminating changes and characterizing various RNA forms. Such techniques may help uncover transcript isoforms, gene fusions, single nucleotide variants (SNVs), and so forth. One factor which those studying RNA must address, however, is the existence ofvariations in how unspliced DNA transcripts, such as mRNA precursor strands, are processed into functional forms. By way of example, an expressed unspliced DNA transcript (e.g., a pre-mRNA) may undergo splicing in order for it to become a useful or functional mRNA strand. Such splicing operations typically are associated with splice sites within the transcript where the initial transcript is cut and / or ligated to facilitate the transition to a functional, spliced form. For example, a spliceosome may remove intronic regions of a pre-mRNA strand while retaining coding regions (i.e., exonic regions) in order to form a functional mRNA strand. In practice, however, there may be sequence variations in the initial transcript, such as due to underlying genetic code variation, that can give rise to splice variants for a given transcript and individual. Such splice variants may be of interest to a researcher, but otherwise difficult to identify and / or characterize.SUMMARY

[0005] A summary of certain embodiments disclosed herein is set forth below. It should be understood that these aspects are presented merely to provide the reader with a brief summary of these certain embodiments and that these aspects are not intended to limit the scope of this disclosure. Indeed, this disclosure may encompass a variety of aspects that may not be set forth below.

[0006] In one implementation, a processor-based nucleic acid sequence processing system is provided. In accordance with such an implementation, the processor-based nucleic acid sequence processing system may comprise: one or more processing circuits configured to access and execute processor-executable code and one or more memory structures configured to store the processor executable code. In such an implementation, the processor executable code, when accessed and executed by the one or more processing circuits, causes acts to be performed comprising: receiving as an input a plurality of nucleic acid sequence reads; mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0007] In a further implementation, a processor-implemented method is provided. In accordance with such an implementation, the method comprises: receiving as an input a plurality of nucleic acid sequence reads; mapping and aligning the plurality of nucleic acid sequence reads to areference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0008] In an additional implementation, one or more non-transitory media are provided comprising processor-executable routines. In accordance with this implementation, the processorexecutable routines, when executed by one or more processors, cause acts to be performed comprising: receiving as an input a plurality of nucleic acid sequence reads; mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0009] Various refinements of the features noted above may exist in relation to various aspects of the present disclosure. Further features may also be incorporated in these various aspects as well. These refinements and additional features may exist individually or in any combination. For instance, various features discussed below in relation to one or more of the illustrated embodiments may be incorporated into any of the above-described aspects of the present disclosure alone or in any combination. The brief summary presented above is intended only to familiarize the reader with certain aspects and contexts of embodiments of the present disclosure without limitation to the claimed subject matter.BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Various aspects of this disclosure may be better understood upon reading the following detailed description and upon reference to the drawings in which:

[0011] FIG. 1 depicts a schematic view of an example of a system that may be used to provide biological or chemical analysis, in accordance with aspects of the present disclosure.

[0012] FIG. 2 depicts a cross-sectional view of an example of a flow cell that may be used in the system of FIG. 1, in accordance with aspects of the present disclosure.

[0013] FIG. 3 depicts a schematic view of another example of a system that may be used to provide biological or chemical analysis, in accordance with aspects of the present disclosure.

[0014] FIG. 4 depicts a schematic view of an example of a networked system in which the system of FIG. 1 or 3 may be incorporated, in accordance with aspects of the present disclosure.

[0015] FIG. 5 depicts a schematic view of an example of a base calling arrangement that may be carried out using the system of FIG. 1, 3, or 4, in accordance with aspects of the present disclosure.

[0016] FIG. 6 depicts a process flow for calling splice variants in RNA sequence data, in accordance with aspects of the present disclosure.

[0017] FIG. 7 depicts a process flow for calling gene fusions events in conjunction with splice variants in RNA sequence data, in accordance with aspects of the present disclosure.

[0018] FIG. 8 depicts an example of a gene fusion event, in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0019] One or more specific embodiments will be described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers’ specific goals, such as compliance with system-related and enterprise-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

[0020] The following detailed description of certain examples will be better understood when read in conjunction with the appended drawings. To the extent that the figures illustrate diagrams of the functional blocks of various examples, the functional blocks are not necessarily indicative of the division between hardware components. Thus, for example, one or more of the functional blocks (e.g., processors or memories) may be implemented in a single piece of hardware (e.g., a general purpose signal processor or random access memory, hard disk, or the like). Similarly, theprograms may be stand-alone programs, may be incorporated as processor-executable routines or sub-routines in an operating system, may be functions in an installed software package, and the like. It should be understood that the various examples are not limited to the arrangements and instrumentality shown in the drawings.

[0021] I. Overview of System for Biological or Chemical Analysis

[0022] Examples described herein may be used in various biological or chemical processes and systems for analysis in the academic, commercial, medical, or other context. More specifically, examples described herein may be used in various processes and systems where it is desired to detect an event, property, quality, or characteristic that is indicative of a designated reaction (e.g., variant RNA splice activity, gene fusion events and their detection, and so forth). Bioassay systems such as those described herein may be configured to perform a plurality of designated reactions that may be detected individually or collectively. For example, bioassay systems may be used to sequence a dense array of nucleic acid features through iterative cycles of enzymatic manipulation and image acquisition. In some examples, nucleic acids can be attached to a surface and amplified. Examples of such amplification are described in U.S. Pat. No. 7,741,463, entitled “Method of Preparing Libraries of Template Polynucleotides,” issued June 22, 2010, the disclosure of which is incorporated by reference herein, in its entirety; and / or U.S. Pat. No. 7,270,981, entitled “Recombinase Polymerase Amplification,” issued September 18, 2007, the disclosure of which is incorporated by reference herein, in its entirety.

[0023] Components that are used in the bioassay systems may include one or more microfluidic channels that deliver reagents or other reaction components to a reaction site. The reaction sites may be randomly distributed across a substantially planar surface; or may be patterned across a substantially planar surface. Each of the reaction sites may be imaged to detect light from the reaction site. The signals indicating photons emitted from the reaction sites and detected by image sensors may provide illumination values. These illumination values may be combined into an image indicating photons as detected from the reaction sites. These images may be further analyzed to identify compositions, reactions, conditions, etc., at each reaction site.

[0024] II. Examples of Fluidics Devices and Fluid Flow Paths - Example of System with Higher Volume Throughput

[0025] FIG. 1 illustrates a schematic diagram of an example of a system 100 that may be used to perform an analysis on one or more samples of interest. In some implementations, the sample may include one or more clusters of nucleotides (e.g., DNA) that have been linearized to form a single stranded DNA (sstDNA). Further, in certain such examples, the DNA may be cDNA (and its complement) generated from an RNA sample via a reverse transcription process. In this manner, the DNA in question may be informative and / or indicative of an RNA sample. In the implementation shown, system 100 is configured to receive a flow cell cartridge assembly 102 including a flow cell assembly 103 and a sample cartridge 104. System 100 includes a flow cell receptacle 122 that receives flow cell cartridge assembly 102, a vacuum chuck 124 that supports flow cell assembly 103, and a flow cell interface 126 that is used to establish a fluidic coupling between system 100 and flow cell assembly 103. Flow cell interface 126 may include one or more manifolds. System 100 further includes a sipper manifold assembly 106, a sample loading manifold assembly 108, and a pump manifold assembly 110. System 100 also includes a drive assembly 112, a controller 114, an imaging system 116, and a waste reservoir 118. Controller 114 is electrically and / or communicatively coupled to drive assembly 112 and to imaging system 116; and is configured to cause drive assembly 112 and / or the imaging system 116 to perform various functions as disclosed herein.

[0026] In the present example, flow cell assembly 103 includes a flow cell 128 having a channel 130 and defining a plurality of first openings 132, which are fluidically coupled to the channel 130 and arranged on a first side 134 of the channel 130. Flow cell 128 further includes a plurality of second openings 136 fluidically coupled to the channel 130 and arranged on a second side 138 of the channel 130. Fluid may thus flow through flow cell 128 via channel(s) 130. While the flow cell 128 is shown including one channel 130, flow cell 128 may include two or more channels 130. Flow cell assembly 103 also includes a flow cell manifold assembly 140 coupled to flow cell 128 and having a first manifold fluidic line 142 and a second manifold fluidic line 144. Flow cell manifold assembly 140 may be in the form of a laminate including a plurality of layers as discussed in more detail below.

[0027] In the implementation shown, first manifold fluidic line 142 has a first fluidic line opening 146 and is fluidically coupled to each of the first openings 132 of flow cell 128; and second manifold fluidic line 144 has a second fluidic line opening 148 and is fluidically coupledto each of the second openings 136. As shown, flow cell assembly 103 includes gaskets 150 coupled to flow cell manifold assembly 140 and fluidically coupled to fluidic line openings 146, 148. In some implementations where flow cell 128 includes a plurality of channels 130, flow cell manifold assembly 140 may include additional fluidic lines 152 that couple first fluidic line openings 146 to a single manifold port 154. In such implementations, a single gasket 150 may be coupled to flow cell manifold assembly 140 that surrounds the manifold port 154 and is in fluidic communication with a plurality of channels 130. In operation, flow cell interface 126 engages with corresponding gaskets 150 to establish a fluidic coupling between system 100 and flow cell 128. The engagement between flow cell interface 126 and gaskets 150 reduces or eliminates fluid leakage between flow cell interface 126 and flow cell 128.

[0028] In the implementation shown, first manifold fluidic line 142 has a portion 156 that is substantially parallel to a longitudinal axis 158 of channel 130; and second manifold fluidic line 144 has a portion 160 that is substantially parallel to longitudinal axis 158 of channel 130. Additionally, first manifold fluidic line 142 is shown being at least partially adjacent a first end 162 of flow cell 128 and spaced from a second end 164 of flow cell 128; and second manifold fluidic line 144 is shown being at least partially adjacent second end 164 of flow cell 128 and spaced from first end 162. Other arrangements of manifold fluidic lines 142, 144 may prove suitable, however.

[0029] In the implementation shown, system 100 includes a sample cartridge receptacle 166 that receives sample cartridge 104 that carries one or more samples of interest (e.g., an analyte). System 100 also includes a sample cartridge interface 168 that establishes a fluidic connection with sample cartridge 104. Sample loading manifold assembly 108 includes one or more sample valves 170. Pump manifold assembly 110 includes one or more pumps 172, one or more pump valves 174, and a cache 176. Valves 170, 174 and pumps 172 may take any suitable form. Cache 176 may include a serpentine cache and may temporarily store one or more reaction components during, for example, bypass manipulations of the system 100. While cache 176 is shown being included in pump manifold assembly 110, cache 176 may alternatively be located elsewhere (e.g., in sipper manifold assembly 106 or in another manifold downstream of a bypass fluidic line 178, etc.).

[0030] Sample loading manifold assembly 108 and pump manifold assembly 110 flow one ormore samples of interest from sample cartridge 104 through a fluidic line 180 toward flow cell cartridge assembly 102. In some implementations, sample loading manifold assembly 108 may individually load or address each channel 130 of flow cell 128 with a respective sample of interest. The process of loading channel 130 with a sample of interest may occur automatically using system 100. As shown in FIG. 1, sample cartridge 104 and sample loading manifold assembly 108 are positioned downstream of flow cell cartridge assembly 102. In the implementation shown, sample loading manifold assembly 108 is coupled between flow cell cartridge assembly 102 and pump manifold assembly 110. To draw a sample of interest from sample cartridge 104 and toward pump manifold assembly 110, sample valves 170, pump valves 174, and / or pumps 172 may be selectively actuated to urge the sample of interest toward pump manifold assembly 110. Sample cartridge 104 may include a plurality of sample reservoirs that are selectively fluidically accessible via the corresponding sample valves 170. To individually flow the sample of interest toward channel 130 of flow cell 128 and away from pump manifold assembly 110, sample valves 170, pump valves 174, and / or pumps 172 may be selectively actuated to urge the sample of interest toward flow cell cartridge assembly 102 and into respective channels 130 of flow cell 128.

[0031] Drive assembly 112 interfaces with sipper manifold assembly 106 and pump manifold assembly 110 to flow one or more reagents that interact with the sample within flow cell 128. In some scenarios, a reversible terminator is attached to the reagent to allow a single nucleotide to be incorporated onto a growing DNA strand. In some such implementations, one or more of the nucleotides has a unique fluorescent label that emits a color when excited. The color (or absence thereof) is used to detect the corresponding nucleotide. In the implementation shown, imaging system 116 excites one or more of the identifiable labels (e.g., a fluorescent label) and thereafter obtains image data for the identifiable labels. The labels may be excited by incident light and / or a laser and the image data may include one or more colors emitted by the respective labels in response to the excitation. The image data (e.g., detection data) may be analyzed by system 100. Examples of features and functionalities that may be incorporated into imaging system 116 will be described in greater detail below.

[0032] After the image data is obtained, drive assembly 112 interfaces with sipper manifold assembly 106 and pump manifold assembly 110 to flow another reaction component (e.g., a reagent) through flow cell 128 that is thereafter received by waste reservoir 118 via a primarywaste fluidic line 182 and / or otherwise exhausted by system 100. Some reaction components may perform a flushing operation that chemically cleaves the fluorescent label and the reversible terminator from the sstDNA. The sstDNA may then be ready for another cycle.

[0033] The primary waste fluidic line 182 is coupled between pump manifold assembly 110 and waste reservoir 118. In some implementations, pumps 172 and / or pump valves 174 of pump manifold assembly 110 selectively flow the reaction components from flow cell cartridge assembly 102, through fluidic line 180 and sample loading manifold assembly 108 to primary waste fluidic line 182. Flow cell cartridge assembly 102 is coupled to a central valve 184 via flow cell interface 126. Central valve 184 is coupled with flow cell interface 126 via a fluidic line 185. An auxiliary waste fluidic line 186 is coupled to central valve 184 and to waste reservoir 118. In some implementations, auxiliary waste fluidic line 186 receives excess fluid of a sample of interest from flow cell cartridge assembly 102, via central valve 184, and flows the excess fluid of the sample of interest to waste reservoir 118 when back loading the sample of interest into flow cell 128, as described herein.

[0034] Sipper manifold assembly 106 includes a shared line valve 188 and a bypass valve 190. Shared line valve 188 may be referred to as a reagent selector valve. Central valve 184 and the valves 188, 190 of sipper manifold assembly 106 may be selectively actuated to control the flow of fluid through fluidic lines 192, 194, 196. Sipper manifold assembly 106 may be coupled to a corresponding number of reagent reservoirs 198 via reagent sippers 200. Reagent reservoirs 198 may contain fluid (e g., reagent and / or another reaction component). In some implementations, sipper manifold assembly 106 includes a plurality of ports. Each port of sipper manifold assembly 106 may receive one of the reagent sippers 200. Reagent sippers 200 may be referred to as fluidic lines. Some forms of reagent sippers 200 may include an array of sipper tubes extending downwardly along the z-dimension from ports in the body of sipper manifold assembly 106. Reagent reservoirs 198 may be provided in a cartridge, and the tubes of reagent sippers 200 may be configured to be inserted into corresponding reagent reservoirs 198 in the reagent cartridge so that liquid reagent may be drawn from each reagent reservoir 198 into the sipper manifold assembly 106.

[0035] Shared line valve 188 of sipper manifold assembly 106 is coupled to central valve 184 via shared reagent fluidic line 196. Different reagents may flow through shared reagent fluidic line196 at different times. In some versions, when performing a flushing operation before changing between one reagent and another, pump manifold assembly 110 may draw wash buffer through shared reagent fluidic line 196, central valve 184, and flow cell cartridge assembly 102.

[0036] Bypass valve 190 of sipper manifold assembly 106 is coupled to central valve 184 via dedicated reagent fluidic lines 194, 196. Each of the dedicated reagent fluidic lines 194, 196 may be associated with a single reagent. The fluids that may flow through dedicated reagent fluidic lines 194, 196 may be used during sequencing operations and may include a cleave reagent, an incorporation reagent, a scan reagent, a cleave wash, and / or a wash buffer.

[0037] Bypass valve 190 is also coupled to cache 176 of pump manifold assembly 110 via bypass fluidic line 178. One or more reagent priming operations, hydration operations, mixing operations, and / or transfer operations may be performed using bypass fluidic line 178. The priming operations, the hydration operations, the mixing operations, and / or the transfer operations may be performed independent of flow cell cartridge assembly 102. Thus, the operations using bypass fluidic line 178 may occur during, for example, incubation of one or more samples of interest within flow cell cartridge assembly 102. That is, shared line valve 188 may be utilized independently of bypass valve 190 such that bypass valve 190 may utilize bypass fluidic line 178 and / or cache 176 to perform one or more operations while shared line valve 188 and / or central valve 184 simultaneously, substantially simultaneously, or offset synchronously perform other operations.

[0038] Drive assembly 112 includes a pump drive assembly 202 and a valve drive assembly 204. Pump drive assembly 202 may be adapted to interface with one or more pumps 172 to pump fluid through flow cell 128 and / or to load one or more samples of interest into flow cell 128. Valve drive assembly 204 may be adapted to interface with one or more of the valves 170, 174, 184, 188, 190 to control the position of the corresponding valves 170, 174, 184, 188, 190.

[0039] Controller 114 of the present example includes a user interface 206, a communication interface 208, one or more processors 210, and a memory 212 storing instructions executable by the one or more processors 210 to perform various functions including the disclosed implementations. User interface 206, communication interface 133, and memory 212 are electrically and / or communicatively coupled to the one or more processors 210. User interface 206may be adapted to receive input from a user and to provide information to the user associated with the operation of system 100 and / or an analysis taking place. User interface 206 may include a touch screen, a display, a keyboard, a speaker(s), a mouse, a track ball, and / or a voice recognition system.

[0040] Communication interface 208 is adapted to enable communication between system 100 and a remote system(s) (e.g., computers) via a network(s) (e.g., the Internet, an intranet, a localarea network (LAN), a wide-area network (WAN), a coaxial-cable network, a wireless network, a wired network, a satellite network, a digital subscriber line (DSL) network, a cellular network, a Bluetooth connection, a near field communication (NFC) connection, etc.). Some of the communications provided to the remote system may be associated with analysis results, imaging data, etc. generated or otherwise obtained by system 100. Some of the communications provided to system 100 may be associated with a fluidics analysis operation, patient records, and / or a protocol(s) to be executed by system 100.

[0041] The one or more processors 210 and / or system 100 may include one or more of a processor-based system(s) or a microprocessor-based system(s). In some implementations, the one or more processors 210 and / or system 100 includes one or more of a programmable processor, a programmable controller, a microprocessor, a microcontroller, a graphics processing unit (GPU), a digital signal processor (DSP), a reduced-instruction set computer (RISC), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a field programmable logic device (FPLD), a logic circuit, and / or another logic-based device executing various routines and / or functions including the ones described herein.

[0042] Memory 212 may include one or more of a semiconductor memory, a magnetically readable memory, an optical memory, a hard disk drive (HDD), an optical storage drive, a solid-state storage device, a solid-state drive (SSD), a flash memory, a read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), a random-access memory (RAM), a non-volatile RAM (NVRAM) memory, a compact disc (CD), a compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a Blu-ray disk, a redundant array of independent disks (RAID) system, a cache and / or any other storage device or storage disk in which information is stored for any duration (e.g., permanently, temporarily, for extended periods of time, for buffering, for caching).

[0043] ITT. Examples of Flow Cell Structures

[0044] As noted above, a system 100 may execute reactions in a flow cell 128 and / or perform analysis on one or more samples of interest (e.g., RNA or reverse transcribed cDNA and complements derived from RNA) in a flow cell 128. The following describes examples of forms that such flow cells 128 may take, it being understood that flow cells 128 may take various other forms and have various other features in addition to or in lieu of the features described below.

[0045] Example of Single-Surface Patterned Flow Cell

[0046] FIG. 2 shows an example of a flow cell 128 that includes a patterned substrate 402, which includes depressions 404 separated by interstitial regions 406, and surface chemistry 410, 412 positioned in the depressions 404. Depressions 404 may be in the form of microwells or nanowells. Depressions 404 may be configured to contain nucleic acid strands or other oligonucleotides and thereby provide a reaction site for SBS and / or for other kinds of processes. In some versions, each depression 404 has a cylindraceous configuration, with a generally circular cross-sectional profile. In some other versions, each depression 404 has a polygonal (e.g., hexagonal, octagonal, square, rectangular, elliptical, etc.) cross-sectional profile. Alternatively, depressions 404 may have any other suitable configuration. It should also be understood that depressions 404 may be arranged in any suitable pattern, including but not limited to a grid pattern.

[0047] Surface chemistry 410, 412 of the present example includes functionalized coating layer 410 and primers 412. While not shown, it is to be understood that the depressions 404 may also have surface preparation or treatment chemistry (e.g., silane or a silane derivative) positioned between the substrate 402 and the functionalized coating layer 410. This same surface preparation or treatment chemistry may also be positioned on the interstitial regions 406. In the present example, a hydrogel 440 is applied before lid 420 is bonded to substrate 402. Hydrogel 440 covers surface chemistry 410, 412 in depressions 404, and at least a portion of the patterned substrate 402 (e.g., those interstitial regions 406 that are not also bonding regions 422). By way of example only, hydrogel 440 may comprise PAZAM, crosslinked polyacrylamide, agarose gel, etc.

[0048] Flow cell 128 of this example further includes a lid 420 bonded to bonding region(s) 422 of patterned substrate 402. In the example shown in FIG. 2, lid 420 includes a top portion 424 that is connected to several sidewalls 426, and these components 424, 426 define aportion of each of the six flow channels 430A, 430B, 430C, 430D, 430E, 430F. The respective sidewalls 426 isolate one flow channel from each adjacent flow channel. Each flow channel (430A, 430B, 430C, 430D, 430E, 430F) is in selective fluid communication with a respective set of depressions 404.

[0049] Lid 420 may be bonded to bonding region 422 of substrate 402 using any suitable technique, such as laser bonding, diffusion bonding, anodic bonding, eutectic bonding, plasma activation bonding, glass frit bonding, or other methods known in the art. In some versions, a spacer layer 428 may be used to bond lid 420 to bonding region 422. Spacer layer 428 may comprise any material that will seal at least some of interstitial regions 404 (e.g., bonding region 422) of substrate 402 and lid 420 together. While not shown, lid 420 or the patterned substrate 402 may include inlet and outlet ports that are to fluidically engage other ports (not shown), such as those of sample cartridge interface 168, for directing fluid(s) into the respective flow channels 430A, 430B, 430C, 430D, 430E, 430F (e.g., from a reagent cartridge or other fluid storage system) and out of the flow channel (e.g., to waste reservoir 118 or another waste removal system). Flow channels 430A, 430B, 430C, 430D, 430E, 430F may serve to, for example, selectively introduce reaction components or reactants to hydrogel 440 and the underlying surface chemistry 410, 412 in order initiate designated reactions in / at depressions 404.

[0050] While flow cell 128 includes a pattern of depressions 404 to provide an array of reaction sites, other variations may provide reaction sites on or at various other kinds of structural features, including but not limited to continuously planer surfaces and / or protruding surfaces, etc. By way of further example only, flow cell 128 may be constructed and operable in accordance with at least some of the teachings of U.S. Pat. No. 10,919,033, entitled “Flow Cells with Hydrogel Coating,” issued February 16, 2021, the disclosure of which is incorporated by reference herein, in its entirety.

[0051] IV. Examples of Imaging System Features

[0052] As noted above, system 100 includes an imaging system 116 that excites one or more identifiable labels (e.g., a fluorescent label) in samples in reaction sites provided by depressions 404, 462, 464 of a flow cell 128; and thereafter obtains image data for the identifiable labels. This image data is used to identify nucleotides as part of a nucleic acid sequencing process.Alternatively, the image data may be used for various other purposes. The following description provides details on how some versions of imaging system 116 may be configured and operable.

[0053] FIG. 3 illustrates a schematic diagram of another example of a system 500 that may be used to perform an analysis on one or more samples of interest. Except as otherwise described below, system 500 of this example may be configured and operable like systems 100 described above. System 500 is configured to perform a large number of parallel reactions within a flow cell 510. Flow cell 510 may be configured and operable like flow cells 128 described above or may have any other suitable configuration. Flow cell 510 may thus include one or more flow channels that receive a solution from system 500 and direct the solution toward reaction sites of flow cell 510.

[0054] System 500 includes a system controller 520 that may communicate with the various components, assemblies, and sub-systems of the system 500. Controller 520 may be configured and operable like controllers 114 described above. An imaging assembly 522 of system 500 includes a light emitting assembly 550 that emits light that reaches reaction sites on flow cell 510. Light emitting assembly 550 may include an incoherent light emitter (e.g., emit light beams output by one or more excitation diodes), or a coherent light emitter such as emitter of light output by one or more lasers or laser diodes. In some implementations, light emitting assembly 550 may include a plurality of different light sources (not shown), each light source emitting light of a different wavelength range. Some versions of light emitting assembly 550 may also include one or more collimating lenses (not shown), a light structuring optical assembly (not shown), a projection lens (not shown) that is operable to adjust a structured beam shape and path, epifluorescence microscopy components, and / or other components. Although system 500 is illustrated as having a single light emitting assembly 550, multiple light emitting assemblies 550 may be included in some other implementations.

[0055] In the present example, the light from light emitting assembly 550 is directed by dichroic mirror assembly 546 through an objective lens assembly 542 onto a sample of a flow cell 510, which is positioned on a motion stage 570. In the case of fluorescent microscopy of a sample, a fluorescent element associated with the sample of interest fluoresces in response to the excitation light, and the resultant light is collected by objective lens assembly 542 and is directed to an image sensor of camera system 540 to detect the emitted fluorescence. In some implementations, a tubelens assembly may be positioned between the objective lens assembly 542 and the dichroic mirror assembly 546 or between the dichroic mirror 546 and the image sensor of the camera system 540. A moveable lens element may be translatable along a longitudinal axis of the tube lens assembly to account for focusing on an upper interior surface or lower interior surface of the flow cell 510 and / or spherical aberration introduced by movement of the objective lens assembly 542.

[0056] In the present example, a filter switching assembly 544 is interposed between dichroic mirror assembly 546 and camera system 540. Filter switching assembly 544 includes one or more emission filters that may be used to pass through particular ranges of emission wavelengths and block (or reflect) other ranges of emission wavelengths. For example, emission filters may be used to direct different wavelength ranges of emitted light to different image sensors of the camera system 540 of imaging assembly 522. For instance, the emission filters may be implemented as dichroic mirrors that direct emission light of different wavelengths from flow cell 510 to different image sensors of camera system 540. In some variations, a projection lens is interposed between filter switching assembly 544 and camera system 540. Filter switching assembly 544 may be omitted in some versions.

[0057] System 500 further includes a fluid delivery assembly 590 that may direct the flow of reagents (e.g., fluorescently labeled nucleotides, buffers, enzymes, cleavage reagents, etc.) to (and through) flow cell 510 and waste valve 580. Fluid delivery assembly 590 may be configured and operable like the various fluid delivery components described herein. System 500 of the present example also includes a temperature station actuator 530 and heater / cooler 532 that may optionally regulate the temperature of conditions of the fluids within the flow cell 510. In some implementations, the heater / cooler 532 may be fixed to sample stage 570, upon which the flow cell 510 is placed, and / or may be integrated into sample stage 570.

[0058] Flow cell 510 may be removably mounted on sample stage 570, which may provide movement and alignment of flow cell 510 relative to objective lens assembly 542. Sample stage 570 may have one or more actuators to allow sample stage 570 to move in any of three dimensions. For example, actuators may be provided to allow sample stage 570 to move in the x, y, and z directions relative to objective lens assembly 542, tilt relative to objective lens assembly 542, and / or otherwise move relative to objective lens assembly 542. Movement of sample stage 570 may allow one or more sample locations on flow cell 510 to be positioned in optical alignmentwith objective lens assembly 542. Movement of sample stage 570 relative to objective lens assembly 542 may be achieved by moving sample stage 570 itself, by moving objective lens assembly 542, by moving some other component of imaging assembly 522, by moving some other component of system 500, or any combination of the foregoing. For instance, in some implementations, the sample stage 570 may be actuatable in the x and y directions relative to the objective lens assembly 542 while a focus component 562 or z-stage may move the objective lens assembly 542 along the z direction relative to the sample stage 570.

[0059] In some implementations, a focus component 562 may be included to control positioning of one or more elements of objective lens assembly 542 relative to the flow cell 510 in the focus direction (e.g., along the z-axis or z-dimension). Focus component 562 may include one or more actuators physically coupled to the objective lens assembly 542, the optical stage, the sample stage 570, or a combination thereof, to move flow cell 510 on sample stage 570 relative to the objective lens assembly 542 to provide proper focusing for the imaging operation. In the present example, the focus component 562 utilizes a focus tracking module 560 that is configured to detect a displacement of the objective lens assembly 542 relative to a portion of the flow cell 510 and output data indicative of an in-focus position to the focus component 562 or a component thereof or operable to control the focus component 562, such as controller 520, to move the objective lens assembly 542 to position the corresponding portion of the flow cell 510 in focus of the objective lens assembly 542.

[0060] In some implementations, an actuator of focus component 562 or for sample stage 570 may be physically coupled to objective lens assembly 542, the optical stage, sample stage 570, or a combination thereof, such as, for example, by mechanical, magnetic, fluidic, or other attachment or contact directly or indirectly to or with the stage or a component thereof. The actuator of focus component 562 may be configured to move objective lens assembly 542 in the z-direction while maintaining sample stage 570 in the same plane (e.g., maintaining a level or horizontal attitude, perpendicular to the optical axis). In some implementations, sample stage 570 includes an x direction actuator and a y direction actuator to form an x-y stage. Sample stage 570 may also be configured to include one or more tip or tilt actuators to tip or tilt sample stage 570 and / or a portion thereof, to account for any slope in its surfaces.

[0061] Camera system 540 may include one or more image sensors to monitor and track theimaging (e.g., sequencing) of flow cell 510. Camera system 540 may be implemented, for example, as a CCD or CMOS image sensor camera, but other image sensor technologies (e.g., active pixel sensor) may be used. By way of further example only, camera system 540 may include a dualsensor time delay integration (TDI) camera, a single-sensor camera, a camera with one or more two-dimensional image sensors, and / or other kinds of camera technologies. While camera system 540 and associated optical components are shown as being positioned above flow cell 510 in FIG.3, one or more image sensors or other camera components may be incorporated into system 500 in numerous other ways as will be apparent to those skilled in the art in view of the teachings herein. For instance, one or more image sensors may be positioned under flow cell 510, such as within the sample stage 570 or below the sample stage 570, or may even be integrated into flow cell 510.

[0062] V. Examples of Data Processing Features

[0063] A. Example of Networked Data Processing Arrangement

[0064] As noted above, a system 100, 500 may include a controller 114, 520 that is configured to process data, execute algorithms, etc., as needed to perform a sequencing operation or other kind of operation. In some scenarios, system 100, 500 may be coupled with other devices via a network to perform further data processing, data storage, execution of algorithms, etc. FIG. 4 shows an example of such an arrangement. In particular, FIG. 4 shows a networked system 800 that includes a sequencing device 810, a server device 820, a client device 830, and a local device 840, with all devices 810, 820, 830, 840 being coupled together via a network 850. Network 850 may take any suitable form as will be apparent to those skilled in the art in view of the teachings herein.

[0065] As shown in FIG. 4, sequencing device 810 comprises a computing device and a sequencing device system 812 for sequencing a genomic sample or other nucleic-acid polymer. In some versions, by executing sequencing device system 812 using a processor, sequencing device 810 analyzes nucleotide fragments or oligonucleotides extracted from genomic samples to generate nucleotide reads or other data utilizing computer implemented methods and systems either directly or indirectly on sequencing device 810. More particularly, sequencing device 810 receives nucleotide-sample slides (e.g., flow cells (128, 510)) comprising nucleotide fragmentsextracted from samples and further copies and determines the nucleobase sequence of such extracted nucleotide fragments. It should be understood that sequencing device 810 may represent a version of systems 100, 500 described above.

[0066] In some versions, the sequencing device 810 utilizes SBS to sequence nucleotide fragments into nucleotide reads and determine nucleobase calls for the nucleotide reads. By executing sequencing device system 812, sequencing device 810 may further store the nucleobase calls as part of base-call data that is formatted as a binary base call (BCL) file and send the BCL file to the local device 840 and / or the server device(s) 820. Sequencing device 810 may communicate the BCL file and / or other data to local device 840 and / or client device 830 via network 850 or directly (i.e., bypassing network 850).

[0067] In some scenarios, local device 840 is located at or near a same physical location of sequencing device 810. For instance, local device 840 and sequencing device 810 may be integrated into a single computing device. Local device 840 may run sequencing system 814 to generate, receive, analyze, store, and transmit digital data, such as by receiving base-call data or determining base-level methylation based on analyzing such base-call data. By executing software in the form of sequencing system 814, local device 840 may align nucleotide reads with a reference genome(s) 824 and determine genetic variants, base-level methylation states, and so forth based on the aligned nucleotide reads. Local device 840 may also send data to client device 830, including a variant call file (VCF) or other information indicating nucleobase calls, sequencing metrics, error data, or other metrics.

[0068] Server device(s) 820 may be located remotely from the local device 840 and sequencing device 810. Server device(s) 820 may comprise a distributed collection of servers, where server device(s) 820 include a number of server devices distributed across network 850 and located in the same or different physical locations. Similar to local device 840, server device(s) 820 may include a version of sequencing system 814. Accordingly, server device(s) 820 may generate, receive, analyze, store, and transmit digital data, such as by receiving base-call data or determining splice variant calls, gene fusion calls, and so forth based on analyzing such base-call data. As indicated above, sequencing device 810 may send (and server device(s) 820 may receive) basecall data from sequencing device 810. Server device(s) 820 may also send data to client device 830, including VCFs or other sequencing related information.

[0069] By executing a sequencing application 832, client device 830 may generate, store, receive, and send digital data. In particular, client device 830 may receive sequencing data from local device 840 or receive call files (e.g., BCL) and sequencing metrics from sequencing device 810. Furthermore, client device 830 may communicate with local device 840 or server device(s) 820 to receive a VCF comprising nucleobase calls and / or other metrics, such as a base-call-quality metrics or pass-filter metrics. Client device 830 may accordingly present or display information pertaining to variant calls (e.g., splice variant calls, gene fusion calls) or other nucleobase calls within a graphical user interface of sequencing application 832 to a user associated with client device 830. For example, client device 830 may present variant calls and / or sequencing metrics for a sequenced sample within a graphical user interface of sequencing application 832.

[0070] As shown in FIG. 4, sequencing application 832 is included in client device 830. Sequencing application 832 may include a web application or a native application stored and executed on client device 830 (e g., a mobile application, desktop application). Sequencing application 832 may include instructions that (when executed) cause client device 830 to receive data from sequencing system 814 and present, for display at client device 830, base-call data or data from a VCF. Furthermore, sequencing application 832 may instruct client device 830 to display summaries for multiple sequencing runs.

[0071] As further illustrated in FIG. 4, a version of sequencing system 814 may be located and implemented (e.g., entirely or in part) on client device 830 or sequencing device 810. In some versions, sequencing system 814 is implemented by one or more other components of networked system 800, such as local device 840. In particular, sequencing system 814 may be implemented in a variety of different ways across sequencing device 810, local device 840, server device(s) 820, and client device 830. For example, sequencing system 814 may be downloaded from server device(s) 820 to sequencing system 814 and / or local device 840 where all or part of the functionality of sequencing system 814 is performed at each respective device within networked system 800.

[0072] B. Examples of Base Calling Schemes

[0073] FIG. 5 illustrates a system 900 that employs two or more base callers for base calling operations on the raw images (z.e., sensor data) output by image sensors in a sequencing machine910. Sequencing machine 910 of this example includes or processes a flow cell 912, which includes a plurality of tiles 914. Each tile 914 includes a plurality of clusters 916. Sequencing machine 910 may be understood to represent a version of systems 100, 500 or sequencing device 810 described above; while flow cell 912 may be understood to represent a version of flow cells 128, 510 described above. Sequencing machine 910 thus outputs sensor data 920 comprising raw images from the tiles 914 of flow cell 912.

[0074] In the present example, system 900 comprises a first base caller 922 and a second base caller 926, though some variations may include more than two base callers 922, 926. Each base caller 922, 926 of this example outputs corresponding base call classification information. For example, first base caller 922 outputs first base call classification information 924; and second base caller 926 outputs second base call classification information 928. A base calling combining module 930 generates final base calls 932, based on one or both first base call classification information 924 and / or second base call classification information 928. In some versions, first base caller 922 is a neural -network based base-caller; while second base caller 926 is a non-neural network based base-caller. For example, first base caller 922 may include a non-linear system employing one or more neural network models for base calling. The first base caller 922 may also be referred to as a DeepRTA (Deep Real Time Analysis) base caller or Deep Neural Network base caller.

[0075] By way of further example only, second base caller 926 may include, at least in part, a linear system used for base calling. For example, some versions of second base caller 926 do not employ a neural network for base calling (or use a smaller neural network model for base calling, compared to a larger neural network model used by first base caller 922). Second base caller 926 may also be referred to as an RTA (Real Time Analysis) base caller. An RTA base caller may use linear intensity extractors to extract features from sequencing images for base calling. In some such versions, RTA performs a template generation step to produce a template image that identifies locations of clusters 916 on a tile 914 using sequencing images from some number of initial sequencing cycles called template cycles. The template image is used as a reference for subsequent registration and intensity extraction steps. The template image is generated by detecting and merging bright spots in each sequencing image of the template cycles, which in turn involves sharpening a sequencing image (e.g., using the Laplacian convolution), determining an “on”threshold by a spatially segregated Otsu approach, and subsequent five-pixel local maximum detection with subpixel location interpolation.

[0076] In another example, locations of clusters 916 on a tile 914 are identified using fiducial markers. A solid support upon which a biological specimen is imaged may include such fiducial markers, to facilitate determination of the orientation of the specimen or the image thereof in relation to probes that are attached to the solid support. Examples of fiducials include, but are not limited to, beads (with or without fluorescent moieties or moieties such as nucleic acids to which labeled probes can be bound), fluorescent molecules attached at known or determinable features, or structures that combine morphological shapes with fluorescent moieties.

[0077] RTA then registers a current sequencing image against the template image. This is achieved by using image correlation to align the current sequencing image to the template image on a sub-region, or by using non-linear transformations (e.g., a full six-parameter linear affine transformation). RTA generates a color matrix to correct cross-talk between color channels of the sequencing images. RTA implements empirical phasing correction to compensate noise in the sequencing images caused by phase errors. After different corrections are applied to the sequencing images, RTA extracts signal intensities for each spot location in the sequencing images. For example, for a given spot location, signal intensity may be extracted by determining a weighted average of the intensity of the pixels in a spot location. For example, a weighted average of the center pixel and neighboring pixels may be performed using bilinear or bicubic interpolation. In some implementations, each spot location in the image may comprise a few pixels (e g., 1-5 pixels). RTA then spatially normalizes the extracted signal intensities to account for variation in illumination across the sampled imaged. For example, intensity values may be normalized such that a 5th and 95th percentiles have values of 0 and 1, respectively. The normalized signal intensities for the image (e.g., normalized intensities for each channel) may be used to calculate mean chastity for the plurality of spots in the image.

[0078] In some implementations, RTA uses an equalizer to maximize the signal-to-noise ratio of the extracted signal intensities. The equalizer may be trained (e.g., using least square estimation, adaptive equalization algorithm) to maximize the signal-to-noise ratio of cluster intensity data in sequencing images. In some implementations, the equalizer is a lookup table (LUT) bank with a plurality of LUTs with subpixel resolution, also referred to as “equalizer filters” or “convolutionkernels.” By way of example only, the number of LUTs in the equalizer may depend on the number of subpixels into which pixels of the sequencing images can be divided. For example, if the pixels are divisible into / / -by-n subpixels (e.g., 5 x 5 subpixels), then the equalizer generates n2LUTs (e g., 25 LUTs).

[0079] In some implementations of training the equalizer, data from the sequencing images is binned by well subpixel location. It should be understood that a “well” may include depressions 404 of a flow cell 128 or any other kind of reaction site (e.g., in a flow cell or otherwise). In an example of sequencing images being binned by well subpixel location, for a 5 x 5 LUT, l / 25th of the wells have a center that is in bin (1,1) (e.g., the upper left corner of a sensor pixel), l / 25th of the wells are in bin (1,2), and so on. The equalizer coefficients for each bin may be determined using least squares estimation on the subset of data from the wells corresponding to the respective bins. This way, the resulting estimated equalizer coefficients are different for each bin. Each LUT / equalizer filter / convolution kernel has a plurality of coefficients that are learned from the training. The number of coefficients in a LUT may correspond to the number of pixels that are used for base calling a cluster. For example, if a local grid of pixels (image or pixel patch) that is used to base call a cluster is of size p xp (e g., 9x 9 pixel patch), then each LUT has p2coefficients (e.g., 81 coefficients). The training may produce equalizer coefficients that are configured to mix / combine intensity values of pixels that depict intensity emissions from a target cluster being base called and intensity emissions from one or more adjacent clusters in a manner that maximizes the signal-to-noise ratio. The signal maximized in the signal -to-noise ratio is the intensity emissions from the target cluster, and the noise minimized in the signal-to-noise ratio is the intensity emissions from the adjacent clusters, i.e., spatial crosstalk, plus some random noise (e.g., to account for background intensity emissions). The equalizer coefficients are used as weights and the mixing / combining includes executing element-wise multiplication between the equalizer coefficients and the intensity values of the pixels to calculate a weighted sum of the intensity values of the pixels, i.e., a convolution operation.

[0080] RTA then performs base calling by fitting a mathematical model to the optimized intensity data. Suitable mathematical models that can be used include, for example, a k-means clustering algorithm, a k-means-like clustering algorithm, expectation maximization clustering algorithm, a histogram-based method, and the like. Four Gaussian distributions may be fit to theset of two-channel intensity data such that one distribution is applied for each of the four nucleotides represented in the data set. In some implementations, an expectation maximization (EM) algorithm may be applied. As a result of the EM algorithm, for each X, Y value (referring to each of the two channel intensities respectively) a value may be generated which represents the likelihood that a certain X, Y intensity value belongs to one of four Gaussian distributions to which the data is fitted. Where four bases give four separate distributions, each X, Y intensity value will also have four associated likelihood values, one for each of the four bases. The maximum of the four likelihood values indicates the base call. For example, if a cluster is “off’ in both channels, the base call is G. If the cluster is “off’ in one channel and “on” in another channel the base call is either C or T (depending on which channel is on), and if the cluster is “on” in both channels the base call is A.

[0081] In some implementations of RTA, the base calling errors get averaged out across many training examples. In some other implementations, the ground truth may be sourced using aligned genomic data, which may provide better quality because aligned genomic data may use reference genome and truth information that incorporate the knowledge gained from multiple sequencing platforms and sequencing runs to average out the noise. The ground truth may include basespecific intensity values (or feature values) that reliably represent intensity profiles of bases A, C, G, and T, respectively. A base caller like RTA base caller 926 base calls clusters by processing the sequencing images and producing, for each base call, color-wise intensity values / outputs. The color-wise intensity values may be considered base-wise intensity values because, depending on the type of chemistry (e.g., 2-color chemistry or 4-color chemistry), the colors map to each of the bases A, C, G, and T. The base with the closest matching intensity profile is called.

[0082] VI. Examples of Processing of RNA Sequencing Data

[0083] The sequencing systems and methodologies described herein may be utilized in various contexts for the generation of RNA splice variant and / or RNA gene fusion detection data with respect to a given genome or sample. By way of background, as part of generating proteins and other biochemical products coded by DNA, portions of that DNA (i.e., genes) are transcribed to an RNA intermediary (i.e., mRNA) that is in turn translated to a protein or other translation product. In many instances the transcription product of the DNA is itself modified prior to being translated in order to form the appropriate mRNA sequences. Thus, the direct transcription productmay constitute a pre-mRNA strand from which portions may be removed (i.e., intronic regions) and the remainder ligated together to form the mRNA to be translated. The locations of the pre-mRNA that are cut and subsequently ligated may, in some instances, be subject to variant sequences, which can lead to splice variants for a given sequence, and corresponding variants in the translation product. That is, for each gene there may be different splice variants which may in turn lead to variations in functionality (i.e., isoforms) for the translation product (e.g., a protein or enzyme). In this manner, splice variants may cause loss of function (LOF) in the translated product, which could lead to amplification of the function of another protein.

[0084] As discussed herein, such splice variants may be detected as part of a secondary analysis in the context of an RNA sequencing operation. As may be understood, in a nucleic acid sequencing context the primary analysis may be equated to the base calling and quality scoring aspects of the sequencing operation and analysis. The secondary analysis, in turn, may correspond to the alignment and variant calling (e.g., splice variant calling, gene fusion detection, and so forth) based on the sequence data generated as part of primary analysis. Correspondingly, tertiary analysis may be understood to relate to the biological interpretation and application analysis performed on the outputs of the secondary analysis. With this in mind, the splice variant caller functionality as described herein may be implemented as part of secondary analysis and utilized to find (i.e., call) splice variants, which may be onco-markers or biomarkers for other genetic diseases.

[0085] By way of example, in certain implementations described herein splice variant caller functionality may include performing the alignment of sequencer generated reads (e.g., short reads, longs reads, paired end reads, and so forth) or, alternatively, accessing previously aligned read data. In the relevant RNA context, a splice aware aligner may then utilize annotation data to look for patterns of exons and introns that are spliced. In the presently described context, however, the described techniques provide a technical improvement by being able to identify transcript splice variants that have not been previously annotated and that are abnormal and which, correspondingly, may have a pathogenic impact. As discussed herein, one aspect of the technical solution involved in this identification process is the use of a mapper that uses an anchored alignment (e.g., an anchored hash table).

[0086] By way of example, and as discussed in greater detail below, the described processesmay be implemented as a sequence of steps or stages. Accordingly, a first phase of the process may be a coarse alignment operation of the sequence reads against the reference sequence. An aspect of such a process may include the identification of one or more discernible gaps in the alignment. Attempts to fill such gaps may be made by shortening matching seed length, which makes it easier to find matches in regions of interest. With respect to the aligned output, as discussed in greater detail below, potential splices are identified and each potential splice scored. Based on the scoring, lower scoring potential splices may be omitted or rejected from reporting or further consideration in favor of higher scoring potential splices. In certain aspects, scoring of potential splices may be based on motifs (e.g., dimers) that are utilized by spliceosomes for identifying start and end sites for splices. Correspondingly, such motifs may be indicative of potential splice cut or ligation sites as well as directionality of a potential splice. The presence of such motifs may, therefore, be a factor in scoring a potential splice. Conversely, the absence of such motifs with respect to a potential splice may result in a lower score (i.e., a penalized score) for the potential splice site.

[0087] In certain examples, scoring may be tweaked so as not to penalize lack or absence of canonical motifs to as great an extent and, in this manner, not penalizing a useful motif as much simply due to it not being recognized as a canonical motif. In particular, the presence of small variants (e.g., single nucleotide polymorphisms (SNPs)) may occasionally cause a sequence to become a variant of a splice, such as by causing an “early” or “late” splice in the sequence or causing the splice to be missed (e.g., an intron retained instead of being spliced out). In this manner, scoring may be made more accommodative of such factors, therefore allowing more splices to be identified. By way of example, such a revised scoring methodology, when applied to publicly available data, went from detecting approximately 10,000 to approximately 35,000 splices. With respect to noise and false positives, by training the respective machine learning (ML) models on long read data (which may be between 1,000 bp to 30,000 bp in length), which can capture the sequence of a whole transcript (in contrast to short read data which may be 50 bp to 300 bp in length), noise and false positives can be reduced. By way of example, in one implementation, the ML model is trained on WTS NIST HG005 with long read data as ground truth and tested on HG004 data. In this manner, variant splices can be better identified within variant isoforms.

[0088] With the preceding general discussion and background in mind, and turning to FIG. 6, an example computational pipeline for calling splice variants in RNA is depicted. As may be appreciated, such a computational pipeline may be implemented on a suitable processor-based system, including but not limited to a next generation sequencing system or workstation. Further, such splice variant functionality implemented by a computational pipeline may be performed on a single, on-premise workstation or device, on networked on-premise workstations or devices, as a cloud-based (e.g., datacenter) implementation, or as a combination of such approaches (i.e., using a mixture of on-premise, networked, and / or cloud-based resources.

[0089] In the depicted example workflow, an input is provided in the form of sequence read data 1000 corresponding to or representative of an RNA sequence(s) (e.g., one or more transcript sequences). By way of example, such RNA sequence read data may be provided in the format of a FASTQ file or files. The sequence data 1000 may be mapped and aligned (step 1004) against a reference sequence, such as a human reference sequence. As used herein, the map and align process may be a splice-aware read mapper and aligner that aligns the whole genome to identify novel alternative splice junction candidates. As discussed herein, the splice junction candidates can be further filtered (or otherwise processed) using additional information, such as a “normals” list, “target regions” list, or a “knowns” list used to whitelist certain detected variants. In practice, and as illustrated in FIG. 6, the reference sequence may be provided in the form of a reference hash table (HT) 1004 to allow the map and align process 1004 to be implemented in a rapid and computationally efficient manner by comparing hash values derived for the sequence data 1000 against the reference hash table 1008.

[0090] The mapping and alignment process 1004 may output the alignments between the sequence reads of the sequence read data 1000 and the reference sequence 1008. Such alignments may be output as a binary alignment map (BAM) 1012. Additionally, in the depicted example, a splice junctions output 1016 is provided as an output of the mapping and alignment process 1004. The splice junctions output 1016 may be derived by assessing the output alignments to determine if a splice junction is indicated. By way of example, read ends may be checked to determine if there is a gap between ends, which may be indicative of a potential splice and therefore included in the splice junctions output.

[0091] In the depicted example, the BAM output 1012 and the splice junctions output 1016may be provided as inputs to a splice variant caller module 1024. Tn practice, the splice junctions output 1016 may be filtered or otherwise modified based on other data, discussed in greater detail below, prior to being provided to the splice variant caller 1024. Alternatively, such other data may be provided to the splice variant caller 1024 along with an intact splice junctions output 1016 and used by the splice variant caller 1024 as part of its operation in calling splice variants. By way of example, in one implementation the splice variant caller 1024 uses the number of reads supporting the reference versus the number of reads supporting the variant splice junction to score the candidate splice junction variants. In such implementations the respective score may be reported with each candidate splice junction variant in the outputs of the splice variant caller 1024. In such a context, for a read to be considered as support for a splice junction candidate factors may be considered such as, but not limited to: (1) presence of a splice junction, as may be indicated by an alignment gap in the CIGAR (Compact Idiosyncratic Gapped Alignment Report) string; and (2) presence of overhangs on either side of the skip that exceed a threshold length (e.g., that are at least 6 base pairs). Reads may be classified based on whether they are marked as PCR duplicates or not and whether they are uniquely mapping (NH=1) or multi -mapping (NH>1). In practice, for a splice variant to be reported by the splice variant caller 1024, at least one deduplicated uniquely mapping read supporting the splice variant candidate must be found.

[0092] In the depicted example, an annotation file 1020, which may be accessed locally or from a third-party data repository, is also illustrated as being provided to the splice variant caller 1024. In practice, the annotation file 1020 may include data regarding known isoforms that may be excluded from being called as splice variants by the splice variant caller 1024 due to their being known and, presumably of less or no interest to the reviewer for clinical diagnosis. That is, for research or diagnostic purposes, novel or previously unseen splice junction variants, which may be associated with genetic disorders or disease, may be of more interest than previously seen splice variants known to not have clinical significance.

[0093] There may be exceptions to this general rule, however, in that in some instances a known splice variant present in the annotation file 1020 may be of interest, either for diagnostic or research purposes. Accordingly, in the depicted example a “knowns” file 1028 may be provided to the splice variant caller 1024, where the knowns file 1028 includes known annotated splice variants that may be present in the annotation file 1020, but which are to be included in the outputof the splice variant caller 1024 if present. In such an example, the knowns file 1028 functions as an exceptions list and may comprise known splice variant annotations that are deemed to be of clinical or research interest or otherwise selected for inclusion in the output of the splice variant caller 1024. That is, in this context the knowns file 1028 may be a list of known splice variants that are exempt from being filtered out of the final output (e.g., operating as a whitelist). In this manner, the splice variant caller, by default, may not consider any splice variant candidates that are found in the input annotation file 1020 (since the splice variant caller 1024 is looking for de novo variants) unless the respective splice variant candidate is included in the knowns file 1028, which directs it not to discard the respective splice variant candidate. As may be appreciated, such a knowns file 1028 may be optional to the operation of the splice variant caller 1024, but may be present when certain known annotated splice variants are to be included in the output of the splice variant caller 1024.

[0094] Similarly, other optional files may be provided to the splice variant caller 1024 to facilitate generation of the desired splice variant calls as an output. In the depicted example a “normals” file 1032 is also illustrated. By way of example, the normals file 1032 may comprise a list of normal splice variants that will be filtered out of the final output (e.g., operating as a blacklist) as long as the splice variants in question are not in the “knowns” list 1028). In this context, the normal file 1032 may include splice junctions or potential splice junctions that should be excluded due to not being symptomatic or otherwise associated with a disease or disorder that is of interest. For example, the normal file 1032 may be generated based on or using non-cancerous tissues across a number of tissue samples (e.g., a panel of normal). Exclusions based on the normal file 1032, therefore, helps eliminate noise or other splice junctions that are known to not be problematic or are not what is being looked for, thereby cleaning up noise in the data. Conversely, the whitelist file 1036 may comprise known regions (e.g., target regions) or splice events of particular interest, and which therefore should pass through the splice variant caller 1024 as splice variants or potential splice variants regardless of other or mitigating factors. By way of example, such a whitelist file 1036 may be useful in contexts where gene panels are employed, allowing false positive alignments outside of the gene panel to be excluded.

[0095] In practice the splice variant caller 1024, once some or all of the preceding inputs are obtained, may identify (i.e., call) potential splice variants present in the RNA sequence read data1000 and may output such calls. By way of example, the splice variant caller may analyze the splice junctions output 1016 from the mapping and alignment process 1004 to generate a set of features (e.g., splice variant calls) based on supporting (and non-supporting) evidence, map quality, geometry of the potential splice (e.g., how wide are the anchors around the potential splice, where long sections of the read supporting the splice variant call may be more supportive of the call than short section of the read), and so forth.

[0096] The splice variant caller 1024 may, as part of calling splice variants or otherwise deriving a list of potential splice variants, generate a confidence score (or other suitable statistical score or parameter) based on the read evidence for each called feature. Such a confidence score may scale linearly or non-linearly and may be used in conjunction with one or more thresholds denoting a degree of confidence in the call. In practice, such scores may be used as, or used in conjunction with, thresholds to effectively call or not call a potential splice variant as a splice variant or not. Further, such scores may be included in the respective output(s) of the splice variant caller 1024 for use by downstream processes (e.g., tertiary analysis process or routines).

[0097] By way of example, in the depicted implementation the splice variant caller 1024 may output one or more of: (1) splice variant calls 1040 (depicted as being output as a variant call format (VCF) file, (2) intragenic splice variants 1044 (depicted as being output as a tab-separated values (TSV) file), and (3) intergenic splice variants 1048 (depicted as being output as a TSV file). As noted above, the various outputs may include respective confidence scores for each call splice variant or for included potential splice variants, which may be utilized in tertiary analyses performed on the respective output.

[0098] As used herein, the intragenic splice variants 1044 output may comprise intragenic alternative splice junctions that result in transcript variants while the intergenic splice variants 1048 output may comprise intergenic alternative splice junctions associated with fusion across genes. By way of context, in some instances a fusion (which may be in the form of a read-through event or comparable occurrence, as discussed in greater detail below) crosses gene boundaries (i.e., is between two genes), effectively creating a fusion of the genes. In such a case, a detected potential splice variant may be an intergenic splice variant that effectively has a different gene on each respective end of the splice. Conversely, intragenic splices may be understood to be splice events that occur within a single gene, with no associated combination or fusion with a secondgene.

[0099] With respect to the outputs (e.g., output files) of the splice variant caller 1024, such outputs (e.g., called splice variants) may be inputs to one or more tertiary processes configured to derive a biological interpretation or significance to associate with the respective called splice variants. By way of example, such a tertiary analysis may interact with a disease phenotype database to associate a called splice variant with a genetic disease or disorder. Additionally, the tertiary analysis may generate a disease association with a called splice variant that may be provided for review or consideration by a clinician or researcher. In practice, such functionality may be implemented via visualization (e.g., displayed mapping and annotation for splice variants), text or graphical association of splice variants above a threshold level with specific phenotypes or diseases, and so forth. Similarly, the tertiary analysis, in the context of a given subject, may be used to facilitate generation of a diagnosis or may otherwise generate such a diagnosis along with treatment recommendations, such as in the context where the called splice variant is or is believed to be an oncomarker.

[0100] As may be appreciated, the splice variant caller 1024 described herein may be implemented as a processor-based pipeline or module within a suitable system configured to process nucleic acid sequence data, such as a next generation sequencing system, a downstream analysis workstation, a cloud-based analysis platform, and so forth. In practice, aspects of the described workflow of FIG. 6 may be performed so as to take advantage of such implementations, such as to leverage parallel processing or multi -threaded processing as part of mapping and aligning reads to the reference sequence and / or as part of analyzing the outputs of the mapping and aligning process for potential splice variants. Further, results of the sequencing and splice variant calling may be performed within clinically relevant time frames (e.g., minutes, hours, or days) in contrast to performing such operations manually. In this manner, the disclosed techniques may be implemented so as to solve the problems associated with identifying potential splice variants using techniques implemented so as to leverage and improve computational efficiency and throughput.

[0101] With the preceding in mind, and as noted herein, in further aspects the splice variant calling functionality may be combined with functionality for calling gene fusion events that are discernible in the transcript sequence data. In such a combination, outputs from the splice variantcaller 1024 may be provided as an input to the fusion caller, which may also leverage additional data stored locally or remotely (e.g., data regarding known “hotspot” genes), to identify potential gene fusion events. By way of example, in one such embodiment passing and failed intergenic splice variants may be passed to a gene fusion caller to be scored and merged into an output of the gene fusion caller.[00102J Turning to FIG. 7, an example of one such combined process flow is depicted. In this example, the processes and data described with respect to the splice variant caller 1024 of FIG. 6 are depicted in conjunction with the added functionality of a fusion caller 1080 module or routines. In practice, the fusion caller 1080 receives an output from the RNA mapping and alignment process 1004 in the form of a chimeric junctions output 1088, which comprises supplementary (i.e., chimeric) alignments that may be analyzed to identify potential breakpoints where a fusion event has occurred. In particular, the chimeric junctions 1088 output may be understood to comprise split reads (i.e., chimeric reads) across two genes, such as may correspond to an alignment that crosses a breakpoint between two genes. In such a context, the chimeric junction may be indicative of a structural variant deletion or translocation. The chimeric junction output, therefore, may be indicative of a break between two genes and a supplemental alignment indicative of such a break. The chimeric junctions output 1088, therefore, comprises supplemental alignments indicative of a fusion event. With this in mind, the fusion caller 1080 accumulates and evaluates read evidence for the gene fusion event candidates. In certain implementations, the fusion caller 1080 employs a machine learning (ML) model to score the possible fusion events to filter out potential false positives.

[0103] As discussed herein, read-through fusions occur when neighboring genes are spliced together and may be, correspondingly, detected by the splice variant caller 1024 as intergenic splice variants on adjacent genes. Correspondingly, when combined with the splice variant caller 1024, the fusion caller 1080 may receive as an input (in addition to the chimeric junctions 1088) the intergenic splice variants 1048 output by the splice variant caller 1024. As discussed herein, the intergenic splice variants 1048 passed to the fusion caller 1080 may include both passing and failed intergenic splice variant calls for gene fusion evaluation.

[0104] In practice, however, this passing of intergenic splice variants 1048 to the gene fusion caller 1080 may be limited based on practical considerations. In particular, by default intergenicsplice variants on adjacent genes may not be passed to the gene fusion caller due to the frequent occurrence of such read-through events. In particular, one may wish to ignore (i.e., not report) or otherwise down weight such read-through events as these events are relatively common and may result in unwanted noise in the data if reported.

[0105] However, to address such considerations, in the depicted example, a list of genes of particular interest may be employed to selectively determine which intergenic splice variants 1048 are passed to the fusion caller 1080. By way of example, a list of known splice variants fusions may be employed, such as at the splice variant caller 1024 such that the listed splice variants are passed through to the fusion caller 1080. With reference to the depicted example, a list or other data store of hotspot genes 1084 (e.g., genes corresponding to known oncomarkers or genes of known clinical interest) may be employed that includes genes deemed of interest that should be included in the input to the fusion caller 1080. The list of hotspot genes corresponds to a list of intergenic splice variants that will not be filtered out but will instead be passed through, if present, to the fusion caller 1080.

[0106] In such a context, the intergenic splice variants 1048 passed to the fusion caller 1080 may be evaluated and scored by the fusion caller (e g., a fusion machine learning (ML) model) configured to call fusion events. In practice, and as noted above, the fusion caller 1080 may generally skip filtered or read-through events as such events are common and may be of little clinical or diagnostic interest. As noted herein, however, the hotspot genes dataset 1084 may be utilized to ensure that intergenic splice variants 1048 occurring at certain genes known to be of clinical or diagnostic interest for fusion events (i.e., hotspots) are passed to the fusion caller 1080, where they may be evaluated for fusions.

[0107] In the depicted example, the output of the fusion caller is an intergenic fusion call outputs file 1092, which may be formatted in any suitable format (e.g., CSV, VCF, and so forth). The fusion caller output may, in practice, comprise the detected gene fusion events, listing each passing gene fusion along with the red names that support the called gene fusion, including split reads, soft-clipped reads, and paired (discordant) reads, along with the passing score.

[0108] By way of further context and example, and turning to FIG. 8, an RNA read-through fusion is depicted for SLC45A3 and ELK4, a known oncomarker for prostate cancer and thus alikely inclusion in a hotspot genes dataset 1084. In this example, the read-through fusion is a cis splicing of neighboring genes. As illustrated, the ELK4 and SLC45A3 genes are part of a read-through fusion via a cis splice 1096. As discussed herein, a clinician would likely want to know of the presence of the depicted fusion event due to the fusion being a known oncomarker. Hence, splice variant output including the cis splice 1096 in question would be passed to the gene fusion caller 1080 as part of the intergenic splice variant output 1048, where its inclusion would be ensured due to inclusion of the genes in question on the hotspot genes dataset 1084.

[0109] As noted above, the gene fusion event in question, due to the two genes being in close proximity to one another, would not present as a split read, and thus would not be present in the chimeric junctions output 1088. Accordingly, the splice variant caller 1024 output (i.e., the intergenic splice variants output 1048) is relied upon as providing the relevant data to the fusion caller 1080. In practice, and as noted above, the intergenic splice variants output 1048 may include a score assigned by the splice variant caller that may be used by the fusion caller in calling the fusion event. As may be appreciated, the fusion caller functionality described may be of particular usefulness in circumstances where there are two close genes that can be read through as one during transcription and where a user wants to be able to detect the fusion event, such as due to known oncogenic effects, so as to alert a clinician, or diagnostician.

[0110] VII. Examples of Combinations

[0111] The following examples relate to various non-exhaustive ways in which the teachings herein may be combined or applied. The following examples are not intended to restrict the coverage of any claims that may be presented at any time in this application or in subsequent filings of this application. No disclaimer is intended. The following examples are being provided for nothing more than merely illustrative purposes. It is contemplated that the various teachings herein may be arranged and applied in numerous other ways. It is also contemplated that some variations may omit certain features referred to in the below examples. Therefore, none of the aspects or features referred to below should be deemed critical unless otherwise explicitly indicated as such at a later date by the inventors or by a successor in interest to the inventors. If any claims are presented in this application or in subsequent filings related to this application that include additional features beyond those referred to below, those additional features shall not be presumed to have been added for any reason relating to patentability.

[0112] Example 1A processor-based nucleic acid sequence processing system, comprising: one or more processing circuits configured to access and execute processor-executable code; andone or more memory structures configured to store the processor executable code, wherein the processor executable code, when accessed and executed by the one or more processing circuits, causes acts to be performed comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0113] Example 2.The processor-based nucleic acid sequence processing system of Example 1, wherein the reference sequence comprises a whole genome.

[0114] Example s.The processor-based nucleic acid sequence processing system of Examples 1-2, wherein mapping and aligning the plurality of nucleic acid sequence reads to the reference sequence utilizes a reference hash table to generate the alignment output and the splice junctions output.

[0115] Example 4The processor-based nucleic acid sequence processing system of Examples 1-3, wherein the splice variant outputs comprise one or more of an intragenic splice variant output or an intergenic splicevariant output.

[0116] Example 5.The processor-based nucleic acid sequence processing system of Examples 1-4, wherein each respective splice variant present in the one or more splice outputs has an associated score based on a number of reads supporting the reference sequence versus the respective splice variant.

[0117] Example 6.The processor-based nucleic acid sequence processing system of Examples 1-5, wherein the splice junction candidates are filtered using a list of normal splice variants for exclusion, wherein the list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

[0118] Example 7.The processor-based nucleic acid sequence processing system of Examples 1-6, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being filtered out.

[0119] Example s.The processor-based nucleic acid sequence processing system of Examples 1-7, wherein the splice junction candidates are filtered using a whitelist of target regions, wherein a respective splice junction candidate that falls within a target region of the whitelist is included.

[0120] Example 9.The processor-based nucleic acid sequence processing system of Examples 1-8, wherein splicejunction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

[0121] Example 10.The processor-based nucleic acid sequence processing system of Examples 1-9, wherein the processor executable code, when accessed and executed by the one or more processing circuits, causes further acts to be performed comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.

[0122] Example 11.The processor-based nucleic acid sequence processing system of Examples 1-10, wherein the intergenic splice variant output is filtered to include intergenic splice variants corresponding to one or more hotspot genes.

[0123] Example 12.A processor-implemented method, comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; andprocessing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0124] Example 13.The processor-implemented method of Example 12, wherein the reference sequence comprises a whole genome.

[0125] Example 14.The processor-implemented method of Examples 12-13, wherein mapping and aligning the plurality of nucleic acid sequence reads to the reference sequence utilizes a reference hash table to generate the alignment output and the splice junctions output.

[0126] Example 15.The processor-implemented method of Examples 12-14, wherein the splice junction candidates are filtered using a list of normal splice variants for exclusion, wherein the list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

[0127] Example 16.The processor-implemented method of Examples 12-15, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being filtered out.

[0128] Example 17.The processor-implemented method of Examples 12-16, wherein splice junction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

[0129] Example 18.The processor-implemented method of Examples 12-17,further comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.

[0130] Example 19.One or more non-transitory media comprising processor-executable routines, wherein the processor-executable routines, when executed by one or more processors, cause acts to be performed comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; andprocessing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

[0131] Example 20.The one or more non-transitory media comprising processor-executable routines of Example 19, wherein the splice junction candidates are fdtered using a list of normal splice variants for exclusion, wherein the list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

[0132] Example 21.The one or more non-transitory media comprising processor-executable routines of Examples 19-20, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being filtered out.

[0133] Example 22.The one or more non-transitory media comprising processor-executable routines of Examples 19-21, wherein splice junction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

[0134] Example 23.The one or more non-transitory media comprising processor-executable routines of Examples 19-22, wherein the processor-executable routines, when executed by the one or more processors, cause further acts to be performed comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.

[0135] VIII. Miscellaneous

[0136] While the foregoing examples are provided in the context of a system 100 that may be used in nucleotide sequencing processes, the teachings herein may also be readily applied in other contexts, including in systems that perform other processes (i.e., other than nucleotide sequencing procedures). The teachings herein are thus not necessarily limited to systems that are used to perform nucleotide sequencing processes.

[0137] It is to be understood that the subject matter described herein is not limited in its application to the details of construction and the arrangement of components set forth in the description herein or illustrated in the drawings hereof. The subject matter described herein is capable of other implementations and of being practiced or of being carried out in various ways. Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding pluralof said elements or steps, unless such exclusion is explicitly stated. Furthermore, references to “one example” are not intended to be interpreted as excluding the existence of additional examples that also incorporate the recited features. The use of “including,” “comprising,” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.[00138J When used in the claims, the term “set” should be understood as one or more things which are grouped together. Similarly, when used in the claims “based on” should be understood as indicating that one thing is determined at least in part by what it is specified as being “based on.” Where one thing is required to be exclusively determined by another thing, then that thing will be referred to as being “exclusively based on” that which it is determined by.

[0139] Unless specified or limited otherwise, the terms “mounted,” “connected,” “supported,” and “coupled” and variations thereof are used broadly and encompass both direct and indirect mountings, connections, supports, and couplings. Further, “connected” and “coupled” are not restricted to physical or mechanical connections or couplings. Also, it is to be understood that phraseology and terminology used herein with reference to device or element orientation (such as, for example, terms like “above,” “below,” “front,” “rear,” “distal,” “proximal,” and the like) are only used to simplify description of one or more examples described herein, and do not alone indicate or imply that the device or element referred to must have a particular orientation. In addition, terms such as “outer” and “inner” are used herein for purposes of description and are not intended to indicate or imply relative importance or significance.

[0140] It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described examples (and / or aspects thereof) may be used in combination with each other. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the presently described subject matter without departing from its scope. While the dimensions, types of materials and coatings described herein are intended to define the parameters of the disclosed subject matter, they are by no means limiting and instead illustrations. Many further examples will be apparent to those of skill in the art upon reviewing the above description. The scope of the disclosed subject matter should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. Further, the limitations of the following claims are not written in means — plus-function format and are not intended to be interpreted based on 35 U.S.C. § 112(f) paragraph, unless and until such claim limitations expressly use the phrase “means for” followed by a statement of function void of further structure.

[0141] With this in mind, the specific embodiments described above have been shown by way of example, and it should be understood that these embodiments may be susceptible to various modifications and alternative forms. It should be further understood that the claims are not intended to be limited to the particular forms disclosed, but rather to cover all modifications, equivalents, and alternatives falling within the spirit and scope of this disclosure.

[0142] The techniques presented and claimed herein are referenced and applied to material objects and concrete examples of a practical nature that demonstrably improve the present technical field and, as such, are not abstract, intangible or purely theoretical. Further, if any claims appended to the end of this specification contain one or more elements designated as “means for [perform]ing [a function]...” or “step for [perform]ing [a function]...”, it is intended that such elements are to be interpreted under 35 U.S.C. 112(f). However, for any claims containing elements designated in any other manner, it is intended that such elements are not to be interpreted under 35 U.S.C. 112(f).

[0143] The following claims recite aspects of certain examples of the disclosed subject matter and are considered to be part of the above disclosure. These aspects may be combined with one another.

Claims

What is claimed is:

1. A processor-based nucleic acid sequence processing system, comprising:one or more processing circuits configured to access and execute processor-executable code; andone or more memory structures configured to store the processor executable code, wherein the processor executable code, when accessed and executed by the one or more processing circuits, causes acts to be performed comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; and processing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

2. The processor-based nucleic acid sequence processing system of claim 1, wherein the reference sequence comprises a whole genome.

3. The processor-based nucleic acid sequence processing system of claim 1, wherein mapping and aligning the plurality of nucleic acid sequence reads to the reference sequence utilizes a reference hash table to generate the alignment output and the splice junctions output.

4. The processor-based nucleic acid sequence processing system of claim 1, wherein the splice variant outputs comprise one or more of an intragenic splice variant output or an intergenic splice variant output.

5. The processor-based nucleic acid sequence processing system of claim 1, wherein each respective splice variant present in the one or more splice outputs has an associated score based on a number of reads supporting the reference sequence versus the respective splice variant.

6. The processor-based nucleic acid sequence processing system of claim 1, wherein the splice junction candidates are filtered using a list of normal splice variants for exclusion, whereinthe list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

7. The processor-based nucleic acid sequence processing system of claim 1, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being fdtered out.

8. The processor-based nucleic acid sequence processing system of claim 1, wherein the splice junction candidates are filtered using a whitelist of target regions, wherein a respective splice junction candidate that falls within a target region of the whitelist is included.

9. The processor-based nucleic acid sequence processing system of claim 1, wherein splice junction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

10. The processor-based nucleic acid sequence processing system of claim 1, wherein the processor executable code, when accessed and executed by the one or more processing circuits, causes further acts to be performed comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.

11. The processor-based nucleic acid sequence processing system of claim 10, wherein the intergenic splice variant output is filtered to include intergenic splice variants corresponding to one or more hotspot genes.

12. A processor-implemented method, comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; andprocessing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

13. The processor-implemented method of claim 12, wherein the reference sequence comprises a whole genome.

14. The processor-implemented method of claim 12, wherein mapping and aligning the plurality of nucleic acid sequence reads to the reference sequence utilizes a reference hash table to generate the alignment output and the splice junctions output.

15. The processor-implemented method of claim 12, wherein the splice junction candidates are fdtered using a list of normal splice variants for exclusion, wherein the list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

16. The processor-implemented method of claim 12, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being filtered out.

17. The processor-implemented method of claim 12, wherein splice junction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

18. The processor-implemented method of claim 12, further comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.

19. One or more non-transitory media comprising processor-executable routines, wherein the processor-executable routines, when executed by one or more processors, cause acts to be performed comprising:receiving as an input a plurality of nucleic acid sequence reads;mapping and aligning the plurality of nucleic acid sequence reads to a reference sequence to generate an alignment output and a splice junction candidates output; andprocessing the alignment output and the splice junction candidates output to generate one or more splice variant outputs.

20. The one or more non-transitory media comprising processor-executable routines of claim 19, wherein the splice junction candidates are filtered using a list of normal splice variants for exclusion, wherein the list of normal splice variants comprises splice variants known to be asymptomatic or that are not associated with a disease of interest.

21. The one or more non-transitory media comprising processor-executable routines of claim 19, wherein the splice junction candidates are processed using a list of known splice variants of interest that are exempt from being filtered out.

22. The one or more non-transitory media comprising processor-executable routines of claim 19, wherein splice junction candidates present in an annotation file of known splice variants are excluded from further consideration when processing the alignment output and the splice junction candidates output.

23. The one or more non-transitory media comprising processor-executable routines of claim 19, wherein the processor-executable routines, when executed by the one or more processors, cause further acts to be performed comprising:processing an intergenic splice variant output of the one or more splice variant outputs to generate fusion calls comprising intergenic fusion calls.