Initialising ocean passiver tracers

1

Hi,

I’m trying to initialise a coupled run (u-dl297) and I wanted to check how initialise the ocean passive tracer section correctly. In app/ocean_passive_tracers/rose-app.conf, I have set:

TOP_START=${ROSE_DATA}/${RUNID}o.restart_trc.nc
TOP_TO_INIT=/projects/ukesm/jamwe/AINITIAL/CH4_emission_runs/br744o_20650101_restart_trc.nc

However, I see that in other suites (e.g. u-br700), TOP_START is initialised and TOP_TO_INIT is left “unset”

TOP_START=/data/d01/hadgf/HCCP6.2.2/ensembles/u-bl593/bl593o_20150101_restart_trc.nc
TOP_TO_INIT=unset

Is there is a difference between these two approaches?

Thanks,

James

2

Just an update on this, when I tried the u-br700 way of doing things in a new suite (u-dl626), both

TOP_START=/projects/ukesm/jamwe/AINITIAL/CH4_emission_runs/br700o_20650101_restart_trc.nc
TOP_TO_INIT=

and

TOP_START=/projects/ukesm/jamwe/AINITIAL/CH4_emission_runs/br700o_20650101_restart_trc.nc
TOP_TO_INIT=unset

failed on init_cfc_age_dump

[FAIL] add_CFC_AGE_IDTRA_to_dump: in_file is not set.
2024-12-09T18:05:46Z CRITICAL - failed/EXIT

So I’m a bit confused as to how u-br700 was run in the first place .

James

3

James

I suggest that you contact the UKESM team - how passive tracers are initialised seems to involve some logic that isn’t clear from the suite.

I’d try Jeremy Walton, or Robin, or Marc Stringer. They should be able to point you in the right direction.

Grenville

4

Thanks, Grenville, will do.

James

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.