Hi there, I'm in no life-threatening hurry. I would like it in the next two months, but if we all agreed on what needs doing, then I could consider helping out.
Thanks Matt On 5 Oct 2011, at 16:03, Alexander Seitel wrote: > Hi Matt, > > we need to discuss this issue internally and will come back to you next > week. > > If you're in a hurry, you can use the MoveCrossToPosition() method of > QmitkStdMultiWidget to move the planes to a mm position. But > interpolation is currently not supported by default for the performed > reslicing. You could activate it by setting the reslice interpolation > property of the image to "Linear" or "Cubic". > > If you have any questions please let us know. > > Regards, > Alex > > On Wed, 2011-10-05 at 10:08 +0200, Clarkson, Matt wrote: >> Hi Alex, >> >> well, there are probably two scenarios: >> >> 1. You display the millimetre coordinates alongside the voxel ones, but keep >> the rendering aligned with voxel slices. If the user edits the millimetre >> coordinates, they are rounded to the nearest whole voxel location, thereby >> keeping the rendering the same as it is now. >> >> 2. You enable true inter-slice 3D interpolation. >> >> To support both would probably need a preference page to switch between >> behaviours, or alternatively, you assume that people who want to have their >> displayed slices correspond to exact voxel planes, will only ever edit the >> number of voxels, and people who want to work in true millimetres, and hence >> need to see arbitrary slices will work entirely in millimetres. >> >> I would actually be happy with option 1. I would have thought the rendering >> pipeline supports both? Is that right? >> >> Matt >> >> >> >> >> >> On 5 Oct 2011, at 07:11, Alexander Seitel wrote: >> >>> Hi Matt, >>> >>> basically it would be a good new feature to also show mm coordinates, >>> especially when MITK is used outside the scope of ExtApp which provides >>> this information in the StatusBar. >>> If I understand you correctly you would like to have a possibility to >>> specify the slice location in "arbitrary" mm coordinates. That would >>> mean we would have to leave the voxel raster of the image and provide >>> interpolated pixel values for displaying the chosen location. >>> Is that it what you would are missing? >>> >>> Best, >>> Alex >>> >>> On Tue, 2011-10-04 at 12:16 +0200, Clarkson, Matt wrote: >>>> Hi there everybody, >>>> >>>> currently the image navigator displays voxel coordinates. >>>> Is there any reason why millimetres could not be displayed alongside it? >>>> (a bit like FSLView). Then you can either specify a slice number, or a >>>> millimetre location? >>>> >>>> Is there any interest in this? >>>> >>>> Thanks >>>> >>>> Matt >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> All the data continuously generated in your IT infrastructure contains a >>>> definitive record of customers, application performance, security >>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>> sense of it. Business sense. IT sense. Common sense. >>>> http://p.sf.net/sfu/splunk-d2dcopy1 >>>> _______________________________________________ >>>> mitk-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/mitk-users >>> >>> >>> >> >> > > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
