I can confirm this bug using the test data from the 3M3-Demodata folder. I'll check this issue.

New remote branch pushed: bug-14736-ExecutionOfRigidRegistration

[883988]: Merge branch 'bug-14712-SceneLoadingCrash'

Merged commits:

2013-11-27 14:38:15 Sven Mersmann [6f5df7]
mitkSceneIO now returns original data storage if scene file cannot be loaded.

New remote branch pushed: bug-14712-SceneLoadingCrash

Alfred, please provide invalid scene file to make this bug reproducible.

What did you assume to be an invalid scene file? One that does not exist? I tried this issue with a normal scene file and it worked perfectly alright. Probable pitfalls: Set path variable for additional third libs, check if file path isspecified correctly. Can you provide an invalid scene file to make this issue reproducible?

Was this issue treated elsewhere? On my maschine the statistics calculation works perfectly fine. I set the bug status on works for me.

I take this bug and check the issue.

After discussion in the MITK meeting the behavior shall be maintained. In order to make the user aware od this issue, the documentation of the exception needs to be adapted accordingly.

Removed RFD flag, documentation needs to be adapted.

Than I'll have a look at it.

The described error did not occur on my system.

Re-assigned bug to Andi who works on T13514. The solution of that bug fixes this issue.

I'll have a look at this issue!

[a3b503]: Merge branch 'bug-13933-ErrorInToFDistanceImageToPointSetFilter'

Merged commits:

2014-03-11 18:40:37 Sven Mersmann [35a790]
If SetSubset() is called before SetInput() the boundary checking is now performed against the biggest possible bounds.

I implemented the suggested solution and enhanced the unit test to see if the fix works.

Tried to reproduce the bug but it works for me. After doublechecking with Christianwho is the reporter, we decided to close this bug, hence it did not appear for a longer time now. Probably resolved with another bug.

This view causes a direct crash upon initialization.

	QtCored4.dll!qt_message_output(QtMsgType msgType=QtFatalMsg, const char * buf=0x000000001179da78)  Line 2247	C++
	QtCored4.dll!qt_message(QtMsgType msgType=QtFatalMsg, const char * msg=0x000000006734d1d0, char * ap=0x0000000000b84c98)  Line 2305 + 0x19 bytes	C++
	QtCored4.dll!qFatal(const char * msg=0x000000006734d1d0, ...)  Line 2489	C++
	QtCored4.dll!qt_assert(const char * assertion=0x0000000065db4800, const char * file=0x0000000065db47e0, int line=1171)  Line 2005	C++

QtGuid4.dll!QHeaderView::setResizeMode(int logicalIndex=5, QHeaderView::ResizeMode mode=ResizeToContents) Line 1171 + 0x21 bytes C++

	liborg_mitk_gui_qt_ext.dll!QmitkModuleView::CreateQtPartControl(QWidget * parent=0x00000000115dd8d0)  Line 62	C++
	liborg_blueberry_ui_qt.dll!berry::QtViewPart::CreatePartControl(void * parent=0x00000000115dd8d0)  Line 25	C++
	liborg_blueberry_ui.dll!berry::ViewReference::CreatePartHelper()  Line 363	C++
	liborg_blueberry_ui.dll!berry::ViewReference::CreatePart()  Line 156 + 0x15 bytes	C++
	liborg_blueberry_ui.dll!berry::WorkbenchPartReference::GetPart(bool restore=true)  Line 467 + 0x29 bytes	C++
	liborg_blueberry_ui.dll!berry::Perspective::ShowView(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & viewId="org.mitk.views.modules", const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & secondaryId="")  Line 1548 + 0x5a bytes	C++
	liborg_blueberry_ui.dll!berry::WorkbenchPage::BusyShowView(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & viewID="org.mitk.views.modules", const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & secondaryID="", int mode=1)  Line 1134 + 0x2a bytes	C++
	liborg_blueberry_ui.dll!berry::WorkbenchPage::ShowView(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & viewID="org.mitk.views.modules", const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & secondaryID="", int mode=1)  Line 3690 + 0x30 bytes	C++
	liborg_blueberry_ui.dll!berry::WorkbenchPage::ShowView(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & viewID="org.mitk.views.modules")  Line 3661 + 0x4c bytes	C++
	liborg_blueberry_ui_qt.dll!berry::QtShowViewAction::Run()  Line 51 + 0xaa bytes	C++
	liborg_blueberry_ui_qt.dll!berry::QtShowViewAction::qt_metacall(QMetaObject::Call _c=InvokeMetaMethod, int _id=0, void * * _a=0x0000000000b86e10)  Line 75	C++
	QtCored4.dll!QMetaObject::metacall(QObject * object=0x000000000e0eebc0, QMetaObject::Call cl=InvokeMetaMethod, int idx=19, void * * argv=0x0000000000b86e10)  Line 238	C++
	QtCored4.dll!QMetaObject::activate(QObject * sender=0x000000000e0eebc0, const QMetaObject * m=0x00000000661162d8, int local_signal_index=1, void * * argv=0x0000000000b86e10)  Line 3272 + 0x49 bytes	C++
	QtGuid4.dll!QAction::triggered(bool _t1=false)  Line 264	C++
	QtGuid4.dll!QAction::activate(QAction::ActionEvent event=Trigger)  Line 1258	C++
	QtGuid4.dll!QAction::trigger()  Line 218 + 0x15 bytes	C++
	QtGuid4.dll!QToolButton::nextCheckState()  Line 1148	C++
	QtGuid4.dll!QAbstractButtonPrivate::click()  Line 529	C++
	QtGuid4.dll!QAbstractButton::mouseReleaseEvent(QMouseEvent * e=0x0000000000b887c8)  Line 1122	C++
	QtGuid4.dll!QToolButton::mouseReleaseEvent(QMouseEvent * e=0x0000000000b887c8)  Line 722	C++
	QtGuid4.dll!QWidget::event(QEvent * event=0x0000000000b887c8)  Line 8188	C++
	QtGuid4.dll!QAbstractButton::event(QEvent * e=0x0000000000b887c8)  Line 1081	C++
	QtGuid4.dll!QToolButton::event(QEvent * event=0x0000000000b887c8)  Line 1164	C++
	QtGuid4.dll!QApplicationPrivate::notify_helper(QObject * receiver=0x000000000e072350, QEvent * e=0x0000000000b887c8)  Line 4396 + 0x15 bytes	C++
	QtGuid4.dll!QApplication::notify(QObject * receiver=0x000000000e072350, QEvent * e=0x0000000000b887c8)  Line 3959 + 0x51 bytes	C++
	mitkWorkbench.exe!QtSafeApplication::notify(QObject * receiver=0x000000000e072350, QEvent * event=0x0000000000b887c8)  Line 47 + 0x1e bytes	C++
	QtCored4.dll!QCoreApplication::notifyInternal(QObject * receiver=0x000000000e072350, QEvent * event=0x0000000000b887c8)  Line 732 + 0x26 bytes	C++
	QtCored4.dll!QCoreApplication::sendSpontaneousEvent(QObject * receiver=0x000000000e072350, QEvent * event=0x0000000000b887c8)  Line 218 + 0x4c bytes	C++
	QtGuid4.dll!QApplicationPrivate::sendMouseEvent(QWidget * receiver=0x000000000e072350, QMouseEvent * event=0x0000000000b887c8, QWidget * alienWidget=0x000000000e072350, QWidget * nativeWidget=0x000000000e0500c0, QWidget * * buttonDown=0x0000000066117fe0, QPointer<QWidget> & lastMouseReceiver={...}, bool spontaneous=true)  Line 3056 + 0x16 bytes	C++
	QtGuid4.dll!QETWidget::translateMouseEvent(const tagMSG & msg={...})  Line 3317 + 0x3f bytes	C++
	QtGuid4.dll!QtWndProc(HWND__ * hwnd=0x00000000079e1110, unsigned int message=514, unsigned __int64 wParam=0, __int64 lParam=1311080)  Line 1657 + 0x15 bytes	C++
	user32.dll!0000000077b09bd1() 	
	[Frames below may be incorrect and/or missing, no symbols loaded for user32.dll]	
	user32.dll!0000000077b098da() 	
	QtCored4.dll!QEventDispatcherWin32::processEvents(QFlags<enum QEventLoop::ProcessEventsFlag> * flags=0x0000000000b8ca70)  Line 806	C++
	QtGuid4.dll!QGuiEventDispatcherWin32::processEvents(QFlags<enum QEventLoop::ProcessEventsFlag> * flags=0x0000000000b8cabc)  Line 1170 + 0x27 bytes	C++
	QtCored4.dll!QEventLoop::processEvents(QFlags<enum QEventLoop::ProcessEventsFlag> * flags=0x0000000000b8cb28)  Line 150	C++
	QtCored4.dll!QEventLoop::exec(QFlags<enum QEventLoop::ProcessEventsFlag> * flags=0x0000000000b8cbb0)  Line 201 + 0x53 bytes	C++
	QtCored4.dll!QCoreApplication::exec()  Line 1009 + 0x23 bytes	C++
	QtGuid4.dll!QApplication::exec()  Line 3673	C++
	liborg_blueberry_ui_qt.dll!berry::QtDisplay::RunEventLoop()  Line 46	C++
	liborg_blueberry_ui.dll!berry::Workbench::RunUI()  Line 764	C++
	liborg_blueberry_ui.dll!berry::Workbench::CreateAndRunWorkbench(berry::Display * display=0x0000000002500b70, berry::WorkbenchAdvisor * advisor=0x0000000005d9e2b0)  Line 190 + 0xa bytes	C++
	liborg_blueberry_ui.dll!berry::PlatformUI::CreateAndRunWorkbench(berry::Display * display=0x0000000002500b70, berry::WorkbenchAdvisor * advisor=0x0000000005d9e2b0)  Line 60	C++
	liborg_mitk_gui_qt_extapplication.dll!QmitkExtApplication::Start()  Line 32 + 0x4b bytes	C++
	liborg_blueberry_osgi.dll!berry::Starter::Run(int & argc=1, char * * argv=0x00000000024e4f10, Poco::Util::AbstractConfiguration * config=0x00000000024f5960)  Line 198 + 0x16 bytes	C++
	mitkWorkbench.exe!main(int argc=1, char * * argv=0x00000000024e4f10)  Line 142 + 0x1e bytes	C++
	mitkWorkbench.exe!__tmainCRTStartup()  Line 586 + 0x19 bytes	C
	mitkWorkbench.exe!mainCRTStartup()  Line 403	C
	kernel32.dll!00000000779e652d() 	
	ntdll.dll!0000000077c1c521()

