Need Help?

Intellance-2: TruSight Tumor 170 panel based RNA-seq

Intellance-2: TruSight Tumor 170 panel based RNA-seq

Request Access

DUO:0000019
version: 2021-02-23

publication required

This data use modifier indicates that requestor agrees to make results of studies using the data available to the larger scientific community.

DUO:0000021
version: 2021-02-23

ethics approval required

This data use modifier indicates that the requestor must provide documentation of local IRB/ERB approval.

DUO:0000026
version: 2021-02-23

user specific restriction

This data use modifier indicates that use is limited to use by approved users.

DUO:0000027
version: 2021-02-23

project specific restriction

This data use modifier indicates that use is limited to use within an approved project.

DUO:0000028
version: 2021-02-23

institution specific restriction

This data use modifier indicates that use is limited to use within an approved institution.

EORTC Data Sharing POL008

https://www.eortc.org/data-sharing/ https://www.eortc.org/app/uploads/2017/03/pol008.pdf Data Sharing Policy 008 1 PURPOSE To define the terms and conditions under which electronic records of individual data from all or from subsets of the patients from EORTC studies may be shared with other organizations or individual researchers for the purpose of scientific research projects or may be posted on data repositories. 2 SCOPE This policy applies whenever electronic records of individual data from all or from subsets of the patients from EORTC studies are shared with individual researchers not employed by EORTC Headquarters or with other academic or non-academic (including for profit) organizations; except for the routine safety reports to authorities and for contractually agreed data transfers to third parties during the course of a trial. This policy does not apply when data of their own patients are transferred back to an EORTC site or when data of the patients from an academic Group that contributed to an intergroup study managed at EORTC are transferred back to that Group, since this requires no specific approval beyond the study intergroup agreement. The shared data may include data generated from EORTC translational research projects. However, only requests for data available to the EORTC Headquarters are covered by this policy. Requests for access and use of Human Biological Material (HBM) are covered by a separate policy (EORTC POL020). Requests for additional data collection usually require further ethical committee and/or other regulatory bodies to review the project and may also require obtaining additional patient consent and/or authorization. Consequently, the information obtained is often incomplete. Retrospective collection of data is expensive and time consuming for the EORTC. Therefore, requests for projects necessitating further data collection must be submitted for review to the EORTC using the appropriate channels (see Policy 016). 3 DEFINITIONS ♦ Coded data: Refers to the result of the process of replacing personal identifiers linked to data or HBM by a code for confidentiality and privacy reasons (also, known as "linked anonymized" or "pseudonymized"). To be distinguished from “anonymized” that refers to when the link between the data and human biological material is irreversibly broken. ♦ EORTC data: All and any electronic records of human clinical and biological data (included but not limited to genetic, any -omic or other molecular data) or centrally stored imaging data in Digital Imaging and Communications in Medicine (DICOM) file format obtained from patients entered in EORTC studies; i.e. individual patient data. Data does not include human biological material samples. As EORTC works exclusively with coded data, the term "EORTC data" in the present document refer exclusively to coded EORTC data. ♦ Data applicant: The person seeking access to EORTC data. ♦ External research project (ERP): A research project that uses EORTC data, the statistical analyses and publications of which are not centralized at the EORTC Headquarters, and thus requires these data to be released outside EORTC Headquarters. ♦ EORTC Research project (EORTC-RP): An EORTC research project that uses EORTC data and the statistical analyses and publications of which are centralized at the EORTC Headquarters but that may require that data be released outside EORTC Headquarters to partner researchers or research organizations. ♦ Data Sharing Coordinator: The EORTC staff member responsible for reviewing, approving and following up the data sharing agreements. ♦ Data Access Committee (DAC) Coordinator: The EORTC Headquarters staff member who is member of the different EORTC DACs. He/she is responsible for executing the decisions of the ODAC regarding EORTC genetic, any -omic and other molecular data stored on access controlled external repositories and approve the posting of data by investigators on public repositories. He/she is also responsible for following-up the decisions of the IDAC regarding the release of EORTC images stored on access controlled imaging platforms in relationship with the EORTC Headquarters expert in imaging translational research. ♦ EORTC OMICS Data Access Committee (ODAC): The EORTC DAC responsible for making decisions regarding the access to EORTC genetic, any -omic and other molecular data that are stored in access controlled external repositories and for granting authorization to post data on public repositories. Inside the EORTC Headquarters, the ODAC functions under the hierarchical supervision of the Medical Director and it reports to the chair of the Translational Research Committee at the EORTC organization level. The ODAC is composed of at least the DAC Coordinator, the Head of the EORTC Translational Research, radiotherapy, and imaging department (or delegate) and at least one more staff member from the Translational Research, Radiotherapy, and Imaging department of the EORTC Headquarters. ♦ EORTC Imaging Data Access Committee (IDAC): The EORTC DAC responsible for making decisions regarding the access to EORTC radiological images that are stored in access controlled imaging platforms. Inside the EORTC Headquarters, the IDAC functions under the hierarchical supervision of the Medical Director and it reports to the chair of the Translational Research Committee at the EORTC organization level. The IDAC is composed of at least the DAC Coordinator, the Head of the EORTC Translational Research, radiotherapy, and imaging department (or delegate) and at least one more staff member from the Translational Research, Radiotherapy, and Imaging department of the EORTC Headquarters. 4 POLICY EORTC is committed to ensuring that the data generated from its studies be put to good use by the cancer research community and, whenever possible, are translated to deliver patient benefit. It is therefore EORTC's policy to consider for sharing upon request from qualified scientific and medical researchers all data generated from its research whilst safeguarding intellectual property, the privacy of patients and confidentiality. Considering that ongoing research contributing to the completion of datasets must not be compromised by premature or opportunistic sharing and analysis of data, the EORTC will not release the data of its study until the primary study results have been published; unless authorization for release has been granted according to the terms of EORTC Policy 009. Whilst EORTC complies with the OECD Principles and Guidelines for Access to Research Data from Public Funding and with the National Institutes of Health Final Statement on Sharing Research Data released on February 26, 2003; it is committed to do so within the limits needed to guarantee the protection of personal data in accordance with the EU data protection rules and other applicable European legislation. Upon explicit approval of EORTC, coded individual patient data that were generated in the framework of translational research studies may be deposited in online public repositories or databases with or without restrictions on access. Authorization for posting data will be granted by the ODAC according to the type and level of the data, and the potential risk associated to the data release. Restricted controlled access to the posted data will then be under the management of the ODAC, unless a specific process/committee exists for the repository to which the ODAC would already have delegated responsibilities. EORTC also reserves itself the right to refuse sharing of data if it judges that the data repository in question does not offer sufficient system protection. 5 HOW TO REQUEST EORTC DATA Data applicants are required to submit a research proposal to document the legitimacy of the research question and the qualifications of the requestor. Research proposals should include, and will be evaluated against the following: a description of the data being requested, including the hypothesis to be tested; the rationale for the proposed research; the analysis plan; a publication and posting plan; qualifications and experience of the proposed research team; and the source of any research funding. Some projects that are performed outside the premises of the EORTC Headquarters and thus require data sharing are however conducted in close collaboration with EORTC Headquarters staff or EORTC Groups, so that the resulting publication(s) will be co-authored by an EORTC staff and/or be published on behalf of EORTC. Such circumstances must be declared upfront in the data submission form so that appropriate terms of use are agreed upon upfront. EORTC may also request to be associated to the research when it finds it relevant. Whenever this was not agreed upfront, and/or there is no EORTC co-author, but the publication appears 'on behalf of EORTC' or if “EORTC” appears in the title, then the use of that mention will require an additional approval from EORTC to modify the initially agreed terms of use. Instructions and a request form are available at http://www.eortc.org/investigators/data-sharing/. All questions concerning EORTC data sharing should be addressed to DataSharing@eortc.be. 6 REVIEW AND APPROVAL OF DATA ACCESS REQUESTS Review of the requests by the relevant EORTC bodies is coordinated by the Data Sharing Coordinator. The scientific merit of each specific request will be evaluated as well as its feasibility: whether there is sufficient data to provide adequate information for analysis, the availability of the required data and the potential costs. Any release of data will also consider individual patient's rights to privacy. The authorization for release will be granted by the Data Sharing Coordinator once all reviewers (detailed in the sections below) have approved the request, and provided legal and contractual agreements allow it. In case of disagreement among study coordinators and/or steering committees of the studies for which data is requested, the chairpersons of the EORTC groups who conducted the trial will arbitrate their positions. EORTC reserves itself the right to deny access to data if similar research is already being conducted by EORTC itself. The EORTC will notify the data applicant of the final decision by e-mail within two (2) months of the application and will inform of the reasons for rejection, whenever data access is not granted. The timing of the data release will be decided by the study statistician for the databases located at EORTC Headquarters. The timing for granting access to genetic, any -omic and other molecular data stored on access controlled external depositories, and to images stored on access controlled imaging platforms will be decided by the DAC Coordinator in order to maintain the study integrity, in accordance with EORTC POL009. The possibility of transferring any EORTC data will be checked against the terms of the Patient Informed Consent. The review process is adapted to the nature of the data that is requested, of the research purpose and of whether the data applicant is from academia as explained below. 6.1 Release of data for projects not yet approved by EORTC The proposal will be reviewed by the steering committee or study coordinator of the studies for which data is sought and by the chairpersons of the EORTC groups who conducted the trial; by the study statistician(s), and by the EORTC Data Sharing Coordinator, as well as by the EORTC staff or EORTC members that are identified as future co-authors of the resulting publication(s). Whenever the request concerns data from the quality of life studies (field studies and the like) the proposal will be approved by representatives of the Quality of Life Group through the Quality of Life Unit (see 6.6). Additionally, when such requests involve EORTC genetic, any -omic or other molecular data stored on access controlled external repositories or EORTC images stored on access controlled imaging platforms, review and approval of the ODAC or IDAC, respectively, is also needed. Finally, release of data collected in a clinical or translational research study conducted under a binding agreement between EORTC and a pharmaceutical/biotechnology company must be in compliance with the terms of this agreement and must be approved by both EORTC and the company. The terms of use in Section 7 apply. 6.2 Release of data for projects already approved by EORTC Specific projects linked to EORTC studies or research projects for example but not limited to translational research projects may involve sending clinical data to other locations, such as to the institution performing the lab work, for analysis. As such, the necessary data exchanges required for conducting such projects may be already approved by the EORTC. If the specific data required and a summary of the analysis plans were clearly described in the study protocol approved by EORTC then data requests for these projects will be approved without further scientific review. The terms of use in Section 7 still apply. If the specific data required and a summary of the analysis plans were clearly described in a research project that was already approved by EORTC Translational Research Advisory Committee or if the data request concerns data release related to an EORTC-RP then the data request will be approved without further scientific review. The terms of use in section 7 still apply Additionally, when such requests involve EORTC genetic, any -omic or other molecular data stored on access controlled external repositories or EORTC images on access controlled imaging platforms, review and approval of the ODAC or IDAC, respectively, is also needed. The terms of use in Section 7 apply. If the requested data or the planned analyses go beyond what EORTC has already agreed then the request must be reviewed by the EORTC, as described in Section 6.1 above. 6.3 Requests for data sets to use for illustration of statistical methodology Requests for data sets to use for illustration of statistical methods in papers intended for publication in the statistical literature follow a simplified path. The Data Sharing Coordinator will assess with the Heads of the statistics department if the data set appears to be appropriate for the project. If so, the Data Sharing Coordinator can approve the request without further review. However, when such requests involve data from studies fully supported by a pharmaceutical company, the necessary approval from the company will be obtained, in accordance with the contractual agreements between EORTC and that company. The study coordinators of the studies involved and the chairpersons of the EORTC groups who conducted the trial(s) will be informed that the data is being used for that purpose. The terms of use in Section 7 still apply. 6.4 Requests for accessing only genetic, any -omic and other molecular data that are stored on access controlled external repositories Such requests will be handled through ODAC which will seek approval of the relevant trial steering committee. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.5 Requests for accessing imaging data in DICOM file format Such requests will be handled through the IDAC which will seek approval of the relevant trial steering committee. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.6 Requests for accessing data of Quality of Life studies Such requests will be handled through the EORTC Quality of Life department which will seek approval of the QLG Group steering committee and the study PI. Whenever the request also covers other type of data centrally stored at the EORTC Headquarters, the approval process specified in 6.1 additionally applies. The terms of use in Section 7 still apply. 6.7 Requests from commercial entities or with commercial purpose Requests emanating from non-academic researchers or from for-profit organizations will follow the review path described in sections 6.1 to 6.5 above. They will additionally be reviewed by the EORTC Directors. Fees may apply and will be calculated on a case by case basis. The feasibility of transferring the data for non-academic research will also be checked against the terms of the Patient Informed Consent. 7 TERMS OF USE Upon submission of the request, the data applicant must agree to the Terms of Use specified in the application form The EORTC must be acknowledged for sharing the data for the research. Unless an EORTC staff is co-authoring the publication or if it was agreed upfront that the publication would be "on behalf of EORTC" or as "EORTC research", the publication must contain the following disclosure “The contents of this publication and methods used are solely the responsibility of the authors and do not necessarily represent the official views of the EORTC ". Additionally, for all projects, the data applicant commits to provide EORTC with references of any publication resulting from research that used EORTC data within two (2) months of the publication; unless the publication is made "on behalf of EORTC" or if "EORTC appears in the study title" in which case the data applicant must submit the publication to DataSharing@eortc.be prior to presentation and/or submission of the results for publication. EORTC reserves itself the right to request the establishment of a formal contract in addition to the above terms of use, when sharing particularly sensitive data and/or for requests in the scope of section 6.5. 8 TERMINATION OF THE AGREEMENT The data applicant must notify EORTC of the completion of the project. This is best done by an email addressed to DataSharing@eortc.be. EORTC reserves itself the right to cease data sharing agreements upon breach of the agreed terms and conditions for use. Requests for extension of existing data sharing agreement must be requested online using the data request form (see section 5). The data request must clearly stipulate that the demand is an extension of an existing agreement and provide reference to that former agreement. Review and approval of extensions follow the rules specified in section 6 above. 9 QUESTIONS Questions regarding the present policy or data sharing should be addressed by email to DataSharing@eortc.be.

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
EGAS00001005437 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 Quality Report
Located in
EGAF00005406219 bam 539.0 MB Report
EGAF00005406220 bam 842.9 MB Report
EGAF00005406221 bam 867.6 MB Report
EGAF00005406222 bam 762.7 MB Report
EGAF00005406223 bam 952.0 MB Report
EGAF00005406224 bam 651.5 MB Report
EGAF00005406225 bam 408.8 MB Report
EGAF00005406226 bam 789.4 MB Report
EGAF00005406227 bam 748.2 MB Report
EGAF00005406228 bam 890.4 MB Report
EGAF00005406229 bam 395.8 MB Report
EGAF00005406230 bam 995.5 MB Report
EGAF00005406231 bam 593.8 MB Report
EGAF00005406232 bam 847.0 MB Report
EGAF00005406233 bam 790.0 MB Report
EGAF00005406234 bam 757.5 MB Report
EGAF00005406235 bam 863.7 MB Report
EGAF00005406236 bam 962.9 MB Report
EGAF00005406237 bam 820.1 MB Report
EGAF00005406238 bam 872.1 MB Report
EGAF00005406239 bam 751.2 MB Report
EGAF00005406240 bam 921.8 MB Report
EGAF00005406241 bam 815.0 MB Report
EGAF00005406242 bam 906.5 MB Report
EGAF00005406243 bam 835.9 MB Report
EGAF00005406244 bam 706.1 MB Report
EGAF00005406245 bam 954.4 MB Report
EGAF00005406246 bam 786.5 MB Report
EGAF00005406247 bam 783.6 MB Report
EGAF00005406248 bam 938.2 MB Report
EGAF00005406249 bam 862.8 MB Report
EGAF00005406250 bam 526.2 MB Report
EGAF00005406251 bam 703.5 MB Report
EGAF00005406252 bam 713.7 MB Report
EGAF00005406253 bam 947.0 MB Report
EGAF00005406254 bam 1.1 GB Report
EGAF00005406255 bam 812.8 MB Report
EGAF00005406256 bam 866.4 MB Report
EGAF00005406257 bam 936.4 MB Report
EGAF00005406258 bam 681.4 MB Report
EGAF00005406259 bam 889.6 MB Report
EGAF00005406260 bam 889.6 MB Report
EGAF00005406261 bam 871.6 MB Report
EGAF00005406262 bam 525.6 MB Report
EGAF00005406263 bam 902.1 MB Report
EGAF00005406264 bam 745.6 MB Report
EGAF00005406265 bam 746.2 MB Report
EGAF00005406266 bam 858.2 MB Report
EGAF00005406267 bam 843.2 MB Report
EGAF00005406268 bam 876.0 MB Report
EGAF00005406269 bam 712.8 MB Report
EGAF00005406270 bam 701.3 MB Report
EGAF00005406271 bam 822.6 MB Report
EGAF00005406272 bam 897.1 MB Report
EGAF00005406273 bam 923.7 MB Report
EGAF00005406274 bam 815.7 MB Report
EGAF00005406275 bam 964.5 MB Report
EGAF00005406276 bam 568.5 MB Report
EGAF00005406277 bam 850.4 MB Report
EGAF00005406278 bam 932.5 MB Report
EGAF00005406279 bam 1.0 GB Report
EGAF00005406280 bam 782.2 MB Report
EGAF00005406281 bam 819.1 MB Report
EGAF00005406282 bam 901.9 MB Report
EGAF00005406283 bam 607.4 MB Report
EGAF00005406284 bam 876.9 MB Report
EGAF00005406285 bam 559.1 MB Report
EGAF00005406286 bam 823.9 MB Report
EGAF00005406287 bam 329.8 MB Report
EGAF00005406288 bam 1.0 GB Report
EGAF00005406289 bam 538.3 MB Report
EGAF00005406290 bam 827.5 MB Report
EGAF00005406291 bam 702.0 MB Report
EGAF00005406292 bam 846.7 MB Report
EGAF00005406293 bam 902.0 MB Report
EGAF00005406294 bam 676.4 MB Report
EGAF00005406295 bam 732.2 MB Report
EGAF00005406296 bam 791.7 MB Report
EGAF00005406297 bam 776.1 MB Report
EGAF00005406298 bam 637.2 MB Report
EGAF00005406299 bam 959.8 MB Report
EGAF00005406300 bam 883.4 MB Report
EGAF00005406301 bam 759.4 MB Report
EGAF00005406302 bam 791.0 MB Report
EGAF00005406303 bam 1.1 GB Report
EGAF00005406304 bam 604.7 MB Report
EGAF00005406305 bam 392.5 MB Report
EGAF00005406306 bam 742.9 MB Report
EGAF00005406307 bam 878.8 MB Report
EGAF00005406308 bam 772.2 MB Report
EGAF00005406309 bam 874.7 MB Report
EGAF00005406310 bam 826.0 MB Report
EGAF00005406311 bam 1.1 GB Report
EGAF00005406312 bam 901.0 MB Report
EGAF00005406313 bam 906.4 MB Report
EGAF00005406314 bam 988.8 MB Report
EGAF00005406315 bam 789.3 MB Report
EGAF00005406316 bam 530.8 MB Report
EGAF00005406317 bam 847.6 MB Report
EGAF00005406318 bam 773.3 MB Report
EGAF00005406319 bam 678.1 MB Report
EGAF00005406320 bam 765.5 MB Report
EGAF00005406321 bam 840.1 MB Report
EGAF00005406322 bam 782.0 MB Report
EGAF00005406323 bam 859.0 MB Report
EGAF00005406324 bam 939.9 MB Report
EGAF00005406325 bam 527.6 MB Report
EGAF00005406326 bam 914.2 MB Report
EGAF00005406327 bam 776.7 MB Report
EGAF00005406328 bam 899.1 MB Report
EGAF00005406329 bam 877.6 MB Report
EGAF00005406330 bam 807.8 MB Report
EGAF00005406331 bam 386.5 MB Report
EGAF00005406332 bam 993.6 MB Report
EGAF00005406333 bam 895.3 MB Report
EGAF00005406334 bam 921.5 MB Report
EGAF00005406335 bam 1.0 GB Report
EGAF00005406336 bam 779.4 MB Report
EGAF00005406337 bam 677.4 MB Report
EGAF00005406338 bam 985.2 MB Report
EGAF00005406339 bam 711.9 MB Report
EGAF00005406340 bam 693.8 MB Report
EGAF00005406341 bam 827.2 MB Report
EGAF00005406342 bam 903.9 MB Report
EGAF00005406343 bam 824.4 MB Report
EGAF00005406344 bam 771.6 MB Report
EGAF00005406345 bam 898.9 MB Report
EGAF00005406346 bam 802.3 MB Report
EGAF00005406347 bam 803.0 MB Report
EGAF00005406348 bam 1.0 GB Report
EGAF00005406349 bam 628.6 MB Report
EGAF00005406350 bam 907.1 MB Report
EGAF00005406351 bam 755.8 MB Report
EGAF00005406352 bam 843.2 MB Report
EGAF00005406353 bam 832.0 MB Report
EGAF00005406354 bam 699.6 MB Report
EGAF00005406355 bam 717.6 MB Report
EGAF00005406356 bam 773.6 MB Report
EGAF00005406357 bam 553.1 MB Report
EGAF00005406358 bam 730.7 MB Report
EGAF00005406359 bam 736.4 MB Report
EGAF00005406360 bam 827.7 MB Report
EGAF00005406361 bam 993.0 MB Report
EGAF00005406362 bam 918.6 MB Report
EGAF00005406363 bam 749.4 MB Report
EGAF00005406364 bam 786.4 MB Report
EGAF00005406365 bam 344.3 MB Report
EGAF00005406366 bam 783.8 MB Report
EGAF00005406367 bam 817.4 MB Report
EGAF00005406368 bam 864.9 MB Report
EGAF00005406369 bam 715.9 MB Report
EGAF00005406370 bam 750.9 MB Report
EGAF00005406371 bam 903.7 MB Report
EGAF00005406372 bam 943.9 MB Report
EGAF00005406373 bam 753.8 MB Report
EGAF00005406374 bam 959.4 MB Report
EGAF00005406375 bam 506.5 MB Report
EGAF00005406376 bam 1.0 GB Report
EGAF00005406377 bam 890.6 MB Report
EGAF00005406378 bam 588.0 MB Report
EGAF00005406379 bam 768.3 MB Report
EGAF00005406380 bam 658.0 MB Report
EGAF00005406381 bam 799.0 MB Report
EGAF00005406382 bam 751.8 MB Report
EGAF00005406383 bam 583.7 MB Report
EGAF00005406384 bam 826.1 MB Report
EGAF00005406385 bam 1.1 GB Report
EGAF00005406386 bam 774.6 MB Report
EGAF00005406387 bam 897.8 MB Report
EGAF00005406388 bam 706.0 MB Report
EGAF00005406389 bam 615.7 MB Report
EGAF00005406390 bam 966.7 MB Report
EGAF00005406391 bam 845.9 MB Report
EGAF00005406392 bam 708.9 MB Report
EGAF00005406393 bam 665.0 MB Report
EGAF00005406394 bam 700.4 MB Report
EGAF00005406395 bam 929.2 MB Report
EGAF00005406396 bam 778.0 MB Report
EGAF00005406397 bam 842.3 MB Report
EGAF00005406398 bam 894.4 MB Report
EGAF00005406399 bam 854.7 MB Report
EGAF00005406400 bam 747.5 MB Report
EGAF00005406401 bam 770.9 MB Report
EGAF00005406402 bam 1.1 GB Report
EGAF00005406403 bam 876.2 MB Report
EGAF00005406404 bam 913.2 MB Report
EGAF00005406405 bam 913.2 MB Report
EGAF00005406406 bam 825.4 MB Report
EGAF00005406407 bam 816.4 MB Report
EGAF00005406408 bam 851.3 MB Report
EGAF00005406409 bam 664.0 MB Report
EGAF00005406410 bam 750.9 MB Report
EGAF00005406411 bam 722.1 MB Report
EGAF00005406412 bam 755.0 MB Report
EGAF00005406413 bam 968.8 MB Report
EGAF00005406414 bam 838.2 MB Report
EGAF00005406415 bam 737.2 MB Report
EGAF00005406416 bam 786.9 MB Report
EGAF00005406417 bam 785.2 MB Report
EGAF00005406418 bam 784.5 MB Report
EGAF00005406419 bam 55.4 kB Report
EGAF00005406420 bam 974.3 MB Report
EGAF00005406421 bam 878.4 MB Report
EGAF00005406422 bam 815.0 MB Report
EGAF00005406423 bam 849.8 MB Report
EGAF00005406424 bam 902.8 MB Report
EGAF00005406425 bam 807.7 MB Report
EGAF00005406426 bam 901.9 MB Report
EGAF00005406427 bam 962.1 MB Report
EGAF00005406428 bam 1.0 GB Report
EGAF00005406429 bam 922.5 MB Report
EGAF00005406430 bam 729.4 MB Report
EGAF00005406431 bam 859.2 MB Report
EGAF00005406432 bam 859.1 MB Report
EGAF00005406433 bam 442.3 MB Report
EGAF00005406434 bam 731.0 MB Report
EGAF00005406435 bam 876.7 MB Report
EGAF00005406436 bam 453.8 MB Report
EGAF00005406437 bam 840.0 MB Report
EGAF00005406438 bam 493.0 MB Report
EGAF00005406439 bam 716.4 MB Report
EGAF00005406440 bam 980.4 MB Report
EGAF00005406441 bam 838.9 MB Report
EGAF00005406442 bam 525.3 MB Report
EGAF00005406443 bam 829.0 MB Report
225 Files (179.1 GB)