ElectreConcordanceWithInteractions

alternatives

Alternatives to consider.

The input value should be a valid XMCDA document whose main tag is <alternatives>.

criteria

Criteria to consider, possibly with preference and indifference thresholds. Each criterion must have a preference direction specified (min or max). It is worth mentioning that this module allows to define thresholds as constants as well as linear functions.

The input value should be a valid XMCDA document whose main tag is <criteria>.

criteriaScales

The scales of the criteria to consider. Each criterion must have a preference direction specified (min or max).

The input value should be a valid XMCDA document whose main tag is <criteriaScales>.

criteriaThresholds (optional)

The criteria’ preference and indifference thresholds. It is worth mentioning that this module allows to define thresholds as constants as well as linear functions.

The input value should be a valid XMCDA document whose main tag is <criteriaThresholds>.

performance_table

The performance of alternatives.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

profiles_performance_table (optional)

The performance of profiles (boundary or central).

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

interactions_sets

Declarations of criteria interactions which should be taken into account. Possible interactions are: “strengthening”, “weakening” and “antagonistic”.

Every such declaration contains a pair of criteria and a numerical value for the interaction coefficient. This value should be negative for “weakening” and positive for “strenghtening” and “antagonistic”. This coefficient should be interpreted as follows: the larger its absolute value, the more important the interaction effect. All interaction coefficients should fulfill positive net balance condition.

The order in which each criterion appears in its interaction definition is significant, i.e. it designates the direction in which certain criterion affects the other, which is especially true when it comes to “antagonistic” interaction (i.e. the second criterion is the affected one).

There are no limits on the number of interactions that can be declared, but keep in mind that it should be rather small to make sense.

It is possible to declare more than one interactions of the same type, although please note that considering the same pair of criteria involved, the “strengthening” and “weakening” interactions are mutually exclusive.

The input value should be a valid XMCDA document whose main tag is <criteriaSets>. It must have the following form:

<criteriaValues mcdaConcept="criteriaInteractions">
  <criterionValue mcdaConcept="strengthening">
    <criteriaSet>
      <element>
        <criterionID>[...]</criterionID>
      </element>
      <element>
        <criterionID>[...]</criterionID>
      </element>
    </criteriaSet>
    <value>
      <real>[...]</real>
    </value>
  </criterionValue>
  <criterionValue mcdaConcept="weakening">
    [...]
  </criterionValue>
  <criterionValue mcdaConcept="antagonistic">
    [...]
  </criterionValue>
</criteraValues>

interactions_values

Declarations of criteria interactions which should be taken into account. Possible interactions are: “strengthening”, “weakening” and “antagonistic”.

Every such declaration contains a pair of criteria and a numerical value for the interaction coefficient. This value should be negative for “weakening” and positive for “strenghtening” and “antagonistic”. This coefficient should be interpreted as follows: the larger its absolute value, the more important the interaction effect. All interaction coefficients should fulfill positive net balance condition.

The order in which each criterion appears in its interaction definition is significant, i.e. it designates the direction in which certain criterion affects the other, which is especially true when it comes to “antagonistic” interaction (i.e. the second criterion is the affected one).

There are no limits on the number of interactions that can be declared, but keep in mind that it should be rather small to make sense.

It is possible to declare more than one interactions of the same type, although please note that considering the same pair of criteria involved, the “strengthening” and “weakening” interactions are mutually exclusive.

The input value should be a valid XMCDA document whose main tag is <criteriaSetsValues>. It must have the following form:

<criteriaValues mcdaConcept="criteriaInteractions">
  <criterionValue mcdaConcept="strengthening">
    <criteriaSet>
      <element>
        <criterionID>[...]</criterionID>
      </element>
      <element>
        <criterionID>[...]</criterionID>
      </element>
    </criteriaSet>
    <value>
      <real>[...]</real>
    </value>
  </criterionValue>
  <criterionValue mcdaConcept="weakening">
    [...]
  </criterionValue>
  <criterionValue mcdaConcept="antagonistic">
    [...]
  </criterionValue>
</criteraValues>

weights

Weights of criteria to consider.

The input value should be a valid XMCDA document whose main tag is <criteriaValues>.

classes_profiles (optional)

Definitions of profiles (boundary or central) which should be used for classes (categories) representation.

The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>.

method_parameters

A set of parameters provided to tune up the module’s operation.

The input value should be a valid XMCDA document whose main tag is <programParameters>. It must have the following form:

<programParameters>
  <programParameter name="comparison_with">
    <values>
      <value>
        <label>%1</label>
      </value>
    </values>
  </programParameter>
  <programParameter name="z_function">
    <values>
      <value>
        <label>%2</label>
      </value>
    </values>
  </programParameter>
 </programParameters>

where:

• %1 is a parameter named “comparison_with”. It can have the following values:

  • alternatives: alternatives vs alternatives
  • boundary_profiles: alternatives vs boundary profiles
  • central_profiles: alternatives vs central (characteristic) profiles

  The default value is item0.

• %2 is a parameter named “z_function”. It can have the following values:

  • multiplication: Z(x, y) = xy
  • minimum: Z(x, y) = min{x, y}

  The default value is item0.

concordance

Matrix of aggregated concordance indices computed from the given data.

The returned value is a XMCDA document whose main tag is <alternativesComparisons>.

messages

Messages or errors generated by this module.

The returned value is a XMCDA document whose main tag is <methodMessages>.