Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expose "add_offset" control in `concatenate_epochs`
See original GitHub issueI find myself frequently using concatenate_epochs function to unite several sets of epochs for different events, and then sorting the epochs afterwards. This proves a great pattern for working with a database-like structure for machine learning applications.
However, the function by default gives an offset to the sets of events, which means that the resulting event timestamps lose their valuable information. Examining the function I have found that it uses _concatenate_epochs where you can disable giving an offset to the events.
I was wondering if there was a specific reason to not expose this control in the public function, and if there wasn’t, would it be ok for me to submit a pull request of the correction? Thanks.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
+0.5 to expose add_offset if it’s needed for you. It’s not too invasive change.
Sorry, caught up in stuff, doing it now