Simple Time Graph using ArcadeDB.
Initialize with:
require 'arcade-time-graph'
Tg::Setup.Init_database # creates database types tg_jahr, tg_monat, tg_tag
# and corresponding edges
Tg::TimeGraph.populate 2020 .. 2025
# populates the timegraph for the given yearsThis Graph is realized
Tg::Jahr -- [Tg::MonthOf] -- Tg::Monat -- [Tg::DayOf] -- Tg::Tag -- [Tg::TimeOf] -- Tg::StundeThe nodes are cross-linked and any point of the grid is easily accessed.
The library provides »to_tg« additions to »Date«, »DateTime« and »String«.
Thus
z = "22.3.2003".to_tg
-> select out('tg_day_of')[ value = 22 ] from ( select expand ( out('tg_month_of')[ value = 3 ] ) from ( select from tg_jahr where value = 2003 ) )
=> #<Tg::Tag rid="#145:147" values={:value=>22} in=2 out=1>
z.datum => Sat, 22 Mar 2003 (returns a Date)
z.next.datum => Sun, 23 Mar 2003
z.prev.datum => Fri, 21 Mar 2003
z.move( -20 ).datum => Sun, 02 Mar 2003
( z + 3 ).datum => Tue, 25 Mar 2003
( z - 3 ).datum => Wed, 19 Mar 2003(datum is a method of Tg::Tag)
To fetch specific date ranges the utility method TG::TimeGraph.grid is present. It returns an Arcade::Match-Object – or, if execute: true` is specified, an array of TG::Tag or .TG::Monat objects
t=TG::TimeGraph.grid( 2020, 5..9 ){ "month.w, contract.shortcut" }
.out(HasPosition)
.node( as: contract )
=> MATCH { type: tg_jahr, where: ( w=2020 ) }
.out('tg_month_of'){ where: ( w between 5 and 9 ), as: month }
.out('has_position'){ as: contract }
RETURN month.w, contract.shortcut # <--- contents of the optional block
t.execute.select_result( :"contract.shortcut" ) # <--- gets a list of shortcuts onlyThe method accepts single values, arrays and ranges as arguments.
The days parameter is optional.
Prerequisites :
-
Ruby 3.1 (or above) and a running ArcadeDB-Server
-
add
gem "arcade-time-graph", git: "https://github.com/topofocus/arcade-time-graph"to your Gemfile -
Run "bundle install" and "bundle update"
-
include
require 'arcade-time-graph'in your script -
customize config/connect.yml
-
Initialize the data-structure by
Tg::Setup.init_database -
Populate the timegraph by
Tg::TimeGraph.populate 2015..2030 -
Verify the setup by
Date.today.to_tg
To play around, start the console by
cd bin
./console t # test-modus
The following database classes are included
DB.hierarchy type: :edge
DB.hierarchy type: :vertex
- Arcade::Edge # ruby-class
- - tg_date_of Tg::MonthOf
- - - tg_day_of Tg::DayOf
- - - tg_month_of Tg::TimeOf
- - grid_of Tg::GridOf
- - has Tg::Has
- Arcade::Vertex
- - tg_time_base Tg::TimeBase
- - - tg_jahr Tg::Jahr
- - - tg_monat Tg::Monat
- - - tg_tag Tg::Tag
- - - stunde Tg::StundeThe graph is populated by calling
TG::TimeGraph.populate( a single year or a range ) # default: 1900 .. 2050The Model-directory contains, customized methods to simplify the usage of the graph.
Some Examples: Assuming, you build a standard day-based grid
include TG # we can omit the TG prefix
Jahr[2000] # --> returns a single object
=> #<Tg::Jahr rid="#193:0" values={:value=>2000} in=0 out=13>
Jahr[2000 .. 2005].map &:w # returns an array
=> [2003, 2000, 2004, 2001, 2005, 2002]
Jahr[2000 .. 2005]{|y| y.nodes( :out, via: HasPosition )}
fires this query: `" select out('has_position') from (select from tg_Jahr where w between 2000 and 2005) "`
This selects six `Jahr`-vertices and performes the Arcade::Query.nodes command on the selection.
## Horizontal Connections
Besides the hierarchically TimeGraph »Jahr <-->Monat <--> Tag <--> Stunde« the Vertices are connected
horizontally via »grid_to«-Edges. This enables an easy access to the neighbours.
On the Tg::TimeBase-Level a method »vector« is implemented, that gathers the adjacent vertices
via traverse.
``` ruby
start = "7.4.2000".to_tg
start.vector(-3).datum
=> ["5.4.2000", "6.4.2000", "7.4.2000"]
start.vector(3).datum
=> ["7.4.2000", "8.4.2000", "9.4.2000"]
start.vector(3) { :w } => generates "select w from ..."
=> [ 7, 8, 9 ]
start.vector(3, function: :median) { :w } => generates "select median(w) from ..."
=> 8.0To assign something to the TimeGrid its sufficient to create an edge-class and connect this »something», which is represented as Vertex, to the grid.
However, if a csv-file with a »date« column is present, it's easier to assign it directly to the grid:
# csv record
Ticker,Date/Time,Open,High,Low,Close,Volume,Open Interest,
^GSPTSE,09.09.2016,14717.23,14717.23,14502.90,14540.00,202109040,0assuming the record is read as string, then assigning is straightforward:
ticker, date, open, high, low, close, volume, oi = record.split(',')
date.to_tg.assign vertex: Ticker.new( high: high, ..), via: OhlcConnect, symbol: ticker The updated TimeBase-Object is returned.
»OhlcConnect« is the edge-class and »Ticker« represents a vertex-class
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent