All,
I have done a reset on how we should proceed with Touchstone 3:
1. We need to add the backward compatibility rule (for Touchstone 2 and
above, not for Touchstone 1)
2. We need to add parsable port information
I do not think we should implement Sparse Data. There were two reasons for
Sparse Data
1. S-parameters to describe a full package
* I do not think the industry is capable of generating a full
s-parameter interconnect model for a 500 pin package.
* When companies who can and want to produce such package, they can
submit a BIRD to support it.
2. S-parameters to describe large connector model.
* Today, connector companies supply an s72p that describes 3 columns of
a 168 column 12 row connector.
i. 72=3*12*2
* I think this can be captured in a general way in parsable port
information records.
I would like to review the rules of formatting the network data. Putting aside
the special rules for s2p, my understanding is:
1. Touchstone 1
* The first line of data for a specific contains that frequency
* That line may have 4 Sij pairs of numbers
* Every row of data in an Sij starts on a new line.
2. Touchstone 2
* Relaxes the number of Sij pairs of numbers on a line
* Every row of data in an Sij starts on a new line.
Walter
Walter Katz
Work 508.647-7633
Cell 720.417-3762
[Description: Description: Visit MathWorks.com]