#2061 closed help (fixed)
UM Nesting Suite: re-using LBC files
Reported by: | dsergeev | Owned by: | um_support |
---|---|---|---|
Component: | UM Model | Keywords: | driving model, lbc |
Cc: | Platform: | MONSooN | |
UM Version: | 10.2 |
Description
Hi,
I've got a small question about running the UM Nesting Suite on MONSooN: how to set up the Suite so that I can run the nested (LAM) model without rerunning the global one, i.e. using LBC data created by a previous run?
I've tried using *alabc_??? files that I copied from ~/cylc-run/u-ae616/share/cycle/20130324T1200Z/NorwegianSea/km2p2/ukv_default/lbcs/ to MOOSE (see the screenshot attached), but the job install_glm_lbcdata_001 failed with
WARNING: ignoring bad site config /work/home/fcm/cylc-6.11.2/conf/global.rc: Illegal item: [task events]register job logs retry delays Traceback (most recent call last): File "/home/deser/cylc-run/u-ae616/bin/install_lbcdata", line 242, in <module> main(sys.argv[1:]) File "/home/deser/cylc-run/u-ae616/bin/install_lbcdata", line 218, in main end = next(i for i in hours if i >= args.end_hour) StopIteration Received signal ERR cylc (scheduler - 2017-01-19T10:30:42Z): CRITICAL Task job script received signal ERR at 2017-01-19T10:30:42Z cylc (scheduler - 2017-01-19T10:30:42Z): CRITICAL failed at 2017-01-19T10:30:42Z WARNING: ignoring bad site config /work/home/fcm/cylc-6.11.2/conf/global.rc: Illegal item: [task events]register job logs retry delays
Am I using the right files?
Cheers,
Denis
Attachments (1)
Change History (5)
Changed 3 years ago by dsergeev
comment:1 Changed 3 years ago by grenville
Hi Denis
Did you check the help for dm_ic_file and dm_lbs_files — there is some explanation of file names which be useful.
Grenville
comment:2 Changed 3 years ago by dsergeev
Posting S. Webster's reply here for future references:
The LBC data needs to be the LBC creation data generated by the original driving model run, not the LBC file that the LAM reads in.
Also the start dump needs to be the reconfigured start dump generated by the original driving model run, i.e. NOT the original analysis, which is likely to be missing various fields that have been added in recent times.
In a nutshell, dm_ic_file should be glm_astart, and dmc_lbc_files should be umglaa_cb???. So in my case, my rose-suite.conf contains
dm_ic_file="moose:/adhoc/projects/accacia/deser/u-ae616/YYYYmmddTHHMMZ/glm/ics/glm_astart" dm_lbc_files="moose:/adhoc/projects/accacia/deser/u-ae616/YYYYmmddTHHMMZ/glm/um/umglaa_cb???"
comment:3 Changed 3 years ago by dsergeev
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 3 years ago by grenville
Denis
Thanks for this.
Grenville
UM Nesting Suite Driving model Option 4