different name of echam executable file

[a270105]

I got a similar error as Yuchen reported here: #1117
To run LGM with awiesm2 we use a slightly different echam version for the first year (bootstrap). To keep different executable files in the bin folder they are named like 'echam6_bootstrap' and 'echam6_std'. Before I could use them by including these lines in my runscript:

    executable: echam6_bootstrap
    bin_sources:
            echam_bin: "${bin_dir}/${executable}"
    bin_in_work:
            echam_bin: "${executable}"

But now (in the esm_toold branch 'awiesm-2.6-recom') it does not work and a2o_flux is not written in the run.../work folder and no restart is possible. I tried with different lengths of the filename. So far, the only way to run the simulation is to rename the executable file to the default name 'echam6'. Can somebody explain where in code the filename is related to the writing of a2o_flux, and why it only affects a2o_flux? Thanks.

[mandresm]

Hi @a270105,

Can somebody explain where in code the filename is related to the writing of a2o_flux, and why it only affects a2o_flux?

I cannot explain it at the moment, I've looked at the config files and I don't understand how the change into the name of the binary in work can result in a correct a2o_flux. That been said I also don't have a experiment that I can inspect. It sounds to me that echam6 is hardcoded somewhere on the coupling but I cannot find where. @a270105, can you provide a path to the broken work path so that I can investigate and understand the root of the problem?

What I can explain is how you can get esm_tools to rename echam binary to echam6 (in essence the same thing @YugengChen found to fix the problem). In the echam.yaml bin_sources and bin_in_work are defined as:

esm_tools/configs/components/echam/echam.yaml

Lines 647 to 650 in 8cb480f

	bin_sources:
	"echam_bin": "${bin_dir}/echam6"
	bin_in_work:
	"echam_bin": "echam6"

This is equivalent to saying cp ${bin_dir}/echam6 echam6. What you are doing is instead:

    executable: echam6_bootstrap
    bin_sources:
            echam_bin: "${bin_dir}/${executable}"
    bin_in_work:
            echam_bin: "${executable}"

Which is equivalent to do cp ${bin_dir}/${executable} ${executable}, in summary, the binary in work is going to be echam6_bootstrap and not echam6. Things that you could change here so that you don't run into problems:

1. The bin_in_work already defined by default is already correct so you don't need to overwrite it.
2. I would refrain from changing the value of the executable since we are a bit concerned that this (for some strange reason) might lead to the problems you are seeing.

So your changes should look like:

-    executable: echam6_bootstrap
    bin_sources:
-            echam_bin: "${bin_dir}/${executable}"
+            echam_bin: "${bin_dir}/echam6_bootstrap"
-    bin_in_work:
-            echam_bin: "${executable}"

In that case you would then be doing cp ${bin_dir}/echam6_bootstrap echam6, and that's what you actually want.

Again, I don't understand why the name of the bin in work matters, further investigation is needed :)