Hi Mark,

thanks for your response. Yes, but I figured that that was what the -e option was for in the more recent versions of featregapply. However, looking at the code, inclusion/exclusion of filtered_func_data only kicks in for melodic runs :(

Given the file-size reasoning it would be very nice if one could explicitly request to also include the filtered_func_data, that would save the extra applywarp command :)


Thanks!
Maarten
 

On Tue, Jun 13, 2017 at 8:10 AM, Mark Jenkinson <[log in to unmask]> wrote:
Hi,

This is the expected behaviour, as resampling the filtered_func_data can lead to enormous files.
However, if you want to do it then it is easily done with the applywarp command.  Just do:
  cd blah/blah.feat
  applywarp -i filtered_func_data -r reg/standard -w reg/example_func2standard_warp -o filtered_func_data_std 

That should do what you want.

All the best,
Mark


On 12 Jun 2017, at 10:53, Maarten Mennes <[log in to unmask]> wrote:

Hello,

I'm running into the weird problem that featregapply skips filtered_func_data.nii.gz. It happy applies the registration to the present example_func, mean, and mask file, but does not do it for filtered_func_data.

Any ideas?
Maarten

--
Maarten Mennes, Ph.D.
Senior Researcher
Donders Institute for Brain, Cognition and Behaviour
Radboud University Nijmegen
Nijmegen
The Netherlands





--
Maarten Mennes, Ph.D.
Senior Researcher
Donders Institute for Brain, Cognition and Behaviour
Radboud University Nijmegen
Nijmegen
The Netherlands

Google Scholar Author Link