Support for execution in scenarios Sample Clauses

Support for execution in scenarios where EAR is not installed Since some defaults are applied when configuration is missing and alternatives have been prepared for the cases where one or more dependencies are missing (be it EAR components or other software dependencies), EAR is ready to be executed even if only the EAR library is present (EAR not installed). In environments where the hardware support is minimal, EAR works similarly to executions where EAR is not installed, dynamically detecting on startup which systems are available and deactivating the ones that cannot be used. Therefore, environments with minimum hardware functionalities (mostly cloud environments, but it also applies to highly virtualized environments) are supported with a reduced feature set which is entirely dependent on the availability of hardware functions. XXXX uses its own metrics and management libraries providing monitoring information and knobs for the CPU, Memory and GPU frequency settings. The API for these libraries has been extended to be completely transparent of the underlying hardware and in all the cases a dummy object has been provided. The API for all the classes includes a common set of functions and few specific depending on the particular metrics. Figure 6 shows the API used to measure FLOPS. The load function is the one including the intelligence to detect what is or not available. All the APIs look similar to this one with load, init, dispose, read, read_diff, etc functions. The fact the API is internally managing the low-level details makes the XXXX more portable and agnostic of the different scenarios. state_t flops_load(topology_t *tp, int eard); state_t flops_get_api(uint *api); state_t flops_init(ctx_t *c); state_t flops_dispose(ctx_t *c); state_t flops_read(ctx_t *c, flops_t *fl); // Data state_t flops_read_diff(ctx_t *c, flops_t *fl2, flops_t *fl1, flops_t *flD, double *gfs); state_t flops_read_copy(ctx_t *c, flops_t *fl2, flops_t *fl1, flops_t *flD, double *gfs); state_t flops_data_diff(flops_t *fl2, flops_t *fl1, flops_t *flD, double *gfs); /* Accumulates flops differences and return its data in GFLOPs (accepts NULL). */ state_t flops_data_accum(flops_t *fA, flops_t *fD, double *gfs); state_t flops_data_copy(flops_t *dst, flops_t *src); state_t flops_data_print(flops_t *flD, double gfs, int fd); state_t flops_data_tostr(flops_t *flD, double gfs, char *buffer, size_t length); Figure 6 FLOPS API example
Sample 1
AutoNDA by SimpleDocs

Related to Support for execution in scenarios

  • Credit for Experience A. Newly employed teachers will receive the equivalent year's credit for each year of experience. The experience granted will be equal to the FTE experience for each year worked. This credit will be granted if, in the judgment of the Superintendent, the teaching experience has been appropriate to the position which has been offered. For example, teaching experience at the secondary level may not be appropriate if the applicant is being considered for an elementary position. Placement on the salary schedule beginning with the 2017-18 contract year will be accomplished in the following manner:

  • For example If an employee utilises two weeks recreation leave over a period of four weeks at half pay, service based entitlements (e.g. personal leave, long service leave, paid parental leave) will be deferred by two weeks.

  • Criteria for Evaluation Criteria for employee performance review shall be made available to the employee before the start of the evaluation period and shall remain unchanged during the evaluation period unless the employee is made aware of the changes.

  • Time Off for Elections Employees shall be allowed four (4) consecutive hours off before the closing of the polls in any Federal, Provincial, or Municipal election or referendum.

  • Reimbursement for Expenses Consultant shall not be reimbursed for any expenses unless authorized in writing by City.

  • Issues for Expedited Arbitration (a) All grievances except those relating to the following shall be resolved by expedited arbitration:

  • PROCEDURES FOR EVALUATION A. The evaluations of school year employees covered by this agreement shall be completed no later than May 30 of each school year for 9-month employees and by June 30 for 10/12-month employees. The evaluation shall be reviewed with the employee, with a copy given to the employee at the conclusion of the review. An employee may present written comments, which shall be attached to the written evaluation document. The evaluator and employee shall sign the evaluation document. The employee’s signature does not constitute approval or disapproval, but only that the evaluation has been reviewed with the employee.

  • Liability for expenses Each party will pay its own expenses incurred in negotiating, executing, stamping and registering this Participation Agreement.

  • Requests for Exclusion Any Settlement Class member who wishes to opt-out of the Settlement must complete and mail a Request for Exclusion (defined below) to the Settlement Administrator within sixty (60) calendar days of the date of the initial mailing of the Notice Packets (the “Response Deadline").

  • Credit for Prior Experience Credit shall be given new employees in initial step placement of the wage scale set forth in Appendix A for prior experience directly related to the same classification. Credit for prior experience which is somewhat related to the position for which the applicant applies will be granted on a basis of one (1) year credit for two (2) years’ experience.

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