#2997 closed help (fixed)

glm reconfiguration error

Reported by: xuemeiwang Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: Monsoon2
UM Version: 11.3

Description

I have a um11.3 reconfiguration error in the global model occurring several times and wonder if you can help me have a look at it.

I was running u-bl886 from 20140911 to 20141011 and the model has broken on 23 Sept for several times. The error is as follows:

******************************************************************************************************
???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!?  Error code: 21?  Error code: 21?  Error code: 21

?  Error code: 21
?  Error from routine: RCF_FIT_FSAT?  Error from routine: RCF_FIT_FSAT

?  Error message: Exp. decay in Vol_Smc_Sat wrongly/not set?  Error message: Exp. decay in Vol_Smc_Sat wrongly/not set

?  Error from routine: RCF_FIT_FSAT?  Error from routine: RCF_FIT_FSAT?  Error code: 21
?  Error from processor: 9

?  Error from processor: 11?  Error message: Exp. decay in Vol_Smc_Sat wrongly/not set
?  Error number: 6
?  Error message: Exp. decay in Vol_Smc_Sat wrongly/not set
?  Error number: 6?  Error from processor: 2
????????????????????????????????????????????????????????????????????????????????
*******************************************************************************************************


I tried using a different suite and started from 23 Sept straight but it also showed the same error, so it's not a run_len problem. Can you help me see what could be wrong?

Thanks,
Xuemei

Change History (9)

comment:1 Changed 11 months ago by willie

Hi Xuemei,

Can you post the full path to the file with that error, please. I'm having trouble finding it.

Willie

comment:2 Changed 11 months ago by xuemeiwang

Hi Willie,

Sorry for the trouble and my late reply (I struggled a bit login to NCAS website). I just made a new run by changing the start date from 20140911 to 20140924 and the model ran. It only crashed on 23 Sept which seems odd.

Alternatively, I currently have another run u-bm001 which starts from 20140923 and it produced the same error when it reached the reconfiguration stage. I have been using it to test the u-bl886 and has the same settings apart from the start date. The error file is in ../log/job/20140923T0000Z/glm_um_recon1/01/.

Thank you so much!

Best,
Xuemei

comment:3 Changed 11 months ago by xuemeiwang

Full path is: /projects/asci/xuewa/cylc-run/u-bm001/log/job/20140923T0000Z/glm_um_recon1/01/job.err

comment:4 Changed 11 months ago by willie

Thanks Xuemei, I'll have a look at it. Please do not run the suite or move any files while I do so.

Willie

comment:5 Changed 11 months ago by willie

Hi Xuemei,

It looks like the start dump

/projects/asci/frfp/startfiles/2014092300_glm_t+0

which is being installed is corrupt. It should be 28GB, but it is only 8.3GB.

I extracted one from MASS - it is in /projects/nexcs-n02/frmy - that you could use.

I also think that your value of CYCLE_INT_HR is wrong: it has to be 6, 12 or 24 hours. If you look at the cycling options under suite conf, you can see the error. It is vital that you only modify the suite parameters through the GUI, as this can trigger other essential changes.

Willie

comment:6 Changed 11 months ago by xuemeiwang

Hi WIllie,

Thank you so much for the help!

I wonder if you can copy the startfile to /projects/asci/frfp/startfiles/ because I want the runs to be continuous but I don't have the permission to do so.

Thank you!

Xuemei

Last edited 11 months ago by xuemeiwang (previous) (diff)

comment:7 Changed 11 months ago by willie

Hi Xuemei,

I can't copy it into other peoples directories since I don't have permission. But you can copy the file

-rw-r--r-- 1 frmy nexcs-n02 28G Aug 20 16:03 /projects/nexcs-n02/frmy/2014092300_glm_t+0

to your own work space. I think you should be able to see it.

Willie

comment:8 Changed 11 months ago by xuemeiwang

Hi Willie,

Thank you so much for your help! I will see what I can do.

Cheers,

Xuemei

comment:9 Changed 11 months ago by willie

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