-x option in antsRegistrationSyNQuick.sh

[AlejandroCallara]

Hello everybody,

When I try to use the bbm.sh script i get an error which says that -x is not an allowed option for the antsResgistrationSyNQuick.sh script; and in fact, looking at the help of antsRegistrationSyNQuick this option do not exist. Is there a way to do the same thing as in bbm.sh with some other scripts?

Best regards,

Alejandro.

[stnava]

see ANTsX/ANTs#400 brian

…

On Thu, Jan 19, 2017 at 4:32 AM, AlejandroCallara ***@***.***> wrote: Hello everybody, When I try to use the bbm.sh script i get an error which says that -x is not an allowed option for the antsResgistrationSyNQuick.sh script; and in fact, looking at the help of antsRegistrationSyNQuick this option do not exist. Is there a way to do the same thing as in bbm.sh with some other scripts? Best regards, Alejandro. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATyflYNGIohb23TP4c1rM0UmmAOCoE0ks5rTy2wgaJpZM4Ln4VV> .

[stnava]

also note that your copy of the script may be out of date - compare to the github version brian

…

On Thu, Jan 19, 2017 at 8:41 AM, brian avants ***@***.***> wrote: see ANTsX/ANTs#400 brian On Thu, Jan 19, 2017 at 4:32 AM, AlejandroCallara < ***@***.***> wrote: > Hello everybody, > > When I try to use the bbm.sh script i get an error which says that -x is > not an allowed option for the antsResgistrationSyNQuick.sh script; and in > fact, looking at the help of antsRegistrationSyNQuick this option do not > exist. Is there a way to do the same thing as in bbm.sh with some other > scripts? > > Best regards, > > Alejandro. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#4>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/AATyflYNGIohb23TP4c1rM0UmmAOCoE0ks5rTy2wgaJpZM4Ln4VV> > . >

[AlejandroCallara]

Hi Brain,

Thank you. The solution you gave me in ANTsX/ANTs#400 is the best one since I started to deal with this partial data.

Concerning the scripts there is something odd which I cannot understand. I have installed ANTs one month ago more or less (following your help page https://brianavants.wordpress.com/2012/04/13/updated-ants-compile-instructions-april-12-2012/ ) , so I did not check about my version since I supposed it could not be out of date. In fact in the folder ~/ANTs/Scripts my version of antsRegistrationSyNQuick.sh is the one with the -x option. However, in the ~/antsbin/bin folder, which is the one of $ANTSPATH, the version of the antsRegistrationSyNQuick.sh script has no -x option.

Do I have to copy the scripts from Scripts folder to the antsbinfolder? Is that "safe"?

[stnava]

yes - copy the scripts to bin brian

…

On Fri, Jan 20, 2017 at 5:22 AM, AlejandroCallara ***@***.***> wrote: Hi Brain, Thank you. The solution you gave me in ANTsX/ANTs#400 <ANTsX/ANTs#400> is the best one since I started to deal with this partial data. Concerning the scripts there is something odd which I cannot understand. I have installed ANTs one month ago more or less (following your help page https://brianavants.wordpress.com/2012/04/13/updated-ants- compile-instructions-april-12-2012/ ) , so I did not check about my version since I supposed it could not be out of date. In fact in the folder ~/ANTs/Scripts my version of antsRegistrationSyNQuick.sh is the one with the -x option. However, in the ~/antsbin/bin folder, which is the one of $ANTSPATH, the version of the antsRegistrationSyNQuick.sh script has no -x option. Do I have to copy the scripts from Scripts folder to the antsbinfolder? Is that "safe"? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AATyfguBJbnUQnLLFyhpVVcaushXVnohks5rUIrZgaJpZM4Ln4VV> .

[AlejandroCallara]

Brian, I called you Brain. Sorry for that!

Thanks.

PS. Do I have to close this issue?