Payu error code 174

General
1

Hi,

Our simulation crashed with error code 174. There was also a comment:

UserWarning: Error occured when attempting to commit runlog

Issue talks about a similar problem as indicated by warning comment above. Adopting the same solution did not fix the problem and variations were implemented. Eventually we adopted the method suggested by @jo-basevi of forcing the git module to be picked up from vk83. This stopped the warning message but NOT the model crashing with error code 174. I have not been able to find documentation of these error codes anywhere? I was skeptical that this solution would fix the underlying issue as this particular simulation is up to year 315. i.e. It hasn’t suffered from this 314 times AND it hasn’t been a show stopper in the hundreds(thousands) of years I have run to date. I’m not saying with certainty that he warning has never been there, it has just never killed a run. The model error file indicates that the model was in bilinear.h (the Helmholz solvers) at the time. Whilst I am not certain that a numerical error did not occur here, it is also hardly surprising as the model spends so long in these solvers. Again what error code 174 means would be a most helpful clue here. I would like to find this out before perturbing the latest restart and trying again

2

The end of atm.fort6.pe0 has

 Tracer Flux/Mass/Loss in kg per timestep
 Flux T01:   -2750086944.73534
 Total Mass/Loss T01:                      NaN                     NaN
 Flux T02:   -187499066.670967
 Total Mass/Loss T02:                      NaN                     NaN
  RHS zero so GCR(                     2 ) not needed

so it looks like the usual fingerprint of an internal UM stability problem.

2 Likes
3

@Jhan, as discussed at the ESM1.6 stand-up, we don’t think it is worth investigating this further. So I’ll close this topic, but let us know if you get other similar error codes from payu, in which case we can look into it.

5

Thats fine. I just perturbed and restarted anyway

6

The error code 174 is from the Intel compiler rather than anything to do with payu.

The error log file has messages

forrtl: severe (174): SIGSEGV, segmentation fault occurred
1 Like