I'll just change the allocation call to force C order, but I'm pretty sure
somewhere in the numpy docs it says they are always by default that order.
It would break tons if code (ours included in several places where we use
ravel) if that weren't the case.
On Jan 29, 2013 8:46 AM, "Martin Luessi" <notifications@github.com> wrote:

> In mne/epochs.py:
>
> > @@ -446,8 +458,11 @@ def _get_data_from_disk(self, out=True, verbose=None):
> >                          % (n_events - len(good_events)))
> >              if not out:
> >                  return
> > -
> > -        data = np.array(epochs)
> > +            # just take the good ones
> > +            assert len(good_events) == n_out
> > +            if n_out > 0:
> > +                # slicing won't free the space, so we resize
> > +                data.resize((n_out,) + data.shape[1:], refcheck=False)
>
> This makes me think, is there a guarantee that data.flags.C_CONTIGUOUS is
> always true or can it be platform or numpy version dependent? Maybe we
> could add an if/else and do the copy if data.flags.C_CONTIGUOUS is false,
> this solution would be guaranteed to always work.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mne-tools/mne-python/pull/410/files#r2811416>.
>
>