In this context, for example, it would mean where exactly did the problem stopped.
Maybe, I could tell you that the code stopped at the 42nd iteration.
And I have captured a screenshot of the reported error of the code and have posted here.
I do not know where can reflect the place which made the code stop.
So, I want to confirm a question. Could the elasticity problem of a 3D mesh with the size of 854 MB be solved by FF++ with PETSc using 25 processors or more? If the above problem could be solved, could you give me some advice about the solvers, for example, the template about set (A, “…”, bs=…, and more ), or other advice about the additional command line option. This is because I think the code is no problem, and my code can run but would stop at the 42nd iteration, this maybe caused by the improper solver or algorithm. Do you think so?
Without a back trace, it’s not even sure that the problem is in the solver and not in the distributed mesh setup.
So, Professor, How can I show you the back trace?
You need to find where the error appears in your code.
Thank you very much professor.