New remote branch pushed: bug-13180-RemoveEventProcessingFromProgressBar

[f90374]: Merge branch 'bug-13180-RemoveEventProcessingFromProgressBar'

Merged commits:

2013-10-09 17:22:22 Sven Mersmann [cf1b01]
Remove qApp->processEvent() from QmitkProgressBar due to crashes during long running operations.This call was responsible for triggering a restart of the operation while the operation was running.

To generate a quick solution to prevent the application from crashes due to restarting operations while they are running, the qApp->processEvents() call was removed from the QmitkProgressBar implementation.
This causes the scene loading to be not displayed in the progress bar, but it eliminates the application crashes.
Adding new T16246, to make the progress bar react on scene reading.
Adding new T16247, to further discuss a better solution for the progress bar implementation.

This bug can cause a lot of other bugs, since the responsivity of the gui during execution of an operation occurs nearly everywhere. Setting importance to high critical since otherwise we might get flooded with related bugs.

The misleading error messages in the GUI have been removed in T15359. The remaining issue of this bug is to decide if the calculation of the statistic along the intensity profile is a requested feature. Therefore, I set this bug to RFD.

Hm, in this context I think this bug needs to be discussed in detail. I set the RFD flag and change the target milestone to "AfterNextRelease".

This bug was discussed in the MITK meeting yesterday. Since the currently implemented behavior is a MINT feature, we won't remove it. However, there seem to be two interaction modes already implemented, but how is it possible to switch between them?

Removing RFD tag. Changing asignee, Markus cares about the interaction at MINT.
@Markus: Is there a solution for this issue? (Some switch to define the interaction pattern).

Adding Markus in CC.
Is this a special mint feature that a control point is set on mouseReleaseEvent? Do you need this behavior?

Ok, nice feature ;-)
We need to disable it on both open and closed figures (line path and polygons). Is this an important feature, than we leave it as it is, otherwise I would just prohibit the event handling in the interactor.

I'll take care of this. My guess is that the mouse click event listens to both the OnPush- and OnReleaseEvent.

I'll take care of this. My guess is that the mouse click event listens to both the OnPush- and OnReleaseEvent.

[083def]: Merge branch 'bug-13086-ImageStatisticsOnSegmentation'

Merged commits:

2013-05-29 16:28:26 Sven Mersmann [bad4cf]
Removed the QmitkStatisticsAction since it is not needed any longer.

The issue is solved and merged to the master. Setting the bug status to resolved, fixed.

I check this issue.

I discussed this issue with Andi and we agreed in removing the function to calculate the statistics from the DataManager context menu. The functionality is in future solely executable from the image statistics view by selecting both the source image and the segmentation from the DataManager. It is sufficient to offer one user interface for one function.

Andi, I don't know that feature, but I guess this mechanism is not included in the image statistics bundle, at least I can't remember any code for that feature. Mathias, did you implement that feature in the image statistics bundle?

[d74532]: Merge branch 'bug-12815-NormalCalculationForSurfaces'

Merged commits:

2013-02-20 16:44:15 Sven Mersmann [4ca673]
Added some exception handling in the class and wrote unit test for mitkImageToSurfaceFilter.

The bug fix is committed and should work now, set this bug on resolved fixed.

New remote branch pushed: bug-12815-NormalCalculationForSurfaces

The problem is solved. The normals are now calculated upon generation of the surface in the mitkImageToSurfaceFilter - IO should work now. After adding the unit test for this class the solution will be committed.

