Opened 7 months ago

Closed 6 months ago

#2742 closed help (fixed)

Nesting suite in free-running mode

Reported by: peterh Owned by: willie
Component: Nesting Suite Keywords: start data
Cc: Platform: ARCHER
UM Version: 11.1

Description

I'm testing out the nesting suite on ARCHER, following the instructions
on https://code.metoffice.gov.uk/trac/rmed/wiki/suites/nesting/worked_eg_2018.

This all worked fine, but now I'd like to switch to a free-running mode. I've ticked 'FREE_RUN' in the 'cycling options'. However, the suite fails at
install_glm_startdata for 20150324T0000Z which is the day after the starting conditions which are 20150323. Can anyone explain what I'm doing wrong please?
Many thanks.

Change History (17)

comment:1 Changed 7 months ago by grenville

Hi Peter

Is this still a problem — if so, please tell us the suite id and machine it's on.

Grenville

comment:2 Changed 7 months ago by peterh

Hi Grenville,
It's u-bf065 on ARCHER.
Thanks,
Peter

comment:3 Changed 7 months ago by grenville

Peter

/home/n02/n02/ggpoh/cylc-run/u-bf065/log/job/20150324T0000Z/install_glm_startdata/01/job.out says:

Source /work/y07/y07/umshared/um-training/NS2018/2015032400_glm_t+0 does not exist

because the value of FREE_RUN is set to false in the Optional override file. Edit opt/rose-suite-ncas.conf:FREE_RUN=false, to say true.

Grenville

comment:4 Changed 7 months ago by peterh

Grenville, I've made that change, cleared out the cylc directory on ARCHER and I'm getting the same error.

From my limited understanding(!), I think I need new initial conditions for the global model for this next cycling period? Only the 20150323 are available in the Nesting suite tutorial example I'm running from (/work/y07/y07/umshared/um-training/NS2018/). Do you know if there are further timesteps on ARCHER somewhere already?

Many thanks.

comment:5 Changed 7 months ago by grenville

Peter

I don't see the same error - it looks like your suite had a communication error, see /home/peterh/cylc-run/u-bf065/log/suite/log

is your ssh agent still running on PUMA

Grenville

comment:6 Changed 7 months ago by grenville

Hmmm - something going on here which I don't understand (other than ssh)

Grenville

comment:7 Changed 7 months ago by peterh

I tried re-running the ancil generation and then re-running the suite in free-run mode. I'm not sure whether this will help though?

comment:8 Changed 7 months ago by peterh

This gives the same error for 'install_glm_startdata'. I'm suppose this means that I need these extra external global fields at all timesteps that the nesting suite is set to run for?

comment:9 Changed 7 months ago by grenville

Peter

I have been confused by this though misunderstanding what FREE RUNNIG means. You're right - you will need more global start files. We don't keep them, but you can request some though us.

Grenville

comment:10 Changed 7 months ago by peterh

Excellent, OK can I request them here? If so, eventually I'd like to run from say July 15th to September 15th 2016. Thanks again.

comment:11 Changed 7 months ago by willie

  • Keywords start data added
  • Owner changed from um_support to willie
  • Platform set to ARCHER
  • Status changed from new to assigned
  • UM Version set to 11.1

Hi Peter,

Do you need daily start dumps at 0Z for the whole period? MASS is down at the moment. I'll start to retrieve these when it's back up.

Willie

comment:12 Changed 7 months ago by willie

That's about 60 files at 25GB each, so you'll need about 1.5 TB storage just for these.

Willie

comment:13 Changed 7 months ago by peterh

My work directory is 0.75 TB … what's the best way to do this? Can they be stored on the RDS?

Also, eventually I want to run a nesting suite with different solar insolation. Do you know how I could generate the 0Z dumps for this? Is there a global setup I can run on ARCHER?

Many thanks.

comment:14 Changed 7 months ago by willie

Hi Peter,

If you want to do a complete run through the start dumps then you will need them all to be on /work. So you need to estimate how much space the run will take. You can do this by scaling up a shorter run. Then put in a ticket asking for more quota on ARCHER if necessary. After the run is complete you can move the data onto the RDF, if you have no further use for the compute nodes.

I don't know about the solar insolation. In the model UM Science Settings → Planet constants you can change the solar irradiance at 1AU (currently set to 1361 W/m2), but the other changes that might be required by this are not clear to me.

Willie

comment:15 Changed 7 months ago by peterh

Is there a suite and STASH I copy to run to generate the required global dumps? I think I know how to alter the insolation as we have done this with GC3 previously.

I think I will start with a 5 day run to estimate the space requirements in the first instance.

Thanks.

comment:16 Changed 6 months ago by willie

Hi Peter,

You data is now ready on the RDF in /nerc/n02/shared/wmcginty/data/2742/. Please copy it to your own workspace as soon as possible. You will need to copy this data onto /work in order to run the UM.

Willie

comment:17 Changed 6 months ago by willie

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