Back to the main page.
Bug 1727 - ft_volumereslice chunks off top of the brain
Status | CLOSED FIXED |
Reported | 2012-09-20 11:17:00 +0200 |
Modified | 2019-08-10 11:56:30 +0200 |
Product: | FieldTrip |
Component: | core |
Version: | unspecified |
Hardware: | PC |
Operating System: | Windows |
Importance: | P3 normal |
Assigned to: | Arjen Stolk |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Arjen Stolk - 2012-09-20 11:17:34 +0200
The brain scan is slightly rotated prior to reslicing, consequentially changing x, y, and z ranges of the image. When running the function with default settings, this may cause the reslicing not to work properly in some cases (range dependent): for example see attachment.
Arjen Stolk - 2012-09-20 11:18:05 +0200
Created attachment 310 top of the head missing
Arjen Stolk - 2012-09-20 14:31:30 +0200
Created attachment 311 correctly resliced
Arjen Stolk - 2012-09-20 14:31:52 +0200
Created attachment 312 incorrectly reslice - prior to the fix
Jan-Mathijs Schoffelen - 2012-09-20 14:33:28 +0200
now it chops of a chunkje of the cerebellum!
Arjen Stolk - 2012-09-20 14:34:38 +0200
The order of actions by ft_volumereslice is now; 1) use the ranges (if specified) 2) otherwise use the dim (if specified) 3) otherwise use default bounding box (25 mm^3)
Arjen Stolk - 2012-09-20 14:35:26 +0200
True, this is a hacked version of an mri scan that originally 256 by 256 by 256. I've tried to see how ft_volumereslice would deal with it if i had changed its dim to 256 by 256 by 176.