Validity Time Mismatch

Unified Model
1

Dear CMS Helpdesk,

I’m encountering an error during the postproc for suite u-dr920:

Validity time mismatch in file /work/n02/n02/ajw1g19/cylc-run/u-dr920/share/data/History_Data/dr920a.pm18500101 to be archived
	--> Expected [1850, 1, 1, 0, 0, 0] and got [1850, 2, 1]

Could you please advise?

Thanks,
Alfred

2

Hi Alfred,

Sorry for the delay. I had to refamiliarise myself with the postprocessing code to see what was going on.

The problem is because of the climate meaning settings in the suite in combination with you setting a .pm stream in STASH.

Unfortunately in the code having create_means = false and create_monthly_mean=false has caused it to go into a part of the code it shouldn’t when it identifies it is dealing with a monthly mean file.

I would suggest as a workaround one of the following 2 options:

  1. Try setting create_means = true but leaving create_monthly_mean = false as well as the seasonal & yearly assuming you don’t want them either.
    or
  2. Change the .pm stream to some other letter

I haven’t been able to test option (1) fully in your suite as there a couple of issues with the setup of it for it to run under cylc8.

  1. For the cylc-run directories to be setup correctly on ARCHER2 we need to have remote_setup task in our suites. See: Upgrading to Cylc 8
  2. All code branches must refer to the mirrors not the MOSRS repos so make sure they are fcm:um.xm-br not fcm:um.x-br, etc
  3. There’s an execution time limit in the wrong place. I can’t remember which file; but when you try to run with cylc8 it’ll tell you there is a syntax error.

Cheers,
Ros.

3

Hi Ros,

Could you explain in more detail where to add the remote_setup tasks in the flow.cylc file?

Thanks,
Alf

4

Hi Alfred,

I’ve just looked at your suite and everything you have added is correct. The only thing missing in the flow.cylc file is that task remote_setup needs to be added before any (ie. all) fcm_make tasks. So in your suite you also need to add remote_setup => in the graph before both the fcm_make_pp and fcm_make_pptransfer tasks.

Once you’ve done that I think the directory symlinks should be setup correctly on ARCHER2.

Cheers,
Ros.