SVN

Abigail Birago Adomako

Your error means the SST file is corrupted. Probably the result of the sst command has not been successful. If you share the terminal output when you run the sst command, I can help you better.

Actually, the SST was successful and it produced the SST input file. If the input file is corrupted, what can I do about it or how do I resolve that?

I cannot help unless I see the result of the sst command.

Input ready at : Sun Jan 1 16:33:26 2023

Successfully generated SST

The above was the feedback. I just run it again

I run the sst command for one day, and you can see my result in the attachment. I am looking for something like this.

Morteza Babaei

Do you mean like the attached?

Or this one?

Morteza Babaei

I changed the central longitude and latitude and I am getting a new error. Could you please take a look?

This is icbc part of the RegCM version 4

SVN Revision: 4.7.1-1027-g0c9c8 compiled at: data : Oct 8 2021 time: 04:29:07

: this run start at : 2023-01-03 06:59:39+0000

: it is submitted by :

: it is running on :

: in directory :

Using Moloch non-hydrostatic dynamical core

GLOBIDATE1 : 2017-01-01 00:00:00 UTC

GLOBIDATE2 : 2018-01-01 00:00:00 UTC

NSTEPS : 1461

Computing weights................ Done.

Computing weights................ Done.

Computing weights................ Done.

131072 data/ERA5/2017/tatm_2017_01.nc 1.8651047010219326E-003 248.48718848036432

196608 data/ERA5/2017/geop_2017_01.nc 7.5211966278559084 245155.51259504544

262144 data/ERA5/2017/qhum_2017_01.nc 2.9496156507563046E-007 9.6659518359635752E-003

327680 data/ERA5/2017/uwnd_2017_01.nc 2.4859166008166628E-003 -2.8601010668209161

393216 data/ERA5/2017/vwnd_2017_01.nc 1.1901257066603134E-003 -6.8985061346306740

READ IN fields at DATE: 2017-01-01 00:00:00 UTC

NetCDF: Index exceeds dimension bound

mod_era5.F90 : 681:Error read var t: -40

STOP Execution terminated because of runtime error

Abigail Birago Adomako

I checked your namelist once again. There is a limitation for horizontal resolution(ds), and you can not use 1 Km.

I changed some parts of your namelist and attached it to this answer. Try the following commands with this namelist.

$> ./bin/terrain test_001.in

$> ls input test_001_DOMAIN000.nc test_001_LANDUSE

$> ./bin/sst test_001.in

$> ls input test_001_DOMAIN000.nc test_001_LANDUSE test_001_SST.nc

$> ./bin/icbc test_001.in

Morteza Babaei

After changing to 10km and 20km, I still get the new error I showed above. Could you help me?

NetCDF: Index exceeds dimension bound

mod_era5.F90 : 681:Error read var t: -40

STOP Execution terminated because of runtime error

Abigail Birago Adomako

Did you try my namelist?

When you change the central longitude and latitude, I think your domain area becomes bigger than your Era5 data area.

The ERA5 is global data, so the central longitude and latitude have no effect. In your namelist, you just used a lesser number of points in the N/S and E/W directions, and also used the Non-hydrostatic dynamical core with pressure vertical coordinates.

Even after changing it to your exact namelist, and running it for a day, I get the same error.

Using non hydrostatic parameters

base_state_pressure = 101325.00

logp_lrate = 47.70

GLOBIDATE1 : 2017-01-01 00:00:00 UTC

GLOBIDATE2 : 2017-01-02 00:00:00 UTC

NSTEPS : 5

Computing weights. Done.

Computing weights. Done.

131072 data/ERA5/2017/tatm_2017_01.nc 1.8651047010219326E-003 248.48718848036432

196608 data/ERA5/2017/geop_2017_01.nc 7.5211966278559084 245155.51259504544

262144 data/ERA5/2017/qhum_2017_01.nc 2.9496156507563046E-007 9.6659518359635752E-003

327680 data/ERA5/2017/uwnd_2017_01.nc 2.4859166008166628E-003 -2.8601010668209161

393216 data/ERA5/2017/vwnd_2017_01.nc 1.1901257066603134E-003 -6.8985061346306740

READ IN fields at DATE: 2017-01-01 00:00:00 UTC

NetCDF: Index exceeds dimension bound

mod_era5.F90 : 681:Error read var t: -40

STOP Execution terminated because of runtime error

I have no idea. Please, let me know if you have solved the problem.

I will do my best.

Morteza Babaei

I changed the gdate from 2017 to 2020 and it worked. I am forced to believe the 2017 data in ERA5 does not cover my domain. Which other data can I use in RegCM to do my simulations?

Abigail Birago Adomako

You can look for other options at the following link:

http://clima-dods.ictp.it/regcm4/

The ERA5 data is OK. I ran the RegCM model with the ERA5 data from 2015 to 2020. The data you downloaded may be corrupted. Instead of the whole globe, re-download the ERA5 data for your region. You can use my python script. Change line 64 to cover your area.

Morteza Babaei

I used your script and ICBC works. Thank you.