tran smart api_nov2013
DESCRIPTION
TranSMART API & Plugin Development: A case study. Presentation at the tranSMART community meeting in Chilly-Mazarin at Sanofi R&D in November 2013.TRANSCRIPT
![Page 1: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/1.jpg)
TranSMART API & Plugin Development: A Case Study
Kees van Bochove, The Hyve TranSMART Community MeeCng
Chilly-‐Mazarin, France
November 6, 2013
![Page 2: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/2.jpg)
Requirements
• HTML5 Genome Browser (in-‐place in UI) • Drag-‐n-‐drop of High-‐Dimensional Data Nodes – VisualizaCon of Genomic Variants
– VisualizaCon of Copy Number VariaCon Data
• VisualizaCon of public data (gene annotaCons, SNP chip coverage, COSMIC annotaCons etc.)
• Switching between genome builds
![Page 3: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/3.jpg)
Community ConsultaCon • Ask transmart-‐discuss mailing list what people are using / planning to use as genome browser
• Ask the same on the LinkedIn group
• Start a wiki topic on the tranSMART FoundaCon wiki with an inventory of pro’s and con’s of the various genome browsers available
![Page 4: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/4.jpg)
SoluCon
• Dalliance genome browser chosen as frontend • MyDAS was chosen as backend
• Both implemented as plugins
• Core API had to be extended with methods for retrieving genomic variant data
![Page 5: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/5.jpg)
Emerging tranSMART Architecture
Kees van Bochove -‐ The Hyve
![Page 6: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/6.jpg)
Extend the core API
![Page 7: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/7.jpg)
Write some tests
![Page 8: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/8.jpg)
Create some implemenCng plugins
• h`ps://github.com/thehyve/transmart-‐mydas • h`ps://github.com/thehyve/dalliance-‐plugin
DB
MyDAS Backend Plugin Dalliance Frontend Plugin
TranSMART Core API
![Page 9: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/9.jpg)
Add them to transmartApp
but don’t force it upon others
![Page 10: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/10.jpg)
Leverage other branches • ImplemenCng VCF loading (and viewing) and GWAS loading and viewing in tranSMART
• VCF loader scripts requested by email and ported to Postgres
• Also, conflicCng variant definiCons (SNP loading) were present in the J&J branch
• It proved challenging to merge both approaches, but we succeeded in the end
• GeneraCng more docs on the wiki!
![Page 11: Tran smart api_nov2013](https://reader033.vdocument.in/reader033/viewer/2022051514/54b36fc84a79594b608b456d/html5/thumbnails/11.jpg)
2. Drag genomic node on genome browser
The end result