Error handling. The Customer shall report any errors without undue delay. The Contractor shall assist with identifying and rectifying errors within the framework defined in Appendix 2, and based on the framework set out in the service level agreement in Appendix 5. If the agreed deadlines are not complied with, the Customer may demand standardised compensation as stipulated in the service level agreement in Appendix 5. Unless otherwise is agreed in Appendix 5, the following error definitions shall apply: A Critical error - Error that results in the stoppage of the software or equipment, a loss of data, or in other functions that, based on an objective assessment, are of critical importance to the Customer not working as agreed. - The documentation being so incomplete or misleading that the Customer is unable to use the software or the equipment, or material parts thereof. B Serious error - Error that results in functions that, based on an objective assessment, are of importance to the Customer not working as described in the agreement, and which it is time-consuming and costly to work around. - The documentation being incomplete or misleading, and this resulting in the Customer being unable to use functions that, based on an objective assessment, are of importance to the Customer. C Less serious error - Error that results in individual functions not working as intended, but which can be worked around with relative ease by the Customer. - The documentation being incomplete or imprecise. To the extent that the services include the maintenance of standard software that the Contractor has not developed itself or does not maintain itself, or where elements of the services are in some other manner delivered by a third party and the Customer has not itself concluded a maintenance agreement with the software producer, the Contractor shall conclude the necessary agreement with the software producer. The terms and conditions for the maintenance that are agreed between the Contractor and the software producer shall be explicitly specified in a separate chapter in Appendix 2, and copies of the terms and conditions for the maintenance shall be appended as Appendix 10. If the Customer has itself concluded a maintenance agreement with the aforementioned software producer, these shall be appended to the Agreement as Appendix 10. The Contractor may request that the Customer assert or, with the agreement with the Customer, itself assert the Customer's rights in relation to the software pro...
Error handling. (Go to section) Instructions: This information applies to errors on both the Producer side and Archive side. Repeat a row for every error condition. Reference the data type to which the information applies by identifying the REF ID header row. Repeat the REF ID header row and subsequent rows in the table for every data type error handling described.
Error handling. This section describes the error handling roles and responsibilities for established EDI Trading Partners, as well as systems and processes for error correction. APMT – Horizon Lines 7 • EDI Format Errors – Errors with EDI Standards, syntax, translation EDI format errors are those that prevent the EDI message and data from being processed through the EDI Translation Application. This includes errors that do not adhere to EDI Standards, syntax issues and translation issues. When an EDI message has errors in format or segment data requirements, the message suspends in the translation process. We will indicate the error back to the partner within the 997. The partner should look into the process further to determine why the message error in the first place. Our translator checks all outbound messages to our partners for syntax related issues prior to transmission.
Error handling. This section describes the error handling roles and responsibilities for established EDI Trading Partners, as well as systems and processes for error correction. APMT – Horizon Lines 7
Error handling. One of the most interesting advantages of using REDUCEME programs is that for each image an associated error image can also be processed throughout the reduction process, allowing for a careful control of the error propagation. A more detailed description of this technique, and its application to the measurement of line-strength indices, is given in these papers: • Xxxxxxx et al. (1998): Reliable random error estimation in the measurement of line-strength indices. • Xxxxxxx et al. (2002): Proper handling of random errors and distortions in astronomical data analysis • Xxxxxxx et al. (2003a): A New Approach in Data Reduction: Proper Handling of Random Errors and Image Distortions • Xxxxxxx et al. (2003b): Using spectroscopic data to disentangle stellar population properties Note: You can also find a general description of REDUCEME in Chapter 3 of my PhD Thesis (see also appendix B and C). In addition, you can find here how to create the REDUCEME logo in LaTeX.
Error handling. R5-esterror: Creates an error file from an initial image, taking into account the r.m.s. measured in each spectrum in a given wavelength range. R5-generror: Creates an error file from an initial image, taking into account the readout noise and gain of the detector. R5-randsc: Creates a fake image through bootstraping from an original image and its associated error frame. In each pixel, the original signal is randomly modified using the correspoding error. R5-snratio: Determines the S/N ratio as a function of binning in the spatial direction.
Error handling. During the approval period the Customer shall, on an ongoing basis and without undue delay, report any errors to the Contractor in writing, which shall include a description of the errors, in accordance with the cooperation plan. The Contractor shall rectify the errors as quickly as possible. Errors shall be rectified in their order of priority. Unless otherwise agreed in Appendix 4, any errors shall be rectified, at the latest, by the end of the approval period. If errors or deviations occur during the approval period for the operational services and these prevent the Customer's examination of the operational services, the Customer shall have the right to extend the approval period by a period of time equal to the duration of the error or deviation.
Error handling at any time failures of the surround- ing components (e.g. airbag activated, low energy in battery,
Error handling. Warnings are purely for information about an (unexpected) event that has occurred (operation could not be executed, a default value had to be used,). In some circumstances they may prevent the execution of an operation, or a series of operations, but not the program run. The list below shows the different error messages that will be generated. No. Description
Error handling. 9.4.3.1 Perform [**] [**] [**] 9.4.3.2 [**] [**] [**]
