Facioscapulohumeral muscular dystrophy (FSHD): RNA-seq of isogenic TIRM+, TIRM- muscle and PBMCs from patients and matched controls
FASTQ files describing paired-end RNA-sequencing of isogenic TIRM+ and TIRM- muscle biopsies from 24 FSHD patients (48 samples) and vastus lateralis muscle biopsies from 11 matched control individuals. FASTQ files are also provided describing RNA-sequencing of 15 FSHD peripheral blood mononuclear samples and 14 matched controls. For muscle biopsies sequencing was at 21.7-35.5 million reads/sample. RNA was extracted from PBMCs followed by globin depletion with sequencing at 19.7-46.5 million reads/sample.
- 88 samples
- DAC: EGAC00001003305
- Technology: Illumina NovaSeq 6000
FSHD data access policy.
A circulating biomarker for severity of facioscapulohumeral muscular dystrophy: Access to Data General principles The van Engelen-Zammit-Banerji collaboration (hereinafter also referred to as the “Project” or ‘’collaboration’’) has performed bulk mRNA-sequencing on muscle biopsies and on peripheral blood mononucleated cells (PBMCs) from patients with facioscapulohumeral muscular dystrophy (FSHD) and of unrelated healthy controls In total, 26 patients with FSHD and 23 healthy controls were included. The following samples were sequenced: 1) 24 out 26 patients underwent 2 MRI-guided muscle biopsies, one targeting an inflamed muscle (defined as TIRM+ on MRI) and one targeting a non-inflamed muscle (defined as TIRM- on MRI) for a total of 48 bulk muscle samples. 2) 15 out 26 patients were sampled for PBMCs for a total 15 patients PBMCs samples. 3) 11 out of 23 healthy controls underwent a needle muscle biopsy for a total of 11 bulk healthy controls muscle samples. 4) 14 out 23 healthy controls were samples for PBMCs, or a total of 14 healthy control PBMCs. The Project is led by Baziel van Engelen and Leo Joosten from Radboud University Medical Centre in Nijmegen, the Netherlands (“Radboudumc”), Peter Zammit from King's College London and Christopher Banerji from The Alan Turing Institute, London. The primary goal of the project is to identify novel biomarkers for potential application in clinical trials for FSHD patients. . Access to Project Data will be granted to qualified researchers for approved use and will be governed by the provisions laid out in the associated informed consent of individual data subjects for each cohort and/or of the associated ethics committee approval of the associated cohort, the Data Access Procedure set forth below and the terms of the Data Access Agreement attached hereto. A qualified researcher refers to a senior investigator who is employed or legitimately affiliated with an academic, non-profit or government institution and who has a track record in the field. Access to Project Data is available by application to the van Engelen-Zammit-Banerji Data Access Committee. Researchers granted access to Project Data must feedback the results of their research to the van Engelen-Zammit-Banerji project , after publication in accordance with the project publication policy set forth in the Data Access Agreement. Access is conditional upon availability of data and on signed agreement by the researcher(s) and the responsible employing institution to abide by the policies and conditions related to publication, data ownership, data return, intellectual property rights, data disposal, ethical approval, confidentiality and commercialization referred herein. Data Available The following Project Data are available: - Bulk muscle mRNA-sequencing data - PBMC mRNA-sequencing data Briefly, RNA extraction from muscle biopsies, purification, quality control, library preparation and sequencing at 21.7-35.5 million reads/sample were performed by Genewiz (https://www.genewiz.com). RNA was extracted from PBMCs followed by globin depletion, quality control, library preparation and sequencing at 19.7-46.5 million reads/sample performed by Genewiz (https://www.genewiz.com. Data Access Committee Applications for access to Project Data must be made to the Project Data Access Committee (DAC). The Project DAC consists of Baziel van Engelen. Data Access Procedure 1. Application for Access The handling of applications, the issue of Project Data and any associated operations, administration and audits will be performed by the Radboudumc on behalf of the Project/Collaboration. Applications for Access to Project Data must be submitted using the online EGA data request procedure and using the form in Appendix 1. The information disclosed in the application will be treated as confidential and will only be disclosed to the persons evaluating the application. All incoming applications will be documented, including any conjunct agreements with the applicants. Unless explicitly consented for by the applicant, this information will not be used for purposes other than evaluation of the application. The research topic of the applications which have been granted will be published on the website of the Project. Applications which have not been granted will not be published. In cases where an application contains classified plans, know-how or trade secrets, the applicant may request the conclusion of a separate confidentiality agreement. 2. Multiple applications Applicants agree to use the Project Data for the approved purpose and project described in the application; use of the data for a new purpose or project will require a new application and approval. The DAC will consider applications that include named collaborators, but each Institution must sign a separate Data Access Agreement. In the event an applicant wishes to share the data with additional collaborators not previously approved, these additional collaborators must make a separate application for access to the Project Data. In the event two or more applications overlap, the DAC may propose the respective applicants to align their applications. 3. Assessment criteria Applications which seek to reserve Project Data for unspecified research goals will not be taken into consideration. Applications for access to Project Data must be Specific, Measurable, Attainable, Resourced and Timely (SMART). Specifically, the Project DAC will assess each application to determine whether: i. it has been submitted by a qualified researcher or researchers, who is employed by or legitimately affiliated with a recognised research institution that can provide institutional responsibility for appropriate research governance; ii. its proposed use of the Project Data is in accordance with and meets the objectives of Project; iii. its proposed use of the Project Data constitutes research in the context of the individual sample donor consent process, and is likely to be understood as such by the individual sample donors; iv. it would breach any of the ethical permissions or restrictions in the consent forms for any component cohort; v. all required ethico-legal approvals, restrictions and commitments for the proposed use of the Project Data have been obtained and adhered to; vi. the proposed research has any adverse potential impact, specifically whether the proposed research could affect minorities; vii. the nature of the funding of the application and the applicant; viii. the research proposal has been peer-reviewed, and, if not, whether the proposal satisfies applicable scientific standards; ix. the requested data are, quantitatively and qualitatively, suitable and not excessive for the applicant’s proposed research; x. there are any similar applications pending or granted; xi. the proposed use of the Project Data has the potential to produce information that will enable identification of the individual sample donors. xii. In the event the applicant(s)’ proposed use of Project Data involves use of his/their your own data the applicant has warranted that he has obtained all required ethico-legal approvals, restrictions and commitments, without limitation his data subject consent and approval of his pertinent medical ethical review board, for his proposed use of his data in combination with the Project Data, as appropriate. 4. Access decision The DAC will decide on an application within a reasonable period of time after it has received all pertinent information. If the DAC grants an application, additional agreements may be made regarding authorships along the lines set forth in the Publication Policy attached to the Data Access Agreement. Rejections of applications will be motivated. Mode of Access to Data; restrictions and authentication The Consortium will make the pseudonymized Project Data available through the European Genome Phenome Archive (EGA), hosted at the European Bioinformatics Institute. Issue of Project Data may be subject to restrictions pursuant to data subject’s or ethics committee’s consent. The issue of Project Data and the Data Access Agreement will be administered by Radboudumc. Data Access Conditions Access to Project Data is conditional on prior receipt by the Consortium of the Data Access Agreement attached as Appendix 2 hereto, signed and dated by the applicant(s) and the responsible employing Institution(s). Authors who use Project Data must: 1. Acknowledge the Project using the following wording: "This study makes use of data generated by the van Engelen-Zammit-Banerji collaboration.“ 2. Acknowledge, by reference, the van Engelen-Zammit-Banerji collaboration where the samples and Project Data have been derived from: Christopher R. S. Banerji, Anna Greco, Leo A. B. Joosten, Baziel G. M. van Engelen and . Peter S. Zammit. A circulating biomarker for severity of facioscapulohumeral muscular dystrophy. Brain Communications. doi: https://doi.org/10.1101/2022.08.31.506017 Application Form for Access toProject Data PLEASE SUBMIT COMPLETED, SIGNED AND DATED FORM BY EMAIL TO: baziel.vanengelen@radboudumc.nl 1. Name and position of the Applicant(s), including employment or affiliation with any organization Please ensure that a full postal and email address is included for each applicant. 2. Title of the study In less than 30 words. 3. Research Question Please describe the study in no more than 750 words. Include: a. outline of the study design; b. an indication of the methodologies to be used; c. proposed use of the Project Data; d. preceding peer-reviews of the study (if any present); e. specific details of what you plan to do with the Project Data; f. timeline; g. key references. 4. Consent and Approvals Does your proposed use of Project Data involve use of your own data? Yes […..] No […..] If Yes, with signing this document you confirm the following: ‘I confirm that I have obtained all approvals required by the rules and regulations of my jurisdiction, including my institution’s institutional rules, and the consent of my data subjects, for my use of my own data in combination with the Project Data in the study.’ 5. Resources, Feasibility & Expertise Please confirm that you have secured funding for your proposed use of the Project Data and that you will carry out your research within a reasonable period of time after the granting of this application: by ticking the following box: Yes, we will □. Please describe your experience and expertise, and that of your collaborators, and how this will be applied to the proposed study (in 250 words). Please provide a list of recent publications (max. 10). Appendix 2 Data Access Agreement This agreement governs the terms on which access will be granted to the Project Data generated by the Project. In signing this agreement, You are agreeing to be bound by the terms and conditions of access set out in this agreement. For the sake of clarity, the terms of access set out in this agreement apply both to the User and the User’s Institution (as defined below). User Institution and User are referred to within the agreement as “You” and “Your” and shall be construed accordingly. Definitions: “Project” refers to the van Engelen-Zammit-Banerji Collaboration , comprising Radboud University Medical Center (“RUMC”) and King's College London. “Project Data” refers to the RNA-sequencing data generated by the Project. “Data Subject” refers to the person whose sample has been used to generate Project Data. “User” refers to a researcher who has successfully applied for access to Project Data. “Publications” refers to, without limitation, articles published in print journals, electronic journals, reviews, books, posters and other written and verbal presentations of research. “User Institution” refers to the organization with which the User is employed, affiliated or enrolled. Terms and Conditions: In signing this Agreement: 1. You agree to use Project Data only for the advancement of scientific and medical research. 2. You agree not to use, and not to allow use of, Project Data or any part thereof for the creation of products or services for sale or for any commercial purpose, whether sale by You or by third parties. 3. You acknowledge that the Project Data You receive is pseudonymised and that the Consortium will under no circumstances provide You with any means to identify any Data Subject. You agree not to use Project Data to identify or contact individual Data Subjects. You agree to preserve, at all times, the confidentiality of information and Project Data. In particular, You undertake not to use, or attempt to use Project Data to compromise or otherwise infringe the confidentiality of information on Data Subjects and their right to privacy. 4. You agree to disclose Project Data only to those of Your employees who strictly need access to it for the purpose of your approved study (Authorized Recipients), and who are bound by a duty of confidentiality which is at least as strict as provided for in this agreement. 5. You agree to ensure that any Authorized Recipient who has access to Project Data is advised of the confidentiality of Project Data. Upon request by the Project, you agree to furnish the Project the names of all Authorized Recipients who have gained access to Project Data. You agree that You are responsible for all breaches of confidentiality and of the terms of this agreement by your Authorized Recipients. 6. You agree to store Project Data on a computer with adequate security controls that prevent unauthorized access to or loss of Project Data and to maintain appropriate control over the Project Data. You represent and warrant that You have in place, and You agree that You will keep having in place, state of the art technical and organizational security measures preventing unauthorized access and loss of Project Data or other forms of unlawful processing of Project Data, including without limitation, physical security measures, access controls, security and privacy technologies, security checks in relation to personnel, security incident response management and audit arrangements. You agree to notify forthwith the administrator of the Project, Radboudumc, of any violations of the foregoing. 7. You represent and warrant that you have obtained and adhered to all required ethico-legal approvals, restrictions and commitments, without limitation data subject consent and approval of the pertinent medical ethical review board, for Your proposed use of Your data in combination with the Project Data. 8. In the event the Project Data is issued to You subject to any Data Subject’s restrictions, you hereby assume the obligation to abide by these restrictions as Your own obligation towards the Data Subject. You agree that Data Subjects can enforce such restrictions as well as any pertinent provisions of this agreement as third-party beneficiaries and, in the event they choose to do so, that You will not object to Data Subjects being represented by an association or other bodies if they so wish. You agree that a Data Subject who has suffered damage(s) as a result of any violation by You of pertinent provisions in this Agreement or of applicable legislation, is entitled to receive compensation from You for the damage(s) suffered. You agree that, in the event of such a violation, the Data Subject may bring an action before a court within the Data Subject’s jurisdiction against You. 9. You agree not to attempt to link Project Data to other information or archive data available for the data sets provided to You under this agreement, even if access to that data has been formally granted to you, or it is freely available without restriction, without the required consents and approvals. You agree to retain control over Project Data, and NOT TO DISTRIBUTE (individual-level or aggregated) Project Data provided under this agreement, in any form, to any entity or individual. 10. You agree not to transfer, share or disclose Project Data, in whole or in part, to or with anybody else, whether or not he or she is affiliated with Your institution, unless he or she is a named and approved collaborator under the Project Data Access Procedure. 11. You agree to use Project Data for the purpose and project described in your application (nr.____________________), as approved by the ProjectData Access Committee; use of the data for a new purpose or project or by another researcher will require a new application and approval. Substantive modification of the original application requires submission of an amendment to the original application. 12. You agree to, when analyses result in newly estimated variables at an individual level (e.g. haplotypes), submit these new variables for archiving with theProject. This should be done no later than that the related paper will be submitted for publication. 13. You accept that Project Data will be reissued from time to time, with suitable versioning. If the reissue is at the request of sample donors and/or subject to other ethical scrutiny, You will destroy earlier versions of the Project Data. 14. You agree to destroy the Project Data after the resulting paper has been published. To meet journals’ requirements for availability of Project Data for reviewers to see and readers to use, you agree to refer to the availability of the Project Data as deposited with EGA, under the terms hereof. You agree that the availability of the data resulting from your study of the Project Data for reviewers to see and readers to use is subject to this Access Policy, Procedure and this Data Access Agreement. 15. You agree to acknowledge in any work based in whole or in part on Project Data, the published paper from which the Project Data derives, the version of the data, and the role of the Project and the relevant primary collectors and their funders, as per the wording provided in the paragraph “Data Access Conditions”. 16. You accept that theProject, the original Project Data generators and the funders of the Project Data: a) bear no legal responsibility whatsoever for the accuracy, completeness or comprehensiveness of the Project Data; and b) accept no liability for direct, indirect, consequential or incidental, damages or losses arising from any use of Project Data by anyone, including without limitation any clinical use and any commercial use thereof, or arising from the unavailability of, or break in access to, the Project Data for whatever reason. 17. You understand and acknowledge that Project Data are protected by copyright, database right and other intellectual property and proprietary rights, and that duplication, sale, licensing or any other form of disposing or distribution or making available, of all or part of the Project Data on any media is not permitted. 18. You acknowledge that the Project Data are made available to you under this agreement on the title of unassignable, non exclusive “loan”. You recognise that nothing in this agreement shall operate to transfer to You any rights, including but not limited to intellectual property rights and database rights, in or relating to Project Data. 19. You accept that this agreement will terminate immediately upon any breach of this agreement by You and You will be required to destroy any Project Data held. 20. You accept that it may be necessary for the Projector its appointed agent to alter the terms of this agreement from time to time in order to address new concerns. In this event, the Projector its appointed agent will contact You to inform You of any changes and You agree that Your continued use of Project Data shall be dependent on the parties entering into a new version of the agreement. 21. You agree that You will submit a report to the ProjectData Access Committee, if requested, on completion of your study of the Project Data. Such report will include the data resulting from your study of the Project Data. The ProjectData Access Committee agrees to treat the report and all information, data, results, and conclusions contained within such report as confidential information. 22. You accept that Project Data may be protected by and subject to national and international laws and that You are responsible for ensuring compliance with any such applicable law. The ProjectData Access Committee reserves the right to request and inspect Your data security and management documentation to ensure the adequacy of data protection measures in countries that have no national laws comparable to that which pertain in the European Economic Area (EEA). 23. This agreement shall be construed, interpreted and governed by the laws of the Netherlands. Signed by: ……………………………………………………………. ………………………………….……………………………………. Name of Applicant: Legal representative of Applicant’s Institution: Affiliation of Applicant with Institution: Name of Applicant’s Institution: ……………………………………………………………. ……………………………………………………………………….. Place:………………………………………………….. Place:……………………………………………………………… Date:…………………………………………………… Date:……………………………..……………………………….. Stamp or Seal of Applicant’s Institution: ………………………………………………………………………..
Studies are experimental investigations of a particular phenomenon, e.g., case-control studies on a particular trait or cancer research projects reporting matching cancer normal genomes from patients.
Study ID | Study Title | Study Type |
---|---|---|
EGAS00001007350 | Other |
This table displays only public information pertaining to the files in the dataset. If you wish to access this dataset, please submit a request. If you already have access to these data files, please consult the download documentation.
ID | File Type | Size | Located in | |
---|---|---|---|---|
EGAF00008110204 | fastq.gz | 2.3 GB | ||
EGAF00008110205 | fastq.gz | 2.5 GB | ||
EGAF00008110206 | fastq.gz | 2.5 GB | ||
EGAF00008110207 | fastq.gz | 2.8 GB | ||
EGAF00008110208 | fastq.gz | 2.6 GB | ||
EGAF00008110209 | fastq.gz | 2.9 GB | ||
EGAF00008110210 | fastq.gz | 2.4 GB | ||
EGAF00008110211 | fastq.gz | 2.6 GB | ||
EGAF00008110212 | fastq.gz | 2.9 GB | ||
EGAF00008110213 | fastq.gz | 3.2 GB | ||
EGAF00008110214 | fastq.gz | 2.8 GB | ||
EGAF00008110215 | fastq.gz | 3.1 GB | ||
EGAF00008110216 | fastq.gz | 2.5 GB | ||
EGAF00008110217 | fastq.gz | 2.7 GB | ||
EGAF00008110218 | fastq.gz | 2.5 GB | ||
EGAF00008110219 | fastq.gz | 2.7 GB | ||
EGAF00008110220 | fastq.gz | 2.0 GB | ||
EGAF00008110221 | fastq.gz | 2.2 GB | ||
EGAF00008110222 | fastq.gz | 2.4 GB | ||
EGAF00008110223 | fastq.gz | 2.6 GB | ||
EGAF00008110224 | fastq.gz | 2.4 GB | ||
EGAF00008110225 | fastq.gz | 2.6 GB | ||
EGAF00008110226 | fastq.gz | 2.3 GB | ||
EGAF00008110227 | fastq.gz | 2.5 GB | ||
EGAF00008110228 | fastq.gz | 2.8 GB | ||
EGAF00008110229 | fastq.gz | 3.1 GB | ||
EGAF00008110230 | fastq.gz | 2.4 GB | ||
EGAF00008110231 | fastq.gz | 2.6 GB | ||
EGAF00008110232 | fastq.gz | 2.2 GB | ||
EGAF00008110233 | fastq.gz | 2.4 GB | ||
EGAF00008110234 | fastq.gz | 2.5 GB | ||
EGAF00008110235 | fastq.gz | 2.7 GB | ||
EGAF00008110236 | fastq.gz | 2.6 GB | ||
EGAF00008110237 | fastq.gz | 2.8 GB | ||
EGAF00008110238 | fastq.gz | 1.9 GB | ||
EGAF00008110239 | fastq.gz | 2.1 GB | ||
EGAF00008110240 | fastq.gz | 2.8 GB | ||
EGAF00008110241 | fastq.gz | 3.0 GB | ||
EGAF00008110242 | fastq.gz | 2.6 GB | ||
EGAF00008110243 | fastq.gz | 2.8 GB | ||
EGAF00008110244 | fastq.gz | 2.7 GB | ||
EGAF00008110245 | fastq.gz | 3.0 GB | ||
EGAF00008110246 | fastq.gz | 2.8 GB | ||
EGAF00008110247 | fastq.gz | 3.0 GB | ||
EGAF00008110248 | fastq.gz | 2.2 GB | ||
EGAF00008110249 | fastq.gz | 2.4 GB | ||
EGAF00008110250 | fastq.gz | 2.7 GB | ||
EGAF00008110251 | fastq.gz | 2.9 GB | ||
EGAF00008110252 | fastq.gz | 2.4 GB | ||
EGAF00008110253 | fastq.gz | 2.6 GB | ||
EGAF00008110254 | fastq.gz | 2.5 GB | ||
EGAF00008110255 | fastq.gz | 2.7 GB | ||
EGAF00008110256 | fastq.gz | 2.5 GB | ||
EGAF00008110257 | fastq.gz | 2.7 GB | ||
EGAF00008110258 | fastq.gz | 2.7 GB | ||
EGAF00008110259 | fastq.gz | 3.0 GB | ||
EGAF00008110260 | fastq.gz | 2.7 GB | ||
EGAF00008110261 | fastq.gz | 2.9 GB | ||
EGAF00008110262 | fastq.gz | 2.6 GB | ||
EGAF00008110263 | fastq.gz | 2.8 GB | ||
EGAF00008110264 | fastq.gz | 2.5 GB | ||
EGAF00008110265 | fastq.gz | 2.8 GB | ||
EGAF00008110266 | fastq.gz | 2.4 GB | ||
EGAF00008110267 | fastq.gz | 2.6 GB | ||
EGAF00008110268 | fastq.gz | 2.3 GB | ||
EGAF00008110269 | fastq.gz | 2.5 GB | ||
EGAF00008110270 | fastq.gz | 2.4 GB | ||
EGAF00008110271 | fastq.gz | 2.6 GB | ||
EGAF00008110272 | fastq.gz | 2.7 GB | ||
EGAF00008110273 | fastq.gz | 2.9 GB | ||
EGAF00008110274 | fastq.gz | 2.4 GB | ||
EGAF00008110275 | fastq.gz | 2.6 GB | ||
EGAF00008110276 | fastq.gz | 2.7 GB | ||
EGAF00008110277 | fastq.gz | 2.9 GB | ||
EGAF00008110278 | fastq.gz | 2.4 GB | ||
EGAF00008110279 | fastq.gz | 2.6 GB | ||
EGAF00008110280 | fastq.gz | 2.6 GB | ||
EGAF00008110281 | fastq.gz | 2.8 GB | ||
EGAF00008110282 | fastq.gz | 2.2 GB | ||
EGAF00008110283 | fastq.gz | 2.5 GB | ||
EGAF00008110284 | fastq.gz | 2.3 GB | ||
EGAF00008110285 | fastq.gz | 2.6 GB | ||
EGAF00008110286 | fastq.gz | 2.3 GB | ||
EGAF00008110287 | fastq.gz | 2.5 GB | ||
EGAF00008110288 | fastq.gz | 2.4 GB | ||
EGAF00008110289 | fastq.gz | 2.6 GB | ||
EGAF00008110290 | fastq.gz | 2.5 GB | ||
EGAF00008110291 | fastq.gz | 2.8 GB | ||
EGAF00008110292 | fastq.gz | 2.5 GB | ||
EGAF00008110293 | fastq.gz | 2.8 GB | ||
EGAF00008110294 | fastq.gz | 2.5 GB | ||
EGAF00008110295 | fastq.gz | 2.7 GB | ||
EGAF00008110296 | fastq.gz | 2.4 GB | ||
EGAF00008110297 | fastq.gz | 2.6 GB | ||
EGAF00008110298 | fastq.gz | 2.4 GB | ||
EGAF00008110299 | fastq.gz | 2.6 GB | ||
EGAF00008110300 | fastq.gz | 2.5 GB | ||
EGAF00008110301 | fastq.gz | 2.7 GB | ||
EGAF00008110302 | fastq.gz | 2.6 GB | ||
EGAF00008110303 | fastq.gz | 2.8 GB | ||
EGAF00008110304 | fastq.gz | 2.5 GB | ||
EGAF00008110305 | fastq.gz | 2.7 GB | ||
EGAF00008110306 | fastq.gz | 2.5 GB | ||
EGAF00008110307 | fastq.gz | 2.8 GB | ||
EGAF00008110308 | fastq.gz | 3.1 GB | ||
EGAF00008110309 | fastq.gz | 3.4 GB | ||
EGAF00008110310 | fastq.gz | 2.5 GB | ||
EGAF00008110311 | fastq.gz | 2.8 GB | ||
EGAF00008110312 | fastq.gz | 2.3 GB | ||
EGAF00008110313 | fastq.gz | 2.5 GB | ||
EGAF00008110314 | fastq.gz | 2.4 GB | ||
EGAF00008110315 | fastq.gz | 2.7 GB | ||
EGAF00008110316 | fastq.gz | 2.2 GB | ||
EGAF00008110317 | fastq.gz | 2.4 GB | ||
EGAF00008110318 | fastq.gz | 2.3 GB | ||
EGAF00008110319 | fastq.gz | 2.5 GB | ||
EGAF00008110320 | fastq.gz | 2.2 GB | ||
EGAF00008110321 | fastq.gz | 2.4 GB | ||
EGAF00008110322 | fastq.gz | 1.8 GB | ||
EGAF00008110323 | fastq.gz | 1.9 GB | ||
EGAF00008110324 | fastq.gz | 1.6 GB | ||
EGAF00008110325 | fastq.gz | 1.6 GB | ||
EGAF00008110326 | fastq.gz | 1.6 GB | ||
EGAF00008110327 | fastq.gz | 1.6 GB | ||
EGAF00008110328 | fastq.gz | 1.9 GB | ||
EGAF00008110329 | fastq.gz | 2.0 GB | ||
EGAF00008110330 | fastq.gz | 1.7 GB | ||
EGAF00008110331 | fastq.gz | 1.8 GB | ||
EGAF00008110332 | fastq.gz | 1.3 GB | ||
EGAF00008110333 | fastq.gz | 1.4 GB | ||
EGAF00008110334 | fastq.gz | 1.9 GB | ||
EGAF00008110335 | fastq.gz | 2.0 GB | ||
EGAF00008110336 | fastq.gz | 1.4 GB | ||
EGAF00008110337 | fastq.gz | 1.4 GB | ||
EGAF00008110338 | fastq.gz | 3.3 GB | ||
EGAF00008110339 | fastq.gz | 3.4 GB | ||
EGAF00008110340 | fastq.gz | 1.9 GB | ||
EGAF00008110341 | fastq.gz | 2.0 GB | ||
EGAF00008110342 | fastq.gz | 2.2 GB | ||
EGAF00008110343 | fastq.gz | 2.2 GB | ||
EGAF00008110344 | fastq.gz | 2.7 GB | ||
EGAF00008110345 | fastq.gz | 2.8 GB | ||
EGAF00008110346 | fastq.gz | 2.2 GB | ||
EGAF00008110347 | fastq.gz | 2.3 GB | ||
EGAF00008110348 | fastq.gz | 1.5 GB | ||
EGAF00008110349 | fastq.gz | 1.5 GB | ||
EGAF00008110350 | fastq.gz | 2.2 GB | ||
EGAF00008110351 | fastq.gz | 2.3 GB | ||
EGAF00008110352 | fastq.gz | 1.3 GB | ||
EGAF00008110353 | fastq.gz | 1.3 GB | ||
EGAF00008110354 | fastq.gz | 2.4 GB | ||
EGAF00008110355 | fastq.gz | 2.5 GB | ||
EGAF00008110356 | fastq.gz | 2.4 GB | ||
EGAF00008110357 | fastq.gz | 2.5 GB | ||
EGAF00008110358 | fastq.gz | 2.3 GB | ||
EGAF00008110359 | fastq.gz | 2.4 GB | ||
EGAF00008110360 | fastq.gz | 1.8 GB | ||
EGAF00008110361 | fastq.gz | 1.9 GB | ||
EGAF00008110362 | fastq.gz | 2.1 GB | ||
EGAF00008110363 | fastq.gz | 2.1 GB | ||
EGAF00008110364 | fastq.gz | 2.6 GB | ||
EGAF00008110365 | fastq.gz | 2.7 GB | ||
EGAF00008110366 | fastq.gz | 2.2 GB | ||
EGAF00008110367 | fastq.gz | 2.3 GB | ||
EGAF00008110368 | fastq.gz | 1.8 GB | ||
EGAF00008110369 | fastq.gz | 1.8 GB | ||
EGAF00008110370 | fastq.gz | 2.6 GB | ||
EGAF00008110371 | fastq.gz | 2.6 GB | ||
EGAF00008110372 | fastq.gz | 2.1 GB | ||
EGAF00008110373 | fastq.gz | 2.2 GB | ||
EGAF00008110374 | fastq.gz | 2.6 GB | ||
EGAF00008110375 | fastq.gz | 2.6 GB | ||
EGAF00008110376 | fastq.gz | 1.4 GB | ||
EGAF00008110377 | fastq.gz | 1.5 GB | ||
EGAF00008110378 | fastq.gz | 2.3 GB | ||
EGAF00008110379 | fastq.gz | 2.4 GB | ||
176 Files (426.3 GB) |