Slicer 4.1x incompatibility with SlicerJupyter

Hi all,

I have been using successfully using SlicerJupyter to process imaging data for the last year. Recently, my hard drive was wiped, and I have been unable to replicate my workflow. I have a couple of questions/issues:

  1. I believe that my working version of Slicer was 4.13. However, I am unable to find it in the previous releases page. The SlicerJupyter Github readme still references 4.13. Does anyone know where I can find a download to this?
  2. To stay consistent with my previous work, I want to continue using Slicer 4.1x instead of Slicer 5.x. Therefore, I tried to use Slicer 4.11 (I tried both the 2020 and 2021 version). I tried to use the Extension Manager to install SlicerJupyter (and that seemed to work initially). However, after trying to start the JupyterServer, I got an error while the package pywinpty was installing (see below). I did not have this issue previously. Following this thread I tried installing the extension from the package specific to my slicer version, but I ran into the same issue with needing Rust. Interestingly, this was not an issue for slicer 5+.
 Cargo, the Rust package manager, is not installed or is not on PATH.
    This package requires Rust and Cargo to compile extensions. Install it through
    the system's package manager or via
  1. I have tested this on two separate machines (both Windows 10), and I have the same issue. Both machines are connected to a hospital network.

Thanks for the help,

The easiest is to go back in time by specifying a date in the download page url. For example:

See more information here.

It is very hard to reproduce a computing environment from several years ago. For example, it would be impossible for you to get Windows7 or an old version of Windows10 now,… Python removed all binary releases older than 3.7 and you would need to rebuild from source if you need it, etc. You cannot get any support for software versions that were replaced several years ago (unless you pay the high price of private support).

If you haven’t saved your computing environment into a docker container or virtual machine image then it is probably better investment of your time if you update your environment to use current software versions. Then, if you want to ensure that this environment remains available for you for several years then you can save this environment in a container or virtual machine image.

About the specific issues you are encountering: Unfortunately, we cannot help you investigating this, because spending time with investigating Slicer 4.x problems (that would maybe help 10 people) would directly take time away from supporting/developing Slicer-5.2 (that would help about 5000-10000 people). If you upgrade to current Slicer version and you encounter problems then we can help with that.

Hi Andras,

I appreciate the quick response. Lesson learned about keeping a backup of my environment. I will try using the date in the link as you say, and if it doesn’t work I will update my functions for Slicer 5.