Data files, clean

The process of scanning a sample is quite simple and very rapid. The sample holder and surface must first be gently cleaned of debris and a reference (usually an internal ceramic Coor s standard) scan taken. The sample may then be placed in the sample holder, which may hold one or more of a specific type of sample. The sample is positioned, the lid closed, and the scan taken. Scan times are usually approximately 40 s. If multiple scans of the same sample are needed, the sample may be removed and rescanned. Instrument software facilitates the process and allows the spectra to be named and stored in data files. 

Time plan Providing a time frame for the preliminary model building and the production of clean file, clean data sets, the analysis, and the report-writing... 

The samples were evaluated with the differential rheometer in the following manner Samples of SE-30 and the material of interest were weighed to 0.3 0.0005 g. For each experimental run the samples were loaded into the sample gaps and the control system activated at the initial sample thickness. The loading of the samples invariably introduced an initial deflection in the load cell blade. The samples were therefore allowed to relax until the blade had returned to the zero position (2-3 min). The input waveform from the function generator was then started at the frequency and amplitude of interest. The APPLE-based data collection system was started at the end of 1 cycle and continued for 4-10 cycles at 50-250 points/cycle. After data collection the samples were removed, the pushrods cleaned and fresh samples loaded. The second pair of samples were inserted with the sample sides reversed and data was collected as before. After all runs were completed the pair of data files for each sample set were subtracted point by point to eliminate much of the coherent noise caused by nonuniformity of the two rod motions. The resultant voltage file was transmitted to the University of Connecticut, Department of University Computer Systems IBM 3081. The voltages... 

The finish up phase is used to clean up the design and write out the data path and control schedule files. Clean up is a simple process of removing any unused ports and modules that were created during the allocation process. After the clean up has been accomplished, the data path and control schedule may be written out. 

The next step of data cleaning is to perform a replicate and pseudo replicate analysis of the experimental values. When replicate data are available, highly discrepant results can point to problems with the experimental data. When replicate results are not available, pseudo replicates are almost always present in the data. Often the same chemical structure exists more than once in the results file, where the different identifiers refer to different batches of the same material. Thus, a... 

Cleaning and Transforming Data. When importing data from diverse data sources (files, databases, spreadsheets, LIMS systems, etc.) into a database or data warehouse, the 4 ta usually needs to be standardized, checked, and sometimes transformed to some common format and content. This allows faster search and retrieval, and serves as a check of data integrity. The rules that define the cleaning/trans-formation process are often termed "business rules," and in the case of chemical data, they may include checking and modification of chemical structures. 

When the data has reached a clean file status, time pressure increases for the modeling of the data. This phase of the project involves the characterization of the model as well as its evaluation. There are a number of different approaches, which will be described next, that can be employed to save time or to be more efficient in this... 

The time required for model development during the time period in which the modeling takes place can be reduced if the model building has already been started before a clean file has been obtained or even before the complete study (i.e., the complete data collection) has been finished. 

A batch production record shall be kept for every batch of products, and the actual condition in every section of production shall be reflected in it. The record shall be clear in handwriting, truthful in content and complete in data and it shall be signed by both the operator and the person who checks it. The record shall be maintained in a clean and tidy state, and it shall not be arbitrarily spoiled and altered when any alteration made to it, the alteration shall permit the reading of the original information and the person for the alteration shall be signed at the space altered. A batch production record shall be filed according to batch number, and it shall be retained for at least one year after the expiry date of the finished product. The batch record for products with no expiry date shall be retained at least for three years. 

Individuals who prepare benchmarkcalculations for code validation are well aware that the benchmark- data sources are voluminous. The reports collected for our bibliography on criticality experiments occupy three five-drawer file cabinets. Finding and selecting the right data can be a trying task. The difficulty is compounded because, in many cases, the same experimental data are reported in several publications, sometimes with corrections of earlier errors, or in an evaluated clean format. To do their jobs properly, the criticality analysts have to be aware of the best sources for their needs. This paper addresses how some tools that are being developed, especially computer data-base systems, can make the job easier. In this paper, we show wlut we have done to make this task easier, and how it may be of beneHt toothers. 

---