Difference between revisions of "Debugging after a run crashes"
(Created page with "aa") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | The best way to find out the reason for a crash is to visualize the surface velocity with ACE/xmvis6. Usually you'll see some large/noisy velocity somewhere, which may give you some hints on forcing etc. | |
| + | |||
| + | Sometimes you want to visualize the problem right before the crash. You cannot use autocombine_MPI_elfe.pl as the last stack of output is incomplete. But you can use the core FORTRAN combine script (e.g., combine_output6) to directly combine an incomplete stack. Just follow the instruction in the header of combine_output6.f90 to prepare the inputs and run. Then visualize the combined outputs with xmvis6. | ||
Latest revision as of 09:43, 30 June 2014
The best way to find out the reason for a crash is to visualize the surface velocity with ACE/xmvis6. Usually you'll see some large/noisy velocity somewhere, which may give you some hints on forcing etc.
Sometimes you want to visualize the problem right before the crash. You cannot use autocombine_MPI_elfe.pl as the last stack of output is incomplete. But you can use the core FORTRAN combine script (e.g., combine_output6) to directly combine an incomplete stack. Just follow the instruction in the header of combine_output6.f90 to prepare the inputs and run. Then visualize the combined outputs with xmvis6.
