Software correction

The ATR technique is a commonly used infrared internal reflection sampling technique. It samples only the surface layer in contact with the ATR element the sampling depth probed is typically of the order of 0.3-3 pm [1]. Unless software corrected, compared with a transmission spectrum, the relative intensity of bands within an ATR spectrum increase in intensity with decreasing wavenumber. Several FTIR instrument companies now supply "ATR-correction" software developed to correct for the different relative intensities of bands observed between ATR and transmission spectra, so that ATR spectra can be more easily compared to and searched against transmission spectra. 

One important aspect of the electron diffractometer, is that any ED pattern can be captured before scanning by a CCD camera that is placed off-axis in relation with the ED pattern (can be any commercial CCD, even a webcam see fig.l). A dedicated software corrects for any type of optical distortions that may be produced due to the position of viewing angle of the CCD in relation with the ED pattern. This has the big advantage that the user that may observe and define interactively the reflections or the area of the ED pattern that will be scanned, allowing at the same time the main beam to be blanked, in order to avoid radiation damage. 

Either electronically or through the computer software, correct for spectral overlap between the ports (for example, for fluorescein fluorescence recorded in the PE channel). 

For a simple lineshape analysis (by, for example, a Fourier transform of the FID) this inhomogeneity, as long as it is not excessive, is of no consequence because it is software correctable (II.B.4.) but there are many experiments for which either the precise knowledge of or a good spatial... 

In these cases, simply trying to get the software correct in terms of accurately implementing the requirements will not make it safer. Software may be highly reliable and correct and still be unsafe when ... 

The software correctly implements the requirements, but the specified behavior is unsafe from a system perspective. 

These definitions imply that the reliability depends not only on product attributes, such as number of faults, but also on how the product is used during operation, i.e., the operational profile. This also implies that software reliability is different from software correctness. Software correctness is a static attribute, i.e., number of faults, while reliability is a dynamic attribute, i.e., number of failures during execution. 

Testing that the application software correctly satisfies its test specification is a verification activity. It is the combination of code review and structural testing that provides that the application software module satisfies its associated specification, i.e., it is verified. 

Many of these interferences are well-documented, and in a well-controlled system, many can be corrected for mathematically. Most instrument companies have interference-correction software as part of their data handling software. A problem with this approach has been that sometimes the necessary data were not collected during analysis, requiring reanalysis if possible. Multiple scans or longer analysis times may have been needed. One instmment that has an advantage with respect to software corrections is the simultaneous ICP-MS, from SPECTRO, described in Chapter 9. Becanse the SPECTRO MS collects the complete mass spectrum simultaneously without scanning, aU data are available. Having been collected at the same time, measmanent-based corrections can be made more reliably. 

On the other hand, we were able to recreate the other anomaly in which the H-VAD system was unable to converge to the specified setting. Figure 8 illustrates how this anomaly is revealed in the blood pressme graph. Partial success of H-VAD software validation in the animal experiment clearly reveals that further analysis of software correctness is absolutely necessary prior to clinical use. 

First 1 sit with my computer (PC) and carry out patch administration. These are software corrections that have to be applied to the systems operating in the varions digital exchanges. I receive the patches from Germany and I issue them to the field technicians. I then check on the final status of the patches once they have been installed in the exchanges. ... 

In connection with the transition of the system to the next state, however, one needs to consider the software module that carries out the calculations to determine the subsequent state. If a transient failure distorts the software, then the software remains in a distorted form in the memory, although the memory would store the software correctly at the next occasion of software upload to the system. Therefore, the software must be written into memory together with a checksum. Moreover, for each application of this software, i.e. also when recomputing the transition to the next system state it is necessary to check the integrity of the software (or portions thereof) with the checksum. 

Normalization is really only meaningful if the spectrum background is free from artifacts. Any background contribution from an accessory or a sampling medium should be removed by absorbance subtraction. Solid samples often have a scatter background superimposed on their spectra. Figure 2c is a simulation of this effect. It is often important to remove this background by software correction. 

Soft errors in microelectronic packages are a difficult, troublesome problem to address. Eliminating them is virtually impossible. Soft error rate effects can be reduced in a number of ways, including the use of shielding, software correction methods (although this reduces performance), alpha particle-tolerant structures (e.g., SOI), and utilization of low-alpha-emitting materials. Let us now focus on the reduction of alpha particle-induced SER from traditional lead-based solders. 

---