Opened 6 years ago

Closed 6 years ago

#1063 closed help (fixed)

Problem running job ximec (copy of xgwtf) on MONSooN

Reported by: yl238 Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: MONSooN
UM Version: 8.2

Description

Hello,

I'm a new user of the UM/Hector/MONSooN, and I've been trying to run the job ximec (a copy of Ros' xgwtf) on MONSooN since 02/05/13. There are basically two problems:

  1. (partially fixed) There was a problem with setting the ancillary version files, as the original values pointed to the non-existent directory /home/odarby/, which is now changed to /home/odarby.old/. I copied the version files in /home/odarby.old/ancil_versions/ to /home/yuliu/ancil_versions/ on ibm02 and changed the path of the version files on the UMUI. After many crashes, I found the file "versions_UM8.2_invert_rivers" unfortunately has the ~odarby/ directory hard-coded into it.

I'm wondering whether it's possible to have a central ancillary version directory on MONSooN so this doesn't happen in the future when people leave? Or is this simply something I need to check each time I use another person's files?

  1. After fixing this, after some trial and error, I compiled the code and reconfiguration with alrfq.astart in $STARTDUMPS (already specified) and ran the job and reconfiguration. This seemed to have worked (/home/yuliu/output/ximec000.ximec.d13126.t115935.leave).

Can you advise if this is the right sequence to run a continuation job anew?

  1. The output file gave a long list of warnings about "Diagnostics not available" e.g see below:

???????????????????????????????????????????????????????????????????????????????
??????????????????????????????????? WARNING ????????????????????????????????????
? Warning in routine: PRELIM
? Warning Code: -30
? Warning Message: DIAGNOSTIC NOT AVAILABLE TO THIS VERSION REQUEST DENIED (M,S,I) 1 0 95
? Warning generated from processor: 0
????????????????????????????????????????????????????????????????????????????????
Are these of significance and how to fix them?

Many thanks for your help,

Sue

Change History (6)

comment:1 Changed 6 years ago by willie

Hi Sue,

Advice on doing continuation runs can be found at http://cms.ncas.ac.uk/wiki/FAQ_T0_F2

The warnings are not significant. You can get rid of them by deselecting the items on the STASH page: double click on the "Y" in the include column.

Regards,

Willie

comment:2 Changed 6 years ago by ros

Hi Sue,

Regarding the ancillary files on MONSooN. There is a central ancillary directory under $UMDIR and I will check that all the required files are there and if not get things synchronized. Thanks for letting us know.

Regards,
Ros.

comment:3 Changed 6 years ago by ros

Hi Sue,

The equivalent directory is under $UMDIR/ancil_versions and all the relevant files are there and identical to those which were in Oliver's directory. I've updated my xgwtf job accordingly.

Regards,
Ros.

comment:4 Changed 6 years ago by yl238

Thank you for your help. Knowing the location of the central directory is most helpful.

I have another question: the run makes use of the startdump "alrfq.astart" in $STARTDUMPS (set to be /projects/user_ancil/N96/atmos/start_dumps/v1) and the job starts on 01/09/1981. Suppose that I would like to start running from 01/10/1991. I understand I can use the same startdump and change the year by turning on reconfiguration, but not change the date. What is the standard thing to do? Is it to run the job for a month and dump the data at the end of it, and then use it as the new startdump and store this in my own directory, or is there a central startdump "store" where I can find suitable startdumps (at least for 01 Jan, April, Sep and Dec)?

comment:5 Changed 6 years ago by willie

Hi Sue,

I can get you a start dump based on ECMWF ERA-Interim data. Just let me know the date and time (0,6, 12, 18Z). If the date is within the past five years I could get a Met Office global start dump.

Regards,

Willie

comment:6 Changed 6 years ago by willie

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.