-
Notifications
You must be signed in to change notification settings - Fork 22
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
"CESAR wrapper command crashed" #119
Comments
Hi @mprincipato CESAR distribution provides a few test samples Then pls try cat XXX.fa | ./cesar /dev/stdin I suspect the current implementation is not quite compatible with WSL. |
Thank you, @kirilenkobm ! I spotted one thing in the documentation (the fact that Python 3.11 was recommended, but my default version was Python 3.10.12) and went down an ill-advised rabbit hole trying to set my default Python3 to 3.11 and wound up breaking things further. I think I was able to undo what I did, though, and these results are from running CESAR after that! example1.fa
example4.fa
Then I tried cat extra/example1.fa | ./cesar /dev/stdin, and here's what I got:
Does anything look unusual here? Any red flags for what might be going on? |
I apologise for the long delay... I should say, there are absolutely 0 red flags in the provided output, which makes everything more complicated. |
Hi! Any update on this issue? I got the same issue in the STEP 7, using dog as reference and ferret as target (GCF_014441545.1
-GCF_011764305.1)
However, if I go to |
I just noticed these responses; apologies for my late response! Back in December 2023, I was finally able to get it to work by running CESAR on a borrowed computer with more memory and (I think) a newer graphics card. (I still used WSL on the new computer.) While I'm not positive the memory amount was the bottleneck, that's my current theory, since I haven't had similar issues with other ML tasks since I upgraded the memory in my computer. |
Hello, dev team!
I'm very new to TOGA, and I'm trying it out on some public data for a class project.
When I run it on my personal Windows machine (using Windows Subsystem for Linux), it runs for about eight and a half hours before saying:
`### CESAR jobs done ###
Checking whether all CESAR results are complete
!!CRITICAL: Too many (4576) CESAR jobs died, please check your input data and re-run TOGA
!!CRITICAL: Too many (4576) CESAR jobs died, please check your input data and re-run TOGA
Program finished with exit code 1`
When I look in the CESAR job logs, I find several error messages like this:
(Slightly edited to remove personal information.)
Here was the command I originally used to run TOGA:
./toga.py ../toga_input/hg38.HLpipKuh2.allfilled.chain supply/hg38.wgEncodeGencodeCompV34.bed ../toga_input/hg38.2bit ../toga_input/HLpipKuh2.2bit --kt -i supply/hg38.wgEncodeGencodeCompV34.isoforms.txt --cesar_mem_limit 5 --cesar_jobs_num 500
Do you have any guesses what might be going wrong to cause the CESAR wrapper command to crash?
As far as my inputs go, I got hg38.HLpipKuh2.allfilled.chain and HLpipKuh2.fa from this Bat1K page, and I converted HLpipKuh2.fa to 2bit using faToTwoBit.
The text was updated successfully, but these errors were encountered: