FMU interfaces Sample Clauses

FMU interfaces. ‌ The model of a valid FMU is simpler. It captures the control flow of an FMU, specifying, at each stage, the API functions to which it can respond. Unsurprisingly, it has some of the restrictions of a master algorithm, but it is much more lax, in that it captures just the expected capabilities of an ^ process FMUStatesManager = i : FMI 2COMP • begin ^ AllowAGet = fmi 2GetFMUState.i?s?st −→ AllowsGetsAndSets(s) ^ AllowsGetsAndSets = s : FMUSTATE • fmi 2GetFMUState.i?t ?st −→ AllowsGetsAndSets(t ) fQmi 2SetFMUState.i!s?st −→ AllowsGetsAndSets(s) • fmi 2Instantiate.i?b −→ AllowAGet end Figure 5: Model of FMUStateManager FMU. At first, the only API function that is available is fmi2Instantiate. The simple action below specifies this behaviour.  Instantiation =  g Q¬ g b status := fmi 2OK ; Instantiated fmi 2Instantiate.i?b −→ b status := fmi 2Fatal ; RUN (FMUAPI (i))  A state component status records the result of the last call to an API function. In this case, it is updated based on the boolean b returned by fmi 2Instantiate. If the instantiation is successful, the behaviour is described by Instantiated , sketched below; otherwise, it is unrestricted: specified by RUN (FMUAPI (i)), which allows the occurrence of any API functions, in any order. Instantiated = Q  g status = fmi 2Fatal g RUN (FMUAPI (i)) status ƒ∈ {fmi 2Error, fmi 2Fatal} fmi 2Get.i?n?v ?st −→ status := st ; Instantiated  Q Q· · ·  fmi 2DoStep.i?t ?hc?st −→ status := st ; Instantiated  st ƒ= fmi 2Fatal g fmi 2FreeInstance!i?st −→ · · · Again, if there is a fatal error, the behaviour is unrestricted. If there is no error, all functions except fmi2Instantiate are available. Finally, if there is a non-fatal error, only fmi2FreeInstance is possible. While a pattern of calls is defined by a master algorithm, so that, for example, all outputs are obtained before the inputs are distributed, the FMU is passive and does not impose such a policy on its use. So, the various actions enforce only the restrictions in the standard [13, p.105]. Although it is possible to specify a more restricted behaviour for FMUs, such a specification rules out robust FMU implementations that handle calls to the API functions that do not necessarily follow the strict pattern of a co-simulation. Next, we describe how to generate FMU models that follow a more restricted pattern that is adequate for use with valid master algo- rithms. InstantiationMode terminates immediately if there has been an error. Oth- erwise...
Sample 1
AutoNDA by SimpleDocs
FMU interfaces. ‌ The model of an FMU is simpler than the MA. It is captured by the process FMUInterface declared below, which takes the FMU identifier as a param- eter. This process captures the control flow of an FMU, specifying, at each stage, the API functions to which it can respond. Unsurprisingly, it has some of the restrictions of a master algorithm, but it is less restrictive in that it captures just the expected capabilities of an FMU. Its purpose hence not to enforce all constraints of the standard but provide a guideline for implementations. ^ process FMUInterface = i : FMUs • begin state State == [status : B] · · · First of all, we introduce a state component status to record the result of the last call to an API function. Upon start-up of the co-simulation, the only API function that is available is fmi2Instantiate. The simple action below specifies this behaviour. Instantiation = fmi 2Instantiate.i ?b −→ b g status ^:= fmi 2OK ; Instantiated   · · ·
Sample 1

Related to FMU interfaces

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Local Switching Interfaces 4.2.13.1 Deland Actel shall order ports and associated interfaces compatible with the services it wishes to provide as listed in Exhibit A. BellSouth shall provide the following local switching interfaces:

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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