configuration file for vistasoft

[JWinawer]

Added config file for vistasoft (github.com/vistalab/vistasoft)

[benjamin-heasly]

Hi @JWinawer --

Thanks for this PR. Glad to include vistasoft and hope ToolboxToolbox is helpful.

I made some small changes aimed at making the configuration portable and automatic.

• Added spm12 as a separate configuration here so that we can deploy it with vistasoft, or any other configurations that might want spm12.
• Include spm12 and RemoteDataToolbox by name instead of explicit url. This is to avoid repeated definitions for the same toolbox in the registry.

I will go ahead and merge this and test it out on my end. Does it work for you?

[JWinawer]

Perfect. Thanks!

Jon

On Thu, Jan 26, 2017 at 11:37 AM, Ben Heasly notifications@github.com wrote:

Merged #19 https://github.com/ToolboxHub/ToolboxRegistry/pull/19.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ToolboxHub/ToolboxRegistry/pull/19#event-938044437, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBX3unvExuiIShPLjuQ1Jk-Bg4LWvmuks5rWMu-gaJpZM4Lt4bs .

-- Jonathan Winawer Assistant Professor of Psychology and Neural Science

New York University 6 Washington Place New York, NY, 10003 (212) 998-7922 (phone) (212) 995-4018 (fax) jonathan.winawer@nyu.edu http://psych.nyu.edu/winawer/

[JWinawer]

To be clear: Yes it works. This is great. If I understand correctly, if you have the toolbox toolbox and toolbox registery on your path, and you do not have vistasoft or github or remote data toolbox, then the first time you call tbUser('vistasoft') you will get all of these things from github, and all put in the right place.

Is that right?

Very handy, especially for new users of vistasoft.

Jon

On Thu, Jan 26, 2017 at 11:45 AM, Jonathan A Winawer < jonathan.winawer@nyu.edu> wrote:

Perfect. Thanks!

Jon

On Thu, Jan 26, 2017 at 11:37 AM, Ben Heasly notifications@github.com wrote:

Merged #19 https://github.com/ToolboxHub/ToolboxRegistry/pull/19.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ToolboxHub/ToolboxRegistry/pull/19#event-938044437, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBX3unvExuiIShPLjuQ1Jk-Bg4LWvmuks5rWMu-gaJpZM4Lt4bs .

-- Jonathan Winawer Assistant Professor of Psychology and Neural Science

New York University 6 Washington Place New York, NY, 10003 (212) 998-7922 (phone) (212) 995-4018 (fax) jonathan.winawer@nyu.edu http://psych.nyu.edu/winawer/

-- Jonathan Winawer Assistant Professor of Psychology and Neural Science

New York University 6 Washington Place New York, NY, 10003 (212) 998-7922 (phone) (212) 995-4018 (fax) jonathan.winawer@nyu.edu http://psych.nyu.edu/winawer/

[benjamin-heasly]

Hi Jon,

Yes, that's about right. Just to rephrase a little --

If you have Git installed and ToolboxToolbox on your Matlab path:

• The first time you type tbUse('vistasoft'), ToolboxToolbox will go and get the ToolboxRegistry, vistasoft, spm12, and RemoteDataToolbox for you. These all come from GitHub with git clone.
• The next time(s) you type tbUse('vistasoft'), ToolboxToolbox will git pull all those same things to keep them up to date.

That is a typical usage. There are other options too, for example you can use SVN instead of Git, or download a .zip from the Matlab file exchange.

Thanks!