Custom Query (3221 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 3221)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#3180 checksum failure in climate mean um_support ggxmy
Description

Dear CMS,

atmos_main failed in one of my UKESM-A nudged simulations with an error message;

ERROR: checksum failure in climate mean
Section  0  item  2
This can be due to invalid values in field, or corruption of partial sum file
Remove or fix diagnostic, and rerun

???!!!???!!!???!!!???!!!???!!!       ERROR        ???!!!???!!!???!!!???!!!???!!!
?  Error code: 4
?  Error from routine: U_MODEL_4A
?  Error message: ACUMPS: Diagnostic error. See output for item no.
?  Error from processor: 0
?  Error number: 688

"Section 0 item 2" is the u wind but maybe it is simply the first diagnostic and could be anything?

I'm currently running 3 almost identical simulations, all of which started from Mohit's release job u-bm242, and the only difference between 3 suites is the low level anthropogenic SO2 emissions. u-br297 uses the regular emission. u-br357 uses the same emission on land and emission from sea surface is masked and set to zero. This one, u-br356, uses the same emission on land and emission from sea surface is set to 20% of the original.

diff -r u-br297 u-br356

doesn't seem to show any substantial difference between two suites except the emission ancillary files.

All of these suites ran for 16 months without a problem. But soon after I extended the runs only this suite crashed. So to me this is strange.

Anyway I turned off the request to 00-002 and restarted the run. Now it failed with this;

?  Error code: 1
?  Error from routine: io:file_open
?  Error message: Failed to open file /home/d03/myosh/cylc-run/u-br356/share/data/History_Data/br356a.da20110101_00
?  Error from processor: 0
?  Error number: 22

br356a.da20110101_00 does not exist indeed. I could try other things but I thought maybe its better to seek help before the situation gets more complicated. Please could I have an advice on this?

Thanks, Masaru

#583 answered 12-hour and 6-hour means lois salvatore
Description

Hello, in my job xfulj I have tried to obstain 12hour means for some fields and in job xfulk 6hour means for the same fields. In order to achieve this, I set two time T12HR and T6HRMN which you can see in the STASH ATMOS panel. For the usage profile I have selected UPA. For the domain profile either DIAG or DIA11, depending whether the field is 2-dim ot 3-dim.

Now it happens that in the first case (12hour), I got what I want only for a few fields while all the remaining are empty, as if the their time means are not processed.

In the second case it's even worse, since the job fails because:

"Message : STWORK : NO. OF FIELDS EXCEEDS RESERVED HEADERS".

I have no idea about how to overtake these problems as it is the first time I use such short time means. What can I do?

Many thanks

Salvatore

#1067 answered Failure of model run using IAU scheme - segmentation fault um_support cflee
Description

I'm trying to run a series of short (32 day) jobs, using the IAU scheme to perturb initial conditions. Each run uses a different set of initial conditions (perturbations to U and V only), to represent an ensemble around an un-perturbed run. Some of the perturbed runs have worked; others have not! The latest attempt (/home/n02/n02/cflee/um/umui_out/xhjqt000.xhjqt.d13131.t193852.leave) has failed with a 'PE RANK 112 exit signal Segmentation fault'. Is this because the model is becoming unstable as a result of the perturbations to U and V that I've introduced?

The same run gave a different (and more typical) fault after an earlier attempt - this time segmentation faults 32 and 0 (xhjqt000.xhjqt.d13130.t104145.leave).

Many thanks,

Chris

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.