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

List what "you" already have that could be added to BIDS-matlab #61

Closed
Remi-Gau opened this issue Oct 16, 2020 · 7 comments
Closed

List what "you" already have that could be added to BIDS-matlab #61

Remi-Gau opened this issue Oct 16, 2020 · 7 comments
Labels
enhancement New feature or request next release Will be in next release
Projects

Comments

@Remi-Gau
Copy link
Collaborator

As discussed in the last meeting (see #59) we will be keeping track of what "people" have already created to deal BIDS that could be added to this repository

@Remi-Gau Remi-Gau added the enhancement New feature or request label Oct 16, 2020
@Remi-Gau
Copy link
Collaborator Author

@bmdeen
Copy link
Collaborator

bmdeen commented Oct 25, 2020

I'm developing a BIDS-compliant pipeline for individual subject fMRI analysis, fMRIPermPipe (fppipe-v2 branch). I've written various low-level functions for interacting with BIDS filenames and metadata files, which might be useful: https://github.com/bmdeen/fmriPermPipe/tree/fppipe-v2/%2Bfpp/%2Bbids .
Functions that may be of interest: 1) fpp.bids.changeName (modifies a BIDS-formatted filename), 2) fpp.bids.jsonChangeValue (changes value in json file), 3) fpp.bids.jsonReorient (modifies metadata for a change in MRI image orientation).

I've also written a number of wrappers for FSL functions like flirt, fnirt, applywarp, invwarp, and convert_xfm, which generate .json files with updated metadata: https://github.com/bmdeen/fmriPermPipe/tree/fppipe-v2/%2Bfpp/%2Bfsl . Probably doesn't make sense to incorporate these directly into bids-matlab, but they may be useful to others.

@Remi-Gau Remi-Gau pinned this issue Oct 29, 2020
@Remi-Gau
Copy link
Collaborator Author

Functions that may be of interest: 1) fpp.bids.changeName (modifies a BIDS-formatted filename), 2) fpp.bids.jsonChangeValue (changes value in json file), 3) fpp.bids.jsonReorient (modifies metadata for a change in MRI image orientation).

I've also written a number of wrappers for FSL functions like flirt, fnirt, applywarp, invwarp, and convert_xfm, which generate .json files with updated metadata: https://github.com/bmdeen/fmriPermPipe/tree/fppipe-v2/%2Bfpp/%2Bfsl . Probably doesn't make sense to incorporate these directly into bids-matlab, but they may be useful to others.

I think some of those functions could be interesting though I suspect that we might want to try to make them more general by providing bids-matlab the ability to create filenames and JSON files that are compliant with BIDS derivatives specs.

@bmdeen
Copy link
Collaborator

bmdeen commented Oct 29, 2020

Yeah, these specific functions are not exactly what you'd want in bids-matlab - e.g., they're designed to be flexible and work with non-BIDS-compliant input filenames. I shared them anyway, since there might be some useful functionality.

@Remi-Gau
Copy link
Collaborator Author

Remi-Gau commented Nov 1, 2020

Pieter Vandemaele: https://github.com/GIfMI/matbids

Henk Mutsaerts:https://github.com/ExploreASL/ExploreASL

@guiomar
Copy link
Contributor

guiomar commented Dec 21, 2020

Hi!
You already mentioned Fieldtrip toolbox and I saw @robertoostenveld as a contributor, so he might have included the functions already, but just in case here you can have some examples and the use of the 'data2bids' function in Fieldtrip:
https://www.fieldtriptoolbox.org/example/bids/

@Remi-Gau Remi-Gau added this to To do in v0.1.0 Nov 7, 2021
@Remi-Gau Remi-Gau added the next release Will be in next release label Nov 7, 2021
@Remi-Gau Remi-Gau unpinned this issue Nov 15, 2021
v0.1.0 automation moved this from To do to Done Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request next release Will be in next release
Projects
No open projects
Development

No branches or pull requests

3 participants