Combine efforts with NiMARE
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
@FeHoff Would y'all be open to combining efforts to porting some of the algorithms you're using here into NiMARE?
I've got a start here: (https://github.com/neurostuff/NiMARE/pull/1009)
I don't think NiMARE's trying to do everything that JALE is trying to do (no GUI for instance) and perhaps there could be a compatibility layer here to get outputs and stats that NiMARE does not compute/workflows that nimare does not create.
Those algorithms could get extra exposure through the NiMARE interface and through neurosynth compose (and we want to get the citation flow on neurosynth down so when people select algorithms they get proper citations). Also implementations of general methods could benefit algorithms beyond ALE (probabilistic ALE could be packaged to be applicable to MKDA as well; and the thresholding for ALEContrast could be applied to MKDAChi2 too). So the benefits could compound/opportunities expand if implementations are combined.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced NiMARE pull request and the algorithms currently implemented in JALE. Clarify which algorithms and outputs should be shared, and whether a compatibility layer is needed. Done means the participating projects agree on a concrete integration scope and workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100