Deleted branch bugfix/T27607-chartExample-UserManual.

I surrendered and deleted the chartExample documentation as it simply was a copy of the dummy documentation anyway (in other words: no documentation). The Ubuntu and macOS dartclients now complain because of the geometrytools plugin. Hence, the Windows dartclient probably reports a complete list as it continues to generate the documentation.

Pushed new branch bugfix/T27608-DocumentationRefurbish-DeveloperManual.

Pushed new branch bugfix/T27607-chartExample-UserManual.

Deleted branch bugfix/T27607-chartExample-UserManual.

Okay, two red herrings here:

These are views that have non-standard view IDs (not beginning with "org.mitk.views"):

• QmitkCESTNormalizeView.cpp
• CommandLineModulesViewConstants.cpp
• QmitkDicomInspectorView.cpp
• FitGeneratorDemoView.cpp
• GenericDataFittingView.cpp
• ModelFitInspectorView.cpp
• PerfusionCurveDescriptionParameterView.cpp
• ConcentrationCurveConverterView.cpp
• MRPerfusionView.cpp
• PETDynamicView.cpp
• PerfusionDataSimulationView.cpp
• MatchPointBrowserConstants.cpp

When fixing these IDs make sure to also change them in the corresponding plugin.xml file and in any \page links in the documentation.

"imageMacro{3}=\image html \1 \2 \n \image latex \1 \2 width=\3cm"

Moving the table of contents above any imageMacros did not work. Next try is to (temporarily) remove the imageMacros and if it works, look into the imageMacro.

Pushed new branch bugfix/T27607-chartExample-UserManual.

Pushed new branch T27603-FibCompression.

So I am not quite sure that about the re-init problem but to further clarify my list:

Deleted branch bugfix/T27085-2DRegionGrowing.

In T27085#207104, @kislinsk wrote:

This bug was introduced in T26167: ExtractSliceFilter handles 3D+t images inefficiently and inconsequently in the ExtractSliceFilter, so more or less every sliced image by this filter is affected. One of the overloads of Image::Initialize() that uses a PlaneGeometry as input is called with the parameter sDim set to 2. I guess the meaning of this parameter was simply misinterpreted as image dimension instead of number of slices.

In T27085#207102, @kislinsk wrote:

The ToolManager reference and working slices are 2d according to their details, but the number of slices is set to 2. An additional empty slice is drawn if these images are added to the data storage for inspection.

Another issue I noticed while working on region growing:

Cleaned up naming of DICOM related modules

@kleina do you still have the problem?

+1

Yes.

In T27507#206802, @kalali wrote:

But either our reinit-algorithm is misleading or the static mask should really only cover this individual timestep, instead of the whole time span. Or am I missing something?

I think you are missing, that one should never reinit on the segmentation itself, but always on the reference image. Then there is always a time slider apropriate to the reference image where you can select the current time point and the reference image content associated with this time point should be used to generate the (static) segmentation.
Could you please recheck your evaluation? I think we have a fundamental difference in the assumption how the segmentation tools should behave an therefore what the correct outcomes of the tools should be. Thank you.

@kislinsk/@kalali Is this bug also solved due to your fix of T27386?

Pushed new branch bugfix/T27085-2DRegionGrowing.

Pushed new branch T27601-FiberSliceThickness.

I would suggest that you land it for now since it solves the bug and I will create another task in which I also take a look into the stepper problem. But both is fine for me :)

Pushed new branch T27597-TrackingSignalSlot.

@thomass Shold we land my solution now, or did you take care in a better way (which would be totaly fine)? In the later case it would make sense that you claim the task and we scrap my D346.

In T27559#206852, @kislinsk wrote:

Start at 16 seconds, end at 30 seconds (sorry @floca):

Deleted branch feature/T27596-UpdateSupportedPlatforms.

Pushed new branch feature/T27596-UpdateSupportedPlatforms.

Ok. @kalali Thank you very much for the clarification.