Nesting Suite UM frame job error

[dsergeev]

Hi,

In one of my UM runs, I decided to increase the run length from 48 to 72 hours. Almost everything works fine, but the um_frame job fails at the forecast period 9 (see screenshot).

Below is the stderr message of that frame job:

Warning in umPrintMgr: umPrintLoadOptions : Failed to get filename for IO control file from environment
Warning in umPrintMgr: umPrintSetLevel : Problem reading $PRINT_STATUS, output level will stay as    2                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          
forrtl: severe (18): too many values for NAMELIST variable, unit 10, file /projects/accacia/deser/cylc-run/u-ae616/work/20080301T1200Z/NorwegianSea_km2p2_ukv_default_um_frame_009/input.nl, line 68, position 81
Image              PC                Routine            Line        Source             
um-createbc.exe    00000000005EA997  Unknown               Unknown  Unknown
um-createbc.exe    000000000061433A  Unknown               Unknown  Unknown
um-createbc.exe    00000000005003E0  lbc_grid_namelist         138  lbc_grid_namelist_file_mod.f90
um-createbc.exe    0000000000401B19  MAIN__                    178  createbc.f90
um-createbc.exe    000000000040050E  Unknown               Unknown  Unknown
um-createbc.exe    00000000006BEEF1  Unknown               Unknown  Unknown
um-createbc.exe    00000000004003E9  Unknown               Unknown  Unknown
[FAIL] um-createbc.exe input.nl # return-code=18
Received signal EXIT
2017-05-04T15:06:02Z CRITICAL - Task job script received signal EXIT
2017-05-04T15:06:02Z CRITICAL - failed

What could be the reason of this error? I've tried restarting the suite from scratch a couple of times, but it fails nonetheless. From time to time this error appears even at the first forecast period.

Thanks,
Denis

[willie]

Hi Denis,

Is this still an issue? The name list file has been deleted.

Regards
Willie

[dsergeev]

Hi Willie,

I'm running the suite for different cases at the moment, so I'm going to close this issue for now. That problem seemed to be persistent, so if I decide to make longer runs again and get the same error, I'll reopen the ticket.

Denis

[dsergeev]

Hi Willie,

I needed to rerun one of my cases for a longer period, and I ran into the same error.

Should I change the frequency of LBC files somehow?

I think the problem is that max_input_files is set to 60 in src/utility/createbc/lbc_output_control_mod.f90, which is reached at frame009 stage (see /projects/accacia/deser/cylc-run/u-ai883/work/20070119T1200Z/NorwegianSea_km2p2_ukv_default_um_frame_009/input.nl).

Now the suite id is u-ai883, and the forecast cycle is 20070119T1200Z.

Could you please look into this?

Best regards,
Denis

[willie]

Hi Denis,

CreateBC is designed to handle up to 1,000 files so it's not that. I'll look further …

Willie

[willie]

Hi Denis,

Oh dear, you're quite right. The UM10.2 Create BC can only do 60 input files; the UM10.3 version can do 1,000 files.

The solution I think is to change, in rose edit, the um_createbc meta data to um-createbc/vn10.3, and then run again.

Regards
Willie