Recently, I found out that flex_extract version 7.0.3 has an error in the extraction of ERA5 data!

PLEASE STOP USING ERA5 DATA EXTRACTION!!!!

Times 17 and 18 do not contain any flux fields (e.g. precipitation). And the rest of the times it seems that the flux fields are shifted in time.

I'll provide a bug fix as soon as possible!

Explanations will follow ...

During a test with ERA5 and CERA with the gateway version (submitting the jobscript to the ecgate server) I had problems in the CONVERT2 Fortran program.

I received the following error with grib_api:

grib_ieee_to_long: Number is too large: x=3.35531257646599394446e+44 > xmax=3.40282346638528859812e+38
/scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c at line 147: assertion failure Assert(0)

Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0  0x3dd543250f in ???
#1  0x3dd5432495 in ???
#2  0x3dd5433c74 in ???
#3  0x7ffff7b38a42 in grib_fail
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_errors.c:111
#4  0x7ffff7b2241b in grib_ieee_to_long
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:147
#5  0x7ffff7b226c7 in grib_ieee_nearest_smaller_to_long
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:237
#6  0x7ffff7b2283e in grib_nearest_smaller_ieee_float
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_ieeefloat.c:280
#7  0x7ffff7b01b1e in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_simple_packing.c:678
#8  0x7ffff7b0627d in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_g2simple_packing.c:206
#9  0x7ffff7b3726a in _grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:559
#10  0x7ffff7b3731b in _grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:586
#11  0x7ffff7b373e0 in grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:608
#12  0x7ffff7b0ef3a in pack_double
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_accessor_class_data_apply_bitmap.c:311
#13  0x7ffff7b3726a in _grib_set_double_array_internal
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:559
#14  0x7ffff7b3731b in _grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:586
#15  0x7ffff7b37474 in __grib_set_double_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/src/grib_value.c:679
#16  0x7ffff7deec6c in grib_f_set_real8_array_
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/grib_api/fortran/grib_fortran.c:2619
#17  0x7ffff7df067a in __grib_api_MOD_grib_set_real8_array
    at /scratch/ma/deploy/metabuilds/ecflow-metab_5062/ecgb/GNU.63/grib_api/builds/fortran/grib_f90.f90:2953
#18  0x409733 in __rwgrib2_MOD_writelatlon
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/rwGRIB2.f90:154
#19  0x417b61 in preconvert
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/preconvert.f90:682
#20  0x418bf9 in main
    at /home/ms/at/km4a/flex_extract_v7.1/source/fortran/preconvert.f90:53 

and the following error while using eccodes:

ECCODES ERROR   :  Maximum value out of range: -nan
ECCODES ERROR   :  unable to compute packing parameters

ECCODES ERROR   :  unable to set double array codedValues (Encoding invalid)
ECCODES ERROR   :  set: values Encoding invalid
 readspectral:            1  records read
 readlatlon:           76  records read
STATISTICS:  97406.7212 97402.4837   908.5665
 readlatlon:           38  records read
 readlatlon:           38  records read
 readlatlon:           38  records read 

When I run flexpart-wrf using the command ./flexwrf_intel_omp I get out of bounds errors when my WRF geographical grid is compared to the grid in flexwrf.input. Where does FLEXPART-WRF look to find the WRF geographical grid to compare to? I have tried multiple settings in flexwrf.input and I can't determine which specific fields in the flexwrf.input file are causing the issue.