faustomilletari / tomaat-slicer Goto Github PK

Hi,

is this project abandoned, or am I missing something?
when clicking on 'discover service' on 3D Slicer, the error in the title appears

thanks -- and thanks anyway for the module

When mutiple studies are loaded and segmentation happens, the results displayed are not shown together with the valume they refer to.

I receive the following error after installing the TOMAAT extension.

Could not install packages due to an EnvironmentError: [Error 5] Access is denied: 'C:\\Program Files\\Slicer 4.11.0-2019-02-19\\lib\\Python\\Lib\\site-packages\\requests_toolbelt'
Consider using the `--user` option or check the permissions.

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:/Users/arankin/AppData/Roaming/NA-MIC/Extensions-27968/TOMAAT/lib/Slicer-4.11/qt-scripted-modules/TOMAAT.py", line 1, in <module>
    import utils.dependencies
  File "C:\Users\arankin\AppData\Roaming\NA-MIC\Extensions-27968\TOMAAT\lib\Slicer-4.11\qt-scripted-modules\utils\dependencies.py", line 20, in <module>
    from requests_toolbelt import MultipartEncoder, MultipartEncoderMonitor
ImportError: No module named requests_toolbelt
SystemError: D:\D\P\Slicer-0-build\Python-2.7.13\Objects\classobject.c:521: bad argument to internal function

Can the missing dependency be packaged with the extension?

I'm looking for the best way to allow remote prediction endpoints (servers) to send over to the clients the blueprints to build a GUI that is specific to each service.

for example: I have a segmentation algorithm that accepts more than one channel of data, or accepts a number of different parameters. I want to tell slicer "hey, look that this server wants to have in the GUI additional fields which should be (for example) [a volume selection drop down menu named 'T1', a volume selection drop down menu named 'T2', 'a slider with max value 1 and min value 0 called 'threshold', 'a checkbox button called 'checkbox'] and then present all of these elements to the user. The values of these elements are then sent via request to the server.

In this way we can extend flexibility, but what is the best way to do this? XML? JSON?

@jcfr

Thinking more about this extension, and after trying it out, I think it would be appropriate (if not mandatory) to have a very prominent warning for the user that the data to be segmented is going to leave the computer.

The approach taken in this extension is highly unconventional to Slicer development model, which usually is to do all analysis locally. Considering the sensitive nature of the image data and regulations, I recommend that for every click of "Segment" button you pop up a message telling user what is going to happen, and what data is going to leave the client. Otherwise, I am afraid, it is only a matter of time before someone can get in trouble...

Only now I realized the importance of the detailed disclaimers you put in the code and documentation, but I don't think those disclaimers will be read by the end users. I think the reality is most users don't read documentation.

cc: @pieper @lassoan @jcfr