filter channel's data constraint in a Reo network with join node

16 weergaven
Naar het eerste ongelezen bericht

Alireza Farhadi

ongelezen,
10 feb 2013, 14:24:4210-02-2013
aan reo...@googlegroups.com
Dear Member,

As all of you know a join node synchronizes all its inputs simultaneously and makes a data item which is combination of all of input data items. If we have a situation in a Reo network such that a filter channel receives joined data item once (through a path contains join node) and receives a single data item in next time from other path. How to deal with this situation in Reo filter channel? Is there a way to distinguish this difference in data dimension over a data sensitive channels?

Regards,
Alireza Farhadi

Natallia Kokash

ongelezen,
10 feb 2013, 20:39:4810-02-2013
aan Alireza Farhadi, reo...@googlegroups.com
Dear Alireza,

you can use type recognition functions in filter conditions.

For example, if we assume that writers supply a singleton x as input and there is a join node in a Reo circuit, the data type that Reo circuit deals with (Data) is either x or a pair of two items of type Data:
Data = struct x?isSingleton | Tuple(t1 : Data, t2 : Data)?isTuple;

So, a filter receives a data item d of type Data and you can use conditions like isSingleton(d) or isTuple)(d) to establish its subtype.

Regards,
Natallia
--
You received this message because you are subscribed to the Google Groups "reo-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reo-dev+u...@googlegroups.com.
To post to this group, send email to reo...@googlegroups.com.
Visit this group at http://groups.google.com/group/reo-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Allen beantwoorden
Auteur beantwoorden
Doorsturen
0 nieuwe berichten