Line style specifiers

Note that adding these two shaded lines of code to your SAS procedure gives you an attractive RTF file. If you do not like the default ODS style template that SAS uses for your output, you can use a different style template supplied by SAS by specifying the STYLE= option in the ODS RTF statement. If you still do not like the way your RTF file looks, you can define your own ODS style template with PROC TEMPLATE. Finally, PROC REPORT allows you to define formatting elements within the SAS procedure itself, where you can customize the appearance of almost any element on the page. For more information about ODS, you can refer to the SAS Press books Output Delivery System The Basics, by Lauren Haworth, and Quick Results with the Output Delivery System, by Sunil Gupta. If you just want more style templates to choose from, you can investigate the templates created by Bernadette Johnson in Instant ODS Style Templates for the SAS Output Delivery System. 

Figure 2 shows the code for the spin-echo pulse sequence. In lines 1-7, NMR object variables are declared. In lines 9-16, these objects are assigned values or specific NMR operations. A lactate spin system is read in from a file using a standard GAMMA text file format. Lines 20-24 are the code for the actual 90°Y-delay-180°Y-delay-acquire pulse sequence. In line 26, the density matrix is parsed into a transition table for the specified observation operator. And the "write results" function in line 27 converts the GAMMA transition table into three arrays of ppm, area and phase values one value for each line found in the transition table. This is a fairly trivial example, and the use of ideal pulses is often not sufficient to account for real-world artefacts in a simulation, but it shows how the object-oriented style of coding results in short amounts of code that is easy to read and comprehend. When compiled with the Visual Studio C++ compiler on a... 

---