Skip to main content
Skip to main navigation
Skip to user menu
Skip to search
Accessibility
Neuroimaging Resources Registry
Neuroimaging Data Repository
Cloud Computing Environment
Member login
|
Register
|
Help
Toggle navigation
Find
By Attribute
By Popularity
By Performance
Participate
Community
Register New Tool or Resource
Community Forums
Recently Active Forums
Calendar of Events
Support
Contact Us
User Help
About NITRC
What is NITRC?
NITRC TEAM
Dataset Acceptance Policy
Our Users
Technical Information
Cite Us
Member login
|
Register
|
Help
search
Search within this tool/resource
This tool/resource's forums
This tool/resource's releases
This tool/resource's documents
Related Web Pages
Related Web Pages Matrix View
Tools/Resources
People
NIF
for
Advanced Search
Support NITRC. Donate Today!
This repository is under review for potential modification in compliance with Administration directives.
Browse Tool Details
Summary
Support
Advanced Search
Documents
Downloads
Execution Options
Forums
Images
PubMed Mentions
Ratings & Reviews
User Reviews
( 1 )
Overall:
Installation:
Documentation:
Individual Rating Results for masked ICA (mICA) Toolbox
Review 1 of masked ICA (mICA) Toolbox on Feb 21, 2017
Version Reviewed:
v1.14
Overall Ease vs. Functionality:
Download/Installation Ease:
Documentation/Support Quality:
Ratings/Long-term Prospects Comments:
The mICA toolbox is a much needed implementation of masked ICA analyses using the FSL command suite. The toolbox includes single subject ICA, group ICA, atlases for masks and a reproducibility algorithm to determine the optimal # of components. There are a few hurdles in using the software. All of the hotkeys are set to an emacs/linux style. It was also a bit of a challenge to execute the binaries independently of the GUI. I had to go in and edit the source code that checks for the presence of the mICA bin path environmental variable before I could call the individual commands from the terminal. A few things would make this tool even better: It would be great if the tool could pick up where a command left off rather than always overwrite the output directory. Estimate time of completion and a bit more integration with parallel processing tools would go a long way to figuring out the best configuration for your analysis.