Archer2 dump file issue

1

Hi,

I’m trying to starting an Archer2 suite, u-do697, using the dump file /work/n02/n02/jweber/dump_files/u-bl593/bl593a.da19750101_00. However, I keep getting the error message on install_cold

[FAIL] file:/work/n02/n02/jweber/cylc-run/u-do734/share/data/do734a.ainitial=source=/work/n02/n02/jweber/dump_files/u-bl593/dk655a.da20031001_00: [Errno 2] No such file or directory: ‘/work/n02/n02/jweber/dump_files/u-bl593/dk655a.da20031001_00’

It looks the suite is looking for a different dump file - dk655a.da20031001_00 - in the correct directory. This incorrect dump file was the last file used by u-do697 predecessor.

I’m a bit confused as I think I have done everything I usually to see the dump file.

Could you see if I have missed anything?

Many thanks for your help,

James

2

Hi James,

your rose-suite.conf has the correct configuration.

AINITIAL_FILE='bl593a.da19750101_00'

ARCHER2_AINITIAL_DIR='/work/n02/n02/jweber/dump_files/u-bl593'

but all this is being overriden in archer2.rc, where we have

{% set AINITIAL = ARCHER2_AINITIAL_DIR + '/dk655a.da20031001_00' %}

what is happening is that the line above in site/archer2.rc hardcodes the old dump file.

Could you please update line 27 in archer2.rc to:

{% set AINITIAL = ARCHER2_AINITIAL_DIR + '/' + AINITIAL_FILE %}

So it keeps everything configurable via rose-suite.conf. Let
me know how it goes.

Best regards,
Juan

3

Hi Juan,

Of course, that makes sense, I now remember editing the archer2.rc file for predecessors of this suite months ago! Thank you for spotting that.

James

4

Hi Juan,

Just to check, should I leave ainitial recon_technical in app/um as:

ainitial=‘$ROSE_DATA/${RUNID}a.ainitial’ ?

Cheers,

James

5

Hi James,

Yes, you can leave the ainitial setting in app/um as it is. That path will correctly resolve to the symbolic link created during the install_cold. Now points to the right dump file.

So no need to change anything further in app/um.

Best regards,
Juan