Changes between Initial Version and Version 3 of Ticket #620


Ignore:
Timestamp:
12/05/11 15:33:30 (9 years ago)
Author:
ros
Comment:

Hi Alessio,

The last atmos dump was indeed xfkmja.daj3310, but the run must have crashed before it could produce the corresponding ocean dump, so your CRUN then tried to start from the beginning of the previous month (.daj3210), but there's only an ocean dump - I assume, as you say, it's deleted the superseded dump.

Can you check if you have run out of quota on MONSooN? I wonder if this is the reason your job originally crashed.

To get going again you will need to do an NRUN, specifying the ocean and atmos dumps you want to start from. You can start from the .daj32l0 dumps, although this is part way through the month which might mess up the climate means.

Regards, Ros.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #620

    • Property Owner changed from um_support to ros
    • Property Status changed from new to assigned
  • Ticket #620 – Description

    initial v3  
    55in the xfkmj005.xfkmj.d11131.t122219.archive file the message is a generic I/O error 
    66 
     7{{{ 
    78Routine generating error: U_MODEL 
    89 Error code:  1 
    910 Error message:  
    1011TRANSIN: I/O read error 
     12}}} 
    1113 
    1214and in the .pe* files the error is: 
    1315 
     16{{{ 
    1417 global_land_field set to  10519 
    1518 Error in FILE_OPEN called from DERV_LAND_FIELD. 
     
    1720 Error returned from DERV_LAND_FIELD. 
    1821 Error code  1 
     22}}} 
    1923 
    2024Now, it seems the error is somehow related to the land-sea mask or to a corrupted dump file, but the model has run with no problems so far.