welcome to the hell of irrational bti offsets! also look at related brainstorm fieldtrip sources to see more traces of battle. that's actually one reason i became reluctant of using the constants.py i wrote myself. this is not a fiff file ;-(

On 30.01.2013, at 00:35, Eric89GXL <notifications@github.com> wrote:

> In mne/fiff/bti/raw.py:
> 
> > +        _correct_offset(fid)  # after each reading
> > +
> > +    return cfg
> > +
> > +
> > +def _read_epoch(fid):
> > +    """Read BTi PDF epoch"""
> > +    out = {'pts_in_epoch': read_int32(fid),
> > +           'epoch_duration': read_float(fid),
> > +           'expected_iti': read_float(fid),
> > +           'actual_iti': read_float(fid),
> > +           'total_var_events': read_int32(fid),
> > +           'checksum': read_int32(fid),
> > +           'epoch_timestamp': read_int32(fid)}
> > +
> > +    fid.seek(28, 1)
> Comment me!
> 
> —
> Reply to this email directly or view it on GitHub.
>