Skip to content

Add write settings.json for back compatibility for early-adopters of SortingAnalyzer#2792

Merged
alejoe91 merged 1 commit intoSpikeInterface:mainfrom
zm711:settings-json
May 2, 2024
Merged

Add write settings.json for back compatibility for early-adopters of SortingAnalyzer#2792
alejoe91 merged 1 commit intoSpikeInterface:mainfrom
zm711:settings-json

Conversation

@zm711
Copy link
Copy Markdown
Member

@zm711 zm711 commented May 1, 2024

Fixes #2788

See issue for full discussion but basically before return_scaled was global the settings.json file was not written and is now required to reload a SortingAnalyzer. This just writes the file to allow for compatibility for early adopters and can be removed at some point in the future.

@samuelgarcia is this what you had in mind based on our discussion in the issue?

@samuelgarcia
Copy link
Copy Markdown
Member

Hi Zach.
Totaly perfect.

@samuelgarcia
Copy link
Copy Markdown
Member

Note that we should do the same for the zarr case no ? Maybe not. Lets do it on demand.

@alejoe91 alejoe91 merged commit 1d88111 into SpikeInterface:main May 2, 2024
@zm711 zm711 deleted the settings-json branch May 2, 2024 10:41
@zm711
Copy link
Copy Markdown
Member Author

zm711 commented May 2, 2024

Note that we should do the same for the zarr case no ? Maybe not. Let's do it on demand.

Yeah based on our issue tracker so far everyone (my group + myself included) are using binary_folder. But that was only because I already had an install of SI without the necessary compression packages and was too lazy to download so I started using binary folder. :)

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.

setting.json file not written before return_scaled was global for a sortinganalyzer and is now a required file for reloading

3 participants