WSL/SLF GitLab Repository
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
meteoio
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
snow-models
meteoio
Repository graph
Repository graph
You can move around the graph by using the arrow keys.
c76f55a591ca3634f5ddc0c40b5729054f54da4b
Select Git revision
Selected
c76f55a591ca3634f5ddc0c40b5729054f54da4b
Branches
4
master
default
protected
BUFR_changes
feature/web-service
limiting_trends
Tags
20
test
MeteoIO-2.11.0
webservice-2022
MeteoIO-2.10.0
MeteoIO-2.9.0
MeteoIO-2.8.0
MeteoIO-2.7.0
MeteoIO-2.6.1
MeteoIO-2.6.0
MeteoIO-2.5.1
MeteoIO-2.5.0
MeteoIO-2.4.2
MeteoIO-2.4.1
MeteoIO-2.4.0
MeteoIO-2.3.0
MeteoIO-2.2.0
MeteoIO-2.1.2
MeteoIO-2.1.1
MeteoIO-2.1.0
MeteoIO-2.0.0
25 results
Select display option
Display full history
Display full history
Display up to revision
Created with Raphaël 2.2.0
16
Nov
15
8
4
3
26
Oct
25
24
12
5
27
Sep
20
15
5
4
1
29
Aug
28
23
22
2
31
Jul
28
27
24
21
20
19
18
17
14
12
11
10
7
6
5
4
3
30
Jun
29
28
27
23
21
20
19
16
15
14
13
12
9
8
7
6
31
May
24
19
18
16
12
25
Apr
21
20
19
11
10
7
6
4
3
31
Mar
30
29
28
27
23
22
20
17
16
15
14
13
10
9
8
7
6
24
Feb
23
22
21
16
13
8
6
2
1
31
Jan
30
26
25
24
23
13
12
11
9
23
Dec
21
16
13
8
5
30
Nov
25
24
17
14
10
9
8
4
3
31
Oct
28
25
24
21
20
7
5
4
3
30
Sep
29
28
27
26
23
22
21
16
15
14
13
12
8
7
5
2
31
Aug
26
25
24
23
22
19
18
17
15
10
9
8
3
2
28
Jul
22
21
12
27
Jun
23
21
17
10
9
7
3
2
27
May
25
23
19
17
14
13
11
5
4
26
Apr
18
15
14
8
7
5
1
31
Mar
24
22
21
18
15
9
8
7
4
3
2
1
29
Feb
26
24
23
20
10
9
8
5
3
29
Jan
28
27
26
25
22
20
14
13
12
11
8
6
22
Dec
21
18
9
7
4
3
30
Nov
27
26
25
24
20
19
18
17
16
11
5
4
31
Oct
28
23
22
15
12
8
6
1
30
Sep
29
28
25
23
22
10
9
8
7
2
1
31
Aug
28
27
11
10
7
3
30
Jul
28
27
23
21
20
17
16
13
9
8
7
2
1
30
Jun
24
17
16
15
12
10
9
29
May
27
21
6
26
Apr
14
10
9
8
2
1
31
Mar
30
26
25
24
25
Feb
17
13
11
10
8
6
3
30
Jan
23
20
22
Dec
19
18
17
12
8
4
2
27
Nov
25
24
20
18
13
12
11
10
7
31
Oct
30
29
28
22
21
13
9
7
6
3
2
1
30
Sep
16
14
4
3
2
29
Aug
27
26
25
22
21
20
19
15
14
12
4
31
Jul
27
18
14
11
10
9
8
26
Jun
25
24
19
18
17
16
14
10
5
3
2
More details about the date formats
fixed an error message in oshdio
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 middle of the DEM or on the sides), leading to a ~20% speed up when reading and processing a DEM. Otherwise, some minor optimizations (const, static, etc)
Minor optimization in Config.h and white spaces
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 was performed twice. This is now properly avoided.
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
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).
Finally, the UnDST time filter works as it should
Finally, the infrastructure for handling timestamps filtering is in place. The UnDST filter is not ready yet, but we can move forward.
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 be performed much earlier than the rest of the filtering and most of the structures are not in place yet... So, do not rely on this version for time filtering yet!
A new kind of filters has been created: on the timestamps themselves. This has lead to some code restructuring (and factorization).
The serialization/deserialization methods have been re-written with more precise types (ostream and istream).
Fixed a potential floating point exception and some comments/white spaces stuff
The VSTATIONS_REFRESH_RATE parameter had an inappropriate default value. When dealing with duplidate VSTATIONS, there was a possibility of segfault.
The version number should have been pushed up long ago...
micro optimization and made a method public (it can be useful for debugging)
Some syntax checking has been added for the filters/generators/interpolations1&2D. The smet_range script now follows links.
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.
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 improvement.
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).
Although this was not necessary for MeteoIO, the compilation flags for the coverage test have been set to the same values as for the other tests (so it is as for alpine3d / snowpack)
Another bug in the handling of the virtual stations... somehow, a wrong commit slipped in!
The coordinates specifications as used by the virtual stations had been very, very badly implemented. This now works as planned. The sme2kml script produces kml files with the list of available fields for each stations. The smet_extract script should now support files with larger headers.
A new spatial interpolation algorithm has been added: NEAREST (it takes the value at the nearest station, for each pixel). This is useful for virtual stations more than for anything else.
A bug in the new features of smet_extract has been fixed. A bug in data_converter when the number of stations changes over time has been fixed. An unnecessary include has been removed from Coords.cc. The Buffer class now has a size() method that returns the number of stations it contains.
improvements to better present the data...
The smet_extract.sh script can now show a summary of which fields are present in each smet file in the current directory
Another small fix for Multilinear regressions (for consistency with the other models)
Bugfix for the multilinear regressions
Documentation improvement
The parsing of the ODKriging spatial interpolation was not properly done. Some small optimizations (also leading to better code clarity) have been implemented. The version number has been pushed up to 2.7.0 in order to account for all the latest changes (specially the new syntax).
More cleanup for clang...
Code cleanup to make clang happy
When evaluating the cloudiness, it is important to know if it is night or day. If ISWR==nodata and use_rswr=false, this was not evaluated anymore, losing some important information (even if the albedo evaluation is very imprecise, at least it can be used to decide if it is night or day). This has been fixed, but how to best temporally interpolate the cloudiness still has to be adressed...
Documentation improvement and more logical "if ... then ... else ..." order
More options have been exposed for the IIR filter and its "type" now describes another option. The documentation has been expanded.
Now, RSWR is NOT anymore used by default to compute ISWR in the AllSky and TauCLD generators, it must be forced with USE_RSWR (since it is not very performant)
More code factorization, improved error messages
The new, named arguments syntax has been brought to the Meto1DInterpolations
making the Meteo1DInterpolator structure closer to DateCreator / ProcessingBlock, etc
Loading