| Run | Spots | Bases | Size | GC content | Published | Access Type |
|---|---|---|---|---|---|---|
SRR3313156 |
66.1M | 13.2Gbp | 8.6G | 46.5% | 2018-01-02 | public |
This run has 2 reads per spot:
| L=100, 100% | L=100, 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 |
|---|---|---|---|---|---|---|---|
| SRX1670130 | Illumina | RNA-Seq | TRANSCRIPTOMIC | cDNA | PAIRED |
| Biosample | Sample Description | Organism | Links |
|---|---|---|---|
| SAMN04590561 (SRS1367769) | Cicer arietinum | PRJNA316845 |
| Bioproject | SRA Study | Title |
|---|---|---|
| PRJNA316845 | SRP072563 | Transcriptome dynamics during seed development in chickpea (JGK3) |
In this study, we aim to present a global view of transcriptome dynamics during seed development in a large-seeded chickpea (genotype JGK3). We generated about 1.5 billion high-quality reads from 24 libraries (leaf and seven seed developmental stages in three biological replicates) using Illumina high-throughput sequencing platform. We mapped the reads to the kabuli chickpea genome for estimation of their transcript abundance in different tissue samples. The transcriptome dynamics was studied by differential gene expression analyses between different samples/stages. Overall design: We collected leaves from the field-grown chickpea plants during mid maturation stage of seed development. Seven different stages of seeds (whole seed) representing the major events occurring within the seed, were collected from the field-grown plants. The tissues were collected in at least three biological replicates. Total RNA isolated from these tissue samples was subjected to Illumina sequencing. The sequenced data was further filtered using NGS QC Toolkit to obtain high-quality reads. The filtered reads were mapped to annotated chickpea genome using TopHat and fragments per exon kilobase per million (FPKM) was calculated using Cufflinks software for each gene in all the samples to measure their gene expression. Differential expression analysis was performed using Cuffdiff software. The differentially expressed genes during various stages of seed development were identified.
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 Lite | 3,261,649 Kb | NCBI | https://sra-downloadb.be-md.ncbi.nlm.nih.gov/sos5/sra-pub-zq-11/SRR003/313/SRR3313156/SRR3313156.sralite.1 | worldwide | anonymous |
| AWS | s3://sra-pub-zq-2/SRR3313156/SRR3313156.sralite.1 | s3.us-east-1 | aws identity | ||
| GCP | gs://sra-pub-zq-101/SRR3313156/SRR3313156.zq.1 | gs.us-east1 | gcp identity | ||
| SRA Normalized | 8,388,841 Kb | AWS | https://sra-pub-run-odp.s3.amazonaws.com/sra/SRR3313156/SRR3313156 | worldwide | anonymous |
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 | 5,215,504 Kb | AWS | s3://sra-pub-src-4/SRR3313156/JS6-2_2.fq.gz | - | Use Cloud Data Delivery |
| fastq | 5,394,162 Kb | AWS | s3://sra-pub-src-7/SRR3313156/JS6-2_1.fq.gz | - | Use Cloud Data Delivery |
- Egress and Access: what does it mean?
-
Egress
term used by cloud providers to describe cost (charged to the user) of moving data outside of the storage region Free Egresscolumn 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.