Closed BaptisteVandecrux closed 10 months ago
Another necessary update was to make extrapolation of GPS coordinates default.
This was necessary because the instantaneous values are taken at the end of the hourly time step and are therefore always one hour ahead of the gps coordinates (which are the average over that same hour and are given the beginning of the hour as timestamp).
> getBUFR --positions --positions-filepath ../aws-l3/AWS_latest_locations.csv
At that site t_i, rh_i, p_i are not available since '2023-05-26 21:00:00' while gps_lon, gps_lat, gps_alt are still available![image](https://github.com/GEUS-Glaciology-and-Climate/pypromice/assets/35140661/aaec53f7-28ef-4abe-8b6a-f3b09e2b4cf7)
The problem might come from the "current_timestamp" being passed to the
find_position
function: https://github.com/GEUS-Glaciology-and-Climate/pypromice/blob/3424f2c6f81619bc04446a565fdc1666eaa16bc1/bin/getBUFR#L238-L246We can see that the "Time checks failed", meaning that the code correctly identify the last instantaneous values as too old. But still it is running find_position on "current_timestamp", which is several months old. I suggest setting
current_timestamp = None
in that situation.