Executor API Clause Samples

Executor API. ‌ The API of the RCLC-Executor can be divided in two phases: Configuration and Running. #### Configuration 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 com- muncation semantics (optional, default ROS2) As the Executor is intended for embedded controllers, dynamic memory management is crucial. Therefore 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 runtime. 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 useful 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 oper- ating on the buffered copy. 3.4.3.1 Running phase As the...
View SourceView Similar (2)

Related to Executor API

  • Automatic Renewal Clauses Incorporated in Awarded Vendor Agreements with TIPS Members Resulting from the Solicitation and with the Vendor Named in this Agreement.

  • Contract Signature If the Original Form of Contract is not returned to the Contract Officer (as identified in Section 4) duly completed, signed and dated on behalf of the Supplier within 30 days of the date of signature on behalf of DFID, DFID will be entitled, at its sole discretion, to declare this Contract void.

  • Residential Use; Pets The bedroom space and apartment may be used solely for private residential purposes and for no other purposes. Resident may not carry on any business or other enterprise from the bedroom space or apartment, nor use any Owner- provided Internet connections for business purposes. Resident may place no signs, placards or other advertisement of any character in the bedroom space or apartment, nor display anything in an apartment or bedroom space that is visible from outside the Property or the apartment. Resident may not store at the Property or connect to a Property electrical outlet any mobility device owned by a third party. Pets are permitted in or about the Property only in specified buildings as Owner may in its discretion allow residents to maintain, in each case only following Owner's signature on a Pet Addendum for a single dog or cat per designated apartment, which requires payment of a registration fee and pet rent as provided in the Pet Addendum. All other pets are prohibited anywhere at the Property, except fish in small tanks to the extent approved by Owner in its sole discretion. Violation of the pet policy will subject Resident to deep-cleaning and daily administration fees in Owner’s discretion and may be considered as a termination of this Housing Agreement by Resident.

  • Multi-year Planning Targets Schedule A may reflect an allocation for the first Funding Year of this Agreement as well as planning targets for up to two additional years, consistent with the term of this Agreement. In such an event, the HSP acknowledges that if it is provided with planning targets, these targets: a. are targets only, b. are provided solely for the purposes of planning, c. are subject to confirmation, and d. may be changed at the discretion of the Funder in consultation with the HSP. The HSP will proactively manage the risks associated with multi-year planning and the potential changes to the planning targets; and the Funder agrees that it will communicate any changes to the planning targets as soon as reasonably possible.

  • Additional Terms Applicable to an Incentive Option In the event this option is designated an Incentive Option in the Grant Notice, the following terms and conditions shall also apply to the grant: (i) This option shall cease to qualify for favorable tax treatment as an Incentive Option if (and to the extent) this option is exercised for one or more Option Shares: (A) more than three (3) months after the date Optionee ceases to be an Employee for any reason other than death or Permanent Disability or (B) more than twelve (12) months after the date Optionee ceases to be an Employee by reason of Permanent Disability. (ii) No installment under this option shall qualify for favorable tax treatment as an Incentive Option if (and to the extent) the aggregate Fair Market Value (determined at the Grant Date) of the Common Stock for which such installment first becomes exercisable hereunder would, when added to the aggregate value (determined as of the respective date or dates of grant) of the Common Stock or other securities for which this option or any other Incentive Options granted to Optionee prior to the Grant Date (whether under the Plan or any other option plan of the Corporation or any Parent or Subsidiary) first become exercisable during the same calendar year, exceed One Hundred Thousand Dollars ($100,000) in the aggregate. Should such One Hundred Thousand Dollar ($100,000) limitation be exceeded in any calendar year, this option shall nevertheless become exercisable for the excess shares in such calendar year as a Non-Statutory Option. (iii) Should the exercisability of this option be accelerated upon a Change in Control, then this option shall qualify for favorable tax treatment as an Incentive Option only to the extent the aggregate Fair Market Value (determined at the Grant Date) of the Common Stock for which this option first becomes exercisable in the calendar year in which the Change in Control occurs does not, when added to the aggregate value (determined as of the respective date or dates of grant) of the Common Stock or other securities for which this option or one or more other Incentive Options granted to Optionee prior to the Grant Date (whether under the Plan or any other option plan of the Corporation or any Parent or Subsidiary) first become exercisable during the same calendar year, exceed One Hundred Thousand Dollars ($100,000) in the aggregate. Should the applicable One Hundred Thousand Dollar ($100,000) limitation be exceeded in the calendar year of such Change in Control, the option may nevertheless be exercised for the excess shares in such calendar year as a Non-Statutory Option. (iv) Should Optionee hold, in addition to this option, one or more other options to purchase Common Stock which become exercisable for the first time in the same calendar year as this option, then the foregoing limitations on the exercisability of such options as Incentive Options shall be applied on the basis of the order in which such options are granted.