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 />

solution is fixed. The decision about pole reduction is made from considering the solution<br />

step (pole is too “fast”), or the duration of the simulation interval (pole is too “slow”).<br />

Therefore, the set of actually used poles is defined “dynamically” from considering the<br />

parameters of the .TRAN command. The generated list of poles/residues (*.pls) file remains<br />

unaffected. Pole reduction does not considerably affect the solution accuracy. However, if<br />

the precise simulation is needed, the option can be disabled by setting<br />

POLE_REDUCTION=0.<br />

• HIGH_PRECISION=val<br />

Set to 1 to increase the fitting accuracy by enabling more poles than in regular mode (with<br />

default value 0). This option can be useful for verification purposes, for example if a<br />

“reference solution” is required. However, it is not recommended if the input data itself is<br />

not very accurate. Also, since high-precision fitting produces more poles, it makes<br />

simulation slower.<br />

• MAXROW=val<br />

Sets the limit (val/2) to the frequency points of the original dependence used in fitting. The<br />

default value is 40000, corresponding to 20,000 points.<br />

• MAXCOL=val<br />

Sets the limit (val/2) to the maximal order of complexity for fitting in CPF. The default<br />

value is 1500, corresponding to an order of complexity of 750. For very complicated (sharp,<br />

irregular) dependencies it is sometimes reasonable to reduce the order of complexity,<br />

especially if we have reasons not to entirely trust the input data at higher frequencies. As a<br />

rule, reducing the order of complexity is a better strategy than reducing the number of points<br />

to consider (MAXROW).<br />

• IDX_F=val<br />

Defines the index (integer number) VAL associated with the S parameter file (IDX_F=VAL<br />

implies that the input parameter file is named sbVAL.par). Alternative way of defining the<br />

input data file; see also the STRING: keyword.<br />

• SINGLE_REFERENCE_NODE=val<br />

Set to 1 to support a single reference node. When the number of pins of the FBLOCK model<br />

is even, Eldo considers that each port has two pins. When the number of pins is odd, Eldo<br />

considers the reference pin is the same for all ports (and it is the last pin). Specify<br />

SINGLE_REFERENCE_NODE=1 to enable the FBLOCK model to consider the last pin as<br />

the common reference pin for all ports if the number of ports is the number of pins−1.<br />

• STRING:<br />

Used to define the name of the touchstone file, CITIfile, or poles/residues file (.pls),<br />

containing the input data. Path definition is allowed. Another way of defining the data file is<br />

using the IDX_F parameter under the keyword PARAM: together with all the other<br />

parameters, not under the STRING: keyword. If not specified, sbVAL.par is used by<br />

default, where VAL is defined by IDX_F, or the number of ports otherwise.<br />

702<br />

Eldo® User's Manual, 15.3

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

Saved successfully!

Ooh no, something went wrong!