CONFIGURATION PARAMETERS. (a) The initial model switch configuration consists of one 3B21 Administrative Module at 5E13 Base Generic, or the then available Generic, one CM2 Communications Module (two pairs), and two SM-2000 Switching Modules containing the following:
(d) ODA to meet WinStar's network requirement.
CONFIGURATION PARAMETERS. Configuration parameters in SAS Drug Development (Display 1) define all aspects surrounding the program, which include all inputs, program “c nfiguration” options and all outputs that need to be returned and saved to the repository. If you omit to specify an output, the output will not be moved to the repository after the program ends executing.
CONFIGURATION PARAMETERS. To be executed the software requires the two configuration files containing parameters (i) for the control of the type of the susceptibility analysis to be performed (“configuration.txt”, Table 2), and (ii) for the spatial data configuration (“configuration_spatial_data.txt”, Table 3).
CONFIGURATION PARAMETERS. Configuration parameters in SAS Drug Development (screenshot below) define all aspects surrounding the program, which include all inputs, program “configuration” options and all outputs that need to be returned and saved to the repository. If you omit to specify an output, the output will not be moved to the repository after the program ends executing. A configuration parameter has several attributes that are specific to what input or output item it represents, but common to all is the name. A program can reference a configuration parameter in two different ways. A global macro variable with the configuration parameter name is automatically created, which value points to the temporary location on the SAS server. The configuration parameters LOG, LST and PGM may not be accessible through global macro variables, but can be obtained in the SAS Drug Development parameter data set as well as the original value of any configuration parameter. The special parameter data set is created for each execution of the full or just a selection of program code and contains all the original parameter values and other house-keeping properties. The data set is of course accessed by specifying the global macro variable SDDPARMS instead of the data set name. The configuration parameters are actually stored within and not separate to the program file in the repository as an eXtensible Markup Language (XML) structure appended to the end of each SAS program. The XML structure, in earlier versions of SAS Drug Development referred to as PACMAN, is interpreted each time a SAS program is executed within SAS Drug Development as the initialisation step. This XML structure remains well hidden from the user and is edited through one of the SAS Drug Development user interfaces, such as the Process Editor or Job Editor, rather than coded by the SAS Drug Development user. 1 The disconnect between the repository and SAS servers is until and including at least SAS Drug Development version 3.5. The difference between how programs are configured between the environments SAS Drug Development and SAS on a workstation or server prohibits a SAS program from being uploaded into SAS Drug Development from a local network share and executed without change. A next logical step is a simple convention that would allow a SAS program to work within and outside of SAS Drug Development and let the upload and download process complete any technical transformations necessary. An efficient process would incorpora...
CONFIGURATION PARAMETERS. The DSP uses various configuration parameters controlled by the Core Processor. These configuration parameters specify frequencies, powers, durations, and thresholds used for detection and generation of tones and voice data. This section defines the various parameters and their format in DSP memory.
