Dear list,
I have recently made some edits to SPM to add a couple of options to the 1st-level specification GUI. For this I made changes to:
spm_cfg_fmri_design.m
spm_cfg_fmri_spec.m
spm_run_fmri_design.m
spm_run_fmri_spec.m
All of which reside in spm8/config. This has worked brilliantly on my laptop. Now I need to get this working on our Linux network, but only for a subset of the users (my direct research group). I hence can't alter the shared SPM8 installation, as this would affect all users.
I had hoped that it would be a simple case of having a local copy of the above files, and then ensuring that these were ahead of the network copy on Matlab's path. However there's two problems with this:
1 - SPM adds its own subdirectories to the Matlab path on startup. This I can work around (by having a local copy of the files that do this and adding '-end' to the addpath statements), which means that I can at least access my new functions via a batch script (I think).
2 - If I understand it correctly, all the GUI entries are actually configured on startup by searching all spm8 subdirectories for 'cfg_mlbatch_appcfg' and then running 'spm_cfg' from within that subdirectory. This means that the stock spm files will always be ahead of my customised versions on the path (as the local directory takes precedence), and so my customisations won't show up in the GUI.
Have I understood the set-up mechanism for the GUI entries correctly? Are there any obvious workarounds I have missed? I admit that this is a bit of an esoteric use case, so I won't be surprised if there aren't.
Thanks in advance,
Toby Wood
|