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

syri stopped running for unknown reasons #264

Open
gaochenx opened this issue Aug 23, 2024 · 2 comments
Open

syri stopped running for unknown reasons #264

gaochenx opened this issue Aug 23, 2024 · 2 comments

Comments

@gaochenx
Copy link

When I run syri to identify structural variations in sam files, syri will keep running, but there is no program in the background.

This is my command line:
syri -c Zm_Ki11_mo17.sort.bam -r ./Zm-Mo17.chr4.fa -q ./Zm_Ki11.chr4.fa -k -F B --prefix Zm_Ki11_mo17 --nc 12

This is the log file:
2024-08-23 14:44:26,071 - Reading Coords - INFO - syri:134 - Reading input from BAM file
2024-08-23 14:50:22,439 - Reading Coords - INFO - syri:134 - Filtering alignments
2024-08-23 14:50:26,062 - syri - INFO - syri:213 - starting
2024-08-23 14:50:26,079 - syri - INFO - syri:213 - Analysing chromosomes: ['chr4']
2024-08-23 14:50:26,213 - syri.chr4 - INFO - mapstar:48 - chr4 (14883, 11)
2024-08-23 14:50:26,213 - syri.chr4 - INFO - mapstar:48 - Identifying Synteny for chromosome chr4
2024-08-23 14:51:06,975 - syri.chr4 - INFO - mapstar:48 - Identifying Inversions for chromosome chr4

I don't know what's going on, this will keep running, but the program has crashed.

I can confirm that there is no problem with my syri, because half of the tasks have been running normally and the corresponding results have been output

@gaochenx
Copy link
Author

Why is syri stuck in last step and using more than 70% memory of server? #118
The situation is somewhat similar to question 118. Mine will just crash, not take up a lot of memory. But the program is still running in the foreground, and the background no longer shows the program

@mnshgl0110
Copy link
Member

Are these maize genomes? For highly repetitive, sometimes the alignments configuration could result in this. Using a smaller value for the --invgaplen should solve this issue.

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

No branches or pull requests

2 participants