Difference between revisions of "2017 Winter Project Week/PyRadiomics"

From NAMIC Wiki
Jump to: navigation, search
 
(4 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
Image:RadiomicsWorkflow.jpg
 
Image:RadiomicsWorkflow.jpg
 
Image:PyRadiomics_structure.jpg
 
Image:PyRadiomics_structure.jpg
 +
Image:SlicerRadiomics.jpg
 
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
 
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
  
Line 33: Line 34:
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week -->
 
* Introduced PyRadiomics to the community
 
* Introduced PyRadiomics to the community
* There are still some issues with the packaging of the extension, SlicerRadiomics. Numpy issue is resolved, PyRadiomics works with numpy 1.9.2, adjusted minimum requirements
+
* There are still some issues with the packaging of the extension, SlicerRadiomics. Numpy issue is resolved, PyRadiomics works with numpy 1.9.2, adjusted minimum requirements. Once these issues are resolved, it will be made publicly available in the [http://github.com/Radiomics Github Radiomics Organisation].
 
* C code performance enhancement is written, but is still causing some issues during compilation. Switch setup to use skbuild and cmake. Latest (offline) tests work with setup.py develop and setup.py test.
 
* C code performance enhancement is written, but is still causing some issues during compilation. Switch setup to use skbuild and cmake. Latest (offline) tests work with setup.py develop and setup.py test.
 +
* Issues related to building SlicerRadiomics have been fixed, extension can now be built and used in the built version in the basic form
 +
* Issues related to packaging SlicerRadiomics have been identified (limitations of Slicer infrastructure packaging external python packages); JC identified the solution approach, and the issue will be resolved soon, we expect the extension to be available publicly within a month
 
|}
 
|}
  
Line 40: Line 43:
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
* [https://Github.com/Radiomics/pyradiomics GitHub Repository]
 
* [https://Github.com/Radiomics/pyradiomics GitHub Repository]
* [pyradiomics.readthedocs.io Documentation]
+
* [http://pyradiomics.readthedocs.io Documentation]
 +
* https://Github.com/Radiomics/SlicerRadiomics

Latest revision as of 16:30, 13 January 2017

Home < 2017 Winter Project Week < PyRadiomics

Key Investigators

  • Joost van Griethuysen
  • Hugo Aerts
  • Steve Pieper
  • Jean-Christophe Fillion-Robin
  • Andrey Fedorov

Project Description

Objective Approach and Plan Progress and Next Steps
  • Introduce PyRadiomics to the community
  • Present, meet collaborators...
  • Discuss issues related to integration with Slicer: external packages, numpy version, Slicer module UI
  • Discuss issues related to enhancing performance using C code
  • Introduced PyRadiomics to the community
  • There are still some issues with the packaging of the extension, SlicerRadiomics. Numpy issue is resolved, PyRadiomics works with numpy 1.9.2, adjusted minimum requirements. Once these issues are resolved, it will be made publicly available in the Github Radiomics Organisation.
  • C code performance enhancement is written, but is still causing some issues during compilation. Switch setup to use skbuild and cmake. Latest (offline) tests work with setup.py develop and setup.py test.
  • Issues related to building SlicerRadiomics have been fixed, extension can now be built and used in the built version in the basic form
  • Issues related to packaging SlicerRadiomics have been identified (limitations of Slicer infrastructure packaging external python packages); JC identified the solution approach, and the issue will be resolved soon, we expect the extension to be available publicly within a month

Background and References