Documentation is missing

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Documentation is missing

Post by flp » Tue Sep 09, 2014 4:29 pm

Actually I miss some documentation about the leftjoin and the intersection is missing.

http://odysseus.informatik.uni-oldenbur ... n+operator
http://odysseus.informatik.uni-oldenbur ... n+operator

Additionally, I would appreciate a bit more detailed documentation about the union, synchronize and the filter operator.

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Documentation is missing

Post by Marco Grawunder » Tue Sep 09, 2014 5:25 pm

Left Join and Intersection do not work at the moment.

I added some further infos to union, synchronize and filter.

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Documentation is missing

Post by flp » Fri Sep 12, 2014 4:32 pm

I appreciate it.

Furthermore, I would like to see an example about the port usage :)

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Documentation is missing

Post by flp » Sat Sep 13, 2014 9:43 pm

Also the DISTINCT operator is not really described. Furthermore, Odysseus does not seem to recognize the operator :/

User avatar
ckuka
Posts: 35
Joined: Tue Jul 29, 2014 10:55 am
Location: Shanghai, P.R. China/中国上海
Contact:

Re: Documentation is missing

Post by ckuka » Sun Sep 14, 2014 2:27 am

The Distinct operator implementation is missing. (Reported as #ODY-718)
kind regards / 祝好
Christian Kuka

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Documentation is missing

Post by Marco Grawunder » Mon Sep 15, 2014 11:06 am

The port usage is described in the general PQL description:

http://odysseus.offis.uni-oldenburg.de: ... Id=4587829

Its simple <PortNr>:Name, e.g 1:SELECT to access the output port 1 of the SELECT-Operator

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Documentation is missing

Post by Marco Grawunder » Mon Sep 15, 2014 11:10 am

DISTINCT is rather needless for our szenario: This meens, the element must have exactly the same validity (time) intervall and the same content.

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Documentation is missing

Post by flp » Tue Sep 16, 2014 12:45 am

Hm, I wanted to use the DISTINCT operator to get a value only once instead of thousand times.

I thought out and implemented some solutions, but noone worked.

Actually, I want to find the timestamp of a goal. But I want to display that only once for every goal.

One idea was it to compare it to the timestamp of the last goal, but that does not return anything:

Code: Select all

add_last_goal_time = STATEMAP({expressions = ['goal_time', ['__last_1.goal_time', 'last_goal_time']]}, goal_time_in_match_minutes)
goals_only_once = COALESCE({predicate='goal_time = last_goal_time', aggregations=[['last', 'goal_time', 'goal_time']]}, add_last_goal_time)
Another idea was to achieve the result by an aggregation:

Code: Select all

add_last_goal_time = STATEMAP({expressions = ['goal_time', ['goal_time', 'goal_time2']]}, goal_time_in_match_minutes)
goals_only_once = AGGREGATE({group_by = ['goal_time'], aggregations=[['first', 'goal_time2', 'goal_time']]}, add_last_goal_time)
I could imagine that the metadata is again the problem. Anyway, I converted all timestamps except the match timestamp to longs.
For understanding reasons I uploaded the query again to the dropbox folder. It's the goal_counter.qry.

https://www.dropbox.com/sh/4nffkv64jfmn ... bmT0a?dl=0

User avatar
Michael Brand
Posts: 12
Joined: Tue Jul 29, 2014 9:56 am
Location: Oldenburg, Germany
Contact:

Re: Documentation is missing

Post by Michael Brand » Tue Sep 16, 2014 7:06 am

Hey,

thought about a ChangeDetect for that goal ts?
http://odysseus.informatik.uni-oldenbur ... t+operator
Note that you should send heartbeats and set a heartbeatrate for ChangeDetect if you use the results for e.g. a join (because goals happen not that often)
Greetings
Michael

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Documentation is missing

Post by flp » Thu Sep 18, 2014 10:42 pm

Great idea, thanks!

Additionally, a bit more information about the merge operator and the merge process would be great.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest