Dear Takashi,
try the attached function, that hopefully solves the problem.
Best,
Christian
On Wed, 22 May 2019 19:58:28 +0900, r-wakalang hiroi <[log in to unmask]> wrote:
>Dear CAT12 users,
>
>I just started using CAT12 and for practice, I'm now trying to run the
>module "Segment longitudinal data" for 6 participants with 2 time-points
>(12 T1-images in total). I did not change default parameter settings except
>for "Data".
>
>my environment:
>MATLAB R2016b
>SPM12(r7487)
>CAT12.6(r1450)
>
>(1)
>At first, this processing continued without any problem, but at the end of
>the processing, a pop-up window appeared saying "An error occurred during
>job execution..." and progress bar stopped at 67%. And I got a following
>error message in the Matlab command window.
>
>==============================================================================================
>------------------------------------------------------------------------
>22-May-2019 12:25:59 - Running job #2
>------------------------------------------------------------------------
>22-May-2019 12:25:59 - Running 'Segment longitudinal data'
>Running job 1 (with datafield 1):
>
>Check log_cat_long_multi_run_20190522_122559_01.txt for logging information
>(PID: 11125).
>_______________________________________________________________
>Running job 2 (with datafield 1):
>
>Check log_cat_long_multi_run_20190522_122559_02.txt for logging information
>(PID: 11177).
>_______________________________________________________________
>Running job 3 (with datafield 1):
>
>Check log_cat_long_multi_run_20190522_122559_03.txt for logging information
>(PID: 11229).
>_______________________________________________________________
>Running job 4 (with datafield 1):
>
>Check log_cat_long_multi_run_20190522_122559_04.txt for logging information
>(PID: 11281).
>_______________________________________________________________
>
>Started 4 jobs with the following PIDs:
> 1) 2 subjects (PID: 11125): log_cat_long_multi_run_20190522_122559_01.txt
> 2) 2 subjects (PID: 11177): log_cat_long_multi_run_20190522_122559_02.txt
> 3) 1 subjects (PID: 11229): log_cat_long_multi_run_20190522_122559_03.txt
> 4) 1 subjects (PID: 11281): log_cat_long_multi_run_20190522_122559_04.txt
>
>Killing of this process will not kill the parallel processes!
>_______________________________________________________________
>Process volumes (see catlog files for details!):
> 1/6 (job 2: 1/2): ..tice/sample_data/Data_NIFTI/1stPre/3/T1
> 2/6 (job 1: 1/2): ..tice/sample_data/Data_NIFTI/1stPre/4/T1
> 3/6 (job 2: 2/2): ..tice/sample_data/Data_NIFTI/1stPre/3/T1
> 4/6 (job 1: 2/2): ..tice/sample_data/Data_NIFTI/1stPre/4/T1
>22-May-2019 13:26:26 - Failed 'Segment longitudinal data'
>エラー: isstruct (<- I means "Error: isstruct".)
>入力引数が多すぎます。 (<- It means "too many input arguments".)
>In file "/Users/hippocampus/SPM/spm12/toolbox/cat12/cat_parallelize.m"
>(v1449), function "cat_parallelize" at line 381.
>In file "/Users/hippocampus/SPM/spm12/toolbox/cat12/cat_long_multi_run.m"
>(v1435), function "cat_long_multi_run" at line 62.
>
>The following modules did not run:
>Failed: Segment longitudinal data
>==============================================================================================
>
>Because the above error message was similar (but slightly different) to
>https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1904&L=SPM&P=R81580, I
>tried the attached function from
>https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1905&L=SPM&P=R61490. But
>the result was the same (i.e., progress bar stopped at 67% and the same
>error message appeared).
>
>Although the error message appeared, mwp1r*.nii and mwp2r*.nii were
>successfully created in subfolder "mri" and any error or warning messages
>did not appear in the "log_cat_long_multi_run_hoge.txt" files, so I thought
>"segment data" itself successfully finished (and some other processing like
>terminating process failed). Is this correct?
>
>(2)
>As the above error message seemed to be related to "Split job into separate
>processes", I changed its value from 4 (defaults value in my environment)
>to 0. This time, the error message disappeared.
>
>So, setting "Split job into separate processes" to 0 seems to be a
>workaround to this error. Is this correct?
>
>
>It would be appreciated if you could answer my question.
>
>Thanks in advance.
>
>Takashi
>
|