-
Notifications
You must be signed in to change notification settings - Fork 15
[ENH] save info concatenation #338
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
Merged
Remi-Gau
merged 3 commits into
cpp-lln-lab:dev
from
Remi-Gau:remi-save_info_concatenation
Apr 7, 2021
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
31 changes: 31 additions & 0 deletions
31
demos/openneuro/models/model-ds000114-lineBisectionRunLevel_smdl.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| { | ||
| "Name": "run level", | ||
| "Description": "contrasts to compute for the line bisection task", | ||
| "Input": { | ||
| "task": "linebisection" | ||
| }, | ||
| "Steps": [ | ||
| { | ||
| "Level": "run", | ||
| "Model": { | ||
| "X": [ | ||
| "trial_type.Correct_Task", | ||
| "trial_type.Incorrect_Task", | ||
| "trial_type.No_Response_Task", | ||
| "trial_type.Response_Control", | ||
| "trial_type.No_Response_Control", | ||
| "trans_x", | ||
| "trans_y", | ||
| "trans_z", | ||
| "rot_x", | ||
| "rot_y", | ||
| "rot_z" | ||
| ] | ||
| }, | ||
| "AutoContrasts": [ | ||
| "trial_type.Correct_Task", | ||
| "trial_type.Incorrect_Task" | ||
| ] | ||
| } | ||
| ] | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
% in tsv file,
foldsrepresent the runs/repetitions of condition, andlabelsrepresent trial type (condition).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I was not sure what terms to use because people in different fields use different words to refer to the same thing...
Should we stick with BIDS nomenclature:
runandtrial_type?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like BIDS labelling. and it is true that folds are used in some other toolboxes... only thing about the
runis, it might be confusing when one has 4D-maps with repetitions (run 1 repetition1, run1 repetition2, ...). No?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ha yes... you are right...
but actually, it could be useful to have both run and repetition, no?
the most "verbose" way of doing this is taking the whole name of the regressor for each image from SPM.mat
this should contain all the info you need: and it is then up to the user to parse this string.
so having the
runinfo AND theregressor_name? there will be a bit of information redundancy because the run number is in the regressor name but...meh...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
at the current form, if i am not mistaken, we needed to change the trial type (in _events.tsv file) for GLM to have separate repetitions modelled as separate regressors (betas). so technically it would work like this:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes sort of (I think that SPM always appends the BF at the end)
But the issue that not everyone will have repetitions, but everyone will have
runsand "trial_type".Also the names of the regressors are longer:
Where
Sn(X)is the number of the 'session' in SPM lingo (more or less a 'run' in the BIDS world... why use the same terms, huh?)