Abstract 3605: ICGC in the cloud
Notice bibliographique
Résumé
Abstract In November 2015 members of this consortium and the International Cancer Genome Consortium (ICGC) jointly announced the availability of more than 1,300 whole cancer genomes in the Amazon Web Services’ elastic compute cloud (EC2). Another 480 whole cancer genomes are available in the Cancer Genome Collaboratory, an academic cloud being built by this consortium. By making the data available in cloud compute form, researchers benefit from the high availability, scalability and economy offered by cloud services, and to avoid the large investment in compute resources and the time needed to download the data. Over the next year, we will increase the number of ICGC genomes available in the cloud, with the goal of placing the entire ICGC data set of ∼25,000 donors in academic and commercial clouds when the project is completed in 2018. For information and a getting-started guide, see https://dcc.icgc.org/icgc-in-the-cloud. Cloud computing represents a fundamental shift in the way that cancer genomics is performed. Because of the large size of the ICGC data set, it can take many months to download the data across a typical university broadband connection, and it requires a substantial investment in hardware in order to analyze it. In practice, this has meant that only large computational groups could perform whole-genome analysis at scale. Using the cloud, research groups of any size can launch large analytic processes, pay only for the compute that they use, and avoid charges for data transfer and long-term data storage. A practical demonstration of the power of working in compute clouds comes from our ongoing collaboration with the PanCancer Analysis of Whole Genomes Project (PCAWG; https://dcc.icgc.org/pcawg), which seeks to interpret patterns of variation in both coding and non-coding portions of cancer genomes. Upwards of 2,800 ICGC whole cancer genomes were subjected to a uniform data processing pipeline that included whole genome alignment, uniform quality control, and standardized germline and somatic variant calling using a large number of software packages that were adapted to run efficiently in the cloud. Using a series of 14 academic and commercial compute clouds, we were able to process this 800 terabyte data set in just over a year's time. Given the improvements in the software that occurred over this period, the whole project would take less than 4 months on just a single commercial cloud if we were to start over. When the project is completed later in 2016, we will again use academic and compute clouds to publish the PCAWG data, its major results, and all the software used during the analysis, thereby allowing the research community to integrate PCAWG with their own data sets, and apply the same analytic procedures. Citation Format: Christina K. Yung, Guillaume Bourque, Paul C. Boutros, Khaled El Emam, Vincent Ferretti, Bartha M. Knoppers, Brian O’Connor, B.F. Francis Ouellette, Cenk Sahinalp, Sohrab P. Shah, Lincoln D. Stein, Cancer Genome Collaboratory Consortium. ICGC in the cloud. [abstract]. In: Proceedings of the 107th Annual Meeting of the American Association for Cancer Research; 2016 Apr 16-20; New Orleans, LA. Philadelphia (PA): AACR; Cancer Res 2016;76(14 Suppl):Abstract nr 3605.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,003 | 0,008 |
| Méta-épidémiologie (sens strict) | 0,001 | 0,001 |
| Méta-épidémiologie (sens large) | 0,001 | 0,001 |
| Bibliométrie | 0,001 | 0,003 |
| Études des sciences et des technologies | 0,003 | 0,001 |
| Communication savante | 0,006 | 0,005 |
| Science ouverte | 0,002 | 0,005 |
| Intégrité de la recherche | 0,002 | 0,004 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,130 | 0,095 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».