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.

VAR_LIST_BEGIN /<br />

VAR_LIST_END<br />

SEG_LIST_BEGIN /<br />

SEG_LIST_END<br />

DATA<br />

BEGIN / END<br />

#KEYWORD<br />

(<strong>user</strong>-defined keyword)<br />

Related Topics<br />

Touchstone Data File Format<br />

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

Instantiating a Block Defined by X-Parameters<br />

Only MAG format supported (revision A.01.00).<br />

List of FREQ associated values in ascending order.<br />

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

CITIfile Data File Format<br />

Table 14-2. CITIfile Data Format Supported Keywords (cont.)<br />

Keyword<br />

Limitations / Requirements<br />

Only one SEG in the block allowed (revision A.01.00).<br />

List of FREQ associated values.<br />

Supported:<br />

• S[i,j], Y[i,j], Z[i,j], G[i,j], H[i,j], T[i,j], A[i,j] (mandatory):<br />

• RI, MAGANGLE, DB supported.<br />

• Any order for [i,j] supported.<br />

• DATA S/Y/Z/G/T/A line number should correspond to the<br />

number of ports (#lines = nb_ports×nb_ports).<br />

• PORTZ[i] (<strong>user</strong>-defined keyword, optional, 50Ω by default):<br />

• RI supported (real format only: ", 0").<br />

• Any order for [i] supported.<br />

• All values in a BEGIN/END block should be identical (same<br />

value for all frequencies).<br />

• DATA PORTZ line number should match number of ports<br />

(#lines = nb_ports).<br />

Data should be complex (2 values per line).<br />

Number of lines should correspond to FREQ.<br />

Any line starting with # is ignored (considered as comment).<br />

Eldo® User's Manual, 15.3 709

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

Saved successfully!

Ooh no, something went wrong!