User Details
- User Since
- Aug 1 2016, 12:10 PM (446 w, 1 d)
- Roles
- Disabled
Aug 2 2016
The indices are calculated the same if we remove the changes implemented in ipSegmentation.h and ipSegnentationP.h. So that does not seem to be the source of the error. GetAffectedWorkingSlice also delivers the right slice. That was tested by initializing a datanode with the slice and adding it to the datastorage. My suggestion is that the calculations of the contour fail due too the switch from unsigned char to unsigned short somewhere in the ipPic sections of the code.
Important note:
[530117]: Merge branch 'bug-19067-surface-loading-dialog-behind-workbench'
Merged commits:
2015-08-19 15:25:18 Vincent Reuter [77abbb]
- added defined Qt::WindowFlags to call of constructor base class of QmitkFileReaderOptionDialog class: Qt::WindowStaysOnTopHint.
QmitkFileReaderOptionDialog class needs a defined Qt::WindowFlags when constructor is called: e.g. Qt::WindowStaysOnTopHint passed to constructor of base class QDialog.
[465fe4]: Merge branch 'bug-18976-PoinstSet-Interaction-crashes-large-coordinate
Merged commits:
2015-08-19 15:35:54 Vincent Reuter [64556b]
- changed static function declaration
crash 1:
adding a point manually to a pointset with large value outside of double precision and afterwards performing a global reinit
-> only occurs in debug mode, not in release mode
-> fixed problem concerning double precision for bounding boxes with 0 extent:
- added throw exception in mitkRenderingManager.cpp if bounding box has 0 extent due to double precision exceeded
- added QMessageBox with warning that input point coordinate exceeds double precision in QmitkEditPointDialog.cpp
I can reproduce the crash for two cases:
Note:
- mitkPointSet.cpp checks itkBounds first: if (width == 0) -> bounds +-0.5
- mitkRenderingManager.cpp checks BaseGeometry::BoundsArrayTyp newBounds afterwards: if(bound 1 equal bound 2) -> second bound +1
case: pointset contains a single point
Crashes in PlaneGeometry::CheckBounds due to bound[1] (witdh) = 0.
Value range is 19 digits like long data type.
Problem suspected in QmitkEditPointDialog::SetPoint in QmitkEditPointDialog.cpp
Second crash is related to mitk::DisplayGeometry Class that should be solved if the recent major geometry changes are integrated into the master branch.
Modalities are MR and CT. I could not determine further differentiations.
Could not reproduce that error on my Linux
Do you mean like this (see screenshot)?
after changing sizeAdjustPoliciy to AdjustToMinimumContents did not change anything
[cd8433]: Merge branch 'bug-18529-image-statistics-compfix'
Merged commits:
2015-03-20 13:36:24 Vincent Reuter [ef4e3d]
COMP fixed with static_cast
new presumption:
[56c29c]: Merge branch 'bug-18529-statistics-bin-size-calc'
Merged commits:
2015-03-18 16:25:09 Vincent Reuter [6c52c2]
fixed bug for bin size calculation
false bin size calculation for histogram
this bug is actually not a bug it is a wanted function.
- label "clip" leads to movie maker in view navigator search in current release version 2014.10.00
this bug is actually not a bug it is a wanted function.
I tried it several times and it did not occur
Bug does not occur anymore.
Still, the default behavior of the "with surface model" checkbox should maybe be changed.