bud_snr()
Returns the budget signal-to-noise-power ratio
Syntax
y = bud_snr(Plan, pinNumber, "simName")
Arguments
| Name | Description | Range | Type | Default | Required |
|---|---|---|---|---|---|
| Plan | number of the selected frequency plan(needed only for HB) | string | no | ||
| pinNumber | Used to choose which pins of each network element are referenced † | [1, ∞) | integer | 1 | no |
| simName | simulation instance name, such as "AC1" or "HB1", used to qualify the data when multiple simulations are performed. | string | no | ||
| † If 1 is passed as the pinNumber, the results at pin 1 of each element are returned; otherwise, the results for all pins of each element are returned. By default, the pinNumber is set to 1 | |||||
Examples
x = bud_snr()
returns the SNR at all frequencies
y = bud_snr(1)
returns the SNR at reference frequencies in plan 1
Defined in
$HPEESOF_DIR/expressions/ael/budget_fun.ael
Notes/Equations
Used in AC and harmonic balance simulations
This is the SNR (in dB) at the terminal(s) of each component, looking into that component. Note that the fundamental frequency at different pins can in general be different, and therefore values are given for all frequencies unless a Plan is referenced. The noise analysis control parameter in the AC and Harmonic Balance Simulation components must be selected. For the AC Simulation component select: "Calculate Noise" and "Include port noise." For the source, the parameter "Noise" should be set to yes. In Harmonic Balance select the "Nonlinear noise" option.
| Note Remember that the budget function can refer only to the default dataset, that is, the dataset selected in the data display window. |
Budget Path Measurements
Instead of all components in alphabetical order, this function can report its values just for the components selected in a budget path, and following the sequence in that path. To facilitate the budget path measurements the name of the budget path variable, as defined in the Schematic window, needs to be entered as the pinNumber argument.
Privacy
Statement
|
Terms of Use
|
Legal |
Contact Us
|
© Agilent 2000-2008 ![]()