<div dir="ltr">Hi Matti,<div><br></div><div>Thanks for the heads-up. In this case, how can I analyse a large file? Should I split the raw file into multiple raw files, and then somehow feed all these raw files into mne_process_raw when I want to create -ave.fif and -cov.fif files?</div>
<div><br></div><div>Thank you,</div><div>Steve</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><br><br></div>Stephen Politzer-Ahles<br>New York University, Abu Dhabi<br>Neuroscience of Language Lab<br>
<a href="http://www.nyu.edu/projects/politzer-ahles/" target="_blank">http://www.nyu.edu/projects/politzer-ahles/</a><br></div></div>
<br><br><div class="gmail_quote">On Mon, Nov 25, 2013 at 1:33 PM, Matti Hamalainen <span dir="ltr"><<a href="mailto:msh@nmr.mgh.harvard.edu" target="_blank">msh@nmr.mgh.harvard.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi Steve,<br>
<br>
Just FYI, MNE-C does not do the splitting in mne_kit2fiff either.<br>
<span class="HOEnZb"><font color="#888888"><br>
- Matti<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Nov 25, 2013, at 3:39 AM, Alexandre Gramfort <<a href="mailto:alexandre.gramfort@telecom-paristech.fr">alexandre.gramfort@telecom-paristech.fr</a>> wrote:<br>
<br>
> hi Steve,<br>
><br>
> looks like you've hit a problem in our python fiff writing code that does not<br>
> splits .fif files to avoid large files.<br>
><br>
> We'll look into it asap<br>
><br>
> Thanks for the report.<br>
><br>
> Best,<br>
> Alex<br>
><br>
><br>
> On Mon, Nov 25, 2013 at 9:34 AM, Stephen Politzer-Ahles <<a href="mailto:spa268@nyu.edu">spa268@nyu.edu</a>> wrote:<br>
>> Hi Alexandre,<br>
>><br>
>> It started as Yokogawa .con data, I wrote it to fif using mne.gui.kit2fiff<br>
>> in the mne-python tools.<br>
>><br>
>> Best,<br>
>> Steve<br>
>><br>
>><br>
>><br>
>> Stephen Politzer-Ahles<br>
>> New York University, Abu Dhabi<br>
>> Neuroscience of Language Lab<br>
>> <a href="http://www.nyu.edu/projects/politzer-ahles/" target="_blank">http://www.nyu.edu/projects/politzer-ahles/</a><br>
>><br>
>><br>
>> On Mon, Nov 25, 2013 at 12:32 PM, Alexandre Gramfort<br>
>> <<a href="mailto:alexandre.gramfort@telecom-paristech.fr">alexandre.gramfort@telecom-paristech.fr</a>> wrote:<br>
>>><br>
>>> Steve,<br>
>>><br>
>>> how did you write this file?<br>
>>><br>
>>> standard .fif file should not exceed 2GB.<br>
>>><br>
>>> Alex<br>
>>><br>
>>><br>
>>> On Mon, Nov 25, 2013 at 7:34 AM, Stephen Politzer-Ahles <<a href="mailto:spa268@nyu.edu">spa268@nyu.edu</a>><br>
>>> wrote:<br>
>>>> Hi Eric,<br>
>>>><br>
>>>> Thanks, I will keep trying various things out in the meantime. I was<br>
>>>> also<br>
>>>> concerned about file size limits, but it seems weird that other<br>
>>>> functions<br>
>>>> like mne_process_raw still work on my big files.<br>
>>>><br>
>>>> If I don't find a solution, is it possible instead to just run<br>
>>>> mne_mark_bad_channels on the averaged data (and make sure to use the<br>
>>>> averaged, rather than the raw, as the --meas file in later steps of the<br>
>>>> pipeline)?<br>
>>>><br>
>>>> Best,<br>
>>>> Steve<br>
>>>><br>
>>>><br>
>>>><br>
>>>> Stephen Politzer-Ahles<br>
>>>> New York University, Abu Dhabi<br>
>>>> Neuroscience of Language Lab<br>
>>>> <a href="http://www.nyu.edu/projects/politzer-ahles/" target="_blank">http://www.nyu.edu/projects/politzer-ahles/</a><br>
>>>><br>
>>>><br>
>>>> On Mon, Nov 25, 2013 at 5:20 AM, Eric Larson <<a href="mailto:larson.eric.d@gmail.com">larson.eric.d@gmail.com</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Hey Steve,<br>
>>>>><br>
>>>>> It is possible that this has to do with file locations being stored<br>
>>>>> using<br>
>>>>> 32-bit integers. I thought FIFF had an effective file-size limit of 2GB<br>
>>>>> for<br>
>>>>> that reason (using 32-bit signed integers would make this the limit),<br>
>>>>> but<br>
>>>>> I'm not 100% sure. If nobody beats me to a more definitive answer and<br>
>>>>> you<br>
>>>>> can't find anything about this issue yourself by tomorrow or Tuesday, I<br>
>>>>> can<br>
>>>>> look into it more then.<br>
>>>>><br>
>>>>> Cheers,<br>
>>>>> Eric<br>
>>>>><br>
>>>>><br>
>>>>> On Sun, Nov 24, 2013 at 12:33 PM, Stephen Politzer-Ahles<br>
>>>>> <<a href="mailto:spa268@nyu.edu">spa268@nyu.edu</a>><br>
>>>>> wrote:<br>
>>>>>><br>
>>>>>> To whom it may concern:<br>
>>>>>><br>
>>>>>> When I try to run mne_mark_bad_channels in tcsh on a raw .fif file<br>
>>>>>> (about<br>
>>>>>> 3.25 GB), I get an error like the following:<br>
>>>>>><br>
>>>>>> "/Volumes/data/....../A0007.fif ... [failed] fseek : Value too large<br>
>>>>>> to<br>
>>>>>> be stored in data type"<br>
>>>>>><br>
>>>>>> As far as I can tell this seems to be some kind of Unix error, not<br>
>>>>>> something specific to MNE...but this happens regardless of which drive<br>
>>>>>> I<br>
>>>>>> happen to be trying to modify data on, and also other functions that<br>
>>>>>> also<br>
>>>>>> need to open the data (such as mne_process_raw) work fine, so I don't<br>
>>>>>> think<br>
>>>>>> it's necessarily a permission or filesystem issue. Does anyone have<br>
>>>>>> any idea<br>
>>>>>> what might be causing this?<br>
>>>>>><br>
>>>>>> Thanks for your input,<br>
>>>>>> Steve<br>
>>>>>><br>
>>>>>><br>
>>>>>> Stephen Politzer-Ahles<br>
>>>>>> New York University, Abu Dhabi<br>
>>>>>> Neuroscience of Language Lab<br>
>>>>>> <a href="http://www.nyu.edu/projects/politzer-ahles/" target="_blank">http://www.nyu.edu/projects/politzer-ahles/</a><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Mne_analysis mailing list<br>
>>>>>> <a href="mailto:Mne_analysis@nmr.mgh.harvard.edu">Mne_analysis@nmr.mgh.harvard.edu</a><br>
>>>>>> <a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> The information in this e-mail is intended only for the person to whom<br>
>>>>>> it<br>
>>>>>> is<br>
>>>>>> addressed. If you believe this e-mail was sent to you in error and the<br>
>>>>>> e-mail<br>
>>>>>> contains patient information, please contact the Partners Compliance<br>
>>>>>> HelpLine at<br>
>>>>>> <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you<br>
>>>>>> in<br>
>>>>>> error<br>
>>>>>> but does not contain patient information, please contact the sender<br>
>>>>>> and<br>
>>>>>> properly<br>
>>>>>> dispose of the e-mail.<br>
>>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Mne_analysis mailing list<br>
>>>> <a href="mailto:Mne_analysis@nmr.mgh.harvard.edu">Mne_analysis@nmr.mgh.harvard.edu</a><br>
>>>> <a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
>>>><br>
>>>><br>
>>>> The information in this e-mail is intended only for the person to whom<br>
>>>> it is<br>
>>>> addressed. If you believe this e-mail was sent to you in error and the<br>
>>>> e-mail<br>
>>>> contains patient information, please contact the Partners Compliance<br>
>>>> HelpLine at<br>
>>>> <a href="http://www.partners.org/complianceline" target="_blank">http://www.partners.org/complianceline</a> . If the e-mail was sent to you<br>
>>>> in<br>
>>>> error<br>
>>>> but does not contain patient information, please contact the sender and<br>
>>>> properly<br>
>>>> dispose of the e-mail.<br>
>>>><br>
>><br>
>><br>
> _______________________________________________<br>
> Mne_analysis mailing list<br>
> <a href="mailto:Mne_analysis@nmr.mgh.harvard.edu">Mne_analysis@nmr.mgh.harvard.edu</a><br>
> <a href="https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis" target="_blank">https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis</a><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div>