2011-07-28 09:54
|
Screen Shot 2011-07-28 at 1.21.38 PM.png (503,559 bytes) |
 |
I believe that is a limitation at the vtk volume rendering level - we should probably detect this case and put up a warning in the volume rendering GUI. |
 |
Cropping is not updated when ROI is translated. I tested this same behavior in Slicer3 -- cropping+rotation is also not working, but translation is working fine. |
|
|
Steve, I don't think this is a limitation at the volume rendering level. I placed ROI under one transform, and Volume under another. If I rotate ROI, volume rendering is not updated, but if I rotate the volume -- it is. Could it be that the ROI normals are not recalculated on ROI rotation in volume rendering? I also tested volume rendeirng in Slicer4 with oblique volumes. ROI oriented with RAS axes crops oblique volume as expected. This is apparently a bug in Slicer3 as well. See screenshots attached. |
|
2011-08-03 08:38
|
Screen shot 2011-08-03 at 12.07.25 PM.png (12,365 bytes) |
|
2011-08-03 08:38
|
Screen shot 2011-08-03 at 12.07.15 PM.png (263,340 bytes) |
|
2011-08-03 08:38
|
Screen shot 2011-08-03 at 12.06.52 PM.png (213,433 bytes) |
|
|
Update: we discussed this on a recent tcon and determined that the cropping planes for volume rendering are specified as extents in world coordinates so we can't apply rotated ROIs for them. Andrey will work around this in the interface to the ChangeTracker. |
 |
Why is this labeled resolved? It is not |
|
|
I am not sure why this is assigned to me. I do not know how to resolve it. Is this a general request, or a specific ChangeTracker-related issue? If this is ChangeTracker-specific request, this should be in a separate bug. This current bug report is about a general functionality missing in volume rendering. |
|
|
I guess Ron got it confused. It was not marked "resolved", it was marked "not fixable" :) |
|
|
what do we do about this bug? |
- Anonymous
