Hello to all,I've been trying to make my own met forcing files to guide CAM offline, however the model crashes when I'm using them.As far as I understood, cesm.log indicates that some variable (but does not tell which) is not found in the met file on the first day of the run.Would anyone know the precise list of the necessary fields to be found in the met files? I have been working with ten of them for now: U, V, Q, T, TAUX, TAUY, TS, PS, SHFLX and QFLX.Thanks,Thibaut.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Necessary variables in offline met-files
- Thread starter thibaut_lurton@cnrs-orleans_fr
- Start date
Thank you Jerry for your answer.I do have these two US and VS variables as well, mapped on (m;n-1) and (m-1;n) grids.So I'm not quite sure what the actual problem might be...Thanks,Thibaut.
Hello,Ok, my error is spotted.Actually, I was changing my met-files list on a restart (branch run). So far, nothing unachievable, but the issue is I also wanted on that restart to turn on the strat_aero_feedback boolean, and turn off the chem_rad_passive. As it turns out, that caused the problem (probably because switching these two booleans entails fetching variables not present in my cam.r file). Running the case without the boolean switch is ok, proving that my met data is probably valid. At the end of the day, the error "variable not found" was surely about the cam.r and not the met-file (this was not really clear in the log, hence my first erroneous interpretation).So, if I want to keep the case I want (namely my customised met-files + radiative forcing booleans), I reckon I have to give up on the idea of branching on my previous run, and perform an initial run. Or is there a solution to this (pretty complex) configuration?Thanks again,Thibaut.