QuantumATK Forum

QuantumATK => General Questions and Answers => Topic started by: basantsaini on October 29, 2022, 08:18

Title: Simulating protein
Post by: basantsaini on October 29, 2022, 08:18
I am trying to simulate a sensor based on silicon nano wire and olfactory receptor protein. I am getting this error.
=================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 72618 RUNNING AT servertech
=   EXIT CODE: 9
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions

Any help from someone who has used QuantumATK for protein simulation, would be really appreciated.
Thank You.......
Title: Re: Simulating protein
Post by: AsifShah on October 31, 2022, 08:29
Probably memory issue. I faced same in other simulations especialy DOS calculations.

My guess would be you are taking too much stringent conditions such as high density of k points, mesh, large energy intervals, high density for energy sampling points, or other convergence parameters.
Title: Re: Simulating protein
Post by: filipr on October 31, 2022, 14:28
Quote
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)

Means that your calculation was killed = stopped by an external process or user. This is in most cases the job scheduling system (Torque, Slurm, SGE, ...) on the cluster that kills the job if it takes longer than the allowed time, uses more memory than allowed or requested or uses more processes than there are cores on the node. If the job scheduler is configured correctly and you configured your submission script for it it should send you an email with clarification of why the job was killed.

If the job used too much memory you will have to run on machines with more memory or try to get the calculation to consume less or distribute the memory use over more nodes (physical machines). This can be done in a multitude of ways:


See also: