Opened 9 years ago

Closed 9 years ago

#706 closed help (fixed)

Wrong no of atmos prognostic fields

Reported by: oma Owned by: um_support
Component: UM Model Keywords:
Cc: Platform:
UM Version: 7.3

Description

Hello,

I'm trying to run the UM vn7.3 with a very recent startdump (from last week, 28 Sept 2011). I'm finding the following error message in the .leave file

*********************************************************************************
 UM ERROR (Model aborting) :
 Routine generating error: INITIAL
 Error code:  102
 Error message: 
INITDUMP: Wrong no of atmos prognostic fields
 *********************************************************************************

The job I'm trying to run is xgoea (username oma) in PUMA.

Thanks in advance for your help.

Oscar

Change History (2)

comment:1 Changed 9 years ago by oma

Hello,

I managed to get rid of the 'Wrong no of atmos prognostic fields' error by following the advice in #127, which involves a reconfiguration. Then, I encountered new problems regarding STASH items that were not found of which the following message is just an example:

 *****************************************************************************
 ERROR!!! in reconfiguration in routine Rcf_Exppx
 Error Code:-  2
 Error Message:-  Cant find required STASH item  493  section  0  model  1  in STASHmaster
 Error generated from processor  0
 *****************************************************************************

To solve this problem I found #584, where Willie advices to include certain user STASH master files which I found in his directory (especifically at ~willie/userSTASH) and copied over to mine. I hope those files were actually intended to solve this problem. In any case, this solution seemed to work and now I have been able to produce a startdump albeit at lower a resolution than that in the original startdump.

I was hoping this to solve all my UM problems but now I have found a different problem, which I'll describe in a new ticket.

Oscar

comment:2 Changed 9 years ago by willie

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