Dear Experts
- Win 10 64bit
- Matlab R2017b
- SPM12 6225
- DPARSF_V4.3_170105
--
According to header, image is already canonically oriented
Time elapsed 94ms
Converting T1 Images:Sub_001 OK
Removing First 10 Time Points: Sub_001 OK
Slice Timing Setup:Sub_001 OK
Initialising batch system... done.
------------------------------------------------------------------------
Running job #1
------------------------------------------------------------------------
Running 'Slice Timing'
SPM12: spm_slice_timing (v6130) 00:54:25 - 10/10/2017
========================================================================
Number of slices is... : 48
Time to Repeat (TR) is... : 3
Parameters are specified as... : slice indices
Completed : 00:54:41 - 10/10/2017
Done 'Slice Timing'
Done
Moving Slice Timing Corrected Files:Sub_001 OK
Realign Setup:Sub_001 OK
------------------------------------------------------------------------
Running job #1
------------------------------------------------------------------------
Running 'Realign: Estimate & Reslice'
SPM12: spm_realign (v6070) 00:54:42 - 10/10/2017
========================================================================
Failed 'Realign: Estimate & Reslice'
Requested 24964497409x1 (186.0GB) array exceeds maximum array size preference. Creation of arrays greater than this limit may take a long time and cause MATLAB to become unresponsive. See array size limit or preference panel for more information.
In file "C:\spm12\spm_realign.m" (v6070), function "realign_series" at line 207.
In file "C:\spm12\spm_realign.m" (v6070), function "spm_realign" at line 136.
In file "C:\spm12\config\spm_run_realign.m" (v6554), function "spm_run_realign" at line 31.
The following modules did not run:
Failed: Realign: Estimate & Reslice
Error using DPARSFA_run (line 754)
Job execution failed. The full log of this run can be found in MATLAB command window, starting with the lines (look for the
line showing the exact #job as displayed in this error message)
------------------
Running job #1
------------------
Error in DPARSFA>pushbuttonRun_Callback (line 1786)
[Error]=DPARSFA_run(handles.Cfg);
Error in gui_mainfcn (line 95)
feval(varargin{:});
Error in DPARSFA (line 30)
gui_mainfcn(gui_State, varargin{:});
Error while evaluating UIControl Callback.
Attachment | Size |
---|---|
err.jpg | 183.55 KB |
You only have 140 time points
You only have 140 time points for your subject?
Seems this can not reach 24964497409x1 (186.0GB).
Could you try another subject?
Re:You only have 140 time points
Dear Dr. Yan
Thanks for your reply.
..You only have 140 time points for your subject?
Yes
..Could you try another subject?
It worked fine with another subject A (6720 DICOM files).
However, I got an error mesagge "Requested 24964497409x1 (186.0GB) array exceeds maximum array size preference" for subject B with a single DICOM image.
--
Capture from ImageJ Show info:
Subject A:
Width: 212.00 mm (64)
Height: 212.00 mm (64)
Resolution: 0.302 pixels per mm
Pixel size: 3.31x3.31 mm
ID: -4
Coordinate origin: 0,0
Bits per pixel: 16 (unsigned)
Display range: 107 - 1537
--
Subject B:
Width: 64 pixels
Height: 64 pixels
Depth: 6720 pixels
Voxel size: 1x1x1 pixel
ID: -2
Coordinate origin: 0,0,0
Bits per pixel: 16 (unsigned)
Display range: 0 - 1637
Image: 1/6720
--
Cheers
Larry
Re:You only have 140 time points
Dear Dr. Yan
Thanks for your reply.
..You only have 140 time points for your subject?
Yes
..Could you try another subject?
It worked fine with another subject A (6720 DICOM files).
However, I got an error mesagge "Requested 24964497409x1 (186.0GB) array exceeds maximum array size preference" for subject B with a single DICOM image.
--
Capture from ImageJ Show info:
Subject A:
Width: 212.00 mm (64)
Height: 212.00 mm (64)
Resolution: 0.302 pixels per mm
Pixel size: 3.31x3.31 mm
ID: -4
Coordinate origin: 0,0
Bits per pixel: 16 (unsigned)
Display range: 107 - 1537
--
Subject B:
Width: 64 pixels
Height: 64 pixels
Depth: 6720 pixels
Voxel size: 1x1x1 pixel
ID: -2
Coordinate origin: 0,0,0
Bits per pixel: 16 (unsigned)
Display range: 0 - 1637
Image: 1/6720
--
Cheers
Larry
I think there is something
I think there is something wrong with that specific data.
Re:I think there is something
Dear Dr. Yan
>I think there is something wrong with that specific data.
Yes, it turned out to be a specific data problem.
Thanks for your feedback.
Cheers
Larry
Seems you are dealing with
Seems you are dealing with data from a 7T scanner? They are different from 3T scanner data, you may encounter some technical issues.
Re: Seems you are dealing with
This data-set contains 3T MRI/fMRI.