i think for your use case there should be to find a meaningful name. we then could add it as option to detect : str

what about 'onset-nonzero' or 'consecutive' while 'offset' | 'onset' | 'all' would be taken in the strict sense namely onset, offset, both.

makes sense?

On 31.01.2013, at 09:45, Alexandre Gramfort <notifications@github.com> wrote:

> In mne/tests/test_event.py:
> 
> >      events2 = find_events(raw)
> >      assert_array_almost_equal(events, events2)
> >  
> > +    # Test that we can handle consecutive events with no gap
> > +    stim_channel = fiff.pick_channels(raw.info['ch_names'], include='STI 014')
> > +    raw._data[stim_channel, :] = 0
> > +    raw._data[stim_channel, 10:20] = 5
> > +    raw._data[stim_channel, 20:30] = 6
> > +    raw._data[stim_channel, 30:40] = 5
> > +    raw._data[stim_channel, 40:50] = 6
> > +    # Re-reference first_samp to 0 for ease of comparison
> > +    raw.first_samp = 0
> > +    events = find_events(raw)
> > +    assert_array_equal(events,
> > +        [[10,  0,  5],
> > +         [20,  0,  6],
> > +         [30,  0,  5],
> > +         [40,  0,  6]])
> option 1: you have your own find_events function option 2: we manage to enumerate common use cases and come up with a simple find_events functions with understandable parameters. my 2c
> —
> Reply to this email directly or view it on GitHub.
>