View source for Documentation/SlicerRT/UsersGuide

= Frequently asked questions =
== Matlab users ==
* Direct data exchange between Slicer and Matlab can be achieved by using the [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Extensions/MatlabBridge MatlabBridge extension]
* Volumetric images saved by 3D Slicer can be loaded into Matlab using [http://www.mathworks.com/matlabcentral/fileexchange/29344 these scripts]

== Running SlicerRT functions from command-line ==
An example for completing a complete RT workflow using Slicer GUI: [http://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/Testing/Python/IGRTWorkflow_SelfTest.py IGRTWorkflow_SelfTest.py]
<!-- Original link: https://subversion.assembla.com/svn/slicerrt/trunk/SlicerRt/src/Testing/Python/NAMIC_Tutorial_2013June_SelfTest.py -->
Options to start a Ptyhon script:
* Open the Python console in Slicer (CTRL+3) and import scripts and/or enter commands
* Run script commands from command-line:<br><code>Slicer.exe --python-code "slicer.util.loadScene('c:/Slicer_Scenes/20130225_PatientHierarchyTree/2013-02-25-Scene.mrml');<br>slicer.util.selectModule('SubjectHierarchy')"</code>
Start a script from command-line: Slicer.exe --python-scipt "myscript.py"
If you don't want the Slicer window to appear while the scripts are running add these switches to the command-line: --no-splash --no-main-window
See related pages about [http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Python_scripting python scripting]

== Creating segmentations from labelmaps/models ==
TODO

= Troubleshooting =
* ''Problem'':<br>On OpenSuse linux: Some SlicerRT modules are not loaded, logged error is "''cannot open shared object file: No such file or directory''"<br>''Solution'':<br>Start Slicer with command: ''LD_LIBRARY_PATH=/home/karl/.config/NA-MIC/Extensions-22288/SlicerRT/lib/Slicer-4.2/qt-loadable-modules ./Slicer''

= Known limitations =
== DICOM-RT import ==
* RTIMAGE import: Datasets exported by the Corvus treatment planning system cannot be loaded properly (geometry cannot be computed for the RT image), because apparently ReferencedSOPInstanceUID points to the SeriesInstanceUID of the plan, which is not standard.
== DVH plotting ==
* Cannot move the legend on DVH plots ([http://www.donotlink.com/bEt #68])
<!-- Original link: https://www.assembla.com/spaces/slicerrt/tickets/68 -->
* The V metrics volume is computed from the DVH value corresponding to the closest dose to the one below and above the requested dose using linear interpolation ([http://www.donotlink.com/bEu #74])
<!-- Original link: https://www.assembla.com/spaces/slicerrt/tickets/74 -->