Opened 9 years ago

Closed 9 years ago

#613 closed help (fixed)

Stash help

Reported by: a.elvidge Owned by: um_support
Component: UMUI Keywords:
Cc: Platform:
UM Version: 7.6

Description

Hi,

I have a couple of stash related queries. In my job xfxkb (on hector vn7.6) I am attempting to output diagnostics more frequently during certain periods of the run. E.g. every 20 mins between hours 14 and 18 of the run (time profile f174_20m). I have used the Specification Type "Regualar intervals Start/Stop? date" option, with Time Units "Timesteps" and frequency every 80 (since my timestep is 15 seconds, this means 20 mins). However, this time profile is failing somehow, since the resulting output files are blank (other than orog and land mask, which are output just once i.e. use a different time profile). Why isn't this working?

Secondly, I would like to copy my stash between jobs. How do I do this? Is this what the 'user stash' options are for? I can't find any instructions on how to do this.

Cheers, Andy

Change History (7)

comment:1 Changed 9 years ago by willie

HI Andy,

For your second point, you need the tool copy_stash, which resides on PUMA in ~umui/umt/vnmain/bin/copy_stash. To use this you need to export the basis files of the two jobs in question. Then

~umui/umt/vnmain/bin/copy_stash basis_joba basis_jobb
a2321

This will modify jobb and then you have to import this.

Regards,
Willie

comment:2 Changed 9 years ago by willie

Hi Andy,

I think what you're doing should work. I suspect that you may need to set the start date in Sub model indep > Start date and Run Length, so that it has a reference time for STASH to work from. Clearly, the date in the start dump isn't being used.

My instructions for copy_stash were not quite clear: it doesn't take any arguments. You are prompted for the basis files instead.

I hope that helps,

Willie

comment:3 Changed 9 years ago by lois

Hello Andy

Having quickly looked at your leave file yesterday before HECToR goes down for maintenance today I think that Willie is probably on the right track. We have no experience of this particular mechanism in the STASH to specify STASH for defined periods and so it will take a bit of investigation to see what it expects for these periods. The fact that it does not print them in your leave file could be just a formatting issue but it does look as though this defined period has not be recognised. If you read the help pages you can see that the issue of date is particularly complicated as there are several ways to reference dates and it is not always clear as to which one takes priority so it might not be a simple as just setting a start date. We will investigate and get back to you as soon as we have some information.

Lois

comment:4 Changed 9 years ago by a.elvidge

It did occur to me that I may need to specify a start date. However, I have actually had the same problem before (about a year ago) with a job in which (Im pretty sure) a start date was set. At the time it wasnt massively important so I made do without the defined periods.

Thanks, Andy

comment:5 Changed 9 years ago by willie

Hi Andy,

You can achieve a more frequent output by dedicating a time profile to this task. If you use the specification 'regular intervals start/stop date' option then you must specify the full date in the panels below and also specify the date of the start dump in the "start date and run length". This will work but there are other problems which make it inadvisable to use.

If you use the specification 'regular intervals', then the starting and ending times are relative to the start of the run.

Regards,

Willie

comment:6 Changed 9 years ago by a.elvidge

Thanks Willie, I will use 'regular intervals'.
Andy

comment:7 Changed 9 years ago by willie

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