Unrolling LTL Specifications Sample Clauses

Unrolling LTL Specifications. ‌ LTL is a temporal logic that specifies properties over the future over paths, where the term temporal refers to a discrete notion of time. LTL does not in itself include the ability to reason about concrete, dense time, but rather considers timing as a sequence of computation steps. For instance, the logic itself provides the means to express that some property should hold after three computation steps, but not that it holds after three seconds, as opposed to more advanced logics such as timed computation tree logic (TCTL). Specifications in LTL are built from a finite set of atomic propositions, Boolean operators and the following temporal modalities: Globally ψ A property ψ shall hold globally, denoted Gψ. Finally ψ Eventually property ψ shall be satisfied, denoted Fψ. Next ψ In the successor state, ψ shall be satisfied, denoted Xψ. ψ1 Until ψ2 Property ψ1 shall hold until ψ2 holds, denoted ψ1Uψ2. These operators can be combined and nested to express complex properties. All LTL formulae are implicitly universally quantified, which means that the properties have to hold for all paths, as opposed to CTL which allows to specify properties over different possible futures by considering the branching structure of the computations1. 1At a first glance, CTL may thus appear to be more expressive than LTL. However, expressiveness of both logics is incomparable, and CTL has certain disadvantages when it comes to its application. See Sect. 2 for a discussion. The semantics of LTL is specified over infinite paths, which are naturally specified as ω-words π = s0s1 . . . over the alphabet 2AP where AP denotes the set of atomic properties. Let πi = sisi+1 . . . denote the suffix of π starting at position i. The satisfaction |= of an ω-word π is then specified as: • π |= p for p ∈ AP if and only iff p ∈ s0 • π |= ¬ψ iff π |= ψ • π |= ψ1 ∧ ψ2 iff π |= ψ1 and π |= ψ2 • π |= ψ1 ∨ ψ2 iff π |= ψ1 or π |= ψ2 • π |= X ψ iff π1 |= ψ. • π |= ψ1 U ψ2 iff there exists iN such that πi |= ψ and for all 0 ≤ k ≤ i, πk |= ψ1. The semantics of Gψ and Fψ follow directly from the following equiva- lences: • G ψ ≡ ¬F ¬ψ • F ψ ≡ true U ψ This semantics can naturally be unrolled until a fixed depth k, for exam- ple: F ψi = ψi ∨ ψi+1 ∨ . . . ∨ ψk G ψi = ψi ∧ ψi+1 ∧ . . . ∧ ψk 2 1 1 2 2 G ψi ∧ F ψi = (ψi ∨ ψi+1 ∨ . . . ∨ ψk) ∧ (ψi ∧ ψi+1 ∧ . . . ∧ ψk) This approach allows the specification to be passed directly to an SMT solver so that M can be checked for satisfiability.
AutoNDA by SimpleDocs

Related to Unrolling LTL Specifications

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

Time is Money Join Law Insider Premium to draft better contracts faster.