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

Explore replacing MELODIC with GIFT #671

Closed
chrisgorgo opened this issue Nov 17, 2017 · 4 comments
Closed

Explore replacing MELODIC with GIFT #671

chrisgorgo opened this issue Nov 17, 2017 · 4 comments

Comments

@chrisgorgo
Copy link
Collaborator

From Vince Calhoun:

If you are just running ica on data without masking, we have efficient pca strategies to solve the pca part with less memory usage. If the ICA is run in deflationary mode with fastICA, then shouldn’t be too much difference between melodic and gift. In general I prefer symmetric mode as I find performance is better.

The newer algorithms (like EBM) move beyond the assumption of a fixed unimodal distribution for the sources (which is what informax & fastICA (i.e. melodic uses)), so should do better if your data has more complex sources. These are a little bit slower though, however will use the memory efficient PCA I mentioned above.

Latest release of GIFT includes nipype interfaces.

@chrisgorgo
Copy link
Collaborator Author

The most problematic aspect of MELODIC is large memory consumption.

@chrisgorgo
Copy link
Collaborator Author

Here are the steps that will be required to replace MELODIC with GIFT:

  1. Implement nipype GIFT Interface that produces HTML visualization (reportlets). See Add GIFTRPT niworkflows#219
  2. Add GIFT installation to Dockerfile.
  3. Replace MELODICRPT with GIFTRPT at https://github.com/poldracklab/mriqc/blob/61b7a32c057b7963c8f9ee22f1bb90e818c861d8/mriqc/workflows/functional.py#L164
  4. (optionally) Adjust the value of mem_gb argument to specify (hopefully) lower memory requirements of GIFT.

@stale
Copy link

stale bot commented Aug 15, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@oesteban
Copy link
Member

Closed in favor of #1329 (discussion)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants