Merge branch 'Pamela_Branch_4' into 'master'

Pamela's Merge Request: 12-26-2021

See merge request !53

models/Application_examples/Martian_Lander.mp

@@ -13,7 +13,7 @@
 │*│ │ Lander, which is an example of real-time system    │ │
 │*│ │ behavior modeling.                                 │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ The landing system operates in one of two modes:   │ │
 │*│ │ normal or emergency. When the system is turned on  │ │
@@ -59,14 +59,14 @@
 │*│ │ Action Time in ms                                  │ │
 │*│ │ RACC  10                                           │ │
 │*│ │ STMR  10                                           │ │
-│*│ │ ADJM 	20                                           │ │
-│*│ │ TDP 	10                                           │ │
-│*│ │ IEM 	10                                           │ │
-│*│ │ ETC 	10                                           │ │
-│*│ │ IVEL 	20                                           │ │
-│*│ │ IALT 	20                                           │ │
-│*│ │ CKDT 	10                                           │ │
-│*│ │ RRM 	10                                           │ │
+│*│ │ ADJM  20                                           │ │
+│*│ │ TDP   10                                           │ │
+│*│ │ IEM   10                                           │ │
+│*│ │ ETC   10                                           │ │
+│*│ │ IVEL  20                                           │ │
+│*│ │ IALT  20                                           │ │
+│*│ │ CKDT  10                                           │ │
+│*│ │ RRM   10                                           │ │
 │*│ │                                                    │ │
 │*│ │ In summary, this model demonstrates the use of     │ │
 │*│ │ COORDINATE statements to model the relationships   │ │

models/Application_examples/Prisoners_Dilemma.mp

@@ -11,7 +11,7 @@
 │*│ │ To demonstrate using MP to model the logic of a    │ │
 │*│ │ game scenario.                                     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Users looking to model exhaustive logical game     │ │
 │*│ │ scenarios may want to use this model as an         │ │

models/Application_examples/Railroad_Crossing_Safety.mp

@@ -10,7 +10,7 @@
 │*│ │ To illustrate timing attribute use in MP, here for │ │
 │*│ │ displaying a railroad crossing scenario.           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using BUILD statements to  │ │
 │*│ │ add time to a model of car and train interactions  │ │

models/Application_examples/Replay_Attack.mp

@@ -10,7 +10,7 @@
 │*│ │ To illustrate MP modeling of a replay attack       │ │
 │*│ │ involving data transmission.                       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates a well known attack        │ │
 │*│ │ strategy on a communication system. Users may use  │ │

models/Application_examples/Small_Package_Delivery.mp

@@ -13,7 +13,7 @@
 │*│ │ search and rescue scenario and to illustrate the   │ │
 │*│ │ impacts of overloading constraints in an MP model. │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates overusing COORDINATE and   │ │
 │*│ │ ENSURE statements to create a model of a complex   │ │

models/Application_examples/Spent_Fuel_Cooling_and_Cleanup.mp

@@ -16,7 +16,7 @@
 │*│ │ and purification system, specifically a spent      │ │
 │*│ │ nuclear fuel cooling pool.                         │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates identifying the components │ │
 │*│ │ of and interactions among a spent nuclear fuel     │ │

models/Application_examples/Spiral_Software_Process.mp

@@ -10,7 +10,7 @@
 │*│ │ To illustrate event sharing in order to model the  │ │
 │*│ │ spiral software development process.               │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates the usage of shared events │ │
 │*│ │ to model the spiral software process to develop a  │ │

models/Application_examples/Supply_Chain_with_Two_Cyber_Threats.mp

@@ -37,7 +37,7 @@
 │*│ │ to demonstrate calculating individual and total    │ │
 │*│ │ risk scores.                                       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates performing detailed risk   │ │
 │*│ │ analysis on a supply chain potentially affected by │ │

models/Application_examples/Surgery.mp

@@ -11,7 +11,7 @@
 │*│ │ involving several actors, including the            │ │
 │*│ │ environment.                                       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model shows an example of decisions made by a │ │
 │*│ │ leader (Physician), a subordinate(s) (Nurse(s)),   │ │

models/Application_examples/Swarm_Search_and_Track.mp

@@ -14,7 +14,7 @@
 │*│ │ unmanned aerial vehicle scenario involving a       │ │
 │*│ │ low fuel condition.                                │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model was developed by an NPS student with    │ │
 │*│ │ UAV operation experience with the intent to        │ │

models/Application_examples/Swarm_UAV.mp

@@ -22,7 +22,7 @@
 │*│ │ are possible to appear within event traces, taking │ │
 │*│ │ effect when the scope is increased.                │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using iteration to model   │ │
 │*│ │ multiple unmanned aerial vehicles (UAVs) with      │ │

models/Application_examples/Turtles_in_the_Desert.mp

@@ -12,7 +12,7 @@
 │*│ │ highlighting the benefits of complete example set  │ │
 │*│ │ generation in MP.                                  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Three turtles are moving on a desert plain, all in │ │
 │*│ │ the same direction. The first has been asked:      │ │

models/Application_examples/UAV_Ingress.mp

@@ -11,7 +11,7 @@
 │*│ │ unmanned aerial vehicle (UAV) launch and ingress   │ │
 │*│ │ scenario.                                          │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model was developed by an NPS student to      │ │
 │*│ │ specify the ingress phase of a UAV on a            │ │
@@ -51,7 +51,7 @@
 │*│ ┌─[ Instructions ]───────────────────────────────────┐ │
 │*│ │ Run for Scope 1. This model contains an unexpected │ │
 │*│ │ behavior in which the UAV status is acceptable but │ │
-│*│ │ the operator aborts the ingress (trace 2).	     │ │
+│*│ │ the operator aborts the ingress (trace 2).         │ │
 │*│ ├─[ Run Statistics ]─────────────────────────────────┤ │
 │*│ │ Scope 1: 2 traces in less than 1 sec.              │ │
 │*│ └────────────────────────────────────────────────────┘ │

models/Application_examples/UAV_OnStation.mp

@@ -17,7 +17,7 @@
 │*│ │ To illustrate the modeling for system of systems   │ │
 │*│ │ behaviors that include failure mode scenarios.     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│													       │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This is a model for an Unmanned Aerial Vehicle in  │ │
 │*│ │ the OnStation Phase of an ISR mission. It          │ │

models/Application_examples/Unmanned_Spacecraft_Comms.mp

@@ -13,7 +13,7 @@
 │*│ │ spacecraft docking with the International Space    │ │
 │*│ │ Station (ISS).                                     │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model describes a spacecraft communication    │ │
 │*│ │ system that works with the International Space     │ │

models/Application_examples/Web_Browser_Formal_Security.mp

@@ -11,7 +11,7 @@
 │*│ │ communication involving a bad server and a good    │ │
 │*│ │ server.                                            │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This example borrowed from (Jackson 2019)          │ │
 │*│ │ demonstrates how MP can check whether Client's web │ │

models/Application_examples/Wide_Range_Search_for_Wreckage_and_Survivors.mp

@@ -12,7 +12,7 @@
 │*│ │ rescue operation with several environmental and    │ │
 │*│ │ coordination concerns to address.                  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model represents an operational process for   │ │
 │*│ │ use as a common baseline against which alternative │ │

models/Application_examples/Work_Productivity.mp

@@ -10,7 +10,7 @@
 │*│ │ To demonstrate how to print all events present in  │ │
 │*│ │ the trace with timing attributes.                  │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│														   │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model demonstrates using MP to show how       │ │
 │*│ │ visitors can distract workers with stacked time    │ │

models/Example01_SimpleMessageFlow_EventCoordination.mp

@@ -9,7 +9,7 @@
 │*│ │ rules and how to coordinate events from each of    │ │
 │*│ │ those rules.                                       │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│													       │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ Event grammar rules for each root define the       │ │
 │*│ │ derivations for event traces. In this case, we     │ │
@@ -44,8 +44,8 @@
 │*│ │ to view the trace in an activity diagram format.   │ │
 │*│ ├─[ Run Statistics ]─────────────────────────────────┤ │
 │*│ │ Scope 1: 2 traces in less than 1 sec.              │ │
-│*│	│ Scope 2: 3 traces in less than 1 sec.              │ │
-│*│	│ Scope 3: 4 traces in less than 1 sec.              │ │
+│*│ │ Scope 2: 3 traces in less than 1 sec.              │ │
+│*│ │ Scope 3: 4 traces in less than 1 sec.              │ │
 │*│ └────────────────────────────────────────────────────┘ │
 └*┴───────────────────────────────────────────────────────*/
 

models/Example01a_UnreliableMessageFlow_VirtualEvents.mp

@@ -9,7 +9,7 @@
 │*│ │ representing the absence or lack of activity, in   │ │
 │*│ │ this case, the event "does_not_receive."           │ │
 │*│ └────────────────────────────────────────────────────┘ │
-│*│												           │
+│*│                                                        │
 │*│ ┌─[ Description ]────────────────────────────────────┐ │
 │*│ │ This model of sending and receiving events         │ │
 │*│ │ incorporates a possibility that some messages get  │ │