![]() Insert into r4CellStay partition by player Select s.playerId, e.timems as endTimems, Select c.pid as playerId, timer.ts as time, c.x,Ĭ.y, c.cell as newCell, c.cell as oldCell,įollowing query use results from above two queries and calculate the time spent on each cell. Join PlayersCell\#window.unique(pid) as c Following query detects when a player has changed the cell.įollowing query join the events with 1 second timer. The queries are given below, and you can find the explanation from the paper. First part we can solve just like with the first usecase, but to make sure we get an event once a second, we had to couple it with a timer. However, this usecase needs updates once every second. Usecase three divides the ground to a grid, and calculate the time a player spends on each cell. Select b.pid as playerId, b.tid as teamId,įollowing query detects hits at the goal. Select p.sid, p.ts, p.x, p.y, p.z, p.a, p.pid,p.tid,įollowing query detects the event streams while a player is in control of the ball. Players\#window.length(1) as p unidirectional Here fuctions like debs:isGoingToGoal(.) and debs:getDistance(.) are java custom functions we wrote and registered with Siddhi. We implemented both using event sequences, and following are the queries. The usecase four is to detect hits and emit events if the ball is going to the goal. We identify hits when a ball is within one meter of a player and its acceleration increases by more than 55ms-2. A player controls the ball from the time he hit the ball until someone has hit the ball, ball goes out of the ground, or game is stopped. Usecase 2
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |