Multiport Combinations Configuration (.MCC)

The data structure for the .mcc file is described to understand and setup the file for a multiport calculation correctly. A template file is created when a multiport data package file is generated from a S-parameter configuration.

Table 1. Elements of a multiport combinations configuration file.
Element	Required	Description
MCC	Required	The main grouping element with the following attributes: Version The version of the .mcc file. creationDate The creation date of the file. solverVersion The version used to generate the .mcc file. template file.
referenceData	Required	The grouping element for the data elements that can be reused in multiple multiport combinations elements to define different combinations to process. units sources loads packages networks
units	Required	The `units` element with the following attributes: current The unit used for the current values. Default is Ampere (A). voltage The unit used for the voltage values. Default is Volt (V). impedance The unit used for impedance. Default is Ohm. capacitance The unit used for capacitance. Default is Farad (F). inductance The unit used for inductance. Default is Henry (H).
sources	Required	The grouping element for the `source` elements used to excite a multiport network.
source	Required	A `source` element used to define an excitation with the following attributes: name The name of the source. type The type of source either `constantVoltage` for a voltage source or `constantCurrent` for a current source. magnitude The magnitude of the source. phase The phase in degrees of the source. referenceImpedance The reference impedance of the source. sourceImpedanceName The name of the `load` element used as in internal source impedance.
packages	Required	The grouping element of the `package` elements which references the multiport data package .mdp file.
package	Required	The package element used to describe a multiport data element with the following attributes: name Name of the multiport data package element. dataPackage The path to the .mdp file. touchstoneFileName The name of the Touchstone file used as the base network for the multiport calculation. numberOfPorts The number of ports for the multiport network.
frequencies	Required	The grouping element for the `frequency` element used in the multiport data package with the following attributes: type The frequency type definition `points` or `range`. minimum The minimum frequency defined in the list. maximum The maximum frequency defined in the list.
frequency	Required	The `frequency` element containing a single value.
quantities	Optional	The grouping element for the additional quantities to be scaled by multiport calculator in the multiport data package. The following attributes are used: indexCharacter The character in the `sourceFile` attribute of the `quantity` element which indicates the port index to which the quantity file maps to. wildcardCharacter The character in the `sourcefile` attribute of the `quantity` element that indicates the active port which was used to generate the quantity file.
quantity	Optional	The quantity element referencing either multiple field data files or a single data file in the multiport data package file with the following attributes: type The quantity type `farfields`. name The name of the quantity. sourceFile The name of the source file in the multiport data package. portIndex The port index which the quantity maps to if the wild card method is not used to identify a group of data files in the multiport data package.
loads	Optional	The grouping element for the `load` element which defines the loads attached to a multiport network.
load	Optional	The load element with the following attributes: name The name of the load. type The type of load complex,series,parallel or Touchstone. re The real part of a complex load. im The imaginary part of the complex load. resistor The resistor value for a series or parallel load type. inductor The inductor value for the series or parallel load type. capacitor The capacitance value for the series or parallel load type. filename The path to the one port Touchstone file.
networks	Optional	The grouping element for the `network` elements.
network	Optional	The `network` element describing the properties of a Touchstone network with the following attributes: name The name of the network. filename The path to the Touchstone file. numberOfPorts The number of network ports.
combinations	Required	The grouping element of the `combination` elements each describing a multiport calculation.
combination	Required	The element that describes the connections to a multiport data package for a single calculation. Multiple of these elements can be defined. The following attributes are required: name The name of the multiport combination. packageName The name of the package element to be used in the multiport calculation defined in the packages group.
combinationFrequencies	Optional	The grouping element for a custom range of frequencies to be used in a multiport calculation. If no `frequency` elements are defined inside the group all frequencies are used inside the `package` element.
combinationPortSetup	Required	The grouping element defining the network connections, excitations and loads connected to the multiport network in the data package. The group can contain a `port` and `nwInstance` elements.
port	Required	The element indicating the type of connection to a multiport network with the following attributes: index The port index of the network in the multiport data package. sourceName The name of the source element attached to the port defined in the sources group. loadName The name of the load attached to the port defined in the ports group. nwInstanceName The name of the `nwInstance` element or network that the port is connected to. portIndex The port index of the `nwInstance` network that the port connects to.
nwInstance	Optional	The network instance element that describes what is connected to an additional Touchstone network. The network instance also contains port elements.

Example of a Multiport Combinations Configuration File

This section shows an example of a multiport combinations configuration file.

<?xml version="1.0" encoding="utf-8"?>
<MCC xmlns="http://www.altair.com/altair/feko/ioxml/iomcc"
     version="1"
     creationDate="2022-09-06 08:23:51"
     solverVersion="Altair Feko - Solver (seq) Version 2022.2-21418 from 2022-09-05">
  <referenceData>
    <units current="A" voltage="V" impedance="Ohm" capacitance="F" inductance="H"/>
    <sources>
      <source name="VoltageSource1" type="constantVoltage" magnitude="1" phase="0" 
referenceImpedance="0"/>
    </sources>
    <loads>
        <load name="Load1" type="complexImpedance" re="50" im="0"/>
        <load name="Load2" type="seriesRLCImpedance" capacitor="0" resistor="50" inductor="0"/>
        <load name="Load3" type="touchstone" filename="<path to touchstone file>"/>
        <load name="Load4" type="parallelRLCImpedance" capacitor="0" resistor="50" inductor="0"/>
    </loads>
    <networks>
      <network name="Amp1" filename="two_port_amp.s2p" numberOfPorts="2"/>    
    </networks>
    <packages>
      <package name="case1_three_port_dipole_array" dataPackage="3_dipole_array.mdp" 
       touchstoneFilename="3_dip_mdp_example_SP_dipole_array.s3p" numberOfPorts="3">
        <frequencies type="points" minimum="  1.00E+09" maximum="  1.00E+09">
          <frequency  value='1000000000'/>
        </frequencies>
        <quantities indexCharacter="#" wildcardCharacter="*">
          <quantity  type="farFields" name="FarField1" 
                     sourceFile="FarField1 - S-parameter Port# (*).ffe"/>
        </quantities>
      </package>
    </packages>
  </referenceData>
  <combinations>
    <combination name="Example" packageName="case1_three_port_dipole_array">
      <combinationFrequencies>
      </combinationFrequencies>
       <combinationPortSetup>
        <port index="1" sourceName="VoltageSource1" loadName="Load1"/>
        <port index="2" nwInstanceName="Amp_inst1" portIndex="2"/>
        <port index="3" loadName="Load2"/>
        <nwInstance name="Amp_inst1" networkName="Amp1">
            <port index="1" sourceName="VoltageSource1"/>
        </nwInstance>
      </combinationPortSetup>
    </combination>
  </combinations>
</MCC>