I am checking the code and there seems to be a problem with the node names, not with the functionality itself. I will tell you when I get to know more.
-- Xabier Artaechevarria Cancer Imaging Laboratory Centre for Applied Medical Research www.cima.es Maleike Daniel <[EMAIL PROTECTED]> ha escrito: > On Thu, 2008-02-07 at 18:08 +0100, Xabier Artaechevarria Artieda wrote: >> Hi all, >> First of all, I would like to thank MITK developers for the great >> SliceBasedSegmentation functionality. >> We think that the functionality does not properly update previously >> segmented regions, though. We have checked it by looking at the >> "ModifiedTime" property of the Data Manager. >> What we do is the following: >> 1. Open an image. >> 2. Segment it with our own functionality. >> 3. Check "Modified Time" property >> 4. Modify segmentation with "Add" tool using SliceBasedSegmentation. >> We "see" the new added regions. >> 5. Check "Modified Time" property -> it is the same as in step 3 (we >> do change from one object to another to be sure that the time is >> updated) >> >> We think that any segmentation functionality can be used to reproduce >> the problem. >> When we access the data object again for visualization using our >> functionality, it turns out to be the old one (step 2), the >> modifications done with SliceBasedSegmentation are gone. >> Could this be solved easily? >> Best regards, > > Hallo Xabi, > > I'm sorry, but I cannot reproduce your problem. I tested two things and > both were fine: > > 1. In mitkContourTool.cpp, after line 134, I added the following code: > > std::cout << "image mtime: " << image->GetMTime() << std::endl; > > This prints out the modified time of the segmentation after each use > of the Add/Substract tool. I changed the other tools in the same way, > always right after the use of OverwriteSliceImageFilter. > > For all tools the output showed that the mitk::Image object of the > segmentation had an increased modified time after each use of the > tools. > > 2. I used a separate functionality to generate a binary segmentation > (of a vessel tree in this case). I then used SliceBasedSegmentation > to remove parts of this binary image. Afterwards I switched back > to the vessel segmentation functionality and created a surface from > the binary image. This surface included all changes that I had made > in SliceBasedSegmentation. > > So I have no clue what could be wrong in your case. Could you give me > more detail? Two things that could help: > > - You wrote "Check "Modified Time" property -> it is the same". What > exactly have you checked. There is no "property" in the MITK sense > called "Modified time". I guess you selected the segmentation and > pressed the "Info" button. There are lots of modified times shown for > the different members of mitk::Image. Are you sure that you checked > the one of the Image object (ok, the output of this dialog is very > badly structured)? > > - Could you either post some of the relevant source code (esp. the part > where you "access the data object again") or give me access to it in > some other way (private mail or someting else)? Perhaps your code does > keep a copy of the segmentation somewhere and doesn't really use the > segmentation from the DataTree? > > Best regards, > Daniel > > -- > Dipl.-Inform. Med. Daniel Maleike Phone: +49 6221 42 2326 > Deutsches Krebsforschungszentrum Im Neuenheimer Feld 280 > Medical and Biological Informatics (E130) 69120 Heidelberg > > ---------------------------------------------------------------- Este mensaje ha sido enviado desde https://webmail.unav.es ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
