2014年4月28日月曜日

Testing with Station Papa

initial condition problem

i assigned too high initial values for ph1 and ph2 which led to population crash for both variables.

closure term has effect on stablizing the ecosystem for runs with initial conditions that are constant throughout the water column (i.e. surface values). or either over- or underestimated initial profiles below surface layer. In particular, 0.003 does not work. >0.03 works.

I decided to test which of the initial profiles are causing the model to crash by adding one profile at a time for initalization (in fabm_input.nml):

no3: done
nh4: done
ph1: crashed on April 19!
ph2: done
psi: done
sil: done
det: done
zo1: crashed on April 5!
zo2: done

So the problem is with ph1 and zo1 profiles. I checked which one is the problem, by initializing with all profiles except ph1 and zo1 separately, and it turns out that the model runs successfully if I comment zo1 profile. The model crashes on April 12 if the zoprof.dat is used for zo1.

So the problem is with zo1.

since zo1 and zo2 use the same profile (zoprof.dat), it might not be the problem of profile data, but the model itself. So I checked the code.

I couldn't find any problems in the code.

I found meteo_file.dat for OSP in GOTM_13_08_02 and used it for surface forcing then the model did not crash! However, I found that temperature was not restored and producing unrealistic annual cycle. So I restored with 24 hr with data. Then the model crashes on April 15... does this mean the crash is somehow related to temperature?

and if I comment only the zo1 initial profile, the model runs fine with T restoring.

I probably need to restore NO3 too.

0 件のコメント:

コメントを投稿