Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

esm_master get-awiesm3-v3.4 gives no feedback #1230

Open
hajlaci opened this issue Oct 14, 2024 · 4 comments
Open

esm_master get-awiesm3-v3.4 gives no feedback #1230

hajlaci opened this issue Oct 14, 2024 · 4 comments
Assignees
Labels
bug Something isn't working error handling better error output required

Comments

@hajlaci
Copy link

hajlaci commented Oct 14, 2024

@JanStreffing and I implemented https://github.com/esm-tools/esm_tools/tree/feat/awiesm3-v3.4
The command
esm_master get-awiesm3-v3.4
results in an empty response. Esm master seemingly finishes the command without anything being done. Nothing is listed for download, nothing is downloaded. We tested this on levante. esm_master without any model does list awiesm3-v3.4 and the get command as available.

Here is what a wrong version will look like

esm_master get-awiesm3-v3.5

No targets found for keyword awiesm3-v3.5. Type 'esm_master' to get a full list
of available targets.
@mandresm mandresm added bug Something isn't working error handling better error output required labels Oct 21, 2024
@mandresm
Copy link
Contributor

So ESM-Tools is not reporting an error, and simply exiting. We will fix that in a new merge request.

The problem is that the grids for the LPG-GUESS coupling fields are not defined. Here you are mapping fields from LPG-GUESS to OpenIFS:

vegin.nc:
- 'LAILVeg:LAIHVeg:FracLVeg:FracHVeg:TypeLVeg:TypeHVeg <--loc_avg-- GUE_LLAI:GUE_HLAI:GUE_TYPH:GUE_FRAH:GUE_TYPL:GUE_FRAL'
- 'T2M_LPJG:TPRE_LPJ:SNOC_LPJ:SNOD_LPJ <--loc_avg-- T2MVeg:TPVeg:SDVeg:SDensVeg'
- 'ST1L_LPJ:ST2L_LPJ:ST3L_LPJ:ST4L_LPJ <--loc_avg-- SoilTVeg.L001:SoilTVeg.L002:SoilTVeg.L003:SoilTVeg.L004'
- 'SM1L_LPJ:SM2L_LPJ:SM3L_LPJ:SM4L_LPJ <--loc_avg-- SoilMVeg.L001:SoilMVeg.L002:SoilMVeg.L003:SoilMVeg.L004'
- 'SWNR_LPJ:LWNR_LPJ:SHUM_LPJ:SPRE_LPJ:WSPD_LPJ <--loc_avg-- SSRVeg:SLRVeg:SHUMVeg:PRESVeg:WSPDVeg'
- 'TMIN_LPJ <--loc_min-- TMINVeg'
- 'TMAX_LPJ <--loc_max-- TMAXVeg'

However, you have not defined grids for these fields, and without that oasis and oasis.py cannot work. You have partially already done that here:

atm_veg_fields: [TODO]
coupling_fields:
"[[atm_oce_fields-->FIELD]]":
grid: atma
"[[atm_veg_fields-->FIELD]]":
grid: atma

In principle all you need to do is to change the TODO by the list of fields in oifs related to this new coupling, and do the same for lpg_guess for its fields as well.

@mandresm
Copy link
Contributor

Note that this is a problem that should not need to pop-up during esm_master since it should only take care of the compilation part and not care about the coupling part, which belongs to esm_runscripts. So, if you want a workaround for now and deal with the problem later on when you are working on running the coupled version, simply comments these lines:

vegin.nc:
- 'LAILVeg:LAIHVeg:FracLVeg:FracHVeg:TypeLVeg:TypeHVeg <--loc_avg-- GUE_LLAI:GUE_HLAI:GUE_TYPH:GUE_FRAH:GUE_TYPL:GUE_FRAL'
- 'T2M_LPJG:TPRE_LPJ:SNOC_LPJ:SNOD_LPJ <--loc_avg-- T2MVeg:TPVeg:SDVeg:SDensVeg'
- 'ST1L_LPJ:ST2L_LPJ:ST3L_LPJ:ST4L_LPJ <--loc_avg-- SoilTVeg.L001:SoilTVeg.L002:SoilTVeg.L003:SoilTVeg.L004'
- 'SM1L_LPJ:SM2L_LPJ:SM3L_LPJ:SM4L_LPJ <--loc_avg-- SoilMVeg.L001:SoilMVeg.L002:SoilMVeg.L003:SoilMVeg.L004'
- 'SWNR_LPJ:LWNR_LPJ:SHUM_LPJ:SPRE_LPJ:WSPD_LPJ <--loc_avg-- SSRVeg:SLRVeg:SHUMVeg:PRESVeg:WSPDVeg'
- 'TMIN_LPJ <--loc_min-- TMINVeg'
- 'TMAX_LPJ <--loc_max-- TMAXVeg'

@pgierz
Copy link
Member

pgierz commented Oct 21, 2024

Note that this is a problem that should not need to pop-up during esm_master

So now I have another one to add to my box of reasons why esm_master is badly designed internally. See #1237

@mandresm
Copy link
Contributor

Hi @hajlaci and @JanStreffing, I have pushed a fix to your branch. It does not solve the problem but at least now you'll get the error. The reason why you were not seen the error before was because the logger was broken, and now it is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working error handling better error output required
Projects
None yet
Development

No branches or pull requests

3 participants