-
Notifications
You must be signed in to change notification settings - Fork 18
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
Encountered internal HISAT2 exception (#1) #31
Comments
If you are running CIRIquant with a large "-t" option, please reduce this number and try again.
I would speculate that your job monitoring system (e.g. SLURM or Torque) is limiting the total amount of threads or memory for your job, so CIRI2 ran out of resources and didn't finish successfully. Maybe you could require more memory in your batch script and try again. |
My -t is 4. Should I reduce that? |
Nope, 4 threads should be fine. Could you post the batch script, log file |
Hi Kevin, CIRIerror.log is empty. batch script is: #!/bin/bash CIRIquant -t 8 prefix.log is: [Thu 2021-06-24 23:30:41] [INFO ] Input reads: SRR1106189_1.fastq,SRR1106189_2.fastq |
This "Killed" error means your script has exceeded the maximum memory allocated. Maybe you could change the memory specified at the header lines of your batch script from |
It says: |
Well, then you have to specify more cores in your batch script. It seems that your server administrator has limited the maximum memory per core. |
Hi Kevin, We solved this problem by deleting useless files as well as increasing tasks-per-node and threads. Thanks for you help. |
Hi Kevin,
I had exactly the same problem as #15 , but I don't really understand what "reducing the number of threads" means. (I only used 4 cores.) Can you elaborate on that? Or it there another way to solve this problem?
Also it's weird. When I was running the test data as a batch file, the run was terminated due to this error. Then I immediately ran the test data in the command line, and I got the desired output in only 2-3 minutes. However, when I ran the experimental data today, running it as a batch file or in the command line both gave this same error. Do you know why does it happen?
The text was updated successfully, but these errors were encountered: