by Thomas Thomsen | May 1, 2019 | Architecture, Data management, History, Syntax
The official Gekko 3.0 is now released. This is a long post, but the intent is to try to explain what Gekko 3.0 really is about. Which is actually not so easy to boil down exactly: it is perhaps best to think of it as a long-term vision, borne out of the realization...
by Thomas Thomsen | Jun 4, 2018 | Architecture, History, Programming, Syntax
Gekko 3.0 is due to be officially released in the autumn of 2018. Version 3.0 entails a rewrite of large parts of Gekko, and the reader may ask him/herself why this is really necessary? As explained in this blog post, Gekko started out (in 2008) just interpreting...
by Thomas Thomsen | Nov 9, 2017 | Architecture, Lags, Programming
One of the main reasons for the modernization of the parser for Gekko 3.0 was that it was deemed important to handle timeseries as objects in Gekko. Timeseries are already objects in Gekko 2.0/2.2, but they are not always handled as such during calculations. To...
by Thomas Thomsen | Nov 9, 2017 | Data management, Frequencies, Programming, Syntax
To denote a timeseries with a particular frequency, AREMOS uses the dot, for instance x.a is x in its annual version, x.q is quarterly, x.m is monthly, etc. In Gekko 3.0, the dot is already quite busy, since it is used to pick out elements in collections. For...
by Thomas Thomsen | Nov 9, 2017 | Programming, Syntax
Gekko uses the ‘funny symbols’ (sigils) % and # to indicate scalars and collections (for instance lists), respectively. More about these in the previous post. But how to think about them? For instance, in Gekko 2.0, a scalar value is written like “VAL v = 100;”, not...
by Thomas Thomsen | Nov 9, 2017 | Programming, Syntax
What is a sigil? In Gekko, sigils are used to denote general variable types, for instance %x if it is a scalar (string/value/date), #x if it is a collection (list, matrix or map), and plain x if it is a timeseries. The use of # was inherited from AREMOS, but AREMOS...
Recent Comments