Merge branch 'Pamela_Branch_4' into 'master'

Pamela's Merge Request: 12-26-2021

See merge request !53

models/Example20_Activity_Diagram.mp

@@ -8,7 +8,7 @@
 │*│ │ To show how to extract Activity Diagrams of root   │ │
 │*│ │ events in a schema.                                │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates how to use "SHOW ACTIVITY  │ │
 │*│ │ DIAGRAM" to display events as a flowcharts similar │ │

models/Example21_DataFlow_LocalReport.mp

@@ -8,7 +8,7 @@
 │*│ │ To show how to produce a local report within a     │ │
 │*│ │ trace.                                             │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														              │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ A report is a sequence of related SAY clauses      │ │
 │*│ │ assembled together to make it easier to read and   │ │

models/Example22_UnreliableMessageFlow_GlobalReport.mp

@@ -9,7 +9,7 @@
 │*│ │ To show how to produce a global report across all  │ │
 │*│ │ traces.                                            │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ A global report may be used to assemble            │ │
 │*│ │ information about all traces, e.g., total number   │ │

models/Example23_CarRace_LocalGraph.mp

@@ -8,7 +8,7 @@
 │*│ │ To demonstrate the construction of a local graph   │ │
 │*│ │ on a trace.                                        │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Graphs are "entity-relation" models extracted from │ │
 │*│ │ event traces in order to visualize certain         │ │

models/Example24_ATMWithdrawal_ComponentDiagram.mp

@@ -8,7 +8,7 @@
 │*│ │ To demonstrate the construction of a global graph  │ │
 │*│ │ from all traces in the schema.                     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model builds upon the ATM Withdrawal behavior │ │
 │*│ │ from Example 4 in the MP manual. It shows how to   │ │

models/Example24a_Compiler_ComponentDiagram.mp

@@ -8,7 +8,7 @@
 │*│ │ To demonstrate the construction of a global graph  │ │
 │*│ │ from all traces in the schema.                     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model builds upon the Compiler behavior from  │ │
 │*│ │ Example 42 in the MP manual. It shows how to       │ │

models/Example25_Graph_as_Data_Structure.mp

@@ -9,7 +9,7 @@
 │*│ │ structure for accumulating and rendering           │ │
 │*│ │ statistics from event traces.                      │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Graphs can be used as container data structures    │ │
 │*│ │ (associative arrays) to store and retrieve data    │ │

models/Example26_UnreliableMessageFlow_GlobalQuery.mp

@@ -8,7 +8,7 @@
 │*│ ┌─[ Purpose ]────────────────────────────────────────┐ │
 │*│ │ To demonstrate the use of GLOBAL attributes.       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This example uses the Unreliable Message Flow from │ │
 │*│ │ Example 8 in the MP manual to show how to          │ │
@@ -29,9 +29,9 @@
 │*│ │ than 5. That can be done using explicit iteration  │ │
 │*│ │ limit (running for instance, for scope 1), like:   │ │
 │*│ │                                                    │ │
-│*│ │ ROOT 	Sender: 	(+<1..7> send +);                │ │
-│*│ │ ROOT 	Receiver: 	(+<1..7> (receive |<<0.2>>       │ │
-│*│ │                            does_not_receive) +);   │ │
+│*│ │ ROOT   Sender:     (+<1..7> send +);               │ │
+│*│ │ ROOT   Receiver:   (+<1..7> (receive |<<0.2>>      │ │
+│*│ │                     does_not_receive) +);          │ │
 │*│ └────────────────────────────────────────────────────┘ │
 │*│                                                        │
 │*│ ┌─[ References ]─────────────────────────────────────┐ │

models/Example27_Table_and_Bar_Chart.mp

@@ -9,7 +9,7 @@
 │*│ │ current trace in a table and then render the table │ │
 │*│ │ as a bar chart.                                    │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This example model shows how to create and         │ │
 │*│ │ populate a table with data collected from a graph  │ │

models/Example28_Histogram.mp

@@ -9,7 +9,7 @@
 │*│ │ histogram from Type 1 probabilities of traces in   │ │
 │*│ │ an MP model.                                       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ A histogram represents the distribution of         │ │
 │*│ │ numerical data into "bins" or "buckets." The first │ │

models/Example29_Gantt_Chart.mp

@@ -8,7 +8,7 @@
 │*│ │ To demonstrate how to construct a Gantt Chart  	 │ │
 │*│ │ using event timing attributes.                     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model shows how to assign non-zero timing     │ │
 │*│ │ attributes to events and visualize the whole-trace │ │

models/Example30_MicrowaveOven_ModelingModelChecking.mp

@@ -7,7 +7,7 @@
 │*│ ┌─[ Purpose ]────────────────────────────────────────┐ │
 │*│ │ To demonstrate model checking for a small scope.   │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This is a behavior model of a microwave oven built │ │
 │*│ │ from states and transitions [Clarke et al. 1999,   │ │

models/Example31_Petri_Net.mp

@@ -7,7 +7,7 @@
 │*│ ┌─[ Purpose ]────────────────────────────────────────┐ │
 │*│ │ To demonstrate the modeling of a Petri net in MP.  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This is a behavior model of the Petri net diagram  │ │
 │*│ │ above Example 28 in the MP v.4 Language Manual.    │ │

models/Example32_ATMWithdrawal_StatechartView.mp

@@ -9,7 +9,7 @@
 │*│ │ To demonstrate how to extract a Statechart view    │ │
 │*│ │ from an MP model.                                  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ A statechart model is a diagram where states       │ │
 │*│ │ represent states of the system and transitions     │ │

models/Example33_FiniteStateDiagram_PathAnnotation.mp

@@ -12,7 +12,7 @@
 │*│ │ 2) generate event traces as annotated paths        │ │
 │*│ │    through the diagram.                            │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ The following MP schema models the behavior of a   │ │
 │*│ │ finite state diagram with a single state loop      │ │

models/Example34_FiniteStateDiagram_PathDiagram.mp

@@ -12,7 +12,7 @@
 │*│ │ 2) the state transition diagram in the global      │ │
 │*│ │    view.                                           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ The following MP code modifies the code in Example │ │
 │*│ │ 26 from the MP Language Manual to add a path graph │ │

models/Example35_Authentication_SystemReuse.mp

@@ -9,7 +9,7 @@
 │*│ │ composition operation. Authentication system's     │ │
 │*│ │ behavior for reuse with MAP operation.             │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model of an authentication subsystem maps     │ │
 │*│ │ reusable behaviors of a generic Requester onto     │ │

models/Example36_Compiler1_ComponentReuse.mp

@@ -11,7 +11,7 @@
 │*│ │ the specification of component behavior and the    │ │
 │*│ │ specification of interactions between components.  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Examples 36 and 37 are models of a bottom-up       │ │
 │*│ │ parser with lexical analyzer based on regular      │ │

models/Example37_Compiler2_ComponentReuse.mp

@@ -10,7 +10,7 @@
 │*│ │ the specification of component behavior and the    │ │
 │*│ │ specification of interactions between components.  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Examples 36 and 37 are models of a bottom-up       │ │
 │*│ │ parser with lexical analyzer based on regular      │ │

models/Example38_Merging_Root_Events_to_Reduce_Run_Time.mp

@@ -10,7 +10,7 @@
 │*│ │ derivations in order to reduce run time for larger │ │
 │*│ │ models.                                            │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model has several interacting root events,    │ │
 │*│ │ where roots B and C have several coordination      │ │