View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002595Slicer4Core: Base Codepublic2012-10-02 07:342013-07-04 12:19
Reportersankhesh Assigned Tojcfr  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
PlatformMac - factory.kitwarein.comOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0002595: Editor Error Dialog - Merge volume modified
Description

The neurosurgical planning tutorial seems to be raising an editor error dialog ( https://github.com/Slicer/Slicer/blob/master/Modules/Scripted/EditorLib/HelperBox.py#L295)
which leads to a wrong 3D reconstructed volume. This does not happen when you try the tutorial manually on the same machine. The test runs smoothly on Linux without this dialog.

Additional Information

Steve:
Gee, I don't know - as you can see in the code, somehow the target
vtkImageData has a more recent Modified time than the inputs so
there's a warning about doing the operation and a backup volume is
created.

Are you saying that replaying the macro using the qt testing menu does
not have this warning but the ctest version does? Or do you mean
manually as in doing the same operations by hand? I guess that's the
clue for debugging, but I'm not sure where it will lead.

I believe Modified is a virtual method so you could make an
implementation in vtkMRMLScalarVolume node and set a breakpoint there
to see what combination of calls leads to the it being called on the
merge volume (but that doesn't sound like an easy task since it will
no doubt be called a lot).

As I mentioned in the bug report I find these Qt tests to be very hard
to debug since you only have the XML files to work with. Maybe
re-implementing the test as a real python script would provide the
right needed for diagnosis - but that's just a guess too.

Good luck and let me know if there's anything I should try on my machines.

TagsNo tags attached.

Activities

sankhesh

sankhesh

2012-10-02 07:36

developer   ~0006326

Last edited: 2012-10-02 07:38

It shows up when replaying the macro but not when the steps are reproduced by hand.
pieper

pieper

2013-07-04 12:19

administrator   ~0008840

Probably this test should be converted into a self test rather than playing back the macro.

Issue History

Date Modified Username Field Change
2012-10-02 07:34 sankhesh New Issue
2012-10-02 07:34 sankhesh Status new => assigned
2012-10-02 07:34 sankhesh Assigned To => kikinis
2012-10-02 07:36 sankhesh Note Added: 0006326
2012-10-02 07:36 sankhesh Assigned To kikinis => sankhesh
2012-10-02 07:36 sankhesh Category GUI => Base Code
2012-10-02 07:37 sankhesh Platform => Mac - factory.kitwarein.com
2012-10-02 07:37 sankhesh Target Version => Slicer 4.3.0
2012-10-02 07:38 sankhesh Note Edited: 0006326
2013-04-09 11:22 sankhesh Target Version Slicer 4.3.0 =>
2013-06-03 05:15 jcfr Assigned To sankhesh => jcfr
2013-07-04 12:19 pieper Note Added: 0008840