JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FSL Archives


FSL Archives

FSL Archives


FSL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

FSL Home

FSL Home

FSL  August 2011

FSL August 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: running a script with FSL

From:

Mark Jenkinson <[log in to unmask]>

Reply-To:

FSL - FMRIB's Software Library <[log in to unmask]>

Date:

Tue, 2 Aug 2011 18:18:34 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (125 lines)

Hi,

Try the following:

cp script.txt badscript.txt
cat badscript.txt | tr \\r \\n > script.txt

but be careful to get this exactly right.

This should do the same job as dos2unix (which doesn't exist on the mac).
However, I suspect you also have an error in that the script is somehow
looking for a file called sta1.txt which it can't find.  So this may not be the
end of your problems, but hopefully it will get rid of the one complaining
about ^M characters.

If you do get the sta1.txt error then try to find this file and put it in the
current working directory.  Or, if it is already there, this file might also contain
characters, so try and save it as plain text and run the above commands
to get rid of the ^M characters if that is the case (but change the file names
appropriately).

All the best,
	Mark



On 2 Aug 2011, at 18:02, Leslie Engineering wrote:

> So I used the same .sh script but made sure it was in plain text format (as per the format tab in textedit) and I reran find ing the same error (i.e. bash: ./sta1.txt: /bin/bash^M: bad interpreter: No such file or  directory) so I tried the 'dos2unix' command, but it wasn't recognized.
> 
> I am on a mac osx 10.6.6, by the way.
> 
> I appreciate all the help! This forum is amazing!
> 
> 
> On Tue, Aug 2, 2011 at 12:16 PM, Xiangzhen Kong <[log in to unmask]> wrote:
> Maybe the command 'dos2unix' help avoiding the error 'bad interpreter: No such file or directory'.
> bash-3.2$ chmod +x script.txt
> bash-3.2$ dos2unix  ./script.txt
> bash-3.2$ ./script.txt
>  
> Best!
>  
> 2011-08-03
> Xiangzhen Kong
> 发件人: Leslie Engineering
> 发送时间: 2011-08-02  22:41:33
> 收件人: FSL
> 抄送:
> 主题: Re: [FSL] running a script with FSL
> Ok, it seems this computer saves things as rich text, so I sent a file from my older computer in plain text format and cut and paste the script. Now I get the following:
> 
> bash-3.2$ chmod +x script.txt 
> bash-3.2$ ./script.txt 
> bash: ./sta1.txt: /bin/bash^M: bad interpreter: No such file or directory
> 
> 
> On Tue, Aug 2, 2011 at 10:31 AM, Leslie Engineering <[log in to unmask]> wrote:
> I am not sure what you mean by plain "ascii" text editor. I opened it in TextEdit on my Mac OSX 10.6.6 and can't seem to find any other plain text applications. Do I need to download something? 
> 
> 
> On Tue, Aug 2, 2011 at 10:24 AM, wolf zinke <[log in to unmask]> wrote:
> looks like this script was edited with a word processor and contains formating that are causing problems as ascii text file. Open this file again with a word processor, copy it into a plain ascii text editor and save t again (as plain text). Do not edit programs with a Word processor.
> 
> 
> hope this helps,
> wolf
> 
> 
> Leslie Engineering wrote:
> Sorry :)
> 
> So this is what I get :
> 
> 
> bash-3.2$ chmod +x script_name.sh bash-3.2$ ./script_name.sh ./sta.sh: line 1: {rtf1ansiansicpg1252cocoartf1038cocoasubrtf350: command not found
> ./sta.sh: line 2: syntax error near unexpected token `}'
> ./sta.sh: line 2: `{\fonttbl\f0\fswiss\fcharset0 Helvetica;}'
> 
> 
> 
> I don't know how to interpret!
> 
> On Tue, Aug 2, 2011 at 10:10 AM, Cunningham, Dustin <[log in to unmask] <mailto:[log in to unmask]>> wrote:
> 
>    It looks like your file is a bash shell script. I think you can
>    just give it executive privileges and run it in the terminal.
> 
>    try this:
> 
>    chmod +x filename
>    ./filename
>    ________________________________________
>    From: FSL - FMRIB's Software Library [[log in to unmask]
>    <mailto:[log in to unmask]>] On Behalf Of Leslie Engineering
>    [[log in to unmask] <mailto:[log in to unmask]>]
> 
>    Sent: Tuesday, August 02, 2011 9:27 AM
>    To: [log in to unmask] <mailto:[log in to unmask]>
> 
>    Subject: [FSL] running a script with FSL
> 
>    A colleague sent a single trial analysis script that he says "runs
>    with FSL 4.0 and above"
> 
>    How do you run a script with fsl?
> 
>    I set the path in xterm:
> 
>    export PATH="$PATH:~/scripts_folder"
> 
>    and tried to source the file
> 
>    source script_name.sh
> 
>    (clearly computers are not like the back of my hand...)
> 
>    Is there something in the fsl gui where I can automatically select
>    the script.. because I am unable to do it in the terminal prompt.
> 
> 
> 
> 
> 

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager