You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vasp jobs run well with my SGE queue system. The single job also run well with atomate, but it will run into error with mutiple queues jobs on one node. The jobs can be submitted successfully, but would encounter a mpirun error.
the vasp.out file shows that : "mpirun noticed that process rank 3 with PID 57743 on node node3 exited on signal 15 (Terminated)"
this error never show in SGE that directly runs with "mpirun -np n vasp".
I think it would be a bug in atomate or custodian.
I just figure out that the vasp pid is submitted by the func "self.pid = _posixsubprocess.fork_exec()" in custodian.
The text was updated successfully, but these errors were encountered:
Please submit help issues to:
https://matsci.org/atomate
The vasp jobs run well with my SGE queue system. The single job also run well with atomate, but it will run into error with mutiple queues jobs on one node. The jobs can be submitted successfully, but would encounter a mpirun error.
the vasp.out file shows that : "mpirun noticed that process rank 3 with PID 57743 on node node3 exited on signal 15 (Terminated)"
this error never show in SGE that directly runs with "mpirun -np n vasp".
I think it would be a bug in atomate or custodian.
I just figure out that the vasp pid is submitted by the func "self.pid = _posixsubprocess.fork_exec()" in custodian.
The text was updated successfully, but these errors were encountered: