Skip to content
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

what are the differences between the "failed tasks" and "failed frame" after finishing 02.fp? #485

Closed
taipinghu opened this issue Aug 4, 2021 · 2 comments

Comments

@taipinghu
Copy link
Contributor

taipinghu commented Aug 4, 2021

Dear developers,

when the 02.fp process is finished, an error occurs in my calculation.
5 2021-08-04 10:55:38,144 - INFO : failed tasks: 0 in 200 0.00 %
6 2021-08-04 10:55:40,876 - INFO : failed frame: 54 in 190 28.42 %
RuntimeError: find too many unsuccessfully terminated jobs

I have carefully check the OUTCAR in 02.fp, but the OUTCAR files in some directories are not return. when the tasks are calculating, I noticed that the SCF iterations were not converged but the OUTCAR still normally terminated.

Why the failed frame is "54 in 190 28.42"? I have modified the ratio_failure (larger than 28.42%) of the Machine file. However, this error still occurs. What are the differences between the "failed tasks" and "failed frame"?

Thanks for your reply.

Taiping

@AnguseZhang
Copy link
Collaborator

@dingzhaohan
Please see this issue.
I think there is a bug in

ratio_failure = self.mdata_resources.get("ratio_failue", 0)

@HuangJiameng
Copy link
Collaborator

failed tasks is about the transmission of the files by dpdispatcher, failed frame is about the result of the calculation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants