Opened 10 years ago
Closed 10 years ago
#585 closed error (fixed)
Cannot get new 1.5km LAM domain to run
Reported by: | cbirch | Owned by: | um_support |
---|---|---|---|
Component: | UM Model | Keywords: | LAM new domain |
Cc: | Platform: | ||
UM Version: | 7.1 |
Description
Hi,
I am trying to set up a new 1.5km LAM domain over the Sahara. I have been successfully running Grenville's vn7.1 12km and 4km Cascade jobs over the Sahel. I changed the domain of these to be over the Sahara desert and have run them successfully to get the LBCs for the 1.5km job. I then changed the location and reduced the size of Grenville's 1.5km cascade job to a region over the Sahara. This is job xftdh. It failed with the error below (xftdh000.xftdh.d11049.t113306.leave), which isn't too helpful:
/work/n02/n02/hum/vn7.1/pathscale_quad/scripts/qsmaster: Failed in qsexecute in model xftdh
Thanks,
Cathryn
Change History (3)
comment:1 Changed 10 years ago by grenville
comment:2 Changed 10 years ago by cbirch
Hi Grenville,
Copying the bin directory as you suggested in ticket 584 worked and the 1.5 km resolution domain works now.
Thanks a lot, you can close this ticket now.
Cathryn
comment:3 Changed 10 years ago by ros
- Resolution set to fixed
- Status changed from new to closed
Hi Cathryn,
The problem with the absence of a $DATAW/bin directory has been tracked down to a bug in the UMUI. The variables set in the "Defined Environment Variables for Directories" table in UMUI window Input/Output? Control and Resources → Time Convention and SCRIPT environment variables weren't being exported in the job compile script. So if a variable in this table was used to define $DATAW (e.g. $DATA_OUT) then the script wouldn't know anything about it.
All variables defined in the above table are now exported in the compile script and the problem has been fed back to the Met Office.
If you do encounter any more problems with the bin directory not being correctly made, please let us know.
I would also recommend that you add the following lines to your .profile to ensure that the environment variables $DATADIR and $WORKDIR are available for use in the compile job scripts.
export UMDIR=/work/n02/n02/hum TARGET_MC=pathscale_quad # Setup UM Variables VN=7.1 if test -f $HOME/.umsetvars_$VN; then . $HOME/.umsetvars_$VN else . $UMDIR/vn$VN/$TARGET_MC/scripts/.umsetvars_$VN fi
Regards,
Ros.
Cathryn
Same problem with the absence of a bin directory where its expecting to find your executable.
Grenville