Extension card · Pythagorean
Pythagorean fuzzy MARCOS
This is the Pythagorean fuzzy form of MARCOS. The support and rejection degrees given to a judgement may sum to more than 1, provided the sum of their squares does not. The output is again a ratio built relative to the ideal and the anti-ideal, combined into a single utility degree.
Base method
MARCOS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Pythagorean →
What this data type is, when to use it, how to write it in a cell: the family's full account is here.
What Changes from the Base Method?
Three things change; the decision logic does not.
Cells. In crisp MARCOS every cell is a single number. Here every cell is a pair: μ, the support degree, and ν, the rejection degree. These two values must satisfy μ² + ν² ≤ 1. The hesitancy margin, π = √(1 − μ² − ν²), is derived from these two degrees; it is not asked of the expert separately. Criterion weights remain crisp numbers and come from outside.
The extended table and scale equalisation. Crisp MARCOS extends the table with two hypothetical rows built from every criterion's observed best and worst value. PF-MARCOS applies the same logic to pairs: for every criterion, the best pair is built from the highest μ and the lowest ν, and the worst pair from the lowest μ and the highest ν. On a cost criterion these two roles swap. Every cell is then ratioed against its own column's best pair; this ratioing corresponds to crisp MARCOS's division operation, except that μ and ν are now ratioed separately.
Combination and row totals. Crisp MARCOS sums the weighted normalised values horizontally. PF-MARCOS performs this summation with the Pythagorean weighted-sum rule; the result is again a single support-rejection pair, not a number. Every alternative's combined pair yields two separate ratios against the ideal and anti-ideal rows' combined pairs. These ratios are turned into a single number by the score function, s = μ² − ν², and then passed through crisp MARCOS's own utility functions.
Result and defuzzification. The output is a single final utility degree, produced by combining the two utility functions; it sits on the same scale as crisp MARCOS. Uncertainty is carried through as the row totals are built by the Pythagorean summation rule; it collapses to a single number only once the score function is applied. This means uncertainty is carried as a pair right up to the last step, and is defuzzified only at the final step.
DecisionMind fixes, for PF-MARCOS, the Pythagorean ratioing rule, the Pythagorean weighted-sum rule, and the score-based utility functions. Criterion weights are taken from outside as crisp numbers; the method does not generate weights.
How to Read the Output
The final utility degree states where an alternative stands relative to the ideal and anti-ideal references in this set; this is the same as in crisp MARCOS. What differs is that these references are now support-rejection pairs. Where the gap in utility degree between two alternatives is large, this gap generally holds regardless of how much the input pairs' μ and ν shift. Where the gap is small, a small change in μ or ν can easily reverse the order, and this must be shown in the report.
Thus instead of writing:
"PF-MARCOS found the best supplier"
the report should read:
"With these weights and this alternative set, this is the alternative with the most balanced utility ratio relative to the ideal and anti-ideal support-rejection references; how far this advantage holds up against small changes in the input pairs should be tested separately"
When to Prefer This over the Base Method
Use this extension where experts give a judgement both strong support and a marked reservation, and you want both how much of the ideal has been reached and how far the anti-ideal has been left behind to appear together. If the two degrees sum to more than 1, the intuitionistic fuzzy constraint forces these pairs to shrink, because that constraint keeps the sum at no more than 1. Pythagorean fuzzy solves this problem. A measured value is not turned directly into a support-rejection pair. It is first converted into a judgement, and only then are μ and ν derived from separate sources; the detail is on the data-type card. The table must hold a single data type throughout; part crisp and part Pythagorean is not allowed. The base method's exit condition applies here too: if no compromise is acceptable on one criterion, this extension is also compensatory and will not eliminate anything below a threshold.
Mistakes Specific to This Extension
Domain violation. Every cell must satisfy μ ∈ [0,1], ν ∈ [0,1] and μ² + ν² ≤ 1. Entering the calculation without this check invalidates the method.
Writing ν as 1 − μ. In that case the sum always comes to exactly 1. The hesitancy margin is zeroed. The extra region the Pythagorean structure offers over the intuitionistic one is never used.
Changing the score function and expecting the same result. s = μ² − ν² is the canonical choice, but not the only one. Defuzzifying the ideal and anti-ideal ratios with a different score can give a different utility degree.
Reversing the ideal and anti-ideal pair's role on a cost criterion. On a benefit criterion, the ideal pair is built from the highest support and the lowest rejection degree. On a cost criterion this is reversed. Skipping this reversal turns the ranking on its head.
Turning a measured value directly into μ. Scaling a measured quantity such as price or time to 0-1 and writing it as μ, with ν given as its complement, does not produce a judgement. It only conceals crisp data.
The governing principle is this:
The PF-MARCOS result is a summary of the alternatives' proportional standing relative to this set's own ideal and anti-ideal support-rejection references. These references shift together with the alternative set, and the report must show this.
Cases
The first case is not a literature case. No single source paper is shared by every member of the PF-MARCOS family; DecisionMind has therefore built a small synthetic table that lets the method's steps be followed by hand, and has produced the result expected from the engine's own formulas. The second case is an illustrative construction.
1. Illustrative example: Three alternatives, three criteria (DecisionMind validation example)
Three alternatives are assessed on three criteria. The first two are "higher is better," the third "lower is better." Every cell is a support-rejection pair. The weights are C1=0.40, C2=0.35, C3=0.25.
| Alternative | C1 | C2 | C3 (lower is better) |
|---|---|---|---|
| A1 | (0.70;0.40) | (0.50;0.50) | (0.60;0.50) |
| A2 | (0.80;0.30) | (0.60;0.40) | (0.40;0.60) |
| A3 | (0.60;0.50) | (0.70;0.40) | (0.50;0.50) |
| Weight | 0.40 | 0.35 | 0.25 |
The method first extends the table with ideal and anti-ideal pairs. It then ratios every cell against its own column's ideal pair, combines every row with the Pythagorean weighted-sum rule, and derives, from this combined pair, two utility ratios and then a single final utility degree.
| Alternative | Final utility degree | Rank |
|---|---|---|
| A3 | 3.3858 | 1 |
| A1 | 1.0101 | 2 |
| A2 | 0.0000 | 3 |
The result reads as follows. A3 looks weak on C1 but holds the best pair on C2 and stays balanced on C3 too; this combination puts A3 clearly first. A2, despite holding the best pair on C1, carries the worst pair on C3, and this drops it to last place.
The decision's hesitation comes from here. Even if the weights are changed as far as C1=0.80, C2=0.10, C3=0.10, A3 keeps first place and A2 stays last. Changing a single cell gives the same result: whether A1's C2 pair is improved from 0.50;0.50 to 0.60;0.40, or A3's C1 pair is worsened from 0.60;0.50 to 0.50;0.60, A3 still comes first. This shows that A3's advantage in this example is robust to both a weight change and a single-cell change.
In the report: "With the given weights, A3 is clearly first, at 3.3858. This order does not change when the weights are varied over a wide range, or when a single cell is improved or worsened; A2's weakness on C3 determines the ranking from the outset."
Source: DecisionMind's validation example for the PF-MARCOS engine. It is a synthetic table, not taken from a paper. The final utility degrees were independently reproduced by running DecisionMind's PF-MARCOS engine, and matched the manifest's own expected values exactly.
2. Maritime: Choosing a cargo-handling equipment supplier at a port operator
A port operator evaluates three suppliers, D1-D3, for container-crane maintenance and supply services, on three criteria: technical fitness, delivery reliability, and maintenance-cost risk. The first two are "higher is better," and maintenance-cost risk is "lower is better." Every cell is the technical team's support-rejection pair for that supplier. The weights have been set so that technical fitness and delivery reliability carry equal shares, with risk given a slightly smaller share: 0.35, 0.35, 0.30.
| Supplier | Technical fitness | Delivery reliability | Maintenance-cost risk (lower is better) |
|---|---|---|---|
| D1 | (0.75;0.45) | (0.65;0.55) | (0.45;0.65) |
| D2 | (0.60;0.60) | (0.80;0.40) | (0.55;0.60) |
| D3 | (0.70;0.50) | (0.55;0.60) | (0.35;0.75) |
| Weight | 0.35 | 0.35 | 0.30 |
The method extends the table with ideal and anti-ideal pairs, ratios every cell, combines the rows with the Pythagorean weighted-sum rule, and calculates the final utility degree. D2 holds the best pair on delivery reliability, and this offsets its relative weakness on technical fitness.
| Supplier | Final utility degree | Rank |
|---|---|---|
| D2 | 3.1599 | 1 |
| D1 | 2.6163 | 2 |
| D3 | 2.5225 | 3 |
The operator's hesitation comes from this weight change. If technical fitness's weight is lowered from 0.35 to 0.20 and delivery reliability is raised from 0.35 to 0.50, D1 moves ahead of D2: D1 rises to 3.3672, and D2 falls to 2.8806. This shows that D2's first place depends on the balance of weight between technical fitness and delivery reliability.
In the report: "With the given weights, D2 is first, at 3.1599. If delivery reliability's weight is raised enough to exceed technical fitness's, 0.50 against 0.20, D1 moves ahead; the preference between these two suppliers therefore depends on the weighting decision and should be stated plainly in the report."
3. What Not to Do
In the illustrative example, had criterion C3, despite being "lower is better," been marked "higher is better," the ideal pair would be built from the highest risk value, and A2's weakness on C3 would turn into an advantage instead. The second mistake is treating the maritime table's D2 final utility degree of 3.1599 as an absolute claim of "the most reliable supplier"; this value only compares these three suppliers against each other on their own ideal and anti-ideal axes. The third mistake is reducing a single cell's support-rejection pair to a single score first and then running crisp MARCOS on it; this hides the hesitancy margin and erases from the report which alternative rests on how uncertain a judgement.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/pf-marcos
Wang, Y., Wang, W., Wang, Z., Deveci, M., Roy, S. K., & Kadry, S. (2024). Selection of sustainable food suppliers using the Pythagorean fuzzy CRITIC-MARCOS method. Information Sciences, 664, 120326. DOI: 10.1016/j.ins.2024.120326
Stević, Ž., Pamučar, D., Puška, A., & Chatterjee, P. (2020). Sustainable supplier selection in healthcare industries using a new MCDM method: Measurement of Alternatives and Ranking according to Compromise Solution (MARCOS). Computers & Industrial Engineering, 140, 106231. DOI: 10.1016/j.cie.2019.106231
Yager, R. R. (2014). Pythagorean membership grades in multicriteria decision making. IEEE Transactions on Fuzzy Systems, 22(4), 958–965. DOI: 10.1109/TFUZZ.2013.2278989