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

fixes behav in singl-session-subjects in long study #24

Merged
merged 12 commits into from
Feb 13, 2017

Conversation

fliem
Copy link
Contributor

@fliem fliem commented Jan 31, 2017

This is the revived PR #22.
In longitudinal studies (studies in which at least one subject has more than one session) and --multiple_sessions='longitudinal') subjects with only one session should undergo the entire longitudinal stream. The changes in #11 broke that behavior. The present changes should fix it.

  • The longitudinal check was moved to the top, as it needs to loop through all subjects and look for sessions, before running the recon-all commands in a second loop.
  • At the moment longitudinal test cases cannot be run as they take >2h (longitudinal tests #23).
  • I've made the test1 check for a recon-all.done file after it is done.

@alexlicohen
Copy link
Collaborator

The run.py code change looks like it would reset longitudinal_study which each subject it checks, thus would be set by how many sessions the last subject has, vs the if any of the subjects had multiple sessions.

@fliem
Copy link
Contributor Author

fliem commented Jan 31, 2017

Thanks. I reverted to my very first implementation that searches for the first multi-sessions subject and stops if it is found. I've also added a multi_session_study variable to make things clearer.

@alexlicohen
Copy link
Collaborator

alexlicohen commented Jan 31, 2017 via email

@fliem
Copy link
Contributor Author

fliem commented Feb 1, 2017 via email

@chrisgorgo chrisgorgo merged commit f23ea1c into bids-apps:master Feb 13, 2017
@fliem fliem deleted the long branch February 14, 2017 06:55
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.

3 participants