Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to open folders with user altered filenames in SpikeGLX #1606

Open
h-mayorquin opened this issue Dec 6, 2024 · 0 comments · May be fixed by #1608
Open

Unable to open folders with user altered filenames in SpikeGLX #1606

h-mayorquin opened this issue Dec 6, 2024 · 0 comments · May be fixed by #1608
Milestone

Comments

@h-mayorquin
Copy link
Contributor

I have a use case when there is multi probe data form SpikeGLX with the following structure:

├── probe_1
│   ├── npx.imec.ap.bin
│   └── npx.imec.ap.meta
├── probe_2
│   ├── npx.imec.ap.bin
│   └── npx.imec.ap.meta
└── probe_3
    ├── npx.imec.ap.bin
    └── npx.imec.ap.meta

The problem is that the probe index was omitted from the name. The pattern {device}{probe_index} is used as a stream_index so in this case we are unable to open this file and the error in this line is triggered:

if key in self.signals_info_dict:
raise KeyError(f"key {key} is already in the signals_info_dict")

The solution, I think, is to determine the probe index directly from the metadata and use that to tell the streams apart. I have some stubbed test data and a patch that I will push soon.

@zm711 zm711 added this to the 0.14.0 milestone Dec 13, 2024
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 a pull request may close this issue.

2 participants