View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003439Slicer4Core: Base Codepublic2013-10-09 07:122018-03-02 11:07
Reporternormandrobert Assigned Tojcfr  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product VersionSlicer 4.3.0 
Target VersionFixed in VersionSlicer 4.6.0 
Summary0003439: Crop functionality unexpected behaviour with volume rendering v 4.3.0-2013-09-30 OsX and Linux
Description

Confirmation of undesired behaviour has been reproduced by Steve Pieper. See additional information section for that bit.

I want to use Crop functionality to limit the size of a volume from which I will be making a surface model to a feature of interest only. Cropping doe not seem to limit the extent of the rendered volume.

Steps to reproduce:

Modules: DICOM. Load volume data from local DICOM database (previously pulled from a server)
All good
Modules: Volume Rendering. Set Crop Enable, Display ROI, ROI Fit to Volume, VTK OpenGL rendering, click on "eye" icon to see the volume, centre the 3D view on the scene and finally adjust the opacity to make features of interest stand out.
All good
Modules:Converter:Crop Volume. Volume shown in selection dialog is indeed the only one in existence. Input ROI in selection dialog is indeed the only ROI in existence. Resize the ROI to be a small subset of the total volume. Leave all other options as is. Click on crop.

Modules: Volume Rendering. Module now shows 2 volumes as expected. Go to original module and make it invisible. Go to new volume created as a result of cropping and make that one visible. Toggle Crop option and watch region outside the ROI appear/disappear. I expected data outside the ROI to be gone in the new volume. The data is gone in the RYG views as expected.

Additional Information

From Steve Pieper reply:

Yes, I can replicate the issues you reported - thanks for letting us know. It does seem to be an interaction between CropVolume and Volume Rendering because as Andrey reports I don't see the same effect when either is used alone. Could you file a mantis report? [1].

Andriy Fedorov could not reproduce the problem but the step he used were different:
From his email:

Can you reproduce the
problem with just CropVolume module, not going to VolumeRendering?

I was able to do the following:

1) load MRHead from "Sample data"
2) in CropVolume select MRHead as input, create ROI
3) do Crop: resulting volume is cropped as expected.

I was not able to reproduce the crash.

AF

TagsNo tags attached.

Relationships

duplicate of 0002864 closedfinetjul Changing selected volume has no effect after cropping 

Activities

jcfr

jcfr

2014-03-07 05:40

administrator   ~0011318

We were able to reproduce the problem.

This would be nice to fix - but we think it's low priority right now. Let
us know if it is high priority for you or if you would like to help us by contributing a patch.

Thanks
jcfr

jcfr

2016-06-14 15:44

administrator   ~0013971

As indicated in [1], closing because unable to reproduce the problem.

[1] http://na-mic.org/Mantis/view.php?id=2864#c13970

Issue History

Date Modified Username Field Change
2013-10-09 07:12 normandrobert New Issue
2013-10-09 07:12 normandrobert Status new => assigned
2013-10-09 07:12 normandrobert Assigned To => jcfr
2014-03-07 05:40 jcfr Note Added: 0011318
2014-03-07 05:40 jcfr Status assigned => acknowledged
2016-06-14 15:42 jcfr Relationship added duplicate of 0002864
2016-06-14 15:44 jcfr Note Added: 0013971
2016-06-14 15:44 jcfr Status acknowledged => resolved
2016-06-14 15:44 jcfr Fixed in Version => Slicer 4.6.0
2016-06-14 15:44 jcfr Resolution open => fixed
2018-03-02 11:07 jcfr Status resolved => closed