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

"to many records" #106

Open
ln-x opened this issue Apr 7, 2022 · 4 comments
Open

"to many records" #106

ln-x opened this issue Apr 7, 2022 · 4 comments

Comments

@ln-x
Copy link

ln-x commented Apr 7, 2022

Hi,

I could run EMEP with wrf-forcing of about one month length now. Now I am trying to using wrf-forcing (of the same grid and setup but) with 356 days. I set the startdate and enddate in config_emep.nml according to the first and last wrf-time step, but receive a:

STOP-ALL ERROR: to many records in ./wrfout_d02_2020-01-10_00:00:00
Abort(9) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 9) - process 0

It is called in "NetCDF_mod.f90:4582,4535,4770: call CheckStop(SIZE(TimesInDays)<NTime_Read,"to many records in "//trim(fileName))

If I change the end date to a previous date I get the same error.

Heidi

@ln-x
Copy link
Author

ln-x commented Apr 7, 2022

It runs after making a cdo mergetime operation with the WRF file, which transformed the Times (Time,DateStrLen) variable to XTIME (XTIME). Before the variable was an array of datetime steps (2020-01-01-00:00:00) afterwards an array of integers (minutes since 1990-01-01-00:00:00)

@ln-x ln-x closed this as completed Apr 8, 2022
@ln-x
Copy link
Author

ln-x commented Apr 27, 2022

The simulations completed without any errors and saving the correct timesteps, but the results forced by the adapted WRF-file using the XTIME variable (last year in graph - 2020) look as if something has been read in wrong.
I checked T2, SWDOWN bottom and wind of the WRF-file. I could not find any mistake there.

Any hint where I can look for errors?

Figure_2b_deposition_2018_2020_ERROR

@ln-x ln-x reopened this Apr 27, 2022
@gitpeterwind
Copy link
Member

Hi Heidi,
It is difficult to say without looking at the WRF file.
You can check that the time variables are defined with the right attribute.
The time is read by the routine ReadTimeCDF in NETCDF_mod.f90; you could try to print out data from there to see if it is correctly interpreted.
Otherwise, you can try to send me a sample of your WRF file (one or two days is probably enough), so that I can try myself.

Best wishes,
Peter

@ln-x
Copy link
Author

ln-x commented May 3, 2022

Thank you! I am waiting on a job to run on VSC. Maybe now everything is fine. If not I will send you a file of 1-2 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants