Error In Size-match Along Non-concatenated Dimension
Previous | Next | Last ] By Author: [ First | Previous | Next | Last ] Font: Proportional Font LISTSERV Archives FSL Home FSL January 2010 Options Subscribe or Unsubscribe Log In Get Password Subject: ERROR: Higher-Level FEAT Report From: jonavil1015 <[log in to unmask]> Reply-To:FSL - FMRIB's Software Library <[log in to unmask]> Date:Thu, 21 Jan 2010 09:36:02 +0000 Content-Type:text/plain Parts/Attachments: text/plain (165 lines) Dear FSL Experts, I am currently running FSL 4.1.4 and I'm running a higher-level group analysis on 16 subjects (8 per group). I get the following error message in the log [under Higher-level input files preparation]: "Error in size-match along non-concatenated dimension." The dimensions for the mask.nii.gz file located in the reg/standard folder was a different size when I compared two individual subjects. For this reason, I reran the feat level 1 analyses for a subset of the sample (3 subjects per group) from scratch and reran the higher-level analyses with these 6 subjects to see if I would replicate the error, which was indeed the case. Any information about what may be causing this problem would be greatly appreciated. Additional error output from the log has been pasted below. `````````````````````````````````````````````````````````````````````` Error in size-match along non-concatenated dimension mkdir -p inputreg /u/home9/FMRI/apps//fsl/current//bin/fslmaths ../mask -mul 6 -Tmean masksum -odt short ** ERROR (nifti_image_read): failed to find header file for '../mask' ** ERROR: nifti_image_open(../mask): bad header info Error: failed to open file ../mask Cannot open volume ../mask for reading! /u/home9/FMRI/apps//fsl/current//bin/fslmaths masksum -thr 6 -add masksum masksum ** ERROR (nifti_image_read): failed to find header file for 'masksum' ** ERROR: nifti_image_open(masksum): bad header info Error: failed to open file masksum Cannot open volume masksum for reading! /u/home9/FMRI/apps//fsl/current//bin/overlay 0 0 -c ../bg_image -a masksum 0.9 12 masksum_overlay ** ERROR (nifti_image_read): failed to find header file for 'masksum' ** ERROR: nifti_image_open(masksum): bad header info Error: failed to open file masksum ERROR: Could not open image masksum Image Exception : #22 :: Failed to read volume masksum terminate called after throwing an instance of 'RBD_COMMON::BaseException' /u/home9/FMRI/apps//fsl/current//bin/slicer masksum_overlay -S 2 750 masksum_overlay.png ** ERROR (nifti_image_read): failed to find header file for 'masksum_overlay' ** ERROR: nifti_image_open(masksum_overlay): bad header info Error: failed to open file masksum_overlay ERROR: Could not open
Previous | Next | Last ] By Author: [ First | Previous | Next | Last ] Font: Proportional Font LISTSERV Archives FSL Home FSL May 2015 Options Subscribe or Unsubscribe Log In Get Password Subject: Re: randomise and inconsistent orientations across runs using fslmaths From: "Anderson M. Winkler" <[log in to unmask]> Reply-To:FSL https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=FSL;57b6ff1a.1001 - FMRIB's Software Library <[log in to unmask]> Date:Thu, 28 May 2015 07:09:32 +0100 Content-Type:multipart/alternative Parts/Attachments: text/plain (207 lines) , text/html (167 lines) Sorry, your browser doesn't support iframes. View Message Top of Message | Previous Page | Permalink JiscMail Tools Files Area | help RSS https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=fsl;b49193d6.1505 Feeds and Sharing RSS 1.0 feed RSS 2.0 feed Atom feed Search Archives Advanced Options Archives October 2016September 2016August 2016July 2016June 2016May 2016April 2016March 2016February 2016January 2016December 2015November 2015October 2015September 2015August 2015July 2015June 2015May 2015April 2015March 2015February 2015January 2015December 2014November 2014October 2014September 2014August 2014July 2014June 2014May 2014April 2014March 2014February 2014January 2014December 2013November 2013October 2013September 2013August 2013July 2013June 2013May 2013April 2013March 2013February 2013January 2013December 2012November 2012October 2012September 2012August 2012July 2012June 2012May 2012April 2012March 2012February 2012January 2012December 2011November 2011October 2011September 2011August 2011July 2011June 2011May 2011April 2011March 2011February 2011January 2011December 2010November 2010October 2010September 2010August 2010July 2010June 2010May 2010April 2010March 2010February 2010January 2010December 2009November 2009October 2009September 2009August 2009July 2009June 2009May 2009April 2009March 2009February 2009January 2009December 2008November 2008October 2008September 2008August 2008July 2008June 2008May 2008April 2008March 2008February 2008January 2008December 2007November 2007October 2007September 2007August 2007July 2007June 2007May 2007April 2007March 2007February 2007January 2007200620052004200320022001 WWW.JISCMAIL.AC.UK
] [ subject ] [ author ] Search archives: What a coincide! Our teams have both chosen the same release cycle strategy :P https://mail.nmr.mgh.harvard.edu/pipermail//freesurfer/2012-July/025043.html I ran bedpostx_postproc and I've got so many errors that makes me think the problem is before this step (see output in attached n1-bedpostx-postproc.txt). So, I ran again bedpostx on the dmri directory, which the first run *seemed* to finish and didn't throw any error (I attached the output in the first email). This run did finish, error in and it did throw errors (full output in n2-bedpostx-dmri.txt): *[...]* *slice 63 has already been processed wc: /volatile/tracula/results/Diff001/dmri.bedpostX/commands.txt: No such file or directory Queuing post processing stage 64 slices processed For some reason the bedpostX process DOES NOT appear to have successfully completed. Please examine your results carefully. kill: 276: No such process* Then I started wondering error in size-match whether I do have the right data to actually run bedpostx, so I run the script that checks that: bedpostx_datacheck, the output (n3-bedpostx-datacheck.txt) doesn't show any signs of errors so I would like to assume everything is ok with the input data... Any idea? Thanks, once again. Sergio. 2012/7/27 Anastasia Yendiki