Opened 5 weeks ago

Closed 3 weeks ago

#2957 closed help (fixed)

Reload u-bj538 with extra startdumps

Reported by: xd904476 Owned by: um_support
Component: UM Model Keywords:
Cc: Platform: ARCHER
UM Version: 10.7

Description

Hi, I would like to write some extra startdumps for suite u-bj538.
I can see that inn the UM settings the model writes them out every 10 days (dumpfrequency), but I can't see them on Jasmin or the RDF. I would like startdumps to be saved on jasmin every 3 months. Shall I change this in the pp transfer? I can't find it, sorry. I would need some help.
Thanks,
Dani

Change History (4)

comment:1 Changed 5 weeks ago by willie

  • Platform set to ARCHER
  • UM Version set to 10.7

Hi Dani,

The start dumps are stored in your cylc-run share/data/History_Data with names like bj538a.da20251211_00. In postproc > Atmosphere, the archiving frequency is set to timestamps which is defined later just to be December and January the first. You could select Monthly, instead, and repeat your run.

Willie

comment:2 Changed 5 weeks ago by xd904476

Hi Willie, thanks.
I did find the january and december restart, but I did not know how to add the others.
I have now changed the timestamp to
[namelist:archiving]
arch_dump_freq=Timestamps
arch_dump_offset=0
arch_timestamps=12-01,01-01,06-01
!!arch_year_month=December
archive_dumps=true
archive_pp=true
archive_switch=true

this is to add the month of June of course.
If I wanted to carry on with the suite without restarting it, can I just run the reload command "rose suite-run —reload", or shall I start the suite again? It has only run for a few years.

thanks,
dani

comment:3 Changed 5 weeks ago by willie

Hi Dani,

If it has been running for a few years then you will have missed several Junes. If the model is still running and you can see that it is not archiving, then I think you can get away with --reload. It will then archive every on the first of every December, January and June after the current model time, whatever that was. In general you should avoid doing this because the model output will not agree with the (changed) suite.

If the model has stopped, then you need to use --restart to pick up from where it left off.

But in this case I think it is easiest to start from the beginning.

Willie

comment:4 Changed 3 weeks ago by willie

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