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

Integration of fMRI in brainstorm #648

Open
Edouard2laire opened this issue Oct 11, 2023 · 2 comments
Open

Integration of fMRI in brainstorm #648

Edouard2laire opened this issue Oct 11, 2023 · 2 comments

Comments

@Edouard2laire
Copy link
Contributor

Edouard2laire commented Oct 11, 2023

Hello,
The aim of this thread is to discuss the potential of integrating fMRI data analysis into Brainstorm. Having fMRI time course in the volumetric space would require too much modification to the existing code base of Brainstorm but I think we can integrate surface-based analysis quite easily.

The main objective, for now, would be to be able to import minimally processed fMRI data on the cortical surface (typically the output from fMRIprep) to be able to then use existing functionally offered by Brainstorm/nirstorm for surface data analysis.

The following post we be used to keep track of the progress :)
Note: It might be needed to add a few processes specific to fMRI. Do you prefer me to add them to Brainstorm or NIRSTORM ?

Here are some very preliminary results. We need to be cautious as i need to check the way i projected the data from the volume to the surface but i think this is encouraging :)

Screenshot 2023-10-11 at 14 30 32

@Edouard2laire
Copy link
Contributor Author

Edouard2laire commented Oct 11, 2023

Data importation

One issue is that surfaces always need to be linked to a data file, notably for the importation of events. We would probably need to create a dummy data file/channel to keep the events functionalities. From fMRIprep, we can import the confound file containing useful time course.

Analysis

  • To write

Misc

Tutorial

@rcassani
Copy link
Member

That would be a good feature to have!

Regarding the data file, it does make sense to have it with confounds and to store events.

Heads-up @tmedani

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

No branches or pull requests

2 participants