Pushed new branch T23431-MemoryConsumptionBug.

We also have creashes with nrrd images containing optical properties (these are basically stored as 4D/3D+t images without any specific typing and the rule described above also comes into action). In our case, if using a commandline structure, images are imported as PeakImages per default causing crashes.

Pushed new branch T24088-FixTimeTest.

The former implementation of vessels "dragged around" spheroids potentially considering each voxel multiple times. When just using partial volume spheres the same way, the results will not be correct if voxels are considered multiple times.

Pushed new branch T23443-FixBasicImageProcessingSubtraction.

installing all 4 packages solved the problem :)

works on linux as well.
Resolve as invalid -> could not reproduce.

works fine on windows with current master

progress slider moves now.
However video playback doesn't work with linux see
{T23459}

slider jumps to specific location in MIDDLE mouse button.
Slider increments/decrements by 10% video length on LEFT mouse button. RIGHT mouse button has no functionality on slider.

Pushed new branch T23431-PartialVolumeEffects.

Pushed new branch T23431-SimulatePartialVolumeEffects.

Tests are running on windows and on Ubuntu 16.04 virtual machine.

Pushed new branch T23425-FixTestsOnUbuntu.

Pushed new branch T23424-FixPluginWarningsInPhotoacousticPlugin.

Pushed new branch T23424-FixLinuxCompileWarningsPart2.

Pushed new branch T23424-FixLinuxCompileWarnings.

Pushed new branch T23424-FixBoostCompileErrors.

Pushed new branch T23423-IntegratePhotoacousticSimulationIntoMaster.

Current code coverage of the test cases is about 47% :/

• 80% in the IO submodule and 40% in the main module

can this even be considered a bug? I think it is just that the checklist explicitly said the preview should be green.
Does not impede functionality..

can we close this?

If you have a look at the sample classes from e.g. the awesome project template or simply from classes of the MITK Core module etc, it should get clear.

It will not be an issue for nearly all use cases. Also didn't find a way to reliably reproduce this.

Closing this, further work will be done in the CAMI experimental repository.

It doesn't work even from within visual studio. Why does the plugin generator have a Qt dependency anyway?

this will be dealt with (hopefully) by using a GPU mcxyz implementation provided by jacques