I see the problem in the data gzombori attached to this bug and try to reproduce the actual issue.

@ Miklos and gzombori: As Alfred I cannot reproduce the problem from Miklos description. I see the problem in the .vtk data you attached to this bug, can you attach the source data the surface was generated from together with a detailed description of the parameters you used to generate the surface.
Did you use the 12-12 release or do you compile MITK from the current git repository?

Thanks Miklos for the data, I can reproduce the error now. Seems to be a problem that occurs exclusively at MR data, or did you made other experiences?

[a3ae9c]: Merge branch 'bug-12408-GeometryInImageCloneMethod'

Merged commits:

2012-08-01 16:16:50 Sven Mersmann [040aa0]
Changed clone method to account for 4D image geometries. Adapted the unit test accordingly.

Fix solution works, waiting for Core_Modification flag.

T3104is pushed into the master meanwhile, this commit might have solved the problem...

Stefan already implemented the clone method in another bug.
@Stefan: In future you should check the bugzilla for existing bugs and discuss such issues in the MITK meeting before starting to implement anything.

This issue was discussed in the MITk meeting. The clone methods are to be implemented for the planar figure classes.

What is the status here, can I close the bug?

What is the status here, can I close the bug?

The first version with working rgb image display can be found on mbits. Branch bug-12129-ToFEndoscopeIntegration hash code rMITKdf07e7fd6fa9.

Changes merged to master!

[31c6af]: Merge branch 'bug-11864-CameraIntrinsicsValidity'

Merged commits:

2012-07-02 11:38:42 Sven Mersmann [687001]
Add new copyright header

The code is integrated in the master!

[5018f5]: Merge branch 'bug-11756-CamboardIntegration'

Merged commits:

2012-06-19 08:06:48 Sven Mersmann [3f9a77]
COMP: Changes due to new method signature.

Implemented first working version, needs some documentation and cleaning.

[4fe921]: Merge branch 'bug-11756-CamboardIntegration'

Merged commits:

2012-06-19 07:21:20 Sven Mersmann [2e5d38]
Some code clean up

[ffb684]: Merge branch 'bug-11756-CamboardIntegration'

Merged commits:

2012-06-19 07:40:21 Sven Mersmann [06647b]
COMP: Added new methods to the stub class.

The method to obtain the raw data only returns the calibrated images and not the taps. The raw data acquisition is only possible with further driver software.

[92e73d]: Merge branch 'bug-11680-RigidRegistrationMasking'

Merged commits:

2013-10-10 14:45:12 Sven Mersmann [283268]
Remove listener after use.

Still valid? I'll check this issue!

What is the status of this bug, did you work on it, Christoph, otherwise I'll have a look at it.

New remote branch pushed: bug-11680-RigidRegistrationMasking

The problem is solved, however, it will not make it to the 09-2013 release.

New remote branch pushed: bug-11680-EnhanceRigidRegMaskOption

I have added two pics, Thomas, is that the problem you just described? After Global reinit everything seems to be fine, after reinit the position of the 2D render windows are at its minimum extend.

After Reinit

After Global Reinit

After Reinit

After Global Reinit

Please uncomment the excluded test cases in the unit test and check if the unit test works.

[cd3a93]: Merge branch 'bug-11162-MeasurementBundleCrash'

Merged commits:

2012-03-07 19:22:13 Sven Mersmann [7a0d01]
COMP: corrected misspelling!

[8169be]: Merge branch 'bug-11162-MeasurementBundleCrash'

Merged commits:

2012-03-07 19:10:07 Sven Mersmann [a240fe]
The CornerAnnotation is not cleaned and therefore the m_MeasurementInfoRenderer remains in an invalid state. The text gets removed now and the renderer is cleaned correctly.

[6d4b8f]: Merge branch 'bug-11162-MeasurementBundleCrash'

Merged commits:

2012-03-08 16:56:43 Sven Mersmann [5fba3f]
added NULL pointer query

The crash is reproducible for this configuration:

1. Load an image
2. Activate the measurement bundle with this image
3. Generate a new planar figure
4. Close the measurement bundle
5. Remove the planar figure from the data storage
6. re-open the measurement bundle and draw new planar figure

-> Crashes

Changes pushed to master!

[8fad91]: Merge branch 'bug-11058-Correct2DImageInit'

Merged commits:

2012-03-21 15:23:23 Sven Mersmann [945e10]
Changed the initialize method in the clone image method. Added test case to guarantee that the dimensionality of the clone image is equivalent to that of the source image

Needs core modification!

According to MITK group meeting the prefered solution for this bug is to change the Initialize() method in the clone method to guarantee correct initialization of the image dimension.

New remote branch pushed: bug-10925-ITK4MigrationToF

New remote branch pushed: bug-10925-ITK4ToFIntegration