R7B6 Dateline with Nest

[drieg]

ICON External Parameter Request

Instructions

1. Give this issue a meaningful title.
2. Replace PASTE_YOUR_REQUEST_HERE with your request that you copied to clipboard:

{
  "extpar": {
      "igrid_type": 1,
      "iaot_type": 1,
      "ilu_type": 1,
      "ialb_type": 1,
      "isoil_type": 1,
      "itopo_type": 1,
      "lsgsl": false,
      "lfilter_oro": false,
      "lurban": false
  },
  "icontools": {
    "grid_level": 5,
    "grid_root": 7,
    "centre": 78,
    "subcentre": 255,
    "lspring_dynamics": true,
    "maxit": 1000,
    "beta_spring": 0.95,
    "outfile": "ICON-Dateline",
    "domains": [
      {
        "region_type": 3,
        "center_lon": -170.0,
        "center_lat": 22.0,
        "hwidth_lon": 20.0,
        "hwidth_lat": 6.5,
        "lrotate": false
      },
      {
        "region_type": 3,
        "center_lon": -160.0,
        "center_lat": 22.0,
        "hwidth_lon": 10.0,
        "hwidth_lat": 5.0,
        "lrotate": false
      }
    ]
  }
}

3. Click on "Preview" to verify that the JSON format of your request is correctly formatted and displayed within a code block.
4. Click on "Submit new issue".

Extpar Data Request will now process your data based on the request you provided here. Once the processing is successful, it will post a link in this issue.
The processed data will be available under that link for up to 7 days.

If you encounter any problems, please add the label to the issue. Make sure you post all relevant information from the logfiles in the issue directly.

Status Labels

Labels reflect the current state of your request:

- Your request is currently under processing. Please wait for further updates.

- Your request has been successfully processed. You can download your data using the provided link.

- Unfortunately, your request could not be processed. Please refer to the log files in the zip file at the download link for more details.

- Your request was aborted. This might be due to a timeout. Please try again or contact support if the problem persists.

[jenkins-apn]

Your data is ready for up to 7 days under this link.

[drieg]

@jonasjucker I tried to use this data set in ICON. I should point out that didn't try any of the previous ones in ICON, up to now was only eyeball comparison. There seems to be something odd with the lakes (i.e. there are lakes but the depth is -1 for the full domain):

    25 : 1111-01-11 00:00:00       0    50280       0 :      0.0000  4.7655e-06    0.079963 : FR_LAKE
    26 : 1111-01-11 00:00:00       0    50280       0 :     -1.0000     -1.0000     -1.0000 : DEPTH_LK

I also see this behavior in other datasets. Is there something wrong with the extpar namelists?

[drieg]

Sorry, my bad. I checked only a similar case. In the other cases I do not see this error. So this seems somehow to be related to the chosen region and resolution I guess. Has this every happened before?

[jonasjucker]

No I did not receive similar reports.
I think usually people do not really check Extpar output.

[drieg]

Well, ICON fails. I guess that I hit a spot with too 'high' resolution where some lakes are resolved without depth information and noone has ever tried this resolution for this part of the world. I will try R3B7N8, if my theory is correct, R3B7 should work and as soon as I add the R3B8 nest it will crash

[drieg]

I can confirm that R3B7 works and R3B8 does not work. So I guess no one ever tested this region before and there is something wrong with the original dataset, the interpolation or, most likely, the consistency check (since depth_lk should have a dummy value in case of fr_lake above a certain threshold).

I will forward this to my extpar and flake colleagues...