diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/Manual.dox index 9e454d636b..450c282732 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/Manual.dox @@ -1,21 +1,14 @@ /** -\page org_mitk_gui_qt_matchpoint_algorithm_batch The MatchPoint Registration Batch Processor Plugin +\page org_mitk_gui_qt_matchpoint_algorithm_batch The MatchPoint Registration Batch Processor View -\imageMacro{map-icon-batch.svg, "Icon of the MatchPoint Algorithm Batch Processor",3} +\imageMacro{map_icon_batch_doc.svg,"Icon of the Segmentation Utilities View",2.00} -\li \ref MAP_BATCH_Introduction -\li \ref MAP_BATCH_Contact -\li \ref MAP_BATCH_Usage +\tableofcontents \section MAP_BATCH_Introduction Introduction -This plugin is very similar to the MatchPoint algorithm controller plugin, but allows to register a set of selected input images in one batch run onto one selected target image. - -\section MAP_BATCH_Contact Contact information -This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics -and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, -find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. +This plugin is very similar to the MatchPoint algorithm controller view, but allows to register a set of selected input images in one batch run onto one selected target image. \section MAP_BATCH_Usage Usage Oops. Documentation is missing and to be done. */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map-icon-batch.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map-icon-batch.svg deleted file mode 100644 index 7280678b79..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map-icon-batch.svg +++ /dev/null @@ -1,129 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map_icon_batch_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map_icon_batch_doc.svg new file mode 100644 index 0000000000..da4687ac7f --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.batch/documentation/UserManual/map_icon_batch_doc.svg @@ -0,0 +1,214 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/Manual.dox index d75c0e48be..3d911805f2 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/Manual.dox @@ -1,58 +1,46 @@ /** \page org_mitk_gui_qt_matchpoint_algorithm_browser The MatchPoint Algorithm Browser View -\imageMacro{map-icon-browser.svg, "Icon of the MatchPoint Algorithm Browser", 3} +\imageMacro{map_icon_browser_doc.svg, "Icon of the MatchPoint Algorithm Browser", 3} -\li \ref MAP_BROWSER_Introduction -\li \ref MAP_BROWSER_Contact -\li \ref MAP_BROWSER_Usage -\li \ref MAP_BROWSER_Profile +\tableofcontents \section MAP_BROWSER_Introduction Introduction This view offers the user a way to search for available registration algorithms and select them for further usage by other views (e.g. MatchPoint Algorithm Control \ref org_mitk_gui_qt_algorithm_control). -\section MAP_BROWSER_Contact Contact information -This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics -and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, -find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. - \section MAP_BROWSER_Usage Usage \remark If you see no algorithms available by the browser, please check the search paths which can be configured at the MatchPoint preference page (Ctrl+P). -DIPP-User: You should activate at least "scan installation directory" to see the algorithms delivered with the DIPP installer. The basic idea of the browser is that you can use this view as central place to search for suitable algorithms. If you select an algorithm you can see its profile in the lower part of the view. -If a algorithm is selected all other views (e.g. \ref org_mitk_gui_qt_algorithm_control or \ref de_dkfz_dwi_gui_qt_crex) which use registration algorithms will be notified and allow to choose the selected algorithm for usage. -\imageMacro{browser.png, "View of the browser with the list of available algorithm and the profile area",14} - -\remark You haven't found a fitting registration algorithm? Please have a look at the registration repository at our SBR share point (http://intracoop/sites/sbr/Lists/RegRepository/default.aspx) -or contact us (dipp@dkfz.de). +If a algorithm is selected all other views (e.g. \ref org_mitk_gui_qt_algorithm_control) which use registration algorithms will be notified and allow to choose the selected algorithm for usage. +\imageMacro{map_browser.png, "View of the browser with the list of available algorithm and the profile area",14} \section MAP_BROWSER_Profile Profile info In the following a short information about the different properties classified in the profile.\n */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map-icon-browser.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map-icon-browser.svg deleted file mode 100644 index 25aaffc180..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map-icon-browser.svg +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/browser.png b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map_browser.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/browser.png rename to Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map_browser.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map_icon_browser_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map_icon_browser_doc.svg new file mode 100644 index 0000000000..8733af7d77 --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.browser/documentation/UserManual/map_icon_browser_doc.svg @@ -0,0 +1,183 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/Manual.dox index e1e7cdcc4e..162da76ff6 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/Manual.dox @@ -1,37 +1,39 @@ /** -\page org_mitk_gui_qt_matchpoint_algorithm_control The MatchPoint Algorithm Control Plugin +\page org_mitk_gui_qt_matchpoint_algorithm_control The MatchPoint Algorithm Control View -\imageMacro{map-icon-run.svg, "Icon of the MatchPoint Algorithm Control", 3} +\imageMacro{map_icon_run_doc.svg,"Icon of the MatchPoint Algorithm Control",3.0} \tableofcontents \section MAP_RUN_Introduction Introduction -This plugin offers the user a way to use a selected registration algorithm in order to determine a registration for two selected images. For the selection of an algorithm please see MatchPoint Algorithm Browser (\ref org_mitk_gui_qt_algorithm_browser). +This plugin offers the user a way to use a selected registration algorithm in order to determine a registration for two selected images. For the selection of an algorithm please see MatchPoint Algorithm Browser (\ref org_mitk_gui_qt_matchpoint_algorithm_browser). \section MAP_RUN_Contact Contact information -This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. +This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics +and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, +find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_RUN_Usage Usage -\imageMacro{control_example.png, "Example screenshot showing the control plugin in use.", 14} +\imageMacro{map_control_example.png, "Example screenshot showing the control plugin in use.", 10} To use the plugin a registration algorithm must be loaded and a moving as well as a target image must be selected.\n The moving image is registered onto the target image. Thus the result is a mapped input image in the geometry (field of view, orientation, spacing) defined by the target image.\n All images are selected in the data manager using multi select (press the CTRL-key while selecting the nodes in the data manager). The first selection is the moving image, the second is the target image.\n If an algorithm is loaded and input images are selected, the plugin will automatically switch to the "Execution" tab. \subsection MAP_RUN_Usage_selection Selection tab -\imageMacro{step1_selection.png, "Details of the selection tab.", 8} +\imageMacro{map_control_step1_selection.png, "Details of the selection tab.", 5} In this tab registration algorithms that are selected in the MatchPoint Algorithm Browser can be chosen. In the tab you see the ID of the algorithm selected by the browser and its profile information.\n If you press "Load selected algorithm", the algorithm will be used by the control plugin. The name of the algorithm occurs in the text field "Loaded algorithm" (at the top of the plugin view).\n At this point, it has no effect if you change the selection in the browser. The control plugin will keep the loaded algorithm until you choose to load another one. \subsection MAP_RUN_Usage_exec Execution tab -\imageMacro{step2_execution.png, "Details of the execution tab.", 8} +\imageMacro{map_control_step2_execution.png, "Details of the execution tab.", 5} In this tab you can specify a name for the registration job (this will determine the names of the result nodes in the data manager).\n You can also choose to "store registration" (which is normally the goal of the whole process, because this is the very result of the algorithm ;).\n Additionally you can choose "Generate + store mapped result". This is a convenience feature which often saves you the time to use the mapper plugin afterwards. It will do the same like using the mapper plugin with the moving and target image, setting padding value "0" and using "linear interpolation". If you need other settings, skip the convenience generation and use the MatchPoint mapper plugin directly.\n "Start" will trigger the registration process. Some algorithms can be stopped while processing takes place. In those cases, there is a "Stop" button enabled, as soon as the registration process starts. \subsection MAP_RUN_Usage_settings Settings tab -\imageMacro{step3_settings.png, "Details of the settings tab.", 8} +\imageMacro{map_control_step3_settings.png, "Details of the settings tab.", 5} In this tab, you can change the parametrization of the loaded algorithm (before it starts), if it offers any possibility to do so. */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map-icon-run.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map-icon-run.svg deleted file mode 100644 index 5395b6f814..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map-icon-run.svg +++ /dev/null @@ -1,133 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/control_example.png b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_example.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/control_example.png rename to Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_example.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step1_selection.png b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step1_selection.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step1_selection.png rename to Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step1_selection.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step2_execution.png b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step2_execution.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step2_execution.png rename to Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step2_execution.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step3_settings.PNG b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step3_settings.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/step3_settings.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_control_step3_settings.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_icon_run_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_icon_run_doc.svg new file mode 100644 index 0000000000..4078f622fc --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.algorithm.control/documentation/UserManual/map_icon_run_doc.svg @@ -0,0 +1,205 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/Manual.dox index 5c967973c7..1a7ecf6d90 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/Manual.dox @@ -1,52 +1,50 @@ /** \page org_mitk_gui_qt_matchpoint_evaluator The MatchPoint Registration Evaluation View -\imageMacro{evaluator.svg, "Icon of the MatchPoint Registration Evaluator", 3} +\imageMacro{map_evaluator_doc.svg, "Icon of the MatchPoint Registration Evaluator", 3} -\li \ref MAP_REGEVAL_Introduction -\li \ref MAP_REGEVAL_Contact -\li \ref MAP_REGEVAL_Usage +\tableofcontents \section MAP_REGEVAL_Introduction Introduction This view offers the possibility to evaluate the quality of the registration/mapping of two given images by visual inspection. One may select no registration. Then the images will be displayed in evaluation mode assuming an identity transform (so no mapping). It is one of several MatchPoint registration plug-ins.\n \section MAP_REGEVAL_Contact Contact information This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_REGEVAL_Usage Usage -\imageMacro{view_example.png, "Example screenshot showing the plug-in in use.", 14} +\imageMacro{map_view_example.png, "Example screenshot showing the plug-in in use.", 14} To use the evaluation view you must have selected at least the moving and the target image you want to use to evaluate. -If you select a registration with referenced target and moving image (the normal state if you generate registrations with the matchpoint plugins) +If you select a registration with referenced target and moving image (the normal state if you generate registrations with the MatchPoint plugins) these images will be auto selected by just clicking on the registration. If you select no registration the view will assume that an identity transform should be used.\n As long as no valid set of data is selected the "Start evaluation" button will be disabled. If its enabled you may start the evaluation mode with it. -\imageMacro{no_data_selected.png, "Example screenshot showing the state if no data is selected", 5} +\imageMacro{map_no_data_selected.png, "Example screenshot showing the state if no data is selected", 5} -If the evaluation view is active you can choose between differnt modes of visualization. For more details see \ref MAP_REGEVAL_Styles.\n +If the evaluation view is active you can choose between different modes of visualization. For more details see \ref MAP_REGEVAL_Styles.\n To stop the evaluation mode, you may use the "Stop evaluation" button or just close the evaluation view. \remark The evaluation view will use the level window settings of the used images. So to changes the level windowing of the evaluation view, you must change the level windowing of the respective images. \section MAP_REGEVAL_Styles Visualization styles You can choose from the following visualization styles to evaluate the registration/mapping quality:\n \li "Blend": Blends the images with a user defined weight. Default is 50:50. -\imageMacro{style_blend.png, "Example for mode: Blend", 5} +\imageMacro{map_style_blend.png, "Example for mode: Blend", 5} \li "Checkerboard": Checkerboard style that composes both images. You may define the resolution of the checkerboard. -\imageMacro{style_checkerboard.png, "Example for mode: Checkerboard", 5} +\imageMacro{map_style_checkerboard.png, "Example for mode: Checkerboard", 5} \li "Color blend": Color blend of the images (blue: target image; yellow: moving). Areas where you see no color implies good intensity matchings. -\imageMacro{style_color_blend.png, "Example for mode: Color blend", 5} +\imageMacro{map_style_color_blend.png, "Example for mode: Color blend", 5} \li "Contour": Blend mode that display one image as blue "background" and the other image in yellow contours. You may choose the role of the images. -\imageMacro{style_contour.png, "Example for mode: Contour", 5} +\imageMacro{map_style_contour.png, "Example for mode: Contour", 5} \li "Difference": Displays the absolute difference of both images. \li "Wipe": Blend mode that makes a rectilinear combination of the images. You can choose the mode how the images are splitted. The split is synchronized with the current selection. So you may interact with the split border to position it on interesting areas. -\imageMacro{style_wipe_cross.png, "Example for mode: Wipe cross", 5} -\imageMacro{style_wipe_horizontal.png, "Example for mode: Wipe horizontal", 5} +\imageMacro{map_style_wipe_cross.png, "Example for mode: Wipe cross", 5} +\imageMacro{map_style_wipe_horizontal.png, "Example for mode: Wipe horizontal", 5} */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/evaluator.svg b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/evaluator.svg deleted file mode 100644 index f04b510934..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/evaluator.svg +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_evaluator_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_evaluator_doc.svg new file mode 100644 index 0000000000..bfa6c7ad7c --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_evaluator_doc.svg @@ -0,0 +1,204 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/no_data_selected.PNG b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_no_data_selected.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/no_data_selected.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_no_data_selected.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_blend.PNG b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_blend.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_blend.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_blend.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_checkerboard.png b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_checkerboard.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_checkerboard.png rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_checkerboard.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_color_blend.png b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_color_blend.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_color_blend.png rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_color_blend.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_contour.png b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_contour.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_contour.png rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_contour.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_wipe_cross.PNG b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_wipe_cross.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_wipe_cross.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_wipe_cross.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_wipe_horizontal.PNG b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_wipe_horizontal.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/style_wipe_horizontal.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_style_wipe_horizontal.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/view_example.PNG b/Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_view_example.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/view_example.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.evaluator/documentation/UserManual/map_view_example.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/Manual.dox index 5f545f2e62..5b5a1cb796 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/Manual.dox @@ -1,64 +1,64 @@ /** -\page org_mitk_gui_qt_matchpoint_framereg The MatchPoint Motion/Frame Correction Plugin +\page org_mitk_gui_qt_matchpoint_framereg The MatchPoint Motion/Frame Correction View -\imageMacro{"icon.svg", "Icon of the MatchPoint Algorithm Control", 3} +\imageMacro{"map_framereg_icon_doc.svg", "Icon of the MatchPoint Algorithm Control", 3} -\li \ref MAP_FRAME_Introduction -\li \ref MAP_FRAME_Contact -\li \ref MAP_FRAME_Usage +\tableofcontents \section MAP_FRAME_Introduction Introduction This plugin offers the user a way to use a selected registration algorithm in order to make a frame/motion correction for a selected 3D+t images. The plugin is for example helpfull if you have a dynamic image with motion artifacts in same time points and you want to reduce/remove this motion artifacts. For the selection of an algorithm please see MatchPoint Algorithm Browser (\ref de_dkfz_matchpoint_mitk_gui_qt_algorithm_browser). \section MAP_FRAME_Contact Contact information This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, -find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. +find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_FRAME_Usage Usage -\imageMacro{"control_example.png" , "Example screenshot showing the plugin in use.", 15} +\imageMacro{"map_framereg_example.png" , "Example screenshot showing the plugin in use.", 15} To use the plugin a registration algorithm must be loaded and the image must be selected, that should be corrected.\n The correction is performed that every frame/timpoint of the image is registered to the first frame. And the corrected frames is mapped in the same geometry then the first frame.\n If an algorithm is loaded and input images are selected, the plugin will automatically switch to the "Execution" tab. \subsection MAP_FRAME_Usage_selection Algorithm selection tab -\imageMacro{step1_selection.png, "Details of the algorithm selection tab.", 6} +\imageMacro{map_step1_selection.png, "Details of the algorithm selection tab.", 6} In this tab you can load/"book" the algorithm selected in the MatchPoint Algorithm Browser. In the tab you see the ID of the algorithm selected by the browser and its profile information.\n If you press "Load selected algorithm", the algorithm will be used by the plugin for the frame correction and the name of the algorithm occurs in the text field "Loaded algorithm" (at the top of the plugin view).\n At this point, it has no effect if you change the the selection in the browser. The plugin will keep the loaded algorithm until you choose to load another one. \subsection MAP_FRAME_Usage_exec Execution tab -\imageMacro{step2_execution.png, "Details of the execution tab.", 8} +\imageMacro{map_step2_execution.png, "Details of the execution tab.", 6} In this tab you can specify a name for the correction job (this will determine the names of the result nodes in the data manager).\n "Start" will trigger the correction process. \subsection MAP_FRAME_Usage_settings Settings tab -\imageMacro{step3_settings.png, "Details of the settings tab.", 8} +\imageMacro{map_step3_settings.png, "Details of the settings tab.", 6} In this tab, you can (1) define the mapping settings \ref MAP_FRAME_Mapper_Settings "(See details)", used for the corrected frames, or (2) parametrize the loaded algorithm (before it starts), if it offers any possibility to do so. -*/ -\section MAP_FRAME_Mapper_Settings Mapper settings +\subsubsection MAP_FRAME_Mapper_Settings Mapper settings For the mapping of corrected images, you have several settings available:\n \li "Allow undefined pixels": Activate to handle pixels of the result image that are not in the field of view of the input image. This pixel will get the "padding value". \li "Allow error pixels": Activate to handle pixels of the result image that can not be mapped because the registration does not support this part of the output image. This pixel will get the "error value". \li "Interpolator": Set to choose the interpolation strategy that should be used for mapping. \ref MAP_FRAME_Interpolation "(see details)" -\section MAP_FRAME_Interpolation Interpolation +\subsubsection MAP_FRAME_Interpolation Interpolation You can choose from the following interpolation strategies:\n \li "nearest neighbour": Use the value of the nearest pixel. Fastest, but high interpolation errors for gray value images. Right choice for label images or masks. \li "Linear": Fast linear interpolation with often sufficient quality. Tends to blur edges. \li "BSpline (3rd order)": Good trade off between time and quality. \li "Windowed Sinc (Hamming)": Good interpolation quality but very time consuming. \li "Windowed Sinc (Welch)": Good interpolation quality but very time consuming. \subsection MAP_FRAME_Usage_frame_selection Frame selection tab -\imageMacro{step4_frameselection.png, "Details of the frame selection tab.", 6} +\imageMacro{map_step4_frameselection.png, "Details of the frame selection tab.", 6} In this tab you can specify the frames of the currently selected image that should be corrected. As default all frames of an image will be corrected. If you only select specific frames, these frames will be corrected all other frames will be just copied unchanged. + +*/ + diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/control_example.png b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/control_example.png deleted file mode 100644 index 424ae7a57e..0000000000 Binary files a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/control_example.png and /dev/null differ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/icon.svg b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/icon.svg deleted file mode 100644 index c75d640660..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/icon.svg +++ /dev/null @@ -1,125 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/framereg_example.png b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_framereg_example.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/framereg_example.png rename to Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_framereg_example.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_framereg_icon_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_framereg_icon_doc.svg new file mode 100644 index 0000000000..e25c2bfcf4 --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_framereg_icon_doc.svg @@ -0,0 +1,214 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step1_selection.png b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step1_selection.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step1_selection.png rename to Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step1_selection.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step2_execution.png b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step2_execution.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step2_execution.png rename to Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step2_execution.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step3_settings.PNG b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step3_settings.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step3_settings.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step3_settings.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step4_frameselection.PNG b/Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step4_frameselection.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/step4_frameselection.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.framereg/documentation/UserManual/map_step4_frameselection.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/Manual.dox index c40d45597c..d376891913 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/Manual.dox @@ -1,75 +1,69 @@ /** \page org_mitk_gui_qt_matchpoint_manipulator The MatchPoint Registration Manipulator View -\imageMacro{manipulator.svg, "Icon of the MatchPoint Registration Manipulator", 3} +\imageMacro{map_manipulator_icon_doc.svg, "Icon of the MatchPoint Registration Manipulator", 3} -\li \ref MAP_REGMANIP_Introduction -\li \ref MAP_REGMANIP_Contact -\li \ref MAP_REGMANIP_Usage -\li \ref MAP_REGMANIP_TransSettings -\li \ref MAP_REGMANIP_EvalSettings +\tableofcontents \section MAP_REGMANIP_Introduction Introduction This view offers the possibility to manually manipulate a registration to establish a good mapping between data. The effect of manipulation is visualized with to user defined images to allow visual inspection.\n It is one of several MatchPoint registration plug-ins.\n -\imageMacro{view_example.png, "Example screenshot showing the plug-in in use", 10} +\imageMacro{map_view_example.png, "Example screenshot showing the plug-in in use", 10} \section MAP_REGMANIP_Contact Contact information This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_REGMANIP_Usage Usage -\imageMacro{view_steps.png, "Illustration of the workflow steps.", 7} +\imageMacro{map_view_steps.png, "Illustration of the workflow steps.", 7} The typical workflow with the manipulator has following steps/sections: 1. Source selection: You can choose between starting a new registration and using a selected registration. For later option, the registration must be selected in the data manager. \remark If you choose a new registration, the manipulator will automatically pre initialize this new transform to align the centers of the used images and therefore starts with sensible settings. \remark If you choose an existing registration, the registration will *not* be altered. It serves as template/baseline for the manipulation, which will be "on top" of the existing registration. 2. Image selection: To allow visual inspection of the manipulation to images are needed. If you have selected a registration (independent from the source selection mode) the manipulator will use the moving and target images used to determine the selected registration as images for the manipulation. You can also explicitly select images in the data manager (press shift while selecting for multi select). 3. Start manual registration: If all settings are valid, you can start the manipulation. The render windows will automatically switch to the visual inspection mode. The views will be reinitialized to the field of view of the target image. 4. Generation settings: You may choose to give the resulting registration a special name. Additionally you can choose the convenience option to map the moving image with the confirmed registration automatically. -\remark For more advanced mapping options please see the MatchPoint Mapper (\ref org_mitk_gui_qt_matchpoint_mapper). 5. Settings: You can alter the settings of the transform (\ref MAP_REGMANIP_TransSettings) and the rendering settings (\ref MAP_REGMANIP_EvalSettings) for the visual inspection. 6. Cancel or confirmation: You may cancel the manipulation process (Closing the view equals cancelation) or confirm the determined registration and store it in the data storage with the given name.\n \section MAP_REGMANIP_TransSettings Transformation settings You can alter the translation and the rotation of the transform. In addition you may choose the center of rotation type. You have the following options:\n - Moving image center: Rotate around the center of the moving image. - World origin: Rotate around (0.0,0.0,0.0), the world origin. - Current navigator position: Rotate around the current navigator position in the render views. \remark FAQ: Why are the translation values "jumping" when I change the center mode or when I am rotating?\n The reason is the relation between center, rotation, and translation.\n A transformation is defined as x' = R (x - C) + C + T\n where x': transformed point; x: point to transform; R: rotation matrix; C: center point; T: translation vector.\n The offset of a transform is defined as O = -RC + C + T\n -The offset as well as the rotation matrix stay constant if the center point changes, those the translation has to be altered. +The offset as well as the rotation matrix stay constant if the center point changes, therefore the translation has to be altered. \note To ease the orientation, the edit fields have background colours which resemble the colours of the plane the changes will "happen".\n For translation, the translation vector will be perpendicular to the indicated plane (The image moves "through" the plane). For rotation, the rotation axis will be perpendicular to the indicated plane. - \section MAP_REGMANIP_EvalSettings Evaluation settings The settings you can choose are equal to the settings of the evaluation view (\ref org_mitk_gui_qt_matchpoint_evaluator). -Please see the documentation of the evaluator for more details. +Please see the documentation of the MatchPoint Registration Evaluator view for more details. */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/manipulator.svg b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/manipulator.svg deleted file mode 100644 index 11f89f36bd..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/manipulator.svg +++ /dev/null @@ -1,123 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_manipulator_icon_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_manipulator_icon_doc.svg new file mode 100644 index 0000000000..0aa48da956 --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_manipulator_icon_doc.svg @@ -0,0 +1,187 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/view_example.PNG b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_view_example.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/view_example.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_view_example.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/view_steps.PNG b/Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_view_steps.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/view_steps.PNG rename to Plugins/org.mitk.gui.qt.matchpoint.manipulator/documentation/UserManual/map_view_steps.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/Manual.dox index 58371aca7a..f3c8878389 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/Manual.dox @@ -1,87 +1,85 @@ /** \page org_mitk_gui_qt_matchpoint_mapper The MatchPoint Image Mapper View -\imageMacro{icon.svg, "Icon of the MatchPoint Image Mapper",3} +\imageMacro{map_mapper_icon_doc.svg, "Icon of the MatchPoint Image Mapper",3} -\li \ref MAP_MAPPER_Introduction -\li \ref MAP_MAPPER_Contact -\li \ref MAP_MAPPER_Usage +\tableofcontents \section MAP_MAPPER_Introduction Introduction This view offers the possibility to map any image or point set in the data manager using a user selected registration object. Using the Mapper to map images the user can control the field of view (image geometry) the image should be mapped into, as well as interpolation strategy that should be used.\n It is one of several MatchPoint registration plugins.\n Typical usage scenarios\n \li You have registered image I1 onto image I2. Now you want to transfer the segmentation of I1 to I2 in order to evaluate I2 within this mapped segmentation using \ref org_mitk_views_imagestatistics . \li You have registered image I1 onto image I2. Now you want to map I3 (e.g. an other MRI sequence of the same session) also onto I2 with the same registration. \li You have registered image I1 onto image I2. Now you want to map a segmentation done on I1 also onto I2 with the same registration. \li You have registered image I1 onto image I2. Now you want to map a point set of image I1 also onto I2 with the same registration. \section MAP_MAPPER_Contact Contact information This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, -find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. +find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_MAPPER_Usage Usage -\imageMacro{mapper-examplescreen.png, "Example screenshot showing the Mapper plugin in use.", 14} +\imageMacro{map_mapper-examplescreen.png, "Example screenshot showing the Mapper plugin in use.", 14} To use the mapper at least an input data (image or point set) must be selected. Additionally you may select a registration object and a reference image. Registration objects are marked with a small blue icon (e.g. the data "Registration" in the data manager of the screen shot above). The Reference image defines the geometry (field of view, orientation, spacing) that should be used for the result image. By default the view will try to automatically determine the reference image (by default it is the target image of the selected registration). If auto selection cannot determine the reference it will choose the input image as reference. The reference image can be also defined by the user explicitly by activating manual selection.\n REMARK: If you map point sets you can ignore the reference image slot. It has no affect.\n -You can multiselect registration and data (press the CTRL-key while selecting the nodes in the data manager). +You can multi select registration and data (press the CTRL-key while selecting the nodes in the data manager). The Mapper will automatically sort the selections in the correct "slots" of the view.\n REMARK: The mapping results will be added as child nodes to the used input node.\n -REMARK: If you do not select an registration the view will assume that you make an identity transform. This is a convinient way if you +REMARK: If you do not select an registration the view will assume that you make an identity transform. This is a convenient way if you just want to resample an image into the geometry of an other image (when no registration is needed). Also in this use case you can take -adventage of the different interpolation and sub/super sampling strategies. +advantage of the different interpolation and sub/super sampling strategies. -\imageMacro{mapper.png, "Details of the mapper view.", 8} +\imageMacro{map_mapper.png, "Details of the mapper view.", 8} (1) The currently selected registration, that will be used for mapping.\n (2) The currently selected input data, that will be mapped.\n (3) The currently (automatically or by user) selected reference image, that defines the geometry of the result.\n (4) The name of the result data in the data manger.\n (5) The start button(s) to commence the mapping process. For details regarding the two options see \ref MAP_MAPPER_Refine.\n (6) Log windows with messages regarding the mapping process.\n\n Every "slot" has the ability to be locked. If locked the last selection will be kept, regardless the current selection in the data manager. You can use this for example to lock the registration, if you want to map multiple images. Doing so it is enough to just select the next image in the data manager. To lock a slot, click at the "lock" button at the right side (see example images below). -\imageMacro{node-unlocked.png, "Unlocked slot/node (default state). Changes with the selections in the data manager.",6} -\imageMacro{ node-locked.png, "Locked slot/node. Stays, regardless the selections in the data manager.",6} +\imageMacro{map_node-unlocked.png, "Unlocked slot/node (default state). Changes with the selections in the data manager.",6} +\imageMacro{map_node-locked.png, "Locked slot/node. Stays, regardless the selections in the data manager.",6} \section MAP_MAPPER_Refine Mapping or geometry refinement The mapper view offers two options to map images:\n \li "Map" (default) \li "Refine geometry" For images "Map" fills the pixels of the output image by interpolating input image pixels using the registration object. This option always works. But may take longer and introduces interpolation errors, because a new image is resampled.\n The second option "Refine geometry" is only offered, if the registration (more precise its inverse kernel) is matrix based and the selected data is an image. In this case it just clones the image and refines the image geometry (origin, orientation, ...); thus no interpolation artefacts are introduced. \remark If you want to use a mapped image in conjunction with the statistic plugin and an mask of the reference image, you must use "Map" to ensure the same geometry. Otherwise the statistic plugin will fail. \section MAP_MAPPER_Settings Settings If you map the image (and not just refine the geometry), you have several settings available:\n \li "Allow undefined pixels": Activate to handle pixels of the result image that are not in the field of view of the input image. This pixel will get the "padding value". \li "Allow error pixels": Activate to handle pixels of the result image that can not be mapped because the registration does not support this part of the output image. This pixel will get the "error value". \li "Interpolator": Set to choose the interpolation strategy that should be used for mapping. \li "Activate super/sub sampling": Activate if you want to use origin and orientation of the reference image but want to alter the spacing. \section MAP_MAPPER_Interpolation Interpolation You can choose from the following interpolation strategies:\n -\li "nearest neighbour": Use the value of the nearest pixel. Fastest, but high interpolation errors for gray value images. Right choice for label images or masks. +\li "nearest neighbor": Use the value of the nearest pixel. Fastest, but high interpolation errors for gray value images. Right choice for label images or masks. \li "Linear": Fast linear interpolation with often sufficient quality. Tends to blur edges. \li "BSpline (3rd order)": Good trade off between time and quality. \li "Windowed Sinc (Hamming)": Good interpolation quality but very time consuming. \li "Windowed Sinc (Welch)": Good interpolation quality but very time consuming. \section MAP_MAPPER_Masks Handling of masks/segmentations If you select an mask as input image, the plugin will be automatically reconfigured to settings that are suitable for the task of mapping masks. -Most importantly the interpolator will be set to "nearest neighbour". +Most importantly the interpolator will be set to "nearest neighbor". */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/icon.svg b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/icon.svg deleted file mode 100644 index 61b42a5b9f..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/icon.svg +++ /dev/null @@ -1,120 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper-examplescreen.png b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper-examplescreen.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper-examplescreen.png rename to Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper-examplescreen.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper-settings.png b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper-settings.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper-settings.png rename to Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper-settings.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper.png b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/mapper.png rename to Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper_icon_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper_icon_doc.svg new file mode 100644 index 0000000000..bcd39e5e84 --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_mapper_icon_doc.svg @@ -0,0 +1,204 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/node-locked.png b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_node-locked.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/node-locked.png rename to Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_node-locked.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/node-unlocked.png b/Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_node-unlocked.png similarity index 100% rename from Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/node-unlocked.png rename to Plugins/org.mitk.gui.qt.matchpoint.mapper/documentation/UserManual/map_node-unlocked.png diff --git a/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/Manual.dox b/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/Manual.dox index ec83f847cb..46cdb16a37 100644 --- a/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/Manual.dox +++ b/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/Manual.dox @@ -1,23 +1,21 @@ /** -\page org_mitk_gui_qt_matchpoint_visualizer The MatchPoint Registration Visualizer Plugin +\page org_mitk_gui_qt_matchpoint_visualizer The MatchPoint Registration Visualizer View -\imageMacro{icon.svg, "Icon of the Registration Visualizer",3} +\imageMacro{map_vis_icon_doc.svg, "Icon of the Registration Visualizer",3} -\li \ref MAP_VIS_Introduction -\li \ref MAP_VIS_Contact -\li \ref MAP_VIS_Usage +\tableofcontents \section MAP_VIS_Introduction Introduction -This plugins is in development to offer the user a way to visualize MatchPoint registrations in an MITK scene. -Currently only a simple grid visualization is implemented.\n -\remark This is an experimental version and work in progress. So please excuse errors or usage issues and report them. This plugin will be improved and polished with the next releases. +This view is in development to offer the user a way to visualize MatchPoint registrations in a MITK scene. +Currently only a simple grid visualization and glyph visualization is implemented.\n +\remark This is an experimental version and work in progress. So please excuse errors or usage issues and report them. This view will be improved and polished with the next releases. \section MAP_VIS_Contact Contact information This plug-in is being developed by the SIDT group (Software development for Integrated Diagnostics and Therapy) at the DKFZ (German Cancer Research Center). If you have any questions, need support, -find a bug or have a feature request, feel free to contact us at dipp@dkfz.de. +find a bug or have a feature request, feel free to contact us at www.mitk.org. \section MAP_VIS_Usage Usage Oops. Documentation is missing and to be done. */ diff --git a/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/icon.svg b/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/icon.svg deleted file mode 100644 index 81c461e166..0000000000 --- a/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/icon.svg +++ /dev/null @@ -1,126 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/map_vis_icon_doc.svg b/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/map_vis_icon_doc.svg new file mode 100644 index 0000000000..59b985fbd5 --- /dev/null +++ b/Plugins/org.mitk.gui.qt.matchpoint.visualizer/documentation/UserManual/map_vis_icon_doc.svg @@ -0,0 +1,205 @@ + + + +image/svg+xml + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file