Feature 'duplicate_with_new_data' for spiketrains, events and epochs #247
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
License format adjustment
|
Many thanks for this. Now that |
…ature/duplicate_with_new_data
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently only analogsignals offer the option to be duplicated keeping the same metadata (annotations, t_start...) but replacing the main signal (times). I added this feature also for spiketrains, events and epochs in order to simplify the modification of these objects, eg when shuffeling spiketimes or shifting all signals in time eg. for alignment of different trials. The current implementation uses helper functions (_copy_data_complement) analogous to the implementation for analogsignals and also contains some basic tests.
Currently only specific attributes are copied (shallow) to the new objects, which could be extended or implemented by a deepcopy in the future.