Reduce memory consumption when writing recorded stimulus #62
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
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.
When recording stimuli in higher resolution memory can become a bottleneck.
In the original implementation of the stimulus to numpy array conversion I did not care about memory.
I changed this now by doing most operations in-place and by setting the
recordedStimarray elements to None to free the memory as soon as one frame was processed.The numpy array also gets stored in a numpy file now instead of in a pickle file (Jonathan preferred that I think).
Also writes an additional boolean numpy array indicating when the trigger/marker (would have) appeared during stimulus presentation.