diff --git a/models/Application_examples/Application_Process.mp b/models/Application_examples/Application_Process.mp index 4c2ad85d3bc601e3449ec5e0bdbdf7e46cf106e6..edf8804059590f80561868b68ae0b33c0de03e17 100644 --- a/models/Application_examples/Application_Process.mp +++ b/models/Application_examples/Application_Process.mp @@ -45,7 +45,8 @@ │*│ └────────────────────────────────────────────────────┘ │ │*│ │ │*│ ┌─[ Search Terms ]───────────────────────────────────┠│ -│*│ │ behavior, application process; isomorphism │ │ +│*│ │ behavior, application process; isomorphism; │ │ +│*│ │ analysis, schedule │ │ │*│ └────────────────────────────────────────────────────┘ │ │*│ │ │*│ ┌─[ Instructions ]───────────────────────────────────┠│ diff --git a/models/Application_examples/Autonomous_Car.mp b/models/Application_examples/Autonomous_Car.mp index 744b00135db9b0ed8410ee2ebff3012780476fc2..231ad6377cc52d430b2a40a4c7b8a37324aeca1d 100644 --- a/models/Application_examples/Autonomous_Car.mp +++ b/models/Application_examples/Autonomous_Car.mp @@ -19,8 +19,8 @@ │*│ │ technology. It applies COORDINATE statements to │ │ │*│ │ add dependencies between the events within the │ │ │*│ │ roots "Car" and "User". Without the COORDINATE │ │ -│*│ │ statements, the event tracesproduce invalid or │ │ -│*│ │ erroneous combinations of events fromdifferent │ │ +│*│ │ statements, the event traces produce invalid or │ │ +│*│ │ erroneous combinations of events from different │ │ │*│ │ roots, such as the car behaving as if it had │ │ │*│ │ arrived at its destination when in fact it had │ │ │*│ │ not. │ │ @@ -35,7 +35,7 @@ │*│ │ │*│ ┌─[ Search Terms ]───────────────────────────────────┠│ │*│ │ behavior, autonomous car; autonomous; │ │ -│*│ │ failure mode analysis; coordination, event │ │ +│*│ │ analysis, failure mode; coordination, event │ │ │*│ └────────────────────────────────────────────────────┘ │ │*│ │ │*│ ┌─[ Instructions ]───────────────────────────────────┠│ diff --git a/models/Application_examples/Dining_Philosophers.mp b/models/Application_examples/Dining_Philosophers.mp index 34562e771d6101bfaceddf485c6f60ffb3be5839..df9fd18e5240482e45234ba7dc364f414d99a273 100644 --- a/models/Application_examples/Dining_Philosophers.mp +++ b/models/Application_examples/Dining_Philosophers.mp @@ -15,7 +15,7 @@ │*│ ┌─[ Description ]────────────────────────────────────┠│ │*│ │ This model demonstrates using COORDINATE, ENSURE, │ │ │*│ │ and IF statements to come up with an answer to a │ │ -│*│ │ problem oftenused to illustrate synchronization │ │ +│*│ │ problem often used to illustrate synchronization │ │ │*│ │ issues. The logic and problem solving potential of │ │ │*│ │ Monterey Phoenix is shown through its ability to │ │ │*│ │ come up with the exhaustive number of solutions to │ │ diff --git a/models/Application_examples/FindAdvisor.mp b/models/Application_examples/FindAdvisor.mp index 160714757263a9bf1948811db17f6cfff1c54deb..51889918bcbcebe1353b6a36d37146076230875a 100644 --- a/models/Application_examples/FindAdvisor.mp +++ b/models/Application_examples/FindAdvisor.mp @@ -16,7 +16,7 @@ │*│ │ terms of possible decisions they could make. This │ │ │*│ │ example models the process of a student finding an │ │ │*│ │ advisor for a potentially MP-related research │ │ -│*│ │ topic. To do so, it uses rootevents, composite │ │ +│*│ │ topic. To do so, it uses root events, composite │ │ │*│ │ events, atomic events, "or" logic ( ... | ... ), │ │ │*│ │ and COORDINATE statements. Users should inspect │ │ │*│ │ this model when considering the process of finding │ │ diff --git a/models/Application_examples/Manufacturing_Process.mp b/models/Application_examples/Manufacturing_Process.mp index 264ade432b0544612d0ab056ab0eac2495ecaadb..a45ea0de79fe4e09f3dd225c229fb47b67fe878f 100644 --- a/models/Application_examples/Manufacturing_Process.mp +++ b/models/Application_examples/Manufacturing_Process.mp @@ -17,8 +17,8 @@ │*│ ┌─[ Description ]────────────────────────────────────┠│ │*│ │ This model demonstrates a cost analysis application│ │ │*│ │ of Monterey Phoenix modeling to a manufacturing │ │ -│*│ │ process. This model was originally composed using │ │ -│*│ │ Eagle6, a prototype MP user interface. Eagle6 did │ │ +│*│ │ process. This model was originally composed using │ │ +│*│ │ Eagle6, a prototype MP user interface. Eagle6 did │ │ │*│ │ not implement COORDINATE statements, probabilities,│ │ │*│ │ or event attributes so the original model used │ │ │*│ │ SHARE ALL to simulate COORDINATE and performed cost│ │ @@ -36,7 +36,7 @@ │*│ │ │*│ ┌─[ Search Terms ]───────────────────────────────────┠│ │*│ │ behavior, manufacturing process; analysis, cost; │ │ -│*│ │ reports, local; reports, global │ │ +│*│ │ report, local; report, global │ │ │*│ └────────────────────────────────────────────────────┘ │ │*│ │ │*│ ┌─[ Instructions ]───────────────────────────────────┠│ diff --git a/models/Application_examples/Martian_Lander.mp b/models/Application_examples/Martian_Lander.mp index 8c6fc315a254b9b84d30ff0d45b1a2e6beaa4f87..7ffd4d1dbd5e330099e761a3fd2f3d34c361988f 100644 --- a/models/Application_examples/Martian_Lander.mp +++ b/models/Application_examples/Martian_Lander.mp @@ -70,7 +70,7 @@ │*│ │ │ │ │*│ │ In summary, this model demonstrates the use of │ │ │*│ │ COORDINATE statements to model the relationships │ │ -│*│ │ of landing eventsand make those events easier to │ │ +│*│ │ of landing events and make those events easier to │ │ │*│ │ understand using charts and "comments" from SAY │ │ │*│ │ statements. Users can reference this model for │ │ │*│ │ advice on COORDINATE statements and using MP to │ │ diff --git a/models/Application_examples/Supply_Chain_with_Two_Cyber_Threats.mp b/models/Application_examples/Supply_Chain_with_Two_Cyber_Threats.mp index ba68f3ab0ed6b95520f5d15ce8eb648089c9d220..4e31a058ad0261ee3b38f1ea04cac24f22ca5281 100644 --- a/models/Application_examples/Supply_Chain_with_Two_Cyber_Threats.mp +++ b/models/Application_examples/Supply_Chain_with_Two_Cyber_Threats.mp @@ -80,7 +80,7 @@ │*│ │ behavior, supply chain; coordination, event; │ │ │*│ │ cyber threat; cyber-attack; │ │ │*│ │ event attribute, number; table; trace annotation; │ │ -│*│ │ risk score; risk analysis; SAY statement; │ │ +│*│ │ risk score; analysis, risk; SAY statement; │ │ │*│ │ MARK command; report, global │ │ │*│ └────────────────────────────────────────────────────┘ │ │*│ │ diff --git a/models/Application_examples/Swarm_Search_and_Track.mp b/models/Application_examples/Swarm_Search_and_Track.mp index eb1df3ef885c89bec3ec18a312ac36c1aceb39bd..4b65e049430457dbcdf2f6553cf75d27ee64147b 100644 --- a/models/Application_examples/Swarm_Search_and_Track.mp +++ b/models/Application_examples/Swarm_Search_and_Track.mp @@ -23,7 +23,7 @@ │*│ │ UAVs. The bingo fuel condition was modeled as an │ │ │*│ │ optional event, in which case a UAV has just │ │ │*│ │ enough fuel remaining to safely return to the │ │ -│*│ │ desired landing site. Among thetraces produced │ │ +│*│ │ desired landing site. Among the traces produced │ │ │*│ │ there is one particularly questionable scenario in │ │ │*│ │ which a UAV reached the bingo fuel condition and │ │ │*│ │ then began to track a target. Several possible │ │ diff --git a/models/Application_examples/Swarm_UAV.mp b/models/Application_examples/Swarm_UAV.mp index 30cb3d4d96304d8b4cf7ca31099cfd94819f2332..478baf42973669287c856144e25a41b7ca681ce9 100644 --- a/models/Application_examples/Swarm_UAV.mp +++ b/models/Application_examples/Swarm_UAV.mp @@ -28,7 +28,7 @@ │*│ │ multiple unmanned aerial vehicles (UAVs) with │ │ │*│ │ identical behavior in preflight, launch, ingress, │ │ │*│ │ egress and recovery phases. The "Perform_Mission" │ │ -│*│ │ event isabstract; see the Swarm_Search_and_Track │ │ +│*│ │ event is abstract; see the Swarm_Search_and_Track │ │ │*│ │ model in the Application_examples folder for an │ │ │*│ │ elaboration on an example mission. │ │ │*│ └────────────────────────────────────────────────────┘ │ diff --git a/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp b/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp index c8c4f9118f33fa2b0c219566063ac866113a008d..71cbcf44db63cabd40e30bd0e2f076016c44e07c 100644 --- a/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp +++ b/models/Example19_StackBehavior_BayesianProbabilityCalculationsType2.mp @@ -26,7 +26,7 @@ │*│ │ constrained to pop only if push occurs before it?" │ │ │*│ │ │ │ │*│ │ When run on Firebird, the output also shows Type 1 │ │ -│*│ │ trace probability (p=nnnn on the right scroll bar, │ │ +│*│ │ trace probability (p=nnnn on the right scroll bar),│ │ │*│ │ which will be different from the calculated Type 2 │ │ │*│ │ values. This difference is owed to the fact that │ │ │*│ │ Type 1 assumes that probability of selecting an │ │ diff --git a/models/Example35_Authentication_SystemReuse.mp b/models/Example35_Authentication_SystemReuse.mp index 116566b7fa9615952401be2aba0b90a1401a0c87..377f198adc8d013f948b196d6b6f393ebbe15997 100644 --- a/models/Example35_Authentication_SystemReuse.mp +++ b/models/Example35_Authentication_SystemReuse.mp @@ -59,8 +59,8 @@ │*│ │ Run for Scopes 1 and up. Viewing of traces also │ │ │*│ │ includes a "Swim Lanes" option. At Scope 3 and │ │ │*│ │ above, the attempts_exhausted event can be seen. │ │ -│*│ │ You may hide the Requestor node in the event trace │ │ -│*│ │ graph, since the User will copy all Requestor's │ │ +│*│ │ You may hide the Requester node in the event trace │ │ +│*│ │ graph, since the User will copy all Requester's │ │ │*│ │ behavior. │ │ │*│ ├─[ Run Statistics ]─────────────────────────────────┤ │ │*│ │ Scope 1: 3 traces in less than 1 sec. │ │