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

Filename wildcards can capture collections in filter_datasets #130

Open
k1o0 opened this issue Sep 25, 2024 · 0 comments
Open

Filename wildcards can capture collections in filter_datasets #130

k1o0 opened this issue Sep 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@k1o0
Copy link
Collaborator

k1o0 commented Sep 25, 2024

for example, with datasets such as

raw_ephys_data/_spikeglx_ephysData_g0_t0.nidq.meta
raw_ephys_data/probe00/_spikeglx_ephysData_g0_t0.ap.meta
raw_ephys_data/probe00/_spikeglx_ephysData_g0_t0.lf.meta

filter_datasets('*.meta', 'raw_ephys_data') returns all three datasets as the filename wildcard is greedy. It should not return the matching filenames in sub-collections.

@k1o0 k1o0 added the bug Something isn't working label Sep 25, 2024
k1o0 added a commit that referenced this issue Sep 25, 2024
k1o0 added a commit that referenced this issue Sep 26, 2024
k1o0 added a commit that referenced this issue Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant