Changes between Version 4 and Version 5 of PTCNets
- Timestamp:
- Mar 27, 2022, 1:38:55 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
PTCNets
v4 v5 84 84 It is possible and intended to inscribe multiple transitions with the same up- or downlink. In that case, a transition has multiple possible communication partners. 85 85 86 Additionally, transition channels may carry parameters in the form of variables and integers (e.g. this:sync(x, 2) and :sync(1, y)). Note that only transitions with the same digits("Stelligkeit") may communicate. Also, if an integer is at position i in the parameter tuple, the communication partner needs a variable at the same position i.86 Additionally, transition channels may carry parameters in the form of variables and integers (e.g. this:sync(x, 2) and :sync(1, y)). Note that only transitions with the same arity ("Stelligkeit") may communicate. Also, if an integer is at position i in the parameter tuple, the communication partner needs a variable at the same position i. 87 87 88 88 Arcs connected to communicating transitions may be inscribed with its variables (e.g. x ). … … 104 104 105 105 Modelers can select these settings in a GUI, that automatically opens whenever the simulation of a syntactically correct PTC-net is started. The GUI for a Sender-Receiver example can be seen in the next figure, together with the panel to manually create synchronization options. 106 107 [[Image(SystemNetGUI.png)]] [[Image(customCompositionGUI.png)]] 108 109 == Examples 110 111 === Producer-Consumer synchronizing within one net instance 112 113 === Trader and Supplier communicating between multiple net instances