SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Advancements in Non-Interactive Tools for Neuroimaging Software Development

seda avatar
seda
14 diapositives · 284 Views · Sep 07, 2014

This document presents the development and challenges of non-interactive tools in neuroimaging at Kitware. It highlights software processes, challenges, and significant tools like CMake, CDash, and XNAT, illustrating their roles in managing neuroimaging data and enhancing software quality. The advancements in high-performance computing, with a focus on GPU and GRID technologies, are also discussed, alongside their applications in schizophrenia, autism, and other neurodevelopmental disorders. The document emphasizes future work goals including integrated project tracking and improved resource allocation.

Advancements in Non-Interactive Tools for Neuroimaging Software Development - slide 1
01 / 14Advancements in Non-Interactive Tools for Neuroimaging Software Development
1 / 17

Télécharger la présentation

Advancements in Non-Interactive Tools for Neuroimaging Software Development
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Non-Interactive Tools Stephen Aylward, Kitware 2010.01.07

  2. Non-interactive tools Software Process • Schizophrenia • Neurodevelopment • Austism • MRI, PET, MR Perf • Shape Analysis • TBI, HD • RadOnc, Neurosurgery • 3,224 commits • 914,446 lines of code • 68 developers • GPU, GRID • Modularity • Qt, KWWidgets • C++, Python, TCL • Mac, Windows, Linux

  3. NA-MIC Kit Infrastructure • Software process • CMake and CPack • CDash and CTest • Data management • High-performance computing • Future work (NA-MIC Renewal)

  4. Software process Challenges: • Provide effective resources for developers…and users • Uphold community standards (quality, style, doc.) • Minimize burden on developers…and users

  5. CMake and CPack • Summary • Cross-platform build control from a single configuration file • Release Candidate 2.9 • 1200 downloads per day • Users: KDE, Blizzard (WoW), Nvidia • Features added • Library support: Qt, R • Superbuild: single run to download and configure multiple libraries and executables • Use cases • 3DSlicer, Teem, CLI Modules, MRML, 3DSlicer Qt

  6. CDash and CTest • Summary • Regression testing on multiple platforms (OS, CPU, Compilers) • Popular: 100 projects freely hosted on cdash.org • Robust: Over 1,000 submissions to ITK’s dashboard fest • Features added • CDash: new statistics, compression of historical data • CTest: parallel tests (ctest –j 8) • Use cases • Over 100 tests added to Slicer in the past few weeks • Coverage, Win7, Snow Leopard, …

  7. Data management • PubDB (MIDAS / Insight Journal) • The Extensible Neuroimaging Archive Toolkit (XNAT) • Management and exploration of neuroimaging and related data. • Secure database backend • Rich web-based user interface • XNAT 1.4 RC3 • XNAT Desktop (XND)

  8. XNAT • Features Added • More robust QC modeling • REST and LDAP support. • Improved memory footprint and efficiency. • Refactored Search UI in the listing engine. • Prebuilt XNAT images using VMWare and Virtualbox • xnatfs provides WebDav access to XNAT instances • Use cases • FetchMI, XNAT Desktop

  9. High-performance computing • GPU volume rendering • BatchMake • Scripting multiple Slicer modules for grid computing • Grid Wizard Enterprise (GWE) • Application scheduler that can run multiple (thousands) modules simultaneously on clusters / grids.

  10. GWE Features added • Interactive experiments' results browser. • Next generation: Record set explorer • CSV and generated commands dumps and preview. • Support for LSF and Lava cluster DRMs. • Ability to override auto-discovered DRMs with configured ones. • Ability to override default database installation location. • Function to extract experiments' parameters from text files. • Operations to delete, pause and resume experiments. Use Cases • Parameter space explorations, GWE MiniRetreats, Project Week

  11. Future work MUCH, including: 1. Integrated project tracking • Goal: generate a comprehensive timeline of a project. • Integrate SVN, CMake, CTest, CDash, Wiki, and BugTracker • E.g., Commit a code change: • wiki page is created for developer to describe the change, • related bug report is annotated, • subsequent dashboard changes are recorded, • all are linked from a central timeline

  12. Future work (cont.) 2. Centralized Test Management via CDash / MIDAS integration • CDash operates as a master for Dashboard slaves • Dashboard slaves set their availability and resources • CDash server allocates tests and testing data to the slaves • Ensures testing of important configurations • More efficient use of available resources • Allocations can change nightly to cover complex combinations CDash

  13. Future work (cont.) 3. IPython for interactive distributed computing • Python chosen as a favored scripting language for Slicer • VTK and Qt are well supported by python • ITK v4 will have python as a target language • Considered perl (biologists), tcl (comp sci), BatchMake, JavaScript, ... • IPython = extensions to python for interactive distributed computing • Threaded, grid, and distributed computing • Reduced setup and learning curve • Broad support

  14. Software process Challenges: • Provide effective resources for developers…and users • Uphold community standards (quality, style, doc.) • Minimize burden on developers…and users