Skip to content

Comments

Add ep argument to compute_perievent#562

Closed
h-mayorquin wants to merge 2 commits intopynapple-org:mainfrom
h-mayorquin:add_ep_to_compute_perievent
Closed

Add ep argument to compute_perievent#562
h-mayorquin wants to merge 2 commits intopynapple-org:mainfrom
h-mayorquin:add_ep_to_compute_perievent

Conversation

@h-mayorquin
Copy link

Should close #526

Both compute_perievent_continuous and compute_event_trigger_average accept an ep parameter to restrict computation to specific epochs, but compute_perievent did not. This inconsistency meant that passing ep=something to compute_perievent was silently ignored via **kwargs (see #526).

This PR adds ep=None to compute_perievent, which when provided restricts both timestamps and tref to the given IntervalSet before alignment. All three perievent functions now share a consistent interface for epoch filtering.

@h-mayorquin h-mayorquin requested a review from gviejo as a code owner February 24, 2026 01:50
@gviejo
Copy link
Contributor

gviejo commented Feb 24, 2026

Hi Heberto, thanks for the PR. This module is currently being remade by @wulfdewolf (see #559). We are unifying compute_perievent and compute_perievent_continuous. I am closing this PR since the other PR should be merged soon.
Thanks again.

@gviejo gviejo closed this Feb 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

compute_perievent does not have an ep argument

2 participants