Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Software coding

Most tolls involve the transfer of proprietary information from one party to the other, typically from the client company to the toller. Each party should have maintained a log of transferred documents or software code to make the return of proprietary documents a simple matter. An initial list of the documents should have been referenced in the contract or as part of the technology package. Keeping records of additional documents transferred during the course of the toll will help eliminate confusion at the end of the project. The toller may need to retain documents appropriate for their process safety system needs. [Pg.138]

Computer software codes are available to deconvolute PIXE spectra and to calculate peak areas with accuracy, so that absolute amounts of elements present in the specimen may be derived. With a beam of 5 mm diameter incident on a thin organic specimen on a thin backing foil, trace elements can be detected at picogram levels. The x-ray production cross-sections, absorption coefficients and the various... [Pg.101]

At the same time, reaction modeling is now commonly coupled to the problem of mass transport in groundwater flows, producing a subfield known as reactive transport modeling. Whereas a decade ago such modeling was the domain of specialists, improvements in mathematical formulations and the development of more accessible software codes have thrust it squarely into the mainstream. [Pg.558]

Figure 10.57 compares the results obtained using this formula with the thermodynamic calculations, while Fig. 10.58 shows the comparison with experimental volume fractions. This formula can now be written in simple software code to provide an almost instant answer to the temperature at which heat treatment will give the ideal 50 50 ratio of austenite to ferrite. [Pg.374]

Figures 10.9S(a,b) show isopleths calculated between (a) corium and siliceous concrete and (b) corium and limestone concrete. Comparison between experimental (Roche et al. 1993) and calculated values for the solidus are in reasonable agreement, but two of the calculated liquidus values are substantially different. However, as the solidus temperature is more critical in the process, the calculations can clearly provide quite good-quality data for use in subsequent process simulations. Solidus values are critical factors in controlling the extent of crust formation between the melt-concrete and melt-atmosphere interface, which can lead to thermal insulation and so produce higher melt temperatures. Also the solidus, and proportions of liquid and solid as a function of temperature, are important input parameters into other software codes which model thermal hydraulic progression and viscosity of the melt (Cole et al. 1984). Figures 10.9S(a,b) show isopleths calculated between (a) corium and siliceous concrete and (b) corium and limestone concrete. Comparison between experimental (Roche et al. 1993) and calculated values for the solidus are in reasonable agreement, but two of the calculated liquidus values are substantially different. However, as the solidus temperature is more critical in the process, the calculations can clearly provide quite good-quality data for use in subsequent process simulations. Solidus values are critical factors in controlling the extent of crust formation between the melt-concrete and melt-atmosphere interface, which can lead to thermal insulation and so produce higher melt temperatures. Also the solidus, and proportions of liquid and solid as a function of temperature, are important input parameters into other software codes which model thermal hydraulic progression and viscosity of the melt (Cole et al. 1984).
The development phase needs to accommodate a software code/configuration review process to ... [Pg.603]

Provide a high level of confidence that the software code or configuration meets the defined operational and technical requirements of the system design specifications and the URS... [Pg.603]

Ensure that the software code or configuration is to a standard that will ensure clear understanding and support maintenance and modification of the software throughout the system validation life cycle... [Pg.603]

Code audits are formal and independent reviews of source code by a person, a team, or tool, to verify its compliance with software design documentation and programming standards. In addition, the software code is evaluated against its supporting documentation to ensure that it correctly describes the code. [Pg.55]

Code review A meeting at which software code is presented to project personnel, managers, users, customers, or other interested parties for comment or approval (IEEE). [Pg.178]

The developer must install the software product in accordance with the installation plan and procedures. It must be ensured that the software code and databases initialize, execute, and terminate as specified in the technical design specification deliverable. The installation events and results must be documented. [Pg.225]

With increasing numbers of X-ray structures being solved, the 3D information can be exploited for ligand design and optimization. There is a need for fast methods for structure-based virtual screening. The recent use of machine clusters and porting of software codes to Linux and Windows platforms has contributed to a signif-... [Pg.203]

The following software code systems can be used to justify nuclear and radiation safety, to determine the SNF nuclide composition and energy release ... [Pg.209]

For the indicated SRP s characteristics to be calculated a number of software code systems can be used. They are briefly considered below, whereas their detailed description is given in [1-4]. [Pg.210]

Another related characteristic of software is the speed and ease with which it can be changed. This characteristic can lead both software and nonsoftware professionals to the false impression that software problems can be easily corrected. This is true at one level, but there are complications. Repairs made to correct software defects actually establish a new design. Because of this, seemingly insignificant changes in the software code can create unexpected and very significant defects to arise mysteriously elsewhere in the software. [Pg.6]

Code software models Build/assemble hardware/peripherals Perform software code reviews... [Pg.98]

Test hardware/peripherals Test software modules Test integrated software code... [Pg.98]

The FS is developed into a hardware design specification (HDS) or a software design specification (SDS) or both. The SDS provides the facihty to break each functional requirement into appropriate subfunctions, increasing in detail at each subsequent level, until eventually the design reaches a state where it can be translated into software code. The SDS should mimic the sections of the FS but be specific to software constraction. Some examples are as follows ... [Pg.593]

As-Built FDA (1995) Pertaining to an actual configuration of software code resulting from a software development project. [Pg.941]

Superfluous Code Software code that unnecessarily recalculates, rechecks, or reperforms calculations or actions that are unnecessary or that have already been done. [Dehned for this book.]... [Pg.948]

Applications are really nothing more than software code installed onto the hard drive of your machine. Because of this, it shouldn t be a big surprise to know you have to obtain a copy of the software installation files before running setup. The most common installation methods today are as follows ... [Pg.635]

Just as in the case of full pattern decomposition, we will use two freely available software codes (LHPM-Rietica and GSAS ) to carry out Rietveld refinements using either or both x-ray and neutron diffraction data. Many... [Pg.600]

These two relationships can be easily programmed in GSAS and in the majority of Rietveld software codes by using a constraint apparatus, which was briefly discussed above (see section 7.3.3 and Eq. 7.9). Since the constraints affect only the shifts that are determined during every least squares refinement cycle but not the values of the related parameters, the latter should be synchronized manually prior to imposing constraints. For example, in our case when the computed shift for g-v2a is 0.02, then the new values of the constrained parameters (Eqs. 7.9, 7.11 and 7.12) will be calculated as follows ... [Pg.673]


See other pages where Software coding is mentioned: [Pg.149]    [Pg.293]    [Pg.301]    [Pg.410]    [Pg.199]    [Pg.200]    [Pg.834]    [Pg.603]    [Pg.735]    [Pg.55]    [Pg.405]    [Pg.110]    [Pg.52]    [Pg.132]    [Pg.133]    [Pg.117]    [Pg.78]    [Pg.188]    [Pg.714]    [Pg.801]    [Pg.813]    [Pg.55]    [Pg.27]    [Pg.218]    [Pg.218]    [Pg.48]   
See also in sourсe #XX -- [ Pg.299 , Pg.301 ]




SEARCH



© 2024 chempedia.info