Opened 10 years ago

Closed 9 years ago

#692 closed help (fixed)

HadGEM2-ES crash cloud fraction less than zero

Reported by: abozzo Owned by: um_support
Component: UM Model Keywords: MONSooN, HadGEM2,cloud fraction,crash
Cc: Platform:
UM Version: 6.6.3

Description

Hi,

my run (xfkmj) ran with no problem for the past 2 months. Few days ago it crashed with the error message:

error = stratiform cloud opt. depth less than zero

With the last call:

isccp_cloud_types_fld-3.4: Calling isccp_cloudtypes:

I restart the run from the last dump, but the model crashed at the same point with the same message.

Any help would be appreciated,

thanks
Alessio

Change History (5)

comment:1 Changed 10 years ago by willie

Hi Alessio,

The output files for the job xfkmj have disappeared, so I will confine my comments to comparing xfkmi, which I am assuming is the working job, and xfkmj. Looking the output below, it looks like you need to check the start dump for odd data and also the ancillary files.

I hope that helps.

Regards

Willie

xfkmj xfkmi job difference

The main differences are the start dump, the use of the ancillary files

Job xfkmi Title cp xfkmk - RUNNING VERSION
Job xfkmj Title cp xfkmi - RUNNING VERSION 861-949
Difference in window subindep_Runlen
 -> Model Selection
   -> Sub-Model Independent
     -> Start Date and Run Length Options
Entry box: Days
 Job xfkmi: Entry is set to '0'
 Job xfkmj: Entry is set to '1'
Entry box: Years
 Job xfkmi: Entry is set to '50'
 Job xfkmj: Entry is set to '3'
Entry box: Year
 Job xfkmi: Entry is set to '897'
 Job xfkmj: Entry is set to '946'

Difference in window atmos_InFiles_Start
 -> Model Selection
   -> Atmosphere
     -> Ancillary and input data files
       -> Start dump
Entry box: and file name
 Job xfkmi: Entry is set to 'xfkmia.dah7c10'
 Job xfkmj: Entry is set to 'xfkmja.dam6c10'

Difference in window atmos_InFiles_PAncil_VegFrac
 -> Model Selection
   -> Atmosphere
     -> Ancillary and input data files
       -> Climatologies & potential climatologies
         -> Vegetation Distribution: Area and structure.
Radio button: Leaf area index of plant functional types to be:
 Job xfkmi: Entry is set to 'Configured'
 Job xfkmj: Entry is set to 'Updated from ancil'
Radio button: Canopy height of plant functional types to be:
 Job xfkmi: Entry is set to 'Configured'
 Job xfkmj: Entry is set to 'Updated from ancil'
Radio button: Grid-box-mean canopy conductance to be:
 Job xfkmi: Entry is set to 'Configured'
 Job xfkmj: Entry is set to 'Updated from ancil'
Entry box: Every
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to '5'
Entry box: Every
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to '5'
Entry box: Every
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to '5'
Radio button: Time
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to 'Days'
Radio button: Time
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to 'Days'
Radio button: Time
 Job xfkmi: Entry is inactive
 Job xfkmj: Entry is set to 'Days'

Difference in window atmos_Control_PostProc_DumpMean
 -> Model Selection
   -> Atmosphere
     -> Control
       -> Post processing, Dumping & Meaning
         -> Dumping and meaning
Entry box: Year
 Job xfkmi: Entry is set to '1860'
 Job xfkmj: Entry is set to '800'

Difference in window ocean_InFiles_Start
 -> Model Selection
   -> Ocean GCM
     -> Input Files
       -> Start dump
Entry box: and file name
 Job xfkmi: Entry is set to 'xfkmio.dah7c10'
 Job xfkmj: Entry is set to 'xfkmjo.dam6c10'

Difference in window ocean_Control_PostProc_DumpMean
 -> Model Selection
   -> Ocean GCM
     -> Control
       -> Post processing, Dumping & Meaning
         -> Dumping and meaning
Entry box: Year
 Job xfkmi: Entry is set to '1860'
 Job xfkmj: Entry is set to '800'

comment:2 Changed 10 years ago by abozzo

Hi Willie,

thank you. The job xfkmi was a starting point, but the actual working version is xfkmj. It ran for 90 years and then it suddently crashed with that error. Some of the output have been archived, but the last months are still in /projects/lastmil/abozzo/um/xfkmj

I'll have a look for odd values in the starting dump. The crash occurs in aug 947. I restarted the model from the dec 946 dump, but I could try to go back to the dec 945 and see if it manages to go over the crash. I can't really understand what could have happened

Thank you,

Alessio

comment:3 Changed 10 years ago by willie

  • Keywords MONSooN, added

comment:4 Changed 10 years ago by willie

Hi Alessio,
Some further issues,

  1. The model is aborting : IOT/Abort trap
  2. conservation enforcement failed numerous times
  3. After 1241 time steps, GCR(2) failed to converge in 50 iterations
  4. S: PSLIMS(PRELIM). INVALID IPLAST. NO CHECKING
  5. There are only 21 stratiform errors but 64 processors
  6. NI_rad_ctl3c is generating a warning about volcanic forcing

I think the failure to converge is the root cause of the problem. You could create a dump at time step 1241 and look at it in xconv to see if there are any problems.

Regards,

Willie

comment:5 Changed 9 years ago by willie

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.