Syntax Changes
Although we are trying hard to keep the syntax stable between versions, it is sometimes necessary to break compatibility by introducing a new syntax. The following reasons can lead to a syntax change:
- improving clarity: sometimes we realize that our naming or syntax leads too many users to struggle and find a much better naming/syntax that is clearer to all.
- making room for the extension of some concepts: for example in order to support stacks of resampling algorithms, the syntax had to be adapted accordingly.
- improving consistency between various components: although we try to name things the same way across MeteoIO, sometimes some inconsistencies slip in. In such cases, a renaming will be performed, usually together with other syntax changes.
The probability of a syntax change is usually much higher for recent features than for older, mature ones. New options, new filters, new plugins... don't count as syntax change as they only extend the syntax without breaking existing syntax.
Migrating INI files
In order to make it easier, here is a list of the syntax changes brought between releases. Moreover, we often implement checks for older syntax in order to alert the users and hint how to update the syntax.
Next release
This is what is currently in development, so what you get by taking the latest from master. Quite a few syntax changes had been postponed until after version 2.11, so expect a few things here!
- the resampling algorithms can now be stacked, so instead of
PSUM::resample = accumulate↵ PSUM::accumulate::period = 3600it is nowPSUM::RESAMPLE1 = ACCUMULATE↵ PSUM::ARG1::PERIOD = 3600; - generally, in the resampling algorithms
WINDOW_SIZEhas been renamed intoMAX_GAP_SIZEfor clarity. Some algorithms (like the new ARIMA) also use aWINDOW_SIZEoption that defines the window over which the statistics are computed before starting gap-filling. - a new
MOVEalgorithm has been written that moves parameters between stations (for example to take TA_2 from station1 and move it as TA of station2). - file-based plugins that used to rely on keys such as
STATION1now use keys such asMETEOFILE1 - the
SUPPRtime filter had aCLEANUPargument. This has been replaced by aDUPLICATESargument for clarity. Please note that this does not sort the timestamps anymore, if the timestamps are not in order it is necessary to call a sort filter first.
release 2.11.0
release 2.10.0
- All the low level "raw data editing" has been moved into a new [InputEditing] section. ALl the associated keys have been moved to this section and the AUTOMERGE key in the [Input] section has been replaced by the automerge InputEditing algorithm that has to be declared within the InputEditing algorithms stack. For example, you can replace
[Input]↵ AUTOMERGE = TRUEby[InputEditing]↵ *::EDIT1 = AUTOMERGE. - the
MOVEDataEditing algorithm has been renamed into a newRENAMEalgorithm.