SlicerRadiomics extension not available for Slicer 4.11.0 on Mac OS about slicerradiomics HOT 9 CLOSED

from slicerradiomics.

@fedorov Thanks. I have now created an account for the Slicer forum. I've read my fair share of threads, it's about time I join, anyway.

I am not opposed to using Slicer 4.10. Up until today I was still using 4.8.1; I figured it was time to upgrade so I went right to the nightly build version. In hindsight, perhaps it was a bad idea to skip over the stable release. But I think it would be perfectly reasonable to use 4.10.

from slicerradiomics.

@warkentinmatt Yes, it will be incorporated in the next nightly build (so tomorrow it should be available I think). I'm not entirely sure, but I think this also means you'll have to get the new nightly build of Slicer.

from slicerradiomics.

Slicer is transitioning to python 3, and I am not sure all issues have been sorted out.

The actual build error is here: http://slicer.cdash.org/viewBuildError.php?buildid=1591412

cc: @jcfr

from slicerradiomics.

@fedorov Thanks for the reply. What sort of timeline might one expect for this to be resolved? Days? Weeks? Months?

I have noticed several other extensions are no longer available in Slicer 4.11.0 (e.g. SlicerCIP). Do extensions ever get archived or are they likely be suffering the same fate (i.e. python build errors)?

I've only done some cursory looking into this, but is there an easy way to tell which Slicer build versions are still Python 2.7? I guess I should downgrade my Slicer to the most recent Python 2.7 based Slicer to ensure these extensions will be available.

from slicerradiomics.

@warkentinmatt I do not have the answers to your questions, although all of them are very reasonable. Your best bet is to find the latest version of Slicer 4.11 and extensions before they were broken by python 3, but I do not know how to do that efficiently. I recommend you post your questions and concerns to the Slicer forum: https://discourse.slicer.org/latest.

I am assuming 4.10 is not an option for you, right?

from slicerradiomics.

Hi all,

I ran into issues like this before. The current one is located in the PyRadiomics setup.py script, where it is reading the README.md file as the long_description (used for PyPi distribution).

However, the reading just uses default encoding and in some cases this is apparently ascii, which fails on a special hyphen located in the readme file. I've updated PyRadiomics to explicitly decode using utf-8, which can handle the special hyphen.

I've decided not to update the hyphen, as these slip in sometimes anyway and I thought it better to use a build system that can cope with this.

from slicerradiomics.

This commit contains the fix: AIM-Harvard/pyradiomics@fab347b

from slicerradiomics.

@JoostJM Thanks for the update. I assume it will still take some time before this change leads to the SlicerRadiomics extension becoming available again?

from slicerradiomics.