INITIAL_4A error

General
1

I am trying to run a suite that has previously worked fine (u-dk323) and am getting the following error during the atmos_main job:

???!!!???!!!???!!!???!!!???!!! ERROR ???!!!???!!!???!!!???!!!???!!!
? Error code: 102
? Error from routine: INITIAL_4A
? Error message: INITDUMP: Wrong no of atmos prognostic fields
? Error from processor: 0
? Error number: 67

I previously tried adding a new tracer, but have since reverted both the UM and UKCA branch back to the version before the addition. Any ideas why I could be getting this error?

I have also tried running in two other suites, with different start dumps, and get the same error.

Additionally, when I load the rose suite (rose suite edit) the following error occurs in the terminal:

[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_requests.py: Traceback (most recent call last):

FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_requests.py”, line 37, in
[FAIL] from custom_monsoon_xc40_cmp_to_key import custom_monsoon_xc40_cmp_to_key as cmp_to_key
[FAIL] ImportError: No module named custom_monsoon_xc40_cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_indices.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_indices.py”, line 75, in
[FAIL] from custom_monsoon_xc40_cmp_to_key import custom_monsoon_xc40_cmp_to_key as cmp_to_key
[FAIL] ImportError: No module named custom_monsoon_xc40_cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_streams.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_streams.py”, line 31, in
[FAIL] from custom_monsoon_xc40_cmp_to_key import custom_monsoon_xc40_cmp_to_key as cmp_to_key
[FAIL] ImportError: No module named custom_monsoon_xc40_cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_naming.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_naming.py”, line 19, in
[FAIL] from custom_monsoon_xc40_cmp_to_key import custom_monsoon_xc40_cmp_to_key as cmp_to_key
[FAIL] ImportError: No module named custom_monsoon_xc40_cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/profile_names.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/profile_names.py”, line 25, in
[FAIL] from custom_monsoon_xc40_cmp_to_key import custom_monsoon_xc40_cmp_to_key as cmp_to_key
[FAIL] ImportError: No module named custom_monsoon_xc40_cmp_to_key

Thanks for any help!

2

Hi Isabella

I see that you have used a different UM app metadata source - have all the problems been fixed?

Grenville

3

Hi Grenville,

I did that to try and debug, but I think I need to use my branch as the UM app meta data source in order to have the correct STASH included, is that right?

Should my branch of the um (vn13.4_nat_psc_mods) have the “custom_monsoon_xc40_cmp_to_key” module? I see that it is a part of the UM trunk, but it isn’t in my branch.

Thanks,
Isabelle

4

Hi Isabelle

I am confused - as far as I can see, your branch came from the trunk at version 13.4, which does not make reference to custom_monsoon_xc40_cmp_to_key. Following the development of your branch shows that reference to custom_monsoon_xc40_cmp_to_key crept in at revision 122596. I assume that any rose suite was using metadata from the 13.4 trunk otherwise you would have seen the problem with rose edit at that time.
Any idea why you used python code that included custom_monsoon_xc40_cmp_to_key ?

A solution may be to add custom_monsoon_xc40_cmp_to_key.py to your branch - but that’d need testing.

Grenville

5

Hi Grenville,

When I look at the UM trac page there is : custom_monsoon_xc40_cmp_to_key.py in the main/trunk/rose-meta/um-atmos/HEAD/lib/python. If I try to open the rose gui without the custom_monsoon_xc40_cmp_to_key.py lines that were added at revision 122596, then I get the error copied below in the terminal. I think this is why I added the custom_monsoon_xc40_cmp_to_key lines.

[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_requests.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_requests.py”, line 34, in
[FAIL] from functools import cmp_to_key
[FAIL] ImportError: cannot import name cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_indices.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/stash_indices.py”, line 72, in
[FAIL] from functools import cmp_to_key
[FAIL] ImportError: cannot import name cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_streams.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_streams.py”, line 28, in
[FAIL] from functools import cmp_to_key
[FAIL] ImportError: cannot import name cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_naming.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/output_naming.py”, line 16, in
[FAIL] from functools import cmp_to_key
[FAIL] ImportError: cannot import name cmp_to_key
[FAIL] Could not load macro /home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/profile_names.py: Traceback (most recent call last):
[FAIL] File “/common/fcm/rose-2019.01.7/lib/python/rose/macro.py”, line 747, in load_meta_macro_modules
[FAIL] modules.append(imp.load_source(as_name, meta_file))
[FAIL] File “/home/d03/isangha/vn13.4_nat_psc_mods/rose-meta/um-atmos/HEAD/lib/python/macros/profile_names.py”, line 22, in
[FAIL] from functools import cmp_to_key
[FAIL] ImportError: cannot import name cmp_to_key

6

Isabelle

Is this problem fixed?

Grenville

7

Hi Grenville,

Yes - including the ‘custom_monsoon_xc40_cmp_to_key’ script to the branch fixed the issue.

Thanks!

8

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