JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  September 2009

FSL September 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: FLAME without feat registration...

From:

Daniel Schwartz <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Wed, 9 Sep 2009 09:09:53 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (226 lines)

The .gfeat directory (and its subdirectories) structure is required as input to fmripower (http://www.fmripower.org/). I'd like to know what my power is for a particular type of analysis stream, which doesn't use the FEAT registration. So, I guess I'll choose the latter that you've listed below; mimic the structure. Ouch. Oh well, off I go!

Thank you again for your help
-Daniel
________________________________________
From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf Of Steve Smith [[log in to unmask]]
Sent: Tuesday, September 08, 2009 11:48 PM
To: [log in to unmask]
Subject: Re: [FSL] FLAME without feat registration...

Hi, I don't understand why you want to create the .gfeat directory
structure if you already have all the data in standard space. Anyway,

On 8 Sep 2009, at 16:21, Daniel Schwartz wrote:

> So, if I need the .gfeat directory structure, I have two choices, I
> think:
>
> 1) I need to manually create the .gfeat/.cope1 directory structure
> with the output of flameo (change ./stats in the exmaple you
> mentioned below)
>
> -or-
>
> 2) I have to do single subject registrations in FSL. It seems
> strange that this needs to happen to get the standard directory
> structure. Is there a way to run the FEAT scripts WITHOUT doing
> within subject registrations?

Sure - you can turn off registration in the GUI - but I can't see why
you would want to do this.

As far as I can see, your two choices that make the most sense are
either to run FEAT fully from scratch using the GUI, or make flameo
run from the command line without running the full FEAT analyses or
generating the FEAT output directory structure. Anything in between
will be complicated as you will need to know exactly how to mimic the
FEAT output structure, which will be more work than just running FEAT.

Cheers.




>
> Thanks
> -Daniel
> ________________________________________
> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf
> Of Steve Smith [[log in to unmask]]
> Sent: Friday, September 04, 2009 10:41 PM
> To: [log in to unmask]
> Subject: Re: [FSL] FLAME without feat registration...
>
> Hi - no, the FEAT scripts generate the .gfeat output directory -
> flameo outputs into a directory determined by the --ld option. An
> example call is:
>
> flameo --cope=cope4D --vc=varcope4D --mask=mask3D --ld=stats --
> dm=design.mat --cs=design.grp \
>                  --tc=design.con --runmode=flame12 --nj=10000 --
> bi=500 --se=1 --fm --zlt=2.25 --zut=2.65
>
> Cheers
>
>
> On 4 Sep 2009, at 21:28, Daniel Schwartz wrote:
>
>> Well, I tried this, using:
>>
>>> fslmerge -t COPE1 *.feat/cope1.nii.gz
>>
>> to concatenate the cope1 files for each subject into one file,
>>
>> then
>>
>>> flameo --cope="COPE1.nii.gz" --mask="mask.nii.gz" --dm=GRP.mat --
>>> tc=GRP.con --cs=GRP.grp --runmode=flame1
>>
>> and I get a logfile, with results, but no .gfeat directory.
>> Shouldn't this be the output of 'flameo' along with a .gfeat/.cope1
>> directory?
>>
>>
>> Thankyou for your prompt replies!
>> -Daniel
>>
>>
>> ________________________________________
>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf
>> Of Daniel Schwartz [[log in to unmask]]
>> Sent: Friday, September 04, 2009 10:05 AM
>> To: [log in to unmask]
>> Subject: Re: [FSL] FLAME without feat registration...
>>
>> More specifically, I guess, ( I think I understand the usage of all
>> the rest of the flameo options), what is the "--cope" cope regressor
>> datafile? A 4D file of all the regression coefficients for that
>> particular condition concatenated over all runs/subjects?
>>
>> -Daniel
>> ________________________________________
>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf
>> Of Daniel Schwartz [[log in to unmask]]
>> Sent: Friday, September 04, 2009 9:18 AM
>> To: [log in to unmask]
>> Subject: Re: [FSL] FLAME without feat registration...
>>
>> Hahahaha... I apologize, I had thought that the 'flame' command line
>> program had vanished... but didn't think it might've been renamed.
>> Why isn't in on the feat tools page? Anyway, I was trying to run
>> FLAME from the GUI, and got the error message that "it seems some
>> reg's hadn't been done". But since I have you on the line, I might
>> as well ask how to do my ridiculously easy analysis in 'flameo'...
>>
>> I have 24 subjects, 12 in one group, 12 in another, 2 runs for each
>> subject (separate .feat directories), two conditions (copes?) for
>> each run, and I just want to know the group contrast for the
>> regression coefficient of each condition (again, for input to
>> fmripower, which requires a .gfeat type of setup). So how should I
>> run it from $>?
>>
>> Thankyou SO MUCH for your help...
>> ________________________________________
>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf
>> Of Steve Smith [[log in to unmask]]
>> Sent: Friday, September 04, 2009 9:09 AM
>> To: [log in to unmask]
>> Subject: Re: [FSL] FLAME without feat registration...
>>
>> Ah - ok, so you don't need the FEAT scripts at all - just the correct
>> call to 'flameo' on the command line.   What command are you trying
>> and what's the error message?
>> Cheers.
>>
>>
>> On 4 Sep 2009, at 17:02, Daniel Schwartz wrote:
>>
>>> I've done ALL my preprocessing with AFNI, then just converted to
>>> NIFTI and ran the single subject GLM for each subject with all
>>> preprocessing turned off (including reg) in feat. There ARE
>>> no .feat/
>>> reg* directories...
>>>
>>> How can I fake them? Do I need to, or is there a way to run the
>>> second level without registration info?
>>> -Daniel
>>> ________________________________________
>>> From: FSL - FMRIB's Software Library [[log in to unmask]] On Behalf
>>> Of Steve Smith [[log in to unmask]]
>>> Sent: Friday, September 04, 2009 9:00 AM
>>> To: [log in to unmask]
>>> Subject: Re: [FSL] FLAME without feat registration...
>>>
>>> Hi - if you've overwritten the lower-level FEAT registration
>>> information correctly (or udpated the .feat/reg_standard directories
>>> correctly) using your custom registrations, then the higher-level
>>> FEAT
>>> (using FLAME etc) should run fine.....at what stage are you
>>> inserting
>>> your custom registrations?
>>>
>>> Cheers.
>>>
>>>
>>> On 4 Sep 2009, at 16:57, Daniel Schwartz wrote:
>>>
>>>> How do I do it? I'm trying to use fmripower for a power analysis,
>>>> I've run
>>>> feat (after my own registration script, and with all registration
>>>> turned
>>>> off) and now want to run FLAME. I get the error message,
>>>> though... I
>>>> noticed
>>>> that there is a solution from 2002, about using the flame command
>>>> line
>>>> program... but it isn't in more recent distros? (Maybe I'm wrong
>>>> about
>>>> this.) Help!
>>>>
>>>> -Daniel
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------------
>>> 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
>>> ---------------------------------------------------------------------------
>>>
>>
>>
>> ---------------------------------------------------------------------------
>> 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
>> ---------------------------------------------------------------------------
>>
>
>
> ---------------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------------
>


---------------------------------------------------------------------------
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
---------------------------------------------------------------------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager