Problem on MODE TD: " file time increments are not constant!" #1249

skmue · 2021-11-10T15:45:29Z

skmue
Nov 10, 2021

Dear all,
I am puzzled as to why I am getting the " file time increments are not constant!" error. All info further below.
Let me know if you need more info, and many thanks for your help!
Sebastian

My input is:
f = Dataset(input_file, 'r')
times = f.variables['time']

In [13]: np.unique(np.diff(times[:]))
Out[13]:
masked_array(data=[30.],
mask=False,
fill_value=1e+20)

and i get:
...
Time Index: 118
Data Shape: (365, 583)
Data Type: dtype('float64')
Valid Time = 2105-11-01 00:00:00
Valid Time strftime=
Accum Time = 000000
Attributes: {'valid': '21051101_000000', 'init': '21051101_000000', 'lead': '00', 'accum': '000000', 'name': 'pr', 'long_name': 'precipitation flux', 'level': 'Surface', 'units': 'mm/hr', 'grid': {'name': 'ALP-3i', 'type': 'LatLon', 'lat_ll': 40.0, 'lon_ll': 1.0, 'delta_lon': 0.0275, 'delta_lat': 0.0275, 'Nlon': 583, 'Nlat': 365}}
Input File: '/home/clima-archive4-b/smueller/MTD/PRECIP_input/ALP-3i_MOHC_HadREM3/rcp85/timsum/timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc'
Time Index: 118
Data Shape: (365, 583)
Data Type: dtype('float64')
Valid Time = 2105-11-01 00:00:00
Valid Time strftime=
Accum Time = 000000
Attributes: {'valid': '21051101_000000', 'init': '21051101_000000', 'lead': '00', 'accum': '000000', 'name': 'pr', 'long_name': 'precipitation flux', 'level': 'Surface', 'units': 'mm/hr', 'grid': {'name': 'ALP-3i', 'type': 'LatLon', 'lat_ll': 40.0, 'lon_ll': 1.0, 'delta_lon': 0.0275, 'delta_lat': 0.0275, 'Nlon': 583, 'Nlat': 365}}
DEBUG 2: mtd_read_data() -> processing file "119"
Input File: '/home/clima-archive4-b/smueller/MTD/PRECIP_input/ALP-3i_MOHC_HadREM3/rcp85/timsum/timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc'
Time Index: 119
Data Shape: (365, 583)
Data Type: dtype('float64')
Valid Time = 2105-12-01 00:00:00
Valid Time strftime=
Accum Time = 000000
Attributes: {'valid': '21051201_000000', 'init': '21051201_000000', 'lead': '00', 'accum': '000000', 'name': 'pr', 'long_name': 'precipitation flux', 'level': 'Surface', 'units': 'mm/hr', 'grid': {'name': 'ALP-3i', 'type': 'LatLon', 'lat_ll': 40.0, 'lon_ll': 1.0, 'delta_lon': 0.0275, 'delta_lat': 0.0275, 'Nlon': 583, 'Nlat': 365}}
Input File: '/home/clima-archive4-b/smueller/MTD/PRECIP_input/ALP-3i_MOHC_HadREM3/rcp85/timsum/timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc'
Time Index: 119
Data Shape: (365, 583)
Data Type: dtype('float64')
Valid Time = 2105-12-01 00:00:00
Valid Time strftime=
Accum Time = 000000
Attributes: {'valid': '21051201_000000', 'init': '21051201_000000', 'lead': '00', 'accum': '000000', 'name': 'pr', 'long_name': 'precipitation flux', 'level': 'Surface', 'units': 'mm/hr', 'grid': {'name': 'ALP-3i', 'type': 'LatLon', 'lat_ll': 40.0, 'lon_ll': 1.0, 'delta_lon': 0.0275, 'delta_lat': 0.0275, 'Nlon': 583, 'Nlat': 365}}
ERROR :
ERROR :
ERROR : mtd_read_data() -> file time increments are not constant!
ERROR :
Out[3]: 1

Answered by CPKalb

Nov 16, 2021

Hi Sebastian:

When looking at time step increments, mtd (and other MET tools) calculate the difference using dates. Since your data is monthly, and the number of days per month varies, mtd computes these different number of days in each month. The time calendar in your file is given as 360_day (30 days for each month), but that information isn't passed to mtd through python embedding, so it's not using this calendar and therefore thinks the time increments are not constant.

We have set up an issue to put in a fix for this, but it's not available yet. In the meantime, there are a few ways to get around this and get mtd running right now.

since MET is open source, change "Error" to "Warni…

View full answer

CPKalb · 2021-11-11T18:38:41Z

CPKalb
Nov 11, 2021
Collaborator

Hi Sebastian:

It looks like you are inputting the data to mtd with a python array. Is time index 118 the first one that is being read into mtd or are there previous times that are read? If 118 isn't the first time index, it would be helpful to see what the previous ones looked like.

Thanks,
Christina

2 replies

skmue Nov 12, 2021
Author

Thanks a lot for trying to help!

Yes, I am using the python read_timestep.py, and my command looks like the following, reading 120 timesteps like this:
mtd -single 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 -config MTDConfig_files/MTDConfig_SKM_python_ALP-3i_ICTP_RegCM4_rcp85_prltTH05_rsmoo8_tsmoo1_minvol1000_oooo -outdir outdir

Here is more info on the file. The time increments really are constants, see:

In [13]: import netCDF4
...: import numpy as np
...: input_file='/home/clima-archive4-b/smueller/MTD/PRECIP_input/ALP-3i_MOHC_HadREM3/rcp85/timsum/timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc'
...: f = netCDF4.Dataset(input_file, 'r')
...: times = f.variables['time'][:]

In [14]: times[:]
Out[14]:
masked_array(data=[52605., 52635., 52665., 52695., 52725., 52755., 52785.,
52815., 52845., 52875., 52905., 52935., 52965., 52995.,
53025., 53055., 53085., 53115., 53145., 53175., 53205.,
53235., 53265., 53295., 53325., 53355., 53385., 53415.,
53445., 53475., 53505., 53535., 53565., 53595., 53625.,
53655., 53685., 53715., 53745., 53775., 53805., 53835.,
53865., 53895., 53925., 53955., 53985., 54015., 54045.,
54075., 54105., 54135., 54165., 54195., 54225., 54255.,
54285., 54315., 54345., 54375., 54405., 54435., 54465.,
54495., 54525., 54555., 54585., 54615., 54645., 54675.,
54705., 54735., 54765., 54795., 54825., 54855., 54885.,
54915., 54945., 54975., 55005., 55035., 55065., 55095.,
55125., 55155., 55185., 55215., 55245., 55275., 55305.,
55335., 55365., 55395., 55425., 55455., 55485., 55515.,
55545., 55575., 55605., 55635., 55665., 55695., 55725.,
55755., 55785., 55815., 55845., 55875., 55905., 55935.,
55965., 55995., 56025., 56055., 56085., 56115., 56145.,
56175.],
mask=False,
fill_value=1e+20)

In [15]: np.diff(times[:])
Out[15]:
masked_array(data=[30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30., 30., 30.,
30., 30., 30., 30., 30., 30., 30., 30., 30.],
mask=False,
fill_value=1e+20)

In [16]: np.unique(np.diff(times[:]))
Out[16]:
masked_array(data=[30.],
mask=False,
fill_value=1e+20)

CPKalb Nov 15, 2021
Collaborator

Hi Sebastian:

Would you be able to send me your file and read_timestep.py so I can take a closer look? Instructions for sending data can be found here: #954.

Thanks,
Christina

skmue · 2021-11-15T20:21:09Z

skmue
Nov 15, 2021
Author

Ciao Christina, I uploaded it all to /incoming/irap/met_help/mueller_data Thanks and cheers Sebastian

2 replies

CPKalb Nov 16, 2021
Collaborator

Thanks, I grabbed them. Do you also have a mtd configuration file that you could send over? It may be small enough to just upload here.

Christina

CPKalb Nov 16, 2021
Collaborator

Apologies, it looks like you did include the configuration file. Thanks

CPKalb · 2021-11-16T21:06:05Z

CPKalb
Nov 16, 2021
Collaborator

Hi Sebastian:

When looking at time step increments, mtd (and other MET tools) calculate the difference using dates. Since your data is monthly, and the number of days per month varies, mtd computes these different number of days in each month. The time calendar in your file is given as 360_day (30 days for each month), but that information isn't passed to mtd through python embedding, so it's not using this calendar and therefore thinks the time increments are not constant.

We have set up an issue to put in a fix for this, but it's not available yet. In the meantime, there are a few ways to get around this and get mtd running right now.

since MET is open source, change "Error" to "Warning" on this line:
https://github.com/dtcenter/MET/blob/64b445a852a0c92923456d563175cecfc49f2613/met/src/tools/other/mode_time_domain/mtd_read_data.cc#L115 (edited)
mtd_read_data.cc
mlog << Error << "\n\n mtd_read_data() -> file time increments are not constant!\n\n";
then, recompile and try re-running mtd
Use nco tools to create separate files for each timestep of your data. For example: ncks -d time,0 timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo_0.nc will separate the first time step. Annoyingly, you would have to do this for all the timesteps. Once you have the files separated, change the variable information in the configuration file to look like this:
fcst = {
field = {
name = "pr";
level = "(0, *, *)";
}
Then, run mtd inputting a list of all the separate files after the -single command. MET reads the calendar in this case so is able to correctly interpret the time steps as constant.

Will either of these solutions work for you?

0 replies

skmue · 2021-11-18T15:40:14Z

skmue
Nov 18, 2021
Author

Dear Christina, thanks for the clarification. I will try option 2. Admittedly I am slightly relieved that it was not a stupid error of mine... I would like to note one more thing: the cartesian grid seems to be a not right. When I compute the distance in betweeen the CENTROID_LON and CENTROID_LAT it gives CDIST_TRAVELLED, as expected. But this is not true when I compute the distance from the cartesian coordinates. Likewise X_DOT and Y_DOT don't seem right. This I computed for two objects which have only 2 time steps. Is the CDIST_TRAVELLED integrated over each time step or simply the distance in between first and last? I will now compute propagation speed simply by CDIST_TRAVELLED/DURATION. Thanks and cheers Sebastian

…

On 16.11.2021 22:06, Christina Kalb wrote: Hi Sebastian: When looking at time step increments, MTD (and other MET tools) calculate the difference using dates. Since your data is monthly, and the number of days per month varies, MTD computes these different number of days in each month and reports that the time increment isn't constant. The time calendar in your file is given as 360_day, but that information isn't being passed to mtd, so it's not using this calendar and therefore thinks the time increments are not constant. We are working on a solution on our end, but it's not available yet. In the meantime, there are a few ways to get around this and get mtd running right now. * since MET is open source, change "Error" to "Warning" on this line, recompile, and try rerunning: https://github.com/dtcenter/MET/blob/64b445a852a0c92923456d563175cecfc49f2613/met/src/tools/other/mode_time_domain/mtd_read_data.cc#L115 [1] (edited) mtd_read_data.cc mlog << Error << "nn mtd_read_data() -> file time increments are not constant!nn"; * Use nco to create separate files for each timestep of your data. For example: ncks -d time,0 timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo_0.nc. Annoyingly, you would have to do this for all the timesteps. Once you have the files separated, change the configuration file to look like this: fcst = { field = { name = "pr"; level = "(0,_,_)"; } Then, run mtd inputting a list of all the separate files after the -single command. Will either of these solutions work for you? -- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5]. Links: ------ [1] https://github.com/dtcenter/MET/blob/64b445a852a0c92923456d563175cecfc49f2613/met/src/tools/other/mode_time_domain/mtd_read_data.cc#L115 [2] #1249 (comment) [3] https://github.com/notifications/unsubscribe-auth/AWNU4ZSPK43NYX7FFT224UTUMLBURANCNFSM5H3DEDZQ [4] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [5] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

0 replies

skmue · 2021-11-18T16:15:03Z

skmue
Nov 18, 2021
Author

Actually rearding CDIST_TRAVELLED I am slightly concerned now. It only comes out correct as the great circle distance (gcd) of CENTROID_LON and CENTROID_LAT, when the object spans only two time steps/ has only two centroids. Else, the distance becomes huge. E.g., for cluster F002 I get 177km, when adding up the gcds between each centroid, while in the MTD 3d_single_simple.txt file I find 453.553 km. See the little python code attached! Cheers Sebastian

On 18.11.2021 16:40, ***@***.*** wrote: Dear Christina, thanks for the clarification. I will try option 2. Admittedly I am slightly relieved that it was not a stupid error of mine... I would like to note one more thing: the cartesian grid seems to be a not right. When I compute the distance in betweeen the CENTROID_LON and CENTROID_LAT it gives CDIST_TRAVELLED, as expected. But this is not true when I compute the distance from the cartesian coordinates. Likewise X_DOT and Y_DOT don't seem right. This I computed for two objects which have only 2 time steps. Is the CDIST_TRAVELLED integrated over each time step or simply the distance in between first and last? I will now compute propagation speed simply by CDIST_TRAVELLED/DURATION. Thanks and cheers Sebastian On 16.11.2021 22:06, Christina Kalb wrote: > Hi Sebastian: > > When looking at time step increments, MTD (and other MET tools) > calculate the difference using dates. Since your data is monthly, and > the number of days per month varies, MTD computes these different > number of days in each month and reports that the time increment isn't > constant. The time calendar in your file is given as 360_day, but that > information isn't being passed to mtd, so it's not using this calendar > and therefore thinks the time increments are not constant. > > We are working on a solution on our end, but it's not available yet. > In the meantime, there are a few ways to get around this and get mtd > running right now. > > * > > since MET is open source, change "Error" to "Warning" on this line, > recompile, and try rerunning: > > https://github.com/dtcenter/MET/blob/64b445a852a0c92923456d563175cecfc49f2613/met/src/tools/other/mode_time_domain/mtd_read_data.cc#L115 > [1] (edited) > mtd_read_data.cc > mlog << Error << "nn mtd_read_data() -> file time increments are not > constant!nn"; > * > > Use nco to create separate files for each timestep of your data. For > example: ncks -d time,0 > timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo.nc > timsum_mmhr_pr_ALP-3i_HadGEM3-GC3.1-N512_rcp85_r1i1p1_HadREM3-RA-UM10.1_x0n1v1_1hr_oooo_0.nc. > Annoyingly, you would have to do this for all the timesteps. Once you > have the files separated, change the configuration file to look like > this: > fcst = { > field = { > name = "pr"; > level = "(0,_,_)"; > } > Then, run mtd inputting a list of all the separate files after the > -single command. Will either of these solutions work for you? > > -- > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub [2], or unsubscribe > [3]. > Triage notifications on the go with GitHub Mobile for iOS [4] or > Android [5]. > > Links: > ------ > [1] > https://github.com/dtcenter/MET/blob/64b445a852a0c92923456d563175cecfc49f2613/met/src/tools/other/mode_time_domain/mtd_read_data.cc#L115 > [2] > #1249 (comment) > [3] > https://github.com/notifications/unsubscribe-auth/AWNU4ZSPK43NYX7FFT224UTUMLBURANCNFSM5H3DEDZQ > [4] > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 > [5] > https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

VERSION MODEL DESC FCST_LEAD FCST_VALID OBS_LEAD OBS_VALID T_DELTA FCST_T_BEG FCST_T_END FCST_RAD FCST_THR OBS_T_BEG OBS_T_END OBS_RAD OBS_THR FCST_VAR FCST_UNITS FCST_LEV OBS_VAR OBS_UNITS OBS_LEV OBJECT_ID OBJECT_CAT TIME_INDEX AREA CENTROID_X CENTROID_Y CENTROID_LAT CENTROID_LON AXIS_ANG INTENSITY_10 INTENSITY_25 INTENSITY_50 INTENSITY_75 INTENSITY_90 INTENSITY_99 V9.0.2 RegCM4p7 NA 000000 20970304_023000 000000 20970304_023000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 74 1026 159.54 214.93 45.91 5.39 60.55 5.56 6.20 7.02 7.81 8.73 10.33 V9.0.2 RegCM4p7 NA 000000 20970304_033000 000000 20970304_033000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 75 2053 162.94 199.82 45.50 5.48 66.05 4.85 6.05 7.20 8.65 10.05 12.89 V9.0.2 RegCM4p7 NA 000000 20970304_043000 000000 20970304_043000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 76 2467 169.61 186.30 45.12 5.66 65.62 4.39 5.46 6.83 8.84 10.39 16.39 V9.0.2 RegCM4p7 NA 000000 20970304_053000 000000 20970304_053000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 77 2142 178.28 183.45 45.04 5.90 66.21 4.38 5.21 6.30 7.76 9.25 12.80 V9.0.2 RegCM4p7 NA 000000 20970304_063000 000000 20970304_063000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 78 1129 186.66 177.81 44.89 6.13 -85.71 3.88 4.86 6.12 7.22 8.83 14.78 V9.0.2 RegCM4p7 NA 000000 20970304_073000 000000 20970304_073000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 79 60 195.30 157.23 44.32 6.37 66.56 2.99 4.73 6.40 7.33 8.25 8.54 V9.0.2 RegCM4p7 NA 000000 20970304_063000 000000 20970304_063000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 78 25 268.36 223.64 46.15 8.38 52.62 1.06 1.85 3.46 4.59 5.17 5.76 V9.0.2 RegCM4p7 NA 000000 20970304_073000 000000 20970304_073000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 79 693 264.69 218.59 46.01 8.28 44.54 3.70 4.93 6.19 7.50 8.97 12.44 V9.0.2 RegCM4p7 NA 000000 20970304_083000 000000 20970304_083000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 80 1666 263.38 221.60 46.09 8.24 54.26 4.19 5.53 6.94 8.45 10.17 13.51 V9.0.2 RegCM4p7 NA 000000 20970304_093000 000000 20970304_093000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 81 2162 266.90 222.46 46.12 8.34 54.65 4.62 6.03 8.06 9.90 11.79 14.95 V9.0.2 RegCM4p7 NA 000000 20970304_103000 000000 20970304_103000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 82 2564 275.76 225.52 46.20 8.58 45.86 4.42 5.66 7.61 9.98 12.22 16.55 V9.0.2 RegCM4p7 NA 000000 20970304_113000 000000 20970304_113000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 83 2408 282.67 227.74 46.26 8.77 38.58 4.54 5.83 7.50 9.84 12.94 19.02 V9.0.2 RegCM4p7 NA 000000 20970304_123000 000000 20970304_123000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 84 2316 291.50 226.62 46.23 9.02 24.62 2.96 4.95 7.28 9.43 12.48 24.43 V9.0.2 RegCM4p7 NA 000000 20970304_133000 000000 20970304_133000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 85 1657 294.70 226.02 46.22 9.10 24.94 3.80 5.28 7.16 8.89 11.50 22.16 V9.0.2 RegCM4p7 NA 000000 20970304_143000 000000 20970304_143000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 86 621 285.94 212.71 45.85 8.86 44.96 2.56 4.43 7.15 10.82 15.89 26.41 V9.0.2 RegCM4p7 NA 000000 20970304_153000 000000 20970304_153000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 87 454 286.86 206.28 45.67 8.89 10.86 2.70 5.76 8.31 12.33 17.66 26.41 V9.0.2 RegCM4p7 NA 000000 20970304_163000 000000 20970304_163000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 88 312 289.25 206.06 45.67 8.95 19.96 3.04 5.09 9.03 11.99 14.28 18.76 V9.0.2 RegCM4p7 NA 000000 20970304_173000 000000 20970304_173000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 89 12 293.75 205.58 45.65 9.08 57.93 5.64 6.04 6.78 8.05 8.85 11.65 V9.0.2 RegCM4p7 NA 000000 20970304_143000 000000 20970304_143000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 86 635 391.44 212.15 45.83 11.76 -3.42 4.65 5.16 5.90 7.06 8.31 10.83 V9.0.2 RegCM4p7 NA 000000 20970304_153000 000000 20970304_153000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 87 1225 404.97 215.87 45.94 12.14 12.58 4.70 6.00 7.76 9.93 11.27 13.40 V9.0.2 RegCM4p7 NA 000000 20970304_163000 000000 20970304_163000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 88 1387 414.99 221.50 46.09 12.41 22.58 5.21 7.05 8.60 10.16 11.87 14.96 V9.0.2 RegCM4p7 NA 000000 20970304_173000 000000 20970304_173000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 89 1431 422.46 229.42 46.31 12.62 24.79 4.67 5.86 7.62 9.85 11.83 15.36 V9.0.2 RegCM4p7 NA 000000 20970304_183000 000000 20970304_183000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 90 1424 430.90 237.52 46.53 12.85 23.79 3.77 5.39 7.00 8.62 10.09 12.96 V9.0.2 RegCM4p7 NA 000000 20970304_193000 000000 20970304_193000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 91 1637 449.45 242.89 46.68 13.36 24.63 4.12 5.54 7.00 8.17 9.50 12.94 V9.0.2 RegCM4p7 NA 000000 20970304_203000 000000 20970304_203000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 92 1276 457.15 241.17 46.63 13.57 23.80 4.45 5.41 6.63 8.02 9.87 15.00 V9.0.2 RegCM4p7 NA 000000 20970304_213000 000000 20970304_213000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 93 702 461.80 233.14 46.41 13.70 -5.64 4.04 5.12 6.44 7.72 9.37 12.09 V9.0.2 RegCM4p7 NA 000000 20970304_223000 000000 20970304_223000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 94 616 479.49 231.23 46.36 14.19 8.64 4.77 5.45 6.46 7.72 8.83 13.55 V9.0.2 RegCM4p7 NA 000000 20970304_233000 000000 20970304_233000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 95 475 491.88 233.80 46.43 14.53 17.81 3.43 4.87 5.96 6.70 7.99 11.29 V9.0.2 RegCM4p7 NA 000000 20970305_003000 000000 20970305_003000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 96 78 509.85 236.00 46.49 15.02 -15.94 3.85 4.48 5.20 5.78 6.41 8.12 V9.0.2 RegCM4p7 NA 000000 20970304_153000 000000 20970304_153000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F004 CF000 87 84 390.32 259.05 47.12 11.73 19.42 4.05 5.48 6.39 7.03 7.77 9.72 V9.0.2 RegCM4p7 NA 000000 20970304_163000 000000 20970304_163000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F004 CF000 88 39 392.15 253.08 46.96 11.78 40.23 4.91 5.55 6.58 7.15 7.58 8.34 V9.0.2 RegCM4p7 NA 000000 20970304_203000 000000 20970304_203000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 92 485 481.85 193.09 45.31 14.25 -51.49 1.41 5.40 7.68 9.88 11.55 14.36 V9.0.2 RegCM4p7 NA 000000 20970304_213000 000000 20970304_213000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 93 1124 503.75 169.87 44.67 14.85 -58.30 1.75 4.41 7.26 11.82 17.08 28.01 V9.0.2 RegCM4p7 NA 000000 20970304_223000 000000 20970304_223000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 94 1588 516.32 159.27 44.38 15.20 -60.80 1.50 4.24 8.20 12.00 17.04 26.42 V9.0.2 RegCM4p7 NA 000000 20970304_233000 000000 20970304_233000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 95 1997 528.56 154.55 44.25 15.54 -53.04 1.41 4.40 7.88 11.38 16.31 36.18 V9.0.2 RegCM4p7 NA 000000 20970305_003000 000000 20970305_003000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 96 2356 536.52 156.27 44.30 15.75 -53.16 2.14 4.16 6.64 10.84 16.90 30.72 V9.0.2 RegCM4p7 NA 000000 20970305_013000 000000 20970305_013000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 97 1953 539.41 164.89 44.53 15.83 -50.56 1.55 4.60 7.23 10.02 13.36 23.46 V9.0.2 RegCM4p7 NA 000000 20970305_023000 000000 20970305_023000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 98 1304 536.54 175.73 44.83 15.75 -44.71 4.17 5.89 7.58 10.35 13.22 18.03 V9.0.2 RegCM4p7 NA 000000 20970305_033000 000000 20970305_033000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 99 950 532.39 189.05 45.20 15.64 -35.20 4.74 5.85 6.94 8.35 9.99 13.97 V9.0.2 RegCM4p7 NA 000000 20970305_043000 000000 20970305_043000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 100 1116 545.18 187.45 45.15 15.99 -18.53 4.15 5.17 6.21 8.11 9.36 12.91 V9.0.2 RegCM4p7 NA 000000 20970305_053000 000000 20970305_053000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 101 824 551.76 184.28 45.07 16.17 -7.50 4.68 5.54 6.88 8.51 10.19 15.41 V9.0.2 RegCM4p7 NA 000000 20970305_063000 000000 20970305_063000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 102 224 552.53 184.66 45.08 16.19 1.53 4.33 4.89 5.46 6.22 7.29 10.33 V9.0.2 RegCM4p7 NA 000000 20970305_043000 000000 20970305_043000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F006 CF000 100 109 425.25 32.88 40.90 12.69 -31.71 3.91 4.59 6.05 6.68 8.58 10.33 V9.0.2 RegCM4p7 NA 000000 20970305_093000 000000 20970305_093000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 105 173 530.86 74.23 42.04 15.60 27.52 2.51 4.06 7.54 12.07 16.24 36.76 V9.0.2 RegCM4p7 NA 000000 20970305_103000 000000 20970305_103000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 106 277 529.68 73.03 42.01 15.57 33.32 4.47 7.05 9.88 12.39 15.87 19.77 V9.0.2 RegCM4p7 NA 000000 20970305_113000 000000 20970305_113000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 107 213 526.96 71.15 41.96 15.49 41.75 6.65 7.65 9.73 11.89 14.57 33.73 V9.0.2 RegCM4p7 NA 000000 20970305_123000 000000 20970305_123000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 108 125 523.20 67.74 41.86 15.39 38.25 2.94 5.94 8.98 13.52 16.95 34.74 V9.0.2 RegCM4p7 NA 000000 20970305_133000 000000 20970305_133000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 109 13 519.00 65.15 41.79 15.27 -0.00 7.05 9.43 11.64 15.31 19.81 21.86 V9.0.2 RegCM4p7 NA 000000 20970306_013000 000000 20970306_013000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F008 CF000 121 1 257.00 292.00 48.03 8.07 0.00 12.09 12.09 12.09 12.09 12.09 12.09 V9.0.2 RegCM4p7 NA 000000 20970306_023000 000000 20970306_023000 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F008 CF000 122 192 255.15 290.07 47.98 8.02 59.64 3.35 4.52 5.93 7.12 8.00 9.31 VERSION MODEL DESC FCST_LEAD FCST_VALID OBS_LEAD OBS_VALID T_DELTA FCST_T_BEG FCST_T_END FCST_RAD FCST_THR OBS_T_BEG OBS_T_END OBS_RAD OBS_THR FCST_VAR FCST_UNITS FCST_LEV OBS_VAR OBS_UNITS OBS_LEV OBJECT_ID OBJECT_CAT CENTROID_X CENTROID_Y CENTROID_T CENTROID_LAT CENTROID_LON X_DOT Y_DOT AXIS_ANG VOLUME START_TIME END_TIME CDIST_TRAVELLED INTENSITY_10 INTENSITY_25 INTENSITY_50 INTENSITY_75 INTENSITY_90 INTENSITY_99 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F001 CF000 171.34 190.77 76.05 45.25 5.71 7.14 -8.94 67.15 8877 74 79 561.973 4.49 5.50 6.72 8.20 9.71 13.80 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F002 CF000 279.29 223.35 82.74 46.14 8.68 4.57 -0.63 40.76 14890 78 89 453.553 3.93 5.49 7.36 9.55 12.23 20.40 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F003 CF000 436.38 230.92 90.11 46.35 13.00 10.81 2.92 25.52 10886 86 96 1450.061 4.40 5.56 7.00 8.71 10.60 14.04 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F004 CF000 390.90 257.15 87.32 47.07 11.75 1.83 -5.97 21.98 123 87 88 18.673 4.22 5.52 6.48 7.04 7.67 9.59 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F005 CF000 530.50 168.63 96.49 44.64 15.59 5.34 2.89 -50.69 13921 92 102 1368.958 2.44 4.91 7.09 10.04 14.12 26.69 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F006 CF000 425.25 32.88 100.00 40.90 12.69 0.00 0.00 0.00 109 100 100 0.000 3.91 4.59 6.05 6.68 8.58 10.33 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F007 CF000 528.02 71.83 106.41 41.98 15.52 -2.62 -2.12 34.27 801 105 109 82.630 3.78 6.74 9.29 12.34 15.86 33.75 V9.0.2 RegCM4p7 NA NA 20970301_003000 NA NA 010000 -1 1 8 >5 -1 1 8 >5 pr kg_m-2_s-1 Surface pr kg_m-2_s-1 Surface F008 CF000 255.16 290.08 121.99 47.98 8.02 -1.85 -1.93 59.64 193 121 122 7.030 3.36 4.54 5.96 7.12 8.03 9.50

0 replies

CPKalb · 2021-11-18T17:19:20Z

CPKalb
Nov 18, 2021
Collaborator

Hi Sebastian:

For some reason, the python code isn't showing up for me on this thread. Would you be able to try sending it over again?

Christina

0 replies

skmue · 2021-11-18T17:43:59Z

skmue
Nov 18, 2021
Author

I just copy it here: Cheers! from math import atan2, sqrt, degrees import numpy as np from math import radians, sin, cos RADIUS = 6371.009 def gc_dist(a, b): from math import radians, sin, cos, sqrt, atan2 lat1, lng1 = radians(a[0]), radians(a[1]) lat2, lng2 = radians(b[0]), radians(b[1]) sin_lat1, cos_lat1 = sin(lat1), cos(lat1) sin_lat2, cos_lat2 = sin(lat2), cos(lat2) delta_lng = lng2 - lng1 cos_delta_lng, sin_delta_lng = cos(delta_lng), sin(delta_lng) d = atan2(sqrt((cos_lat2 * sin_delta_lng) ** 2 + (cos_lat1 * sin_lat2 - sin_lat1 * cos_lat2 * cos_delta_lng) ** 2), sin_lat1 * sin_lat2 + cos_lat1 * cos_lat2 * cos_delta_lng) return RADIUS * d COs=[[46.15,8.38],[46.01,8.28],[46.09,8.24],[46.12,8.34],[46.2,8.58],[46.26,8.77],[46.23,9.02],[46.22,9.1],[45.85,8.86],[45.67,8.89],[45.67,8.95],[45.65,9.08]] CD=0. for i_CO in range(len(COs)-1): CD+=gc_dist(COs[i_CO],COs[i_CO+1]) print(CD)

…

On 18.11.2021 18:19, Christina Kalb wrote: Hi Sebastian: For some reason, the python code isn't showing up for me on this thread. Would you be able to try sending it over again? Christina -- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4]. Links: ------ [1] #1249 (comment) [2] https://github.com/notifications/unsubscribe-auth/AWNU4ZW75FY4X3CGAVVNCG3UMUYSFANCNFSM5H3DEDZQ [3] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [4] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

0 replies

CPKalb · 2021-11-18T22:14:49Z

CPKalb
Nov 18, 2021
Collaborator

Hi Sebastian:

When looking at the mtd code to calculate the cdist_travelled, it's using the centroid lat/lon at the first timestep as the reference in the distance calculations for all timesteps. Specifically, if I update the "CD" calculation in your python code to look like: CD+=gc_dist([46.15,8.38],COs[i_CO+1]), I end up with a number close to the mtd output.

This is not the way the calculation should be performed. It should take the distance between each successive centroid latitude and longitude. But, this also explains why your numbers match when an object only has 2 centroids, but not when there are more. We now have an issue out to correct this (dtcenter/MET#1976).

Have you updated your configuration file? I would like to include a reference to this discussion so we can test the mtd calculation. However, the configuration file I have for this data is not producing the same objects as what is in your copied output above. Or, is that output from a different dataset perhaps?

Christina

0 replies

CPKalb · 2021-11-24T16:38:58Z

CPKalb
Nov 24, 2021
Collaborator

Hi Sebastian:

We have put in a fix for the bug and the new version of MET is available here: https://github.com/dtcenter/MET

I've checked that it works as expected. Do you have additional questions or can I mark this discussion as "answered."

Christina

0 replies

skmue · 2021-11-24T17:04:24Z

skmue
Nov 24, 2021
Author

Ciao Christina! Many thanks! You can close the discussion! Best regards Sebastian

…

On 24.11.2021 17:39, Christina Kalb wrote: Hi Sebastian: We have put in a fix for the bug and the new version of MET is available here: https://github.com/dtcenter/MET [1] I've checked that it works as expected. Do you have additional questions or can I mark this discussion as "answered." Christina -- You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [2], or unsubscribe [3]. Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5]. Links: ------ [1] https://github.com/dtcenter/MET [2] #1249 (comment) [3] https://github.com/notifications/unsubscribe-auth/AWNU4ZV3UAPDJG53F7J2LQDUNUIK3ANCNFSM5H3DEDZQ [4] https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 [5] https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Problem on MODE TD: " file time increments are not constant!" #1249

{{title}}

Replies: 10 comments 4 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Problem on MODE TD: " file time increments are not constant!" #1249

skmue Nov 10, 2021

Replies: 10 comments · 4 replies

CPKalb Nov 11, 2021 Collaborator

skmue Nov 12, 2021 Author

CPKalb Nov 15, 2021 Collaborator

skmue Nov 15, 2021 Author

CPKalb Nov 16, 2021 Collaborator

CPKalb Nov 16, 2021 Collaborator

CPKalb Nov 16, 2021 Collaborator

skmue Nov 18, 2021 Author

skmue Nov 18, 2021 Author

CPKalb Nov 18, 2021 Collaborator

skmue Nov 18, 2021 Author

CPKalb Nov 18, 2021 Collaborator

CPKalb Nov 24, 2021 Collaborator

skmue Nov 24, 2021 Author

skmue
Nov 10, 2021

Replies: 10 comments 4 replies

CPKalb
Nov 11, 2021
Collaborator

skmue Nov 12, 2021
Author

CPKalb Nov 15, 2021
Collaborator

skmue
Nov 15, 2021
Author

CPKalb Nov 16, 2021
Collaborator

CPKalb Nov 16, 2021
Collaborator

CPKalb
Nov 16, 2021
Collaborator

skmue
Nov 18, 2021
Author

skmue
Nov 18, 2021
Author

CPKalb
Nov 18, 2021
Collaborator

skmue
Nov 18, 2021
Author

CPKalb
Nov 18, 2021
Collaborator

CPKalb
Nov 24, 2021
Collaborator

skmue
Nov 24, 2021
Author