<div dir="ltr">I'm not familiar with the buffer, but if you can read in your data successfully, then to convert it to the structure that ft_volumewrite wants, you can get some information inside ft_datatype_volume for what are required or optional fields.<div>
<br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/24 Andrew Brooks <span dir="ltr"><<a href="mailto:andmib@gmail.com" target="_blank">andmib@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Thanks Johanna. Ft_read_mri only pulls from a file, correct? I'm trying to pull a single volume from the buffer using ft_read_data, and then write it out to a nifti file using ft_volumewrite, but ft_read_data does not output the volume in a structure that ft_volumewrite wants.</div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 24, 2013 at 4:21 AM, Johanna Zumer <span dir="ltr"><<a href="mailto:johanna.zumer@donders.ru.nl" target="_blank">johanna.zumer@donders.ru.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Dear Andrew,<div><br></div><div>To read EPI (MRI) data, you should use ft_read_mri instead. Then hopefully the format will match what ft_volumewrite wants.</div>
<div><br></div><div>Cheers,</div><div>
Johanna</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/23 Andrew Brooks <span dir="ltr"><<a href="mailto:andmib@gmail.com" target="_blank">andmib@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
<div dir="ltr">Hello all,<div><br></div><div>I am new to FieldTrip, so this is a very basic question I was hoping someone might know an answer to.</div><div><br></div><div>I am using ft_read_data to read the first EPI volume after dummy scans are thrown out. I want to write this volume to a .nii file to my disk. For some reason, I am unable to figure out the correct structure that ft_volumewrite wants. Using the output from ft_read_data ('dat') does not seem to work. Does anybody have any suggestions?</div>
<div><br></div><div>[ For a longer explanation of exactly what I am aiming to do, in case you have any suggestions: I have ROI that is defined in Talairach space. This is the ROI I would like to pull my real-time data from for each subject in my study. To do this, I plan to register a talairach template brain to individual subject-space, and then apply that transformation to my ROI so that it is in subject space. I was going to simply write out the subject's EPI to an .nii file, and then run SPM's co-registration step which allows for a 'child dataset' to be set (my ROI), with the source file being the template, and the reference being the individual ROI].</div>
<div><br></div><div>Thanks</div><span><font color="#888888"><div>Andrew</div></font></span></div>
<br></div></div>_______________________________________________<br>
fieldtrip mailing list<br>
<a href="mailto:fieldtrip@donders.ru.nl" target="_blank">fieldtrip@donders.ru.nl</a><br>
<a href="http://mailman.science.ru.nl/mailman/listinfo/fieldtrip" target="_blank">http://mailman.science.ru.nl/mailman/listinfo/fieldtrip</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
fieldtrip mailing list<br>
<a href="mailto:fieldtrip@donders.ru.nl" target="_blank">fieldtrip@donders.ru.nl</a><br>
<a href="http://mailman.science.ru.nl/mailman/listinfo/fieldtrip" target="_blank">http://mailman.science.ru.nl/mailman/listinfo/fieldtrip</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
fieldtrip mailing list<br>
<a href="mailto:fieldtrip@donders.ru.nl">fieldtrip@donders.ru.nl</a><br>
<a href="http://mailman.science.ru.nl/mailman/listinfo/fieldtrip" target="_blank">http://mailman.science.ru.nl/mailman/listinfo/fieldtrip</a><br></blockquote></div><br></div>