use CAIMAN_TEMP to store mcorr memmap and then move back to parent dir #22
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
This was referenced May 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is necessary because caiman has no way to set a filename prefix for saving mcorr memmaps.
Once this is merged upstream in caiman: flatironinstitute/CaImAn#978 this PR in
mesmerize-corecan be merged. The file is first stored by caiman according toCAIMAN_TEMPand then moved back to the same dir as the input data using the UUID for the filename prefix. Very roundabout but caiman has no way to set filenames for mcorr memmaps ¯\_(ツ)_/¯