Closed xuefenfei712 closed 4 years ago
PALEOMIX definitely should not take that long to validate prefixes, as that just involves a bit of file IO. I'd expect a few seconds normally and maybe a couple of minutes if one of them needs to be indexed.
Are your FASTA files by any chance located on a network drive that was not properly connected? That is the only case I can currently think of that could cause it to hang like this.
If it is still running, or if it happens when you run it, then please try to press Ctrl+C and copy/paste the output here. It should give us a clue as to where the program got stuck.
Best, Mikkel
Thanyou for your reply, I just use the example data you provided, and reference is rCRS.fasta, also indexed well (see blow picture1), and this time I use "paleomix bam_pipeline dryrun 000_makefile.yaml" also get the same problem. Sorry for that, my friends (Clio) and I don't know how to solve it.
This definitely should not happen, but I cannot find any obvious reasons why your copy of PALEOMIX would lock up in this manner.
You say that you are able to trigger the same problem using "paleomix bam_pipeline dryrun 000_makefile.yaml", but what happens if you kill the process using CTRL+C? Are you able to do that and does Python print a traceback upon being killed? If possible, try to paste that traceback here, as it may include information about the cause of this problem.
Best, Mikkel
Thankyou for your reply, I type ctrl+c and get the below result
^CTraceback (most recent call last):
File "/home/user/anaconda3/envs/python27/bin/paleomix", line 11, in
The problem seems to happen when Paleomix tries to check if the version of java that is installed.
The command that Paleomix tries to run is something close to the following:
java -server -Djava.awt.headless=true -XX:+UseSerialGC -d64 -version
Try to run that command directly on your server and see what happens.
after running your code, and get the result: java version "1.8.0_101" Java(TM) SE Runtime Environment (build 1.8.0_101-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode) However, also not working now..... I also reinstalled paleomix, Adapteremoval and the result like before. Thankyou more!
That is strange.
Can you try the following and tell me what happens (does Paleomix still get stuck?):
Run paleomix with the option "--jre-option=-Xmx4g". That should skip the check where Paleomix seems to get stuck:
$ paleomix bam_pipeline run --jre-option=-Xmx4g 000_makefile.yaml
Run paleomix with the option "--temp-root":
$ paleomix bam_pipeline run --temp-root ./temp/ 000_makefile.yaml
Best regards, Mikkel
On Wed, Jan 8, 2020 at 2:42 PM xuefenfei712 notifications@github.com wrote:
after running your code, and get the result: java version "1.8.0_101" Java(TM) SE Runtime Environment (build 1.8.0_101-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode) However, also not working now..... I also reinstalled paleomix, Adapteremoval and the result like before. Thankyou more!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MikkelSchubert/paleomix/issues/24?email_source=notifications&email_token=AASMY23UWECYQAVWA6HBR2LQ4XJ4ZA5CNFSM4J3XTE72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIMONZY#issuecomment-572057319, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASMY26QTDGTEPB4AVO6FCTQ4XJ4ZANCNFSM4J3XTE7Q .
Closing due to lack of activity. Feel free to open a new issue if you still have this problem
I have installed paleomix, and run the example, for a few days, but no result. we refer to top, it accounts for ZERO CPU. only like this ... Reading makefiles ...