AgeSort asc/desc | Change |
---|---|
Prev 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 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 Next | |
Nov 16, 2017 | |
3 years 2 months | Getting-MeteoIO, Removed obsolete comment about PATH |
Change of Getting-MeteoIO, by Mathias Bavay | |
Nov 15, 2017 | |
3 years 2 months | fixed an error message in oshdio |
Commit 2027, by Mathias Bavay | |
Nov 8, 2017 | |
3 years 2 months | When using virtual stations, the DEM is now kept within Meteo2DInterpolator. This leads to another factor 2 speed up. The DEM slope, azimuth, etc are now computed in a more efficient way (the pixel values are retrieved differently if they are in the |
Commit 2026, by Mathias Bavay | |
Nov 4, 2017 | |
3 years 2 months | Minor optimization in Config.h and white spaces |
Commit 2025, by Mathias Bavay | |
Nov 3, 2017 | |
3 years 2 months | In some cases (for example hourly data with hourly sampling rate requested), the i_date_down and i_date_up used to determine which spatial interpolations have to be requested for virtual stations would end up being the same, so the same interpolation |
Commit 2024, by Mathias Bavay | |
3 years 2 months | The handling of buffered DEMs was quite bad since it was requesting the recomputation of all DEM properties (slope, azimuth, etc) when requesting a DEM |
Commit 2023, by Mathias Bavay | |
Oct 26, 2017 | |
3 years 2 months | Since auto_ptr is getting deprecated (it should be replaced by c++11 smart pointers, although auto_ptr is valid c++98), replacing them by normal pointers (their use case are trivial). |
Commit 2022, by Mathias Bavay | |
Oct 25, 2017 | |
3 years 2 months | Finally, the UnDST time filter works as it should |
Commit 2021, by Mathias Bavay | |
3 years 2 months | Finally, the infrastructure for handling timestamps filtering is in place. The UnDST filter is not ready yet, but we can move forward. |
Commit 2020, by Mathias Bavay | |
Oct 24, 2017 | |
3 years 2 months | In order to have a wide range of TIME filters, a new structure has to be designed. So far, a TimeProcStack has been implemented but this is just a work in progress as this does not fulfill the requirements yet. This is because the time filtering must |
Commit 2019, by Mathias Bavay | |
Oct 12, 2017 | |
3 years 3 months | A new kind of filters has been created: on the timestamps themselves. This has lead to some code restructuring (and factorization). In MathOptim, some minor optimizations. |
Commit 2018, by Mathias Bavay | |
Oct 5, 2017 | |
3 years 3 months | The serialization/deserialization methods have been re-written with more precise types (ostream and istream). |
Commit 2017, by Mathias Bavay | |
Sep 27, 2017 | |
3 years 3 months | Fixed a potential floating point exception and some comments/white spaces stuff |
Commit 2016, by Mathias Bavay | |
Sep 20, 2017 | |
3 years 3 months | The VSTATIONS_REFRESH_RATE parameter had an inappropriate default value. When dealing with duplidate VSTATIONS, there was a possibility of segfault. |
Commit 2015, by Mathias Bavay | |
Sep 15, 2017 | |
3 years 4 months | The version number should have been pushed up long ago... |
Commit 2014, by Mathias Bavay | |
3 years 4 months | micro optimization and made a method public (it can be useful for debugging) |
Commit 2013, by Mathias Bavay | |
Sep 5, 2017 | |
3 years 4 months | Some syntax checking has been added for the filters/generators/interpolations1&2D. The smet_range script now follows links. |
Commit 2012, by Mathias Bavay | |
Sep 4, 2017 | |
3 years 4 months | The NetCDF library was not found anymore by cmake, swapping to the latest FindNetCDF from VTK. In smet_range, an error has been found in the sampling rate computation. |
Commit 2011, by Mathias Bavay | |
Sep 1, 2017 | |
3 years 4 months | Now when converting coordinates to UTM with an "invaliud" zone (ie not the zone it should be), no warning will be printed (assuming that when this occurs, users actually don't have any other choice). Otherwise, code cleanup and small documentation im |
Commit 2010, by Mathias Bavay | |
Aug 29, 2017 | |
3 years 4 months | One gcc option (Wvector-operation-performance) is only supported for gcc>=4.7.0 so it is now skiped for gcc<4.8.0 (since we already have options when gcc>=4.8). |
Commit 2009, by Mathias Bavay |