Changes between Version 6 and Version 7 of ReferenceNetsReachabilityGraph

Timestamp:

May 3, 2019, 7:14:56 PM (6 years ago)

Author:

5willrod

Comment:

--

ReferenceNetsReachabilityGraph

@@ -42 +42 @@
 Any node represents the root net instance with a certain marking.
 They can be expanded, which will open a copy of the root net instance in this particular state.
-This net instance behaves like a simulation step which can be fully explored, meaning that all nets that this net has a reference of can be explored with their current marking, including, again, nets referenced in this net.
+This net instance behaves like a simulation step which can be fully inspected, meaning that all nets that this net has a reference of can be explored with their current marking, including, again, nets referenced in this net.
 
 For any firing that happens within a subnet, the arrow is labeled with the identifier of the subnet proceeding the transition identifier, whereas transitions in the root net are only labeled with their identifier.
@@ -48 +48 @@
 === Example 1
 
+The first example is the classic producer consumer problem, where producer and consumer are distributed into an own net each.
+Their net instances are created in the system net, which also holds the storage place for the producer and consumer.
+The synchronisation happens via synchronous channels.
+
 [[Image(prodcons-complete.pdf)]]
+
+The ReferenceNetsReachabilityGraph Plugin is started with the system net as the root net.
+As the synchronous calls are initiated from the system net, they are listed without a prefix.
+The internal state changes of the producer/consumer have the net instance id as prefix.
 
 [[Image(prod-cons-rg-2.pdf)]]
 
+The arrow inscription with the yellow background is an extended inscription.
+It showcases how synchronous channels are listed.
+
+
 === Example 2