Custom Query (3327 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 3327)

Ticket Resolution Summary Owner Reporter
#74 fixed Wrong no of atmos prognostic fields jeff caroline@…
Description

Hi NCAS,

Some of my model runs have fallen over. I get the error message below but I can't see anything obvious in my umui.

thanks, Caroline

* UM ERROR (Model aborting) : Routine generating error: INITIAL Error code: 102 Error message:

INITDUMP: Wrong no of atmos prognostic fields

*

1525-013 The sequential or stream WRITE statement cannot be completed because an errno value of 14 (A memory address is not in the address space for the process.) was received while writing the file /hpcx/devt/n02/n02-ncas/cbain/xaewd/xaewd.fort6.pe25. The program will stop. ERROR: 0031-300 Forcing all remote tasks to exit due to exit code 1 in task 25 ERROR: 0031-250 task 12: Terminated ERROR: 0031-250 task 9: Terminated 1525-013 The sequential or stream WRITE statement cannot be completed because an errno value of 14 (A memory address is not in the address space for the process.) was received while writing the file /hpcx/devt/n02/n02-ncas/cbain/xaewd/xaewd.fort6.pe3. The program will stop.

#75 fixed NDdiag problems jeff g.n.petersen@…
Description

Hi!

I'm having my first attempts using NDdiag and, alas, I'm having problems. My pp-file is xcmiha_pa000, a 12h job The file looks OK in xconv and contains all the variables that NDdiag needs on model levels.

When I run NDdiag the message I get is that it has Problems reading from file, see below. Any ideas what NDdiag isn't happy about? Is there a problem with the variables being on model levels but not pressure levels? I've kept the default header in NDdiag.CONTROL and the only changes I've made to run_NDdiag is to change the NDdiagBASEDIR.

Cheers,

Nina

g.n.petersen@…

—-

e607@envgnp1:~/Forrit> ./run_NDdiag infile executable file name is NDdiag_Linux

Input file is: infile

================================================================

NDdiag v6.0 —————-

Pressure-level diagnostics from UM data on the NEW DYNAMICS grid

Original Author: Peter Panagi

Author & Support: Changgui Wang

Dept. Meteorology, Room 1L44, JCMM Univ. Reading PO Box 243 Reading RG6 6BB Tel: 0118 3788794 email: chang.wang@…

c.g.wang@…

www: http://www.met.reading.ac.uk/~sws00cw2

Please acknowledge the author and support in ALL publications that have

made use of this software

================================================================

450.0000 1000.000

Problems reading from file

FORTRAN STOP Successful run of NDdiag mv: cannot stat `NDdiag.OUTPUT': No such file or directory

#76 fixed Error in COEX um_support hanneke
Description

Hello,

I had a run working but realized I was using the wrong land mask. I changed this (and the number of land points), reran the reconfiguration (I do this in a separate run) and ran the same run again. I have used this land mask before and it didn't give me any problems. However, my run is now failing with this error:

GATHER_FIELD: Message: GATHER_FIELD: Error in COEX

STASH_GATHER_FIELD : Failed during GATHER_FIELD Error code : 2 Message : GATHER_FIELD: Error in COEX Error occured in STASH while gathering data for output. STASH : Error processing diagnostic section 3 , item 209 , code 2

Failed to gather field

RHS zero so GCR( 2 ) not needed ==============================================

GATHER_FIELD: Non-Zero Error Code 2 GATHER_FIELD: Message: GATHER_FIELD: Error in COEX STASH_GATHER_FIELD : Failed during GATHER_FIELD Error code : 2 Message : GATHER_FIELD: Error in COEX Error occured in STASH while gathering data for output. STASH : Error processing diagnostic section 16 , item 204 , code 2

Failed to gather field

* UM ERROR (Model aborting) : Routine generating error: Atm_Step Error code: 2 Error message:

Failed to gather field Ad÷ÈOÿÿÿþèCXOÿÿÿþèkXOÿÿÿÿþz OÿÿÿþâÖp?A¢P AP1%P APÃzHOÿÿÿþâ×@

*

What is this COEX? I've tried to make changes in the STASH to exclude those items, but then it just gives the same problem with a different item. Does anyone know where this error comes from?

Thanks a lot! Hanneke

PS Have attached the basis file for the job in case you need it.

Note: See TracQuery for help on using queries.