In util/SEBESOLWEIGCommonFiles/Solweig_v2015_metdata_noload.py the dectime is loaded in this way:
|
dectime = met[:, 1] + met[:, 2] / 24 + met[:, 3] / (60 * 24.0) |
The columns of the metadata used are column 1, 2 and 3, i.e. id, it and imin respectively.
I understand the columns as follows:
id: Day of Yearit: hour of day (integer in the range 0-23)imin: minute of hour (integer in the range 0-59)
This is at least given in the manual as well
The last part of the dectime calculation implies that imin is giving minutes of day independently from the current hour (so integer in the range 0-60*24).
I think it should be corrected to:
dectime = met[:, 1] + met[:, 2] / 24 + met[:, 3] / 60
I guess, often metfiles with imin=0 are used, i.e. hourly timesteps. Hence, this issue never showed.
In util/SEBESOLWEIGCommonFiles/Solweig_v2015_metdata_noload.py the
dectimeis loaded in this way:UMEP-processing/util/SEBESOLWEIGCommonFiles/Solweig_v2015_metdata_noload.py
Line 25 in 0c28715
The columns of the metadata used are column 1, 2 and 3, i.e.
id,itandiminrespectively.I understand the columns as follows:
id: Day of Yearit: hour of day (integer in the range 0-23)imin: minute of hour (integer in the range 0-59)This is at least given in the manual as well
The last part of the
dectimecalculation implies thatiminis giving minutes of day independently from the current hour (so integer in the range 0-60*24).I think it should be corrected to:
dectime = met[:, 1] + met[:, 2] / 24 + met[:, 3] / 60I guess, often metfiles with
imin=0 are used, i.e. hourly timesteps. Hence, this issue never showed.