Run Browser : Browse : Sequence Read Archive : NCBI/NLM/NIH

Run	Spots	Bases	Size	GC content	Published	Access Type
SRR1524948	26.6M	5.4Gbp	3.9G	44.4%	2014-11-14	public

Quality graph (bigger)(smaller)

241

Phred quality score

This run has 2 reads per spot:

L=101, 100%

Legend

		Technical read
		Application Read
L=4, 100%		Length is 4, 100% spots contain this read
̅L=165, σ=92.8, 66%		Average length is 165, standard deviation is 92.8, 66% spots contain this read

Experiment	Library Name	Platform	Strategy	Source	Selection	Layout	Action
SRX661220	24h wounded roots	Illumina	RNA-Seq	TRANSCRIPTOMIC	PolyA	PAIRED

Show designHide design

RNA was extracted from 24h micro-wounded roots of three plants. Total RNA was extracted using a Spectrum Plant Total RNA Kit (Sigma-Aldrich, St. Louis, MO, USA) according to the manufacturer’s instructions. Any DNA contamination was removed by DNaseI treatment on column (Roche, Basel, Switzerland). The RNA-quality tests were performed with the Agilent 2100 bioanalyzer (Agilent Technologies, Santa Clara, CA, USA) using an RNA 6000 Pico assay kit (Agilent Technologies, Santa Clara, CA, USA). We pooled RNA and made cDNA libraries for sequencing in Illumina HiSeq 1000 sequencer. Two replicates were sequenced on different lines. After trimming and cleaning, we obtained 53.361.340 paired-end reads of 101bp length and 35 Phred quality (10,78 Gb).

Biosample	Sample Description	Organism	Links
SAMN02937428 (SRS666183)		Olea europaea	PRJNA256033

Bioproject	SRA Study	Title
PRJNA256033	SRP044780	Olea europaea Transcriptome or Gene expression

Abstract:

Control and plants responding to biotic and abiotic stress were sequenced by Illumina HiSeq 1000 paired-end.

SRA archive data

SRA archive data is normalized by the SRA load process and used by the SRA Toolkit to read and produce formats like FASTQ, SAM, etc. The default toolkit configuration enables it to find and retrieve SRA runs by accession.

Public SRA files are now available from GCP and AWS cloud platforms as well as from NCBI. Access to most data in the cloud requires a user account with the cloud service provider. The user’s account will incur costs for cloud compute or to copy data outside of the specified cloud service region.

Type	Size	Location	Name	Free Egress	Access Type
SRA Normalized	3,772,653 Kb	AWS	https://sra-pub-run-odp.s3.amazonaws.com/sra/SRR1524948/SRR1524948	worldwide	anonymous
SRA Lite	1,369,995 Kb	NCBI	https://sra-downloadb.be-md.ncbi.nlm.nih.gov/sos5/sra-pub-zq-11/SRR001/524/SRR1524948/SRR1524948.sralite.1	worldwide	anonymous
		AWS	s3://sra-pub-zq-8/SRR1524948/SRR1524948.sralite.1	s3.us-east-1	aws identity
		GCP	gs://sra-pub-zq-102/SRR1524948/SRR1524948.noqual.1	gs.us-east1	gcp identity

Original format

The original files submitted to SRA. These files may require specific software to open, read and interpret data.

Type	Size	Location	Name	Free Egress	Access Type
fastq	2,190,489 Kb	AWS	s3://sra-pub-src-13/SRR1524948/12021_CAGATC_L002_R1_001_BC0MPLACXX.filt.fastq.gz	-	Use Cloud Data Delivery
fastq	2,249,554 Kb	AWS	s3://sra-pub-src-9/SRR1524948/12021_CAGATC_L002_R2_001_BC0MPLACXX.filt.fastq.gz	-	Use Cloud Data Delivery

Egress and Access: what does it mean?

Egressterm used by cloud providers to describe cost (charged to the user) of moving data outside of the storage region

Free Egress column indicates where the data can be accessed without an egress charge:

worldwide can be downloaded from anywhere for free
s3.us-east-1 is free to access from machines running in Amazon's us-east-1 region, access from other regions or transport outside of AWS will require paying egress charges
gs.US is free to access from machines running in Google’s gs.US region, access from other regions or transport outside of GCP will require paying egress charges

Access Typedescribes whether a cloud service user account is necessary for data access. "anonymous" access means general public access

Namecolumn provides either a link to free download location at NCBI or a URL for the cloud provider storage location. Either s3:// for Amazon or gs:// for Google storage

Why is SRA data in the cloud?

In order to support large scale (hyper parallel) data analyses SRA data is now available at GCP and AWS with few caveats:

SRA data is copied to the cloud from NCBI. There may be a lag between availability from NCBI and from CSP (cloud service providers)
To access public data user account with the cloud service provider is required. Your account will incur costs for cloud compute and/or to copy data (either archival or results of your comute) outside of the specified cloud service region
Distribution of protected data is signed by NIH account and requires user to operate in the same region as the data

SRA has also begun to provide access to originally submitted source files:

not all files have been validated by SRA
not all files have been copied to cloud locations (recovering it from NCBI tape system takes time ).
the volume of this type of data a much larger and it is not used as often so we will keep most of it on tape or "cold" storage in cloud. As a result the data may not be available instantly and restore requests will be served on first-come first-served basis and cost of resore may be charged to your user account.

What is "Cloud Data Delivery"?: Please visit SRA Data Delivery service to request Sequence Read Archive (SRA) data to be delivered to an Amazon Web Services (AWS) or Google Cloud Platform (GCP) bucket of your choice.

Taxonomy Analysis

Unidentified reads: 96.79%
Identified reads: 3.21%

View in Krona

Strong signals

SuperKingdom	Organism	Rank	%%	Kbp
Eukaryota	Sesamum indicum	species	0.6	33,976
Eukaryota	Nicotiana	genus	0.3	13,451
Eukaryota	Gossypium hirsutum	species	0.2	12,470
Eukaryota	Nectria haematococca mpVI 77-13-4		0.2	10,789
Eukaryota	Papilionoideae	subfamily	0.2	10,647
Eukaryota	Maleae	tribe	0.2	9,993
Eukaryota	Erythranthe guttata	species	0.2	9,992
Eukaryota	Solanum	genus	0.2	8,395
Eukaryota	Capsiceae	tribe	0.1	7,109

How to read results?: Results show distribution of reads mapping to specific taxonomy nodes as a percentage of total reads within the analyzed run. In cases where a read maps to more than one related taxonomy node, the read is reported as originating from the lowest shared taxonomic node. So when a read maps to two species belonging to the same genus, it is assigned at the genus level. Sequence reads from a single organism will map to several taxonomy nodes spanning the organism’s lineage. The number of reads mapping to higher level nodes will typically be greater than those that map to terminal nodes.

STAT results are proportional to the size of sequenced genomes. Given a mixed sample containing several organisms at equal copy number, proportionally more reads originate from the larger genomes. This means that the percentages reported by STAT will reflect genome size and must be considered against the genomic complexity of the sequenced sample.

How can I query this analysis data?: Please take a look at NCBI SRA Cloud-based Taxonomy Analysis Table

How taxonomy analysis is done?: A fast, scalable, MinHash-based k-mer tool to assess Sequence Read Archive next generation sequence submissions

Roots wounding 24h Olea europaea(SRR1524948)

Abstract:

SRA archive data

Original format

Taxonomy Analysis

Strong signals

Intensity graph

	View: biological readstechnical readsquality scoresadvanced options Hide Reads base space color space show separated reads quality score with bases show clipped show 4 channel quality scorewith bases Intensity graph Signals table
	Intensity graph