 |
 |
Hi Mark, We are still running into the issue even after removing special characters. We loaded a design from a working analysis, changed the zstat threshold and output name. This gave us the same error as in http://pastebin.com/9akqACE2 - "ERROR: Could not open image thresh_zstat1". This is really bizarre and you're right there should be no reason the analysis fails by only changing the threshold. Are there any possible things we might be able to check that could be causing the issue? We are at a loss as to what the problem is. Thanks, Daniel On Wed, Jan 8, 2014 at 3:54 AM, Mark Jenkinson <[log in to unmask] > wrote: > Hi, > > There is no reason that analyses should fail (i.e. crash) by changing > the threshold. You could get zero significant activations, but that is not > what we would consider to be a fail. > > If you did have special characters then that could easily cause things > to behave erratically, so fix that first and see if that is the cause. > > All the best, > Mark > > > On 6 Jan 2014, at 17:01, Daniel Cole <[log in to unmask]> wrote: > > Hi, > Thank you very much for responding. I am trying the analysis again with > the directory path having no special characters. > > However, I'm pretty confident this is not the problem in our case. We > have run multiple seeds using the same directory path and obtained results > and finalized reports. Our problem is that we get errors having run one > seed at 1.9 threshold and, using the same design file, changed the > threshold to 2.3 and had the analysis fail. All things in the design were > the same excluding the z-threshold and the output name (name changed from > 1.9 to 2.3). > > Is there any reason that an analysis might fail after only changing the > z-threshold? Maybe the special characters cause FEAT to act somewhat > erratically? I will try without the use of any special characters but > perhaps there is a different issue. > > Thank you, > Daniel > > > > On Sat, Jan 4, 2014 at 2:32 AM, Stephen Smith <[log in to unmask]>wrote: > >> Hi - it's possible that this is failing because you have illegal >> characters in your pathname? >> In general UNIX scripts often cannot handle spaces, %, etc. >> Cheers, Steve. >> >> >> >> On 3 Jan 2014, at 17:21, Daniel Cole <[log in to unmask]> wrote: >> >> Hello FSLers, >> >> I'm running into an issue when running a higher-level analysis with >> seed timeseries lower-level FEAT directories as inputs. I've gotten the >> analysis to work for many of the seed regions but some are failing after >> the only change being to the inputs directories and in one case only >> changing the z-threshold. Here is a link to the report_log - >> http://pastebin.com/9akqACE2 . >> >> I've tried checking the lower-level FEAT inputs but they seem to have >> ran fine and have worked in other analyses. Any help would be greatly >> appreciated, this seems like a very odd issue since it works for some of >> the seeds. I've attached two sample design files, one that worked and one >> that does not. >> >> Many thanks, >> Daniel >> >> -- >> Daniel Cole >> University of Rochester >> Rochester Center for Brain Imaging >> [log in to unmask] >> <Archive.zip> >> >> >> >> >> --------------------------------------------------------------------------- >> Stephen M. Smith, Professor of Biomedical Engineering >> Associate Director, Oxford University FMRIB Centre >> >> FMRIB, JR Hospital, Headington, Oxford OX3 9DU, UK >> +44 (0) 1865 222726 (fax 222717) >> [log in to unmask] http://www.fmrib.ox.ac.uk/~steve >> >> --------------------------------------------------------------------------- >> >> Stop the cultural destruction of Tibet <http://smithinks.net/> >> >> >> >> >> > > > -- > Daniel Cole > University of Rochester > Rochester Center for Brain Imaging > [log in to unmask] > > > -- Daniel Cole University of Rochester Rochester Center for Brain Imaging [log in to unmask]