I have noticed that the order of the transmission terms (S12 and S21) in Touchstone formatted and *.mdm formatted files are reversed. Q1: Is there any particular reason for this ? Q2: Can one simply edit the *.mdm file, transposing the column headers and get the correct behavior in ICCAP upon IMPORT ? (I admit that I haven't fully explored doing this, but was wondering if you guys at EESOF have, and what the result is. What I am wondering is if the IMPORT function re-sorts the data, looking for a specific order as specified by the *.mdm header).
Q3: is there a chance that the *.mdm header can be re-structured such that it conforms to the Touchstone convention (S21 data preceeds S12 data) ?
Q3: is there a chance that the *.mdm header can be re-structured such that it conforms to the Touchstone convention (S21 data preceeds S12 data) ?
Your observation is correct:
However, remember that mdm was intended to be universal to all types of data exported from IC-CAP. Â I recommend using PEL approach shown below instead of mdm to get touchstone file exported or imported into IC-CAP:
If you were using ADS to simulate the resulting IC-CAP touchstone file, as shown in the following IC-CAP/ADS example, using the PEL approach can easily be imported into ADS simulations…
see IC-CAP 2006B example: /examples/ demo_features/ 5_PEL_PROGRAMMING/ 1_data_import_export/ 2read_write_data/ Spar_Touchstone/ 02_write_read_touchstone.mdl
IC-CAP 2006B/ADS 2006A: How to import touchstone S2P file exported via IC-CAP 2006B example PEL program into ADS dataset... https://edasupportweb.soco.agilent.com/portal/page?_pageid=36,39980&_dad=portal&_schema=PORTAL&id=273092&search=IC-CAP%20ADS%20Touchstone&ref=search
Hope this helps... Â Otherwise, if you have more specific questions, please feel free to contact your local Agilent EEsof IC-CAP technical support desk.
Regards,
Mark