| Run | Spots | Bases | Size | GC content | Published | Access Type |
|---|---|---|---|---|---|---|
SRR10894060 |
24.5M | 7.4Gbp | 3.0G | 44.6% | 2021-01-13 | public |
This run has 2 reads per spot:
| L=150, 100% | L=150, 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 |
|---|---|---|---|---|---|---|---|
| SRX7562994 | Illumina | RNA-Seq | TRANSCRIPTOMIC | cDNA | PAIRED |
| Biosample | Sample Description | Organism | Links |
|---|---|---|---|
| SAMN13863975 (SRS6000868) | Lactuca sativa | PRJNA601218 |
| Bioproject | SRA Study | Title |
|---|---|---|
| PRJNA601218 | SRP241952 | Transcriptome profiling of Cd resistance by exogenous treatment of melatonin in Italian Lettuce |
This study is the first transcriptome study for Cd and melatonin treatment in lettuce, both transcriptomes and the expression profile would provide the foundation for further exploring the molecular mechanism of Cd accumulation, and develop breeding strategies aimed at decreasing Cd in crop plants. Overall design: Italian Lettuce (Lactuca sativa L. var. ramose Hort.) seeds were sterilized with 10 % hydrogen peroxide for 10 min and rinsed thoroughly with distilled water for three times, then germinated on moist filter paper in the dark at 20 °C. After the initiation for 0.5 cm, the seeds were transferred to a salver (40 x 30 cm) filled with perlite and covered by vermiculite for moisture holding. Then, they were transferred into the incubator under 23?/18? for 14h/10h in day and night time, respectively. The relative humidity set as 70% and the light intensity was 15,000 lx. After the formation of seedlings, they were watered with 200ml half-strength Hoagland's nutrient solution per day for 20 days, subsequently cultivated in a growth chamber. 20 days later, the seedlings were divided into two groups: 1) seedlings cultivated with the nutrient solution with 1µmol/L (Sigma-Aldrich, USA) melatonin. 2) seedlings cultivated with the nutrient solution without melatonin. Then, these two groups were treated by 50 µmol/L CdCl2 for simulation a Cd stress environment, and the nutrient solution was replenished regenerated once for three days to maintain constant concentrations. The leaves and root of 0d, 1d, and 5d seedlings in two groups have been sampled, and three biological repeats were included for each treatment . All samples were stored in Ultra-low Temperature Freeze under -80° before conducting.
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 | 2,946,266 Kb | AWS | https://sra-pub-run-odp.s3.amazonaws.com/sra/SRR10894060/SRR10894060 | worldwide | anonymous |
| SRA Lite | 1,799,395 Kb | NCBI | https://sra-downloadb.be-md.ncbi.nlm.nih.gov/sos3/sra-pub-zq-22/SRR010/10894/SRR10894060/SRR10894060.lite.1 | worldwide | anonymous |
| AWS | s3://sra-pub-zq-6/SRR10894060/SRR10894060.lite.1 | s3.us-east-1 | aws identity | ||
| GCP | gs://sra-pub-zq-106/SRR10894060/SRR10894060.lite.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,071,906 Kb | AWS | s3://sra-pub-src-10/SRR10894060/LCd5_1_1.fq.gz.1 | - | Use Cloud Data Delivery |
| fastq | 2,344,480 Kb | AWS | s3://sra-pub-src-10/SRR10894060/LCd5_1_2.fq.gz.1 | - | 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.
Taxonomy Analysis
- Unidentified reads: 1.12%
- Identified reads: 98.88%
Strong signals
| SuperKingdom | Organism | Rank | %% | Kbp | Coverage |
|---|---|---|---|---|---|
| Eukaryota | Lactuca sativa | species | 98.3 | 7,233,773 | |
| Eukaryota | Tetranychus urticae | species | 0.3 | 20,601 | |
| Eukaryota | Takifugu rubripes | species | 0.1 | 8,985 | |
| Bacteria | Bacteria | superkingdom | 0.1 | 5,317 | |
| Eukaryota | Homininae | subfamily | 0.1 | 4,383 | |
| Bacteria | Proteobacteria | phylum | 0.0 | 403 | |
| Viruses | Bean common mosaic virus | species | 0.0 | 4 |
- 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