ERROR CODE is 2014 NetCDF: Invalid dimension ID or name – in #8: General Questions

please help me. Im stuck

  @sinclairchinyoka in #553143b

please help me. Im stuck

Can you try to increase the debug level:
e.g. idbg_level=20
(in the int2lm control section)
Maybe this tells you more.

  @andreasdobler in #cd18b89

Can you try to increase the debug level:
e.g. idbg_level=20
(in the int2lm control section)
Maybe this tells you more.

Did you have a look at the ASCII file “ YUCHKDAT ” created by INT2LM.
Already the data of the external data set (first entries in the file) look strange.
Everything is zero or even undefined.

You should check the external data set first!

  @hans-jürgenpanitz in #1e6a4fe

Did you have a look at the ASCII file “ YUCHKDAT ” created by INT2LM.
Already the data of the external data set (first entries in the file) look strange.
Everything is zero or even undefined.

You should check the external data set first!

i made the changes and have more debug lines. see attachment

  @sinclairchinyoka in #7b1ceb4

i made the changes and have more debug lines. see attachment

Increasing the debug level does not give more information.
See my previous comment and check the external data set (zimbawe.nc)

  @hans-jürgenpanitz in #c7396e8

Increasing the debug level does not give more information.
See my previous comment and check the external data set (zimbawe.nc)

Okay thank you very much. I checked the file. I used the same external file with ncep1 data from 1980-2015 and its working.
I attached the file information

  @sinclairchinyoka in #7ab50e1

Okay thank you very much. I checked the file. I used the same external file with ncep1 data from 1980-2015 and its working.
I attached the file information

But when running int2lm with CNRM -CM5 data from 2018 thats when i get this error

  @sinclairchinyoka in #7fc6e78

But when running int2lm with CNRM -CM5 data from 2018 thats when i get this error

Can you provide the whole file (zimbawe.nc) or some values (cdo infov zimbawe.nc)?

  @andreasdobler in #96812aa

Can you provide the whole file (zimbawe.nc) or some values (cdo infov zimbawe.nc)?

Okay. I have attached the infomation

  @sinclairchinyoka in #46af443

Okay. I have attached the infomation

this external data set does certainly not cover Zimbawe or any other land area in the world.
The region represented by the data seems to be somewhere over the ocean.
HUSRF=FIS=0, T_CL not defined, soiltype=9, FR_LAND=0, FOR _D=FOR_E=LAI=PLCOV=0, etc, etc; all these values indicate that the whole area is covered by water at Sea Level.

I guess, this is not what you really want, isn’t it?

  @hans-jürgenpanitz in #cab1247

this external data set does certainly not cover Zimbawe or any other land area in the world.
The region represented by the data seems to be somewhere over the ocean.
HUSRF=FIS=0, T_CL not defined, soiltype=9, FR_LAND=0, FOR _D=FOR_E=LAI=PLCOV=0, etc, etc; all these values indicate that the whole area is covered by water at Sea Level.

I guess, this is not what you really want, isn’t it?

Very true. Thats not what i want. My domain should be Zimbabwe. Let create a new external Data and try again.

Thank you very much. Maybe its because im failing to create the external data. Im new in cosmo-clm

  @sinclairchinyoka in #50b998c

Very true. Thats not what i want. My domain should be Zimbabwe. Let create a new external Data and try again.

Thank you very much. Maybe its because im failing to create the external data. Im new in cosmo-clm

Yes, these values can not be correct (e.g HSURF is equal to zero).
I see the same in your NCEP driven runs.

  @andreasdobler in #58b9713

Yes, these values can not be correct (e.g HSURF is equal to zero).
I see the same in your NCEP driven runs.

Thank you once again. Can you help me to create a right external data. These ones i created them using WebPEP.

  @sinclairchinyoka in #0ac3271

Thank you once again. Can you help me to create a right external data. These ones i created them using WebPEP.

o.k.
I now realized (by converting the rotated pole indicated in the ncdump of your ext. data to geographical coordinates, using the tools in Web_PEP) that the origin of your rotated system is
more or less in the centre of Zimbawe. That’s o.k.
But your mistake was the definition of startlon and starlat. They have to be given in rotated coordinates, not in geographical ones as you did. Therefore, your model domain
was over the ocean south-east of Madagascar.
I attach a screen-shot of Web-Pep page with corrected settings of startlon and startlat, keeping the geographical coordinates of the origin of your rotated system and also the number of
grid-points. This is only a suggestion.

Please, note that there is a “preview” button in the Wep- PEP page, which creates a plot of the region that corresponds to your settings.
Thus, you can check whether your settings make sense or not

  @hans-jürgenpanitz in #145f6f7

o.k.
I now realized (by converting the rotated pole indicated in the ncdump of your ext. data to geographical coordinates, using the tools in Web_PEP) that the origin of your rotated system is
more or less in the centre of Zimbawe. That’s o.k.
But your mistake was the definition of startlon and starlat. They have to be given in rotated coordinates, not in geographical ones as you did. Therefore, your model domain
was over the ocean south-east of Madagascar.
I attach a screen-shot of Web-Pep page with corrected settings of startlon and startlat, keeping the geographical coordinates of the origin of your rotated system and also the number of
grid-points. This is only a suggestion.

Please, note that there is a “preview” button in the Wep- PEP page, which creates a plot of the region that corresponds to your settings.
Thus, you can check whether your settings make sense or not

Thank you very much. It really makes sense. Let me try that

  @sinclairchinyoka in #479204c

Thank you very much. It really makes sense. Let me try that