Slicer: Difference between revisions

From Alliance Doc
Jump to navigation Jump to search
(Page creation)
 
(remove Draft tag)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<languages/>
<languages/>
[[Category:Software]]
[[Category:Software]]
{{Draft}}
 
<translate>
<translate>


<!--T:1-->
<!--T:1-->
[https://www.slicer.org/ 3D Slicer] 3D Slicer is an open source software platform for medical image informatics, image processing, and three-dimensional visualization. Built over two decades through support from the National Institutes of Health and a worldwide developer community, Slicer brings free, powerful cross-platform processing tools to physicians, researchers, and the general public.
[https://www.slicer.org/ 3D Slicer] is an open source software platform for medical image informatics, image processing, and three-dimensional visualization. Built over two decades through support from the National Institutes of Health and a worldwide developer community, Slicer brings free, powerful cross-platform processing tools to physicians, researchers, and the general public.
 
<!--T:2-->
IMPORTANT


<!--T:3-->
<!--T:3-->
Never make intense use of Slicer on the login nodes! Submit jobs using the command line whenever possible and if you must visualize your data using the GUI, please do so on an interactive node. Using parallel rendering on the shared login nodes will result in the termination of your session.
'''IMPORTANT''': Never make intense use of Slicer on the login nodes! Submit jobs using the command line whenever possible and if you must visualize your data using the GUI, please do so on an interactive node. Using parallel rendering on the shared login nodes will result in the termination of your session.
 
== Loading Slicer == <!--T:4-->
 
{{Command
|module load slicer/4.10.1
}}


== Using the GUI == <!--T:19-->
== Using the GUI == <!--T:19-->
Line 23: Line 14:


<!--T:21-->
<!--T:21-->
You can find information on how to connect with MobaXTerm and use X11 fowarding on the [[Connecting_with_MobaXTerm]] page.
You can find information on how to connect with MobaXTerm and use X11 fowarding at [[Connecting_with_MobaXTerm|Connecting with MobaXTerm]].


==== extension "MIT-SHM" missing ====<!--T:22-->
==== Use an interactive node ==== <!--T:23-->
Xlib:  extension "MIT-SHM" missing on display "localhost:86.0".


==== Use an interactive node ====<!--T:23-->
<!--T:30-->
Runtime is limited on the login nodes, so you will need to request a testing job to have more time for exploring and visualizing your data. Additionally, by doing so, you will have access to the 40 cores of each of the nodes requested.
Runtime is limited on the login nodes, so you should request an [[Running_jobs#Interactive_jobs|interactive job]] to have more time for exploring and visualizing your data. Additionally, by doing so, you will be able to use more cores for faster processing.


<!--T:24-->
<!--T:24-->
request an interactive job, ie.
Request an interactive job, ie.
   [name@login ~]$ salloc --time=1:0:0 --ntasks=2 --x11 --account=def-someuser
   [name@server ~]$ salloc --time=1:0:0 --ntasks=2 --x11 --account=def-someuser


this will connect you to a node. Note the --x11 argument, which will enable X11 forwarding on the interactive node.  
<!--T:29-->
This will connect you to a compute node. Note the --x11 argument.  


<!--T:25-->
<!--T:25-->
Line 43: Line 34:


<!--T:27-->
<!--T:27-->
Once you are done and have closed Slicer, you can terminate the allocation
Once you are done and have closed Slicer, don't forget to terminate the interactive job:
{{Command|exit}}
{{Command|exit}}
== Using the command line == <!--T:31-->
<!--T:32-->
If you have to perform the same task on a large number of images,
or if you don't need to see the processed images as they are created,
you should use the command line interface and batch processing.
For examples see
* https://discourse.slicer.org/t/rtstruct-to-label-map/2437
* https://discourse.slicer.org/t/slicer-batch-processing-question-no-main-window-python-script/1863


</translate>
</translate>

Latest revision as of 20:47, 5 March 2019

Other languages:


3D Slicer is an open source software platform for medical image informatics, image processing, and three-dimensional visualization. Built over two decades through support from the National Institutes of Health and a worldwide developer community, Slicer brings free, powerful cross-platform processing tools to physicians, researchers, and the general public.

IMPORTANT: Never make intense use of Slicer on the login nodes! Submit jobs using the command line whenever possible and if you must visualize your data using the GUI, please do so on an interactive node. Using parallel rendering on the shared login nodes will result in the termination of your session.

Using the GUI

Using the Slicer GUI requires X11 forwarding, which you should make sure is enabled.

You can find information on how to connect with MobaXTerm and use X11 fowarding at Connecting with MobaXTerm.

Use an interactive node

Runtime is limited on the login nodes, so you should request an interactive job to have more time for exploring and visualizing your data. Additionally, by doing so, you will be able to use more cores for faster processing.

Request an interactive job, ie.

 [name@server ~]$ salloc --time=1:0:0 --ntasks=2 --x11 --account=def-someuser

This will connect you to a compute node. Note the --x11 argument.

You can then load Slicer and run it on the interactive node.

Question.png
[name@server ~]$ module load slicer
Question.png
[name@server ~]$ Slicer

Once you are done and have closed Slicer, don't forget to terminate the interactive job:

Question.png
[name@server ~]$ exit

Using the command line

If you have to perform the same task on a large number of images, or if you don't need to see the processed images as they are created, you should use the command line interface and batch processing. For examples see