<div dir="ltr"><div><div><div>Hi Eric,<br><br></div>Thanks, I will keep trying various things out in the meantime. I was also concerned about file size limits, but it seems weird that other functions like mne_process_raw still work on my big files.<br>
<br></div>If I don't find a solution, is it possible instead to just run mne_mark_bad_channels on the averaged data (and make sure to use the averaged, rather than the raw, as the --meas file in later steps of the pipeline)?<br>
<br>Best,<br></div>Steve<br></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 5:20 AM, Eric Larson <span dir="ltr"><<a href="mailto:larson.eric.d@gmail.com" target="_blank">larson.eric.d@gmail.com</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">Hey Steve,<div><br></div><div>It is possible that this has to do with file locations being stored using 32-bit integers. I thought FIFF had an effective file-size limit of 2GB for that reason (using 32-bit signed integers would make this the limit), but I'm not 100% sure. If nobody beats me to a more definitive answer and you can't find anything about this issue yourself by tomorrow or Tuesday, I can look into it more then.</div>
<div><br></div><div>Cheers,</div><div>Eric</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Sun, Nov 24, 2013 at 12:33 PM, Stephen Politzer-Ahles <span dir="ltr"><<a href="mailto:spa268@nyu.edu" target="_blank">spa268@nyu.edu</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">To whom it may concern:<div><br></div><div>When I try to run mne_mark_bad_channels in tcsh on a raw .fif file (about 3.25 GB), I get an error like the following:</div>
<div><br></div><div>"/Volumes/data/....../A0007.fif ... [failed] fseek : Value too large to be stored in data type"</div>
<div><br></div><div>As far as I can tell this seems to be some kind of Unix error, not something specific to MNE...but this happens regardless of which drive I happen to be trying to modify data on, and also other functions that also need to open the data (such as mne_process_raw) work fine, so I don't think it's necessarily a permission or filesystem issue. Does anyone have any idea what might be causing this?</div>
<div><br></div><div>Thanks for your input,</div><div>Steve<span><font color="#888888"><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>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
Mne_analysis mailing list<br>
<a href="mailto:Mne_analysis@nmr.mgh.harvard.edu" target="_blank">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 it is<br>
addressed. If you believe this e-mail was sent to you in error and the e-mail<br>
contains patient information, please contact the Partners Compliance 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 in error<br>
but does not contain patient information, please contact the sender and properly<br>
dispose of the e-mail.<br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>