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 3d911805f2..336b706c50 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,46 +1,46 @@
/**
-\page org_mitk_gui_qt_matchpoint_algorithm_browser The MatchPoint Algorithm Browser View
+\page org_mitk_views_matchpoint_algorithm_browser The MatchPoint Algorithm Browser View
\imageMacro{map_icon_browser_doc.svg, "Icon of the MatchPoint Algorithm Browser", 3}
\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_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).
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) 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
- UID Unique identifier for the registration algorithm (e.g. used in the library; may not be "human readable/understandable")
- Author Name of the author(s) that has (have) developed the algorithm.
- Terms Terms of usage for the algorithm.
- Data type The type of date which is used by the algorithm to determine the registration. E.g. Image, point set, contour or surface
- Computation style Specifies of the algorithm determines the registration by an iterative optimization process or analytically (e.g. closed form solution).
Deterministic Specifies if the algorithm is deterministic (same input -> same output) or stochastic (e.g. by sampling the image while determining the registration). Results of stochastic algorithm may vary (slightly) because of their random aspect.
Resolution style Defines if the algorithm uses a multi resolution/scale approach.
- Dim (Moving) Number of dimensions of the frame of reference within which the data is defined that should be registered.
- Modality (Moving) Modality of the moving entity (image). Thus the frame of reference where the registration should map from. E.g. CT, MRI, PET
- Dim (Target) Number of dimensions of the frame of reference into which the data should be mapped.
- Modality (Target) Modality of the target entity (image). Thus the frame of reference where the registration should map into. E.g. CT, MRI, PET
- Subject Defines if the algorithm was developed to register data of the same subject (intrasubject), to register two subjects (intersubject) or to register onto an atlas.
- Object Specifies for which "part" of the anatomy the algorithm was developed for.
- Transformation model Specifies the type of transformation used by the algorithm. E.g.: affine, b-spline, non-rigid.
- Transformation domain Defines it the transformation operates globally (e.g. Matrix) or locally (e.g. vector field).
- Optimization strategy The used optimization strategy (if an optimizer is used).
- Metric The cost function/metric that is used by the optimizer (if an optimizer is used).
- Citation/Reference Reference to literature that contains information about the algorithm and should be used to cite the algorithm.
- Literature Secondary literature regarding the algorithm or used concepts in the algorithm. Use the field "Citation/Reference" for the literature that should be cited when using the algorithm.
- Contact Internal contact for questions regarding the algorithm.
*/
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 ac1d07d340..fee72e6aca 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 View
+\page org_mitk_views_matchpoint_framereg The MatchPoint Motion/Frame Correction View
\imageMacro{"map_framereg_icon_doc.svg", "Icon of the MatchPoint Algorithm Control", 3}
\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 German Cancer Research Center (DKFZ). 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_FRAME_Usage Usage
\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{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{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{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.
\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)"
\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{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/plugin.xml b/Plugins/org.mitk.gui.qt.matchpoint.framereg/plugin.xml
index 0386b0c385..92f222248b 100644
--- a/Plugins/org.mitk.gui.qt.matchpoint.framereg/plugin.xml
+++ b/Plugins/org.mitk.gui.qt.matchpoint.framereg/plugin.xml
@@ -1,12 +1,12 @@
-
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 1a23e3e98a..29de129d59 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,21 +1,21 @@
/**
-\page org_mitk_gui_qt_matchpoint_visualizer The MatchPoint Registration Visualizer View
+\page org_mitk_views_matchpoint_visualizer The MatchPoint Registration Visualizer View
\imageMacro{map_vis_icon_doc.svg, "Icon of the Registration Visualizer",3}
\tableofcontents
\section MAP_VIS_Introduction Introduction
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 German Cancer Research Center (DKFZ). 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_VIS_Usage Usage
Oops. Documentation is missing and to be done.
*/