Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run stopped #59

Open
ddesai5 opened this issue Aug 23, 2022 · 2 comments
Open

Run stopped #59

ddesai5 opened this issue Aug 23, 2022 · 2 comments
Labels
question Further information is requested

Comments

@ddesai5
Copy link

ddesai5 commented Aug 23, 2022

Hello, I am running tormes for the first time on a mac. This is the 'error' I am getting. Thanks!

Warning message:
In read.table("ecoli_practice/output_genomes/ERR022075metadata.txt", :
incomplete final line found by readTableHeader on 'ecoli_practice/output_genomes/ERR022075metadata.txt'

  • All the software is properly installed.
  • The data included in the metadata file is correct.

tormes version 1.3.0 analysis will start now

Status can be seen in "/Users/abc/sequence_analysis/ERR022075_1/tormes.log"

/Users/abc/opt/anaconda3/envs/tormes-1.3.0/bin/tormes: line 929: syntax error near unexpected token >' /Users/abc/opt/anaconda3/envs/tormes-1.3.0/bin/tormes: line 929: if ls $OUTWD/Raw_reads/*fastq &>>/dev/null; then'

@biobrad
Copy link
Collaborator

biobrad commented Sep 1, 2022

Hi @ddesai5
Did you create your metadata file in windows or in linux?
Check that the file is unix compatible for 'new line'. If you are using windows, use notepad++ and make sure that under the edit menu that EOL Conversion is set to Unix.

Alternatively, you can put your fasta files and .fastq.gz files in a folder, then run this script which will create the samples_metadata.txt file for you with all the correct spacing etc:

https://github.com/biobrad/Tormes-Meta-Create/blob/main/tormes_meta_create

good luck.
cheers
Brad

@nmquijada nmquijada added the question Further information is requested label Dec 19, 2022
@nmquijada
Copy link
Owner

Hi @ddesai5
Did you try @biobrad solution?

Alternatively, you can run TORMES again but by redirecting the output:

[YOUR TORMES COMMAND] &>>error-tormes.txt 2>>error-tormes.txt &

By doing so, you won't see anything in the terminal. This is intended, so please don't kill the process. The command will record everything occurring in your tormes run, errors included, so we might be able to track them.
Once the analysis is done, please share with us the error-tormes.txt file

Thanks,
Narciso

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants