2016年9月30日金曜日

NaN in tracer.stat

I finally found the reason for segmentation fault (I think). It is because at least one of the newly added tracers (icechl, iceno3, and/or icenh4 in this case) has value of NaN, as seen in tracer.stat (which calculates sum of all 3d tracers, see ztrai in trcstp.F90):

         1  0.7883947556E+03
         2               NaN

This happens at the second time step. This means that either or both DMSPd or/and DMS becomes NaN in the second time step...

Actually this was not the cause of segmentation fault, as the run passed the second time step when key_my_trc_iceeco was excluded:

         1  0.7883947556E+03
         2               NaN
         3               NaN
         4               NaN
         5               NaN

Anyway, it is good to know that my 3d tracers are erraneous as well :(

0 件のコメント:

コメントを投稿