UMPsychMethodsCore / MethodsCore

All of the projects that the methods core develops, combined into one repository!
7 stars 0 forks source link

updating SPM8 to R6313, updating spm8Batch, and creating spm12Batch #374

Closed rcwelsh closed 8 years ago

rcwelsh commented 8 years ago

hi folks @UMPsychMethodsCore/developers

who wants to take on the task of putting spm8_with_R6313 into the distribution? once it's in i'll like to update spm8Batch to use that as I'm looking to migrate to using the latest MATLAB. eventually we need to update matlab on PANLAB and spm8_with_R4667 doesn't work with newer MATLAB.

i'm doing some local testing on my machine.

i'll also be looking to convert spm8Batch to spm12Batch, which will be a new branch.

dankessler commented 8 years ago

It looks like there are 3 major things you want to do here.

1) add spm8_R6313 to the repo. #376 does this (although core_beta will then need to get merged into public before we can consider this done)

2) update spm8Batch to use spm8_R6313. #377 does this, though again, once merged it will necessitate spm8Batch_beta being merged into public

3) Introduce spm12Batch (a brand new tool that will serve as spiritual successor to spm8Batch). In practice, this will probably branch off of existing spm8Batch code, though if it's going to leave under a different tree it's probably better to do this in a hacky-way: branch off of public and copy-paste spm8Batch stuff into an spm12Batch tree and start hacking there.

@rcwelsh how much effort do you think creating spm12Batch will be? If it's a big undertaking, maybe it'd be valuable to do a quick survey of other neuroimaging pipeline management tools (e.g. nipype, CWAS [though CWAS is built on nipype]) to make sure there isn't some effort to be saved by either adopting or building on top of an existing project.

OTOH: if it's a fairly trivial tweak from spm8Batch -> spm12Batch, then we might as well go ahead, although the suggestion I made above still stands.

dankessler commented 8 years ago

I'm going to close this issue because points (1) and (2) have been addressed and merged into their appropriate toolbox branches, which will soon be bundled into public