Wavelet Analysis

Several of the wavelet subroutines take arguments that are options vectors that specify user input. For example, the third argument in a WAVFT subroutine call is an options vector that specifies which wavelet and which boundary treatment are used in computing the wavelet transform. Typical code that defines this options vector is as follows:

  
     optn    = j(1, 4, .); 
     optn[1] = 0;    
     optn[3] = 1;   
     optn[4] = 3;   

A problem with such code is that it is not easily readable. By using symbolic names readability is greatly enhanced. SAS macro variables provide a convenient mechanism for creating such symbolic names. For example, the previous code could be replaced by the following code:

  
      optn            = &waveSpec;    
      optn[&family]   = &daubechies;   
      optn[&member]   = 3; 
      optn[&boundary] = &zeroExtension; 

where the symbolic macro variables (names with a preceding ampersand) resolve to the relevant quantities. Symbolic names also improve code readability when substituted for integer arguments that control what actions a multipurpose subroutine performs. Consider the following code:

  
     call wavget(n,decomposition,1); 
     call wavget(fWavelet,decompostion,8); 

This code can be replaced by the following statements:

  
     call wavget(n,decomposition,&numPoints); 
     call wavget(fWavelet,decompostion,&fatherWavelet); 

A set of symbolic names is defined in the autocall WAVINIT macro. The following tables list the symbolic names that are defined in this macro.