10.06.2016 Views

eldo_user

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Working with S, Y, Z Parameters<br />

Instantiating a Block Defined by S, Y, Z Parameters<br />

• NO_DELAY=val<br />

Used to enable or prevent delay extraction in the CPF or DSP methods. NO_DELAY=0<br />

enables delay extraction, NO_DELAY=1 disables it. The default value is 0.<br />

• GROUPFIT=val<br />

Used in CPF to force group fitting instead of individual for every matrix component. As a<br />

rule, with this option, fitting requires less effort but this might compromise accuracy. The<br />

default value is 0, corresponding to individual fitting.<br />

• SYMMETRY=val<br />

The default assumption (SYMMETRY=1) made in CPF on the fitting stage is that the<br />

original S (or Y or Z) matrix is symmetric. Matrix symmetry is a valid assumption as long as<br />

the S-model describes a reciprocal subcircuit. We cannot simply rely on symmetry of the<br />

matrices in the input data. Very often, the input matrices generated by field-solvers or<br />

measured from reciprocal systems, are not strictly symmetric, however they should be<br />

handled as symmetric. Set to 0 to disable the default assumption.<br />

• FORCE_PASSIVITY=val<br />

Enables or disables each of the two different types of passivity enforcement available in the<br />

CPF method. These types are (1) pre-fit passivity enforcement, in which the original<br />

sampled data is worked with to make it “passive,” and (2) post-fit enforcement, in which<br />

poles/residues are corrected in such a way as to make the approximation strictly passive.<br />

FORCE_PASSIVITY=0 means there is no passivity enforcement.<br />

FORCE_PASSIVITY=1 activates pre-fit passivity enforcement.<br />

FORCE_PASSIVITY=2 activates post-fit enforcement.<br />

FORCE_PASSIVITY=3 (default) activates them both.<br />

Pre-fit passivity enforcement is recommended for all passive devices. It removes occasional<br />

passivity violations from the input data (which may result from measurement errors).<br />

However, even for the passive data created by pre-fit passivity enforcement, fitting may still<br />

result in a non-passive model if this data is defined within a limited frequency range (typical<br />

case). With two different methods of passivity enforcement, you can determine the true<br />

reason for non-passivity: poor accuracy of the input data or fitting errors. The reason for<br />

both could be incomplete frequency range, non-causality, or insufficient resolution of the<br />

input data. For causal, accurate, and smooth input data, fitting accuracy is quite high.<br />

By default, Eldo performs a passivity check on the Touchstone file S parameter data. When<br />

non-passivity is detected, data passivity will be enforced and a corresponding information<br />

message will be issued. After the fitting of the S parameter data a new passivity check is<br />

performed on the fitting results. If passivity violation is detected then passivity of the fitting<br />

is enforced and a message is again issued.<br />

Warning message examples:<br />

o non-passive data found:<br />

700<br />

Eldo® User's Manual, 15.3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!