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

[FIX] Fixes greedy participant selection #426

Merged
merged 1 commit into from
Mar 15, 2017
Merged

Conversation

oesteban
Copy link
Member

Adds the possibility of using the star (*) wildcard to select participants
with the --participant_label argument. Before this, the default was
using the greedy search.

Now,

mriqc data/ out/ participant --participant_label 32322A

will match only sub-32322A. And

mriqc data/ out/ participant --participant_label 32322A*

will match sub-32322A, sub-32322AB, etc. As well as:

mriqc data/ out/ participant --participant_label "*32322A"

that will match sub-32322A and sub-032322A, but won't match
sub-32322AB. Please note the use of quotes so that the shell
does not expand the star
.

Finally,

mriqc data/ out/ participant --participant_label "*32322A*"

will match all previous examples (sub-32322A, sub-032322A, and sub-032322AB).

Close #385

Adds the possibility of using the star (*) wildcard to select participants
with the `--participant_label` argument. Before this, the default was
using the greedy search.

Now,
```
mriqc data/ out/ participant --participant_label 32322A
```
will match only `sub-32322A`. And
```
mriqc data/ out/ participant --participant_label 32322A*
```
will match `sub-32322A`, `sub-32322AB`, etc. As well as:
```
mriqc data/ out/ participant --participant_label "*32322A"
```
that will match `sub-32322A` and `sub-032322A`, but won't match
`sub-32322AB`. **Please note the use of quotes so that the shell
does not expand the star**.

Finally,
```
mriqc data/ out/ participant --participant_label "*32322A*"
```
will match all previous examples (`sub-32322A`, `sub-032322A`, and `sub-032322AB`).

Close nipreps#385
@chrisgorgo
Copy link
Collaborator

chrisgorgo commented Mar 14, 2017 via email

@oesteban
Copy link
Member Author

Ok, shouldn't be hard to roll this back. Let's go ahead with this fix, and when pybids fixes this we'll roll this back.

@oesteban
Copy link
Member Author

After upgrading pybids and applying #427, this problem seems to keep happening. I've tried this branch with the new pybids-0.1.0 and works as expected. Merging in.

@oesteban oesteban merged commit f46e8eb into nipreps:master Mar 15, 2017
@oesteban oesteban deleted the fix/385 branch March 15, 2017 16:05
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.

2 participants