Subject: Re: Problem with CCM 3.6.6 (T31) blowing up within 2 years ...
From: Bala Govindasamy (bala@llnl.gov)
Date: Fri Mar 01 2002 - 12:55:06 MST
Hello Dave,
I think your timestep is large. Reduce the timestep to 20 or 25 min. It
should run perfectly well then.
Bala.
Dave Newman wrote:
> Dear CCM users --
>
> I am having a problem with CCM 3.6.6 blowing up within 2 years, and
> wanted to see if anyone was experiencing anything similar, or if anyone
> had any suggestions on what may be causing the problem. Here is some
> relevant information:
>
> Version: CCM 3.6.6
> Res: T31
> DIME: 1800 (=30 mins)
> Mode: DST_FRC (i.e. no feedbacks)
> DIF4: 0.2E17
> Machine: SGI
>
> The run stops at NSTEP=28660 (approx day=597, year=1.6) with the message:
> CUBYDR: Departure point out of bounds: jcen,icount,pgls= 9, 1726, 1728
>
> I noticed that the Courant limit seemed to be creeping up as well.
> Also, I reran exactly the same model/case at T42, and it ran perfectly
> fine for several years (well beyond day=597)
>
> Does anyone have any suggestions or comments? Any help would be greatly
> appreciated!
>
> Thanks,
> Dave Newman
> newman@uci.edu
-- Bala ---------------------------------------- Bala Govindasamy L-103, Atmospheric Science Division Lawrence Livermore National Laboratory Livermore CA 94550 Ph.: 925 423 0771 Fax: 925 422 6388 Email: bala@LLNL.GOV; bala_indu@yahoo.com http://en-env.llnl.gov/cccm/balacv.html -----------------------------------------
This archive was generated by hypermail 2b27 : Fri Mar 01 2002 - 13:05:05 MST