Data ASCII

We shall find the equation that best fits the points in columns 1 and 3 of Table 1-3 with TableCurve. On opening TableCurve, one is presented with a blank desktop with several commands at the top. The command to enter data is not Enter but Edit. Two formats are available, the TableCurve editor and the ASCII editor. The TableCurve format is probably a little simpler than the ASCII format, but they are both fairly self-evident and either should yield a data file resembling the data... 

The program uses two ASCII input files for the SCF and properties stages of the calculation. There is a text output file as well as a number of binary or ASCII data files that can be created. The geometry is entered in fractional coordinates for periodic dimensions and Cartesian coordinates for nonperiodic dimensions. The user must specify the symmetry of the system. The input geometry must be oriented according to the symmetry axes and only the symmetry-unique atoms are listed. Some aspects of the input are cumbersome, such as the basis set specification. However, the input format is documented in detail. 

System can communicate with other systems (e.g., Lotus, dBASE, ASCII, and DIF data formats Macintosh and IBM equipment). 

The disk contains over 120 models in files that may contain source and executable code, sample input lilcs, other data files, sample output files, and in many cases, model documentation in WordPerfect, ASCII text or other formats. The disk contains IMES with information on >clecting tin appropriate model, literature citations on validation of models in actual applications, and a demonstration of a model uncertainty protocol. 

The data will likely come in as ASCII which must be imported into the database manager. 

All setup data and results are stored in Data Resource Files rather than standard sequential or random access files. This has turned out to be a key feature contributing to a flexible and low maintenance system. These are ASCII files which can be typed to the screen, printed, or edited with a word processor. They contain information organized by variable name, value, and units. The following is an example of a data resource file ... 

The only data not stored as Data Resource Files is raw numerical data for curves. This is stored in binary to conserve disk space and speed access but is accessible via editing and ascii conversion options. 

Importing Relational Databases and Clinical Data Management Systems 42 SAS/ACCESS SQL Pass-Through Facility 42 SAS/ACCESS LI BN AM E Statement 43 Importing ASCII Text 44... 

In most cases, the data that you use for clinical trial analyses are found in some kind of computer file external to the SAS System. The data you need may be found in a permanent SAS data set, a relational database table found in Oracle or Microsoft SQL Server, a Microsoft Access or Excel file, a simple delimited ASCII text file, or even an XML file. In any case SAS provides a wide array of ways in which to import data files into SAS. We explore these tools and the advantages and disadvantages of each in this chapter. 

On occasion you may find that you need to import data from ASCII text files for analysis. In this section, traditional rectangular ASCII text files are discussed. Although XML files are composed of ASCII text, they pose unique challenges that are discussed later in this chapter. Some examples of ASCII text data that you might need to import include... 

SAS provides many ways of importing ASCII text files. These methods include using PROC IMPORT and the Import Wizard, the SAS DATA step, and SAS Enterprise Guide. 

The data are stored as simple ASCII text, so they are easily readable. 

Because the data are stored as simple ASCII text, text file browsers far into the future should still be able to read an XML file created today. 

You can mix complicated DATA NULL reports with more efficient PROC REPORT reports when necessary. Because your output is ASCII text with both types of reports, it is easy to combine these two reporting tools and still have a consistent look and feel to your reporting. 

On occasion you will need to export your SAS data as ASCII text. You may find that the recipient of your data requires that you send some form of delimited ASCII text, because that is all their software can read. In fact, delimited ASCII text is a primitive data exchange format that almost any software can read. 

PROC EXPORT provides a quick way to create ASCII text files from SAS data sets. You can call PROC EXPORT by typing in the SAS code, or you can use the convenient SAS windowing environment Export Wizard that builds the PROC EXPORT code for you. Let s start by looking at using the SAS 9.1 windowing environment Export Wizard... 

There are other options for creating delimited ASCII files from the Export Wizard. From the Select Export Type window you can pick tab delimited or delimited file as one of the standard data sources if you want delimited files. If you choose the delimited file option, you can choose your field delimiter by clicking the Options button. For instance, if you were creating a pipe-delimited file, the Select Export Type window would look like this ... 

You can see how the (pipe) character is entered as the delimiter in the Options dialog box. If you have more complex requirements for the ASCII text file you want to export, you can invoke External File Interface in the Select Export Type window, write customized DATA step code with FILE and PUT statements, or use some of the ODS tagsets supplied by SAS, found at http //support.sas.com/md/base/topics/odsmarkup/, that have the ability to create numerous types of ASCII text formats. 

You may find that you need to export your SAS data as something other than regular ASCII text or Microsoft Office files. In this case, the export wizards in the SAS windowing environment in SAS 9 and SAS Enterprise Guide 3.0 can easily export the following file formats ... 

Once the experiment setup information has been successfully entered, 1t 1s stored in an ASCII file. This experiment setup file can then be placed In the queue of experiments to be run on this Instrument or 1t can be saved for later use with the manual data collection program. Any of the information entered in the experiment setup phase can be changed with the experiment setup editor. The editor Is accessed through the main menu program and works the same as the initial experiment setup program. 

This file may be a part of the scattering pattern file or a file of its own. For the sake of easy viewing the monitor data are, in general, human-readable text ( ASCII—header or ASCII —file ). 

After you have collected the first scattering patterns check that the data files have arrived in the expected directories. Check the size of the files. Open the ASCII files or the ASCII headers in a text editor and check that the environmental data have arrived in the files. Vary environmental parameters in test measurements and check that the values in the ASCII files vary accordingly. If possible, calibrate environmental parameters (e.g., sample temperature, straining force, cross-bar position). Ask the beamline staff to demonstrate what they tell you. Double check Otherwise your effort may be wasted. 

When such a TIC is established, one will find that some unusual benefits accme. One now has immediate and uninterrupted access to libraries of valuable and comprehensive scientific data. This access is free of on-line constraints and designed to be user friendly, with readily retrievable information available 24 hours a day, 7 days a week. The retrieved information can also usually be manipulated in electronic form, so one can use it in reports and/or store it in machine-readable form as ASCII files. 

A computer program, containing the data for all compounds, is available for a nominal fee (Carl L. Yaws, Box 10053, Lamar University, Beaumont, TX 77710, phone/FAX 409-880-8787). The computer program (random data file) is in ASCII which can be accessed by other software. 

---