-
Notifications
You must be signed in to change notification settings - Fork 16
Question about sgt_constructor (stuck at 100% w/o error) - mafft/dvtditr #135
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
Comments
Hi @Edouard94, Thank you for providing this well documented information. What happens when you just try to resubmit? It's strange to me 956 of 960 steps complete but there are no errors in the log file. At least by rerunning we can see which genes are being problematic and at which step. At the moment the log is kind of hard to tease that out without there being error messages. Best, |
Thanks for your quick response. After running twice the sgt_constructor script, it seems to stop at the gene srprNP586132. Run 1:
Run 2:
And the mafft/dvtditr from my last run (run 2, started the 30th of April) is still running in the background. I am attaching the results of the last run here (link expires in 3 day): https://we.tl/t-R4mk7eOSmq And here the orthologue (database) fasta file for this specific gene: srprNP586132.txt Let me know if I can share other files. Thanks again for your help! |
Hi @Edouard94, Can you send me the output from your job scheduler? |
Hi Robert, Do you mean this one: |
Yes. Thank you! I think what is happening is that you still have an instance running since you used nohup. I think srprNP586132 is fine. There must be one gene still trying to get through mafft. |
Yes, I think you are right, that would also explain the mafft/dvtditr command running in the background? (for days) Should I try to run the script without nohup? |
I don't think that's necessary. I think you will just need to wait for it to finish. It is not uncommon for mafft to take a really long time on files with many and/or long sequences. |
Ok good to know, I will update you when the mafft/dvtditr command comes to an end! Thank you for your help Robert. |
No problem! Just for your reference it seems to be rpo-CNP585937 that is still in mafft. |
Ah nice, did you just find out thanks to the log? It is the biggest ortholog file in the database, so it makes sense. And maybe the most prevalent gene in the input proteomes as well? |
I did. It could be. I didn't check to see how many sequences there were in that file. |
Dear @robert-ervin-jones,
I would just like to have some insights on my last PhyloFisher run and specifically on the sgt_constructor.py script.
This is the code I ran so far (I copy pasted a custom database folder from another user to my own user directory for this run):
The sgt_constructor.py step seems to take a long time and I just wanted to check if this was normal.
These were the last lines of my sgt_out.log:
So there are no new steps since Wed Apr 30 but a mafft/dvtditr command is running in the background:
Is this normal behaviour for sgt_constructor?
So far I have these output files in my sgt folder:
Here is the full sgt_constructor.py log: sgt_out.log
Thank you for your insights on this Robert.
Best wishes,
Edouard
The text was updated successfully, but these errors were encountered: