VDM-RT State Types Sample Clauses

VDM-RT State Types. We describe the types needed to describe the state of a VDM-RT model, in terms of CPUs, threads, busses, statements, objects, message and so on. The majority of the types are adapted from [28] but modified for Xxxxxxxx/HOL, for example by the replacement of union types with disjoint unions and algebraic datatypes. Moreover the names of primitives and types differ slightly and we have made a number of simplifications. Datatypes not directly relevant for the semantics (such as patterns) are omitted from the presentation, though present in the Isabelle theories. We also specify some basic types like VDMValue and VDMExpr, and functions like the VDM-SL typing relation x :v t that are omitted. A number of identifier types are also defined, including: • cla-id – class identifier • obj-id – object identifier • op-id – operation identifier • fun-id – function identifier • thr-id – thread identifier • bus-id – bus identifier • var-id – variable identifier We first describe bindings Σ, that are partial functions mapping variables identifiers to VDM values. They are used widely in the semantics to represent state spaces, let definitions, and the result of executing pattern matches. type-synonym Σ = var-id - VDMValue Next we defined pending updates to a state, which are partial mappings from object identifiers to bindings. Each write within an object does not update the global CPU state until specific synchronisation times. Until then, they are stored in a pending buffer. type-synonym Pending = obj-id - Σ An assignment associated variable identifier, or object and variable identifier, with an expres- sion. record Assignment = × asntarget :: var-id + (obj-id var-id) asnexp :: VDMExpr record CallContext = ccpending :: Pending ccstate :: Σ ccpost :: VDMExpr option type-synonym Definition = var-id ∗ VDMExpr The statement type specifies all the different kind of statements that can be constructed in VDM-RT. = Skip A null statement | | | × × × AsyncCall (name: (obj-id op-id) + (cpu-id obj-id op-id)) (args: VDMExpr list) Asychronous call, consisting of a method identifier and arguments × × × | × SyncCall (ctarget: (var-id + (cpu-id thr-id)) option) (name: (obj-id op-id) + (cpu-id obj-id op-id)) (args: VDMExpr list) Sychronous call | × Cases (exp: VDMExpr) (cases: (Pattern Stm) list) Stm option Case statement | Cycles (cycles: VDMExpr) (body: Stm) Cycles statement | DurOrPDur (durOf : DurOrPDur) Either a duration statement or a (semantic) partial duration statement | ForIndex ...
AutoNDA by SimpleDocs

Related to VDM-RT State Types

  • Auction Schedule; Method of Submission of Orders (a) The Funds and the Auction Agent shall conduct Auctions for each series of Preferred Shares in accordance with the schedule set forth below. Such schedule may be changed at any time by the Auction Agent with the consent of the Fund, which consent shall not be withheld unreasonably. The Auction Agent shall give notice of any such change to BD. Such notice shall be received prior to the first Auction Date on which any such change shall be effective. Time Event ---- ----- By 9:30 A.M. Auction Agent advises the Funds and the Broker-Dealers of the Maximum Rate as set forth in Section 3.2(a) hereof.

  • Wage Schedules The Parties shall, upon completing a wage adjustment calculation, forthwith prepare, publish, post and distribute a wage schedule resulting therefrom. The final determination of the wage schedules shall be issued no later than the 7th day of March or September, for the May and November adjustments, respectively.

  • Particular Methods of Procurement of Goods Works and Services (other than Consultants’ Services)

  • Outage Schedules The Connecting Transmission Owner shall post scheduled outages of its transmission facilities on the NYISO OASIS. Developer shall submit its planned maintenance schedules for the Large Generating Facility to Connecting Transmission Owner and NYISO for a minimum of a rolling thirty-six month period. Developer shall update its planned maintenance schedules as necessary. NYISO may direct, or the Connecting Transmission Owner may request, Developer to reschedule its maintenance as necessary to maintain the reliability of the New York State Transmission System. Compensation to Developer for any additional direct costs that the Developer incurs as a result of rescheduling maintenance, including any additional overtime, breaking of maintenance contracts or other costs above and beyond the cost the Developer would have incurred absent the request to reschedule maintenance, shall be in accordance with the ISO OATT. Developer will not be eligible to receive compensation, if during the twelve (12) months prior to the date of the scheduled maintenance, the Developer had modified its schedule of maintenance activities other than at the direction of the NYISO or request of the Connecting Transmission Owner.

  • Additional Wet Weather Procedure 14.15.1 Remaining On Site a) for more than an accumulated total of four hours of ordinary time in any one day; or b) after the meal break, as provided for in clause 17.1 of the Award, for more than an accumulated total of 50% of the normal afternoon work time; or c) during the final two hours of the normal work day for more than an accumulated total of one hour, the Enterprise will not be entitled to require the employees to remain on site beyond the expiration of any of the above circumstances.

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • Time Schedule 4.1. A project schedule is included in Appendix A. 4.2. Any delay of services or change in sequence of tasks must be approved in writing by Delaware. 4.3. In the event that Vendor fails to complete the project or any phase thereof within the time specified in the Contract, or with such additional time as may be granted in writing by Delaware, or fails to prosecute the work, or any separable part thereof, with such diligence as will insure its completion within the time specified in this Agreement or any extensions thereof, Delaware shall suspend the payments scheduled as set forth in Appendix A.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

  • General Provisions Regarding Accounts (a) So long as no Default or Event of Default shall have occurred and be continuing, all or a portion of the funds in the Trust Accounts shall be invested by the Indenture Trustee at the written direction of the Servicer in Permitted Investments as provided in Sections 4.1 and 4.7 of the Sale and Servicing Agreement. All income or other gain (net of losses and investment expenses) from investments of monies deposited in the Trust Accounts shall be withdrawn by the Indenture Trustee from such accounts and distributed (but only under the circumstances set forth in the Sale and Servicing Agreement) as provided in Sections 4.1 and 4.7 of the Sale and Servicing Agreement. The Servicer shall not direct the Indenture Trustee to make any investment of any funds or to sell any investment held in any of the Trust Accounts unless the security interest granted and perfected in such account will continue to be perfected in such investment or the proceeds of such sale, in either case without any further action by any Person, and, in connection with any direction to the Indenture Trustee to make any such investment or sale, if requested by the Indenture Trustee, the Issuer shall deliver to the Indenture Trustee an Opinion of Counsel, acceptable to the Indenture Trustee, to such effect. (b) Subject to Section 6.1(c), the Indenture Trustee shall not in any way be held liable by reason of any insufficiency in any of the Trust Accounts resulting from any loss on any Permitted Investment included therein, except for losses attributable to the Indenture Trustee’s failure to make payments on such Permitted Investments issued by the Indenture Trustee, in its commercial capacity as principal obligor and not as trustee, in accordance with their terms. (c) If (i) the Servicer shall have failed to give written investment directions for any funds on deposit in the Trust Accounts to the Indenture Trustee by 11:00 A.M. (New York City time) (or such other time as may be agreed upon by the Issuer and Indenture Trustee), on the Business Day preceding each Distribution Date, (ii) a Default or Event of Default shall have occurred and be continuing with respect to the Notes but the Notes shall not have been declared immediately due and payable pursuant to Section 5.2 or (iii) the Notes shall have been declared immediately due and payable following an Event of Default, amounts collected or receivable from the Trust Estate are being applied in accordance with Section 5.4 as if there had not been such a declaration, then the Indenture Trustee shall, to the fullest extent practicable, invest and reinvest funds in the Trust Accounts in one or more Permitted Investments.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!