Open joakimkjellsson opened 4 years ago
I had the same problem with FOCI and just renamed the exectutable (nemo.exe --> oceanx) after compilation. See setup2models.yaml
Hi guys...currently, the coupler is hard coded to use the name under executable
. We can change that to allow the configuration to also specify a coupler name, which would be used if defined, and otherwise it will use the executable name.
@joakimkjellsson: do you have a preference? coupler_name
? You'd have to put in your OpenIFS.yaml:
model: oifs
#... other stuff ...
coupler_name: oifs
executable: master.exe
Hi Paul Something like "coupler_name" would make a lot of sense! Cheers Joakim
(1.5 years later...) Did this ever get taken care of? I am making my to-do list for next week. If not, I will add it for Monday.
Hi Paul
I don't think so. Currently we do what @seb-wahl said, i.e. rename the executables. It's not a priority to solve this as far as I'm concerned, but if it's a fast fix, then I recommend using the "coupler_name" as above, and setting it to be e.g. "oifs", "oceanx" etc by default to make sure nothing breaks.
Cheers Joakim
Hi y'all
I started working on focioifs (OpenIFS+NEMO+XIOS+Runoffmapper) and realised that the way ESM-Tools are written we assume that the executable name, i.e. what is generated when compiling, is the same as the model name when OASIS_INIT_COMP is called and what is written under "NBMODEL" in namcouple.
Typically I would write
in namcouple, but the executables are named "nemo.exe", "master.exe" and "rnfmap.exe". But now I get
in the namcouple file and OASIS can't connect these names with what is sent to OASIS_INIT_COMP from the models.
Is there a way to specify a model name under NBMODEL that is not the same as the executable name?
Cheers Joakim