Executor API Sample Clauses

Executor API. ‌‌ The API of the rclc Executor can be divided in two phases: Configuration and Running. #### Configu- ration phase During the configuration phase, the user shall define: - the total number of callbacks - the sequence of the callbacks - trigger condition (optional, default: ANY) - data communcation semantics (optional, default ROS2) As the Executor is intended for embedded controllers, dynamic memory management is crucial. There- fore at initialization of the rclc Executor, the user defines the total number of callbacks. The necessary dynamic memory will be allocated only in this phase and no more memory in the running phase. This makes this Executor static in the sense, that during runtime no additional callbacks can be added. Then, the user adds handles and the corresponding callbacks (e.g. for subscriptions and timers) to the Executor. The order in which this takes place, defines later the sequential processing order during run- time. For each handle the user can specify, if the callback shall be executed only if new data is available (ON_NEW_DATA) or if the callback shall always be executed (ALWAYS). The second option is use- ful when the callback is expected to be called at a fixed rate. The trigger condition defines when the processing of these callbacks shall start. For convenience some default conditions have been defined: - trigger_any(default) : start executing if any callback has new data - trigger_all : start executing if all callbacks have new data - trigger_one(&data) : start executing if data has been received - user_defined_function: the user can also define its own function with more complex logic With ‘trigger_any’ being the default, the current semantics of the rclcpp Executor is selected. The data communication semantics can be - ROS2 (default) - LET To be compatible with ROS2 rclcpp Executor, the existing rclcpp semantics is implemented as ‘ROS2’. That is, with the spin-function the DDS-queue is constantly monitored for new data (rcl_wait). If new data becomes available, then is fetched from DDS (rcl_take) immediately before the callback is executed. All callbacks are processed in the user-defined order, this is the only difference to the rclcpp Executor, in which no order can be specified. Secondly, the LET semantics is implemented such that at the beginning of processing all available data is fetched (rcl_take) and buffered and then the callbacks are processed in the pre-defined operating on the buffered copy. 3.5.2.1 Running phase A...
AutoNDA by SimpleDocs

Related to Executor API

  • Assignment; Successors; Binding Agreement 1. Executive may not assign, pledge or encumber his interest in this Agreement or any part thereof. 2. The Company will require any successor (whether direct or indirect, by purchase, merger, consolidation or otherwise) to all or substantially all of the business and/or assets of the Company, operation of law or by agreement in form and substance reasonably satisfactory to Executive, to assume and agree to perform this Agreement in the same manner and to the same extent that the Company would be required to perform it if no such succession had taken place. 3. This Agreement shall inure to the benefit of and be enforceable by Executive's personal or legal representatives, executors, administrators, successors, heirs, distributee, devisees and legatees. If Executive should die while any amount is at such time payable to him hereunder, all such amounts, unless otherwise provided herein, shall be paid in accordance with the terms of this Agreement to Executive's devisee, legates or other designee or, if there be no such designee, to his estate.

  • Assignment; Successors in Interest No assignment or transfer by either party of such party’s rights and obligations hereunder shall be made except with the prior written consent of the other party hereto. This Agreement shall be binding upon and shall inure to the benefit of the parties and their respective successors and permitted assigns, and any reference to a party shall also be a reference to the successors and permitted assigns thereof, including, without limitation, successors through merger, consolidation, or sale of substantially all of the Company’s equity interests or assets, and shall be binding upon Employee.

  • NO ATTACHMENT; BINDING ON SUCCESSORS (a) Except as required by law, no right to receive payments under this Agreement shall be subject to anticipation, commutation, alienation, sale, assignment, encumbrance, charge, pledge, or hypothecation, or to execution, attachment, levy, or similar process or assignment by operation of law, and any attempt, voluntary or involuntary, to effect any such action shall be null, void, and of no effect. (b) This Agreement shall be binding upon, and inure to the benefit of, Executive and the Bank and their respective successors and assigns.

  • Binding Agreement; Successors (a) This Agreement will be binding upon and inure to the benefit of the Executive (and his personal representative), the Company and any successor organization or organizations which shall succeed to substantially all of the business and property of the Company, whether by means of merger, consolidation, acquisition of all or substantially of all of the assets of the Company or otherwise, including by operation of law. (b) The Company will require any successor (whether direct or indirect, by purchase, merger, consolidation or otherwise) to all or substantially all of the business and/or assets of the Company to assume expressly and agree to perform this Agreement in the same manner and to the same extent that the Company would be required to perform it if no such succession had taken place. (c) For purposes of this Agreement, the term “Company” includes any subsidiaries of the Company and any corporation or other entity which is the surviving or continuing entity in respect of any merger, consolidation or form of business combination in which the Company ceases to exist; provided, however, that for purposes of determining whether a Change in Control has occurred herein, the term “Company” refers to Union Bankshares Corporation or its successors.

  • Binding Agreement; Successors and Assigns All covenants and agreements in this Agreement by the Issuer shall bind its successors and assigns, whether so expressed or not. All agreements of the Secured Party or the Securities Intermediary in this Agreement shall bind its successors, co-trustees and agents.

  • Agreement Binding Upon Successors and Assigns This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective heirs, successors, assigns, executors, trustees or other legal representatives, but the rights and obligations of the parties hereunder may not be Transferred or delegated except as provided in this Agreement and any attempted Transfer or delegation thereof that is not made pursuant to the terms of this Agreement shall be void.

  • Assignment; Binding Upon Successors and Assigns No party hereto may assign any of its rights or obligations hereunder without the prior written consent of the other parties hereto. This Agreement will be binding upon and inure to the benefit of the parties hereto and their respective successors and permitted assigns.

  • BINDING EFFECT; SUCCESSORS & XXXXXXX This Contract shall be binding upon and shall inure to the benefit of the parties hereto and their respective successors and assigns.

  • Assignment; Successors and Assigns, etc Neither the Employer nor the Executive may make any assignment of this Agreement or any interest herein, by operation of law or otherwise, without the prior written consent of the other party; provided that the Employer may assign its rights under this Agreement without the consent of the Executive in the event that the Employer shall effect a reorganization, consolidate with or merge into any other corporation, partnership, organization or other entity, or transfer all or substantially all of its properties or assets to any other corporation, partnership, organization or other entity. This Agreement shall inure to the benefit of and be binding upon the Employer and the Executive, their respective successors, executors, administrators, heirs and permitted assigns.

  • Assignment; Successors and Assigns Neither of the parties hereto may assign its rights or interest under this Indenture, except as provided in Section 9.8 in the case of the Warrant Agent, or as provided in Section 8.2 in the case of the Corporation. Subject thereto, this Indenture shall enure to the benefit of and be binding upon the parties hereto and their respective successors and permitted assigns.

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