Extension card · Pythagorean
Pythagorean fuzzy MOORA
This is the Pythagorean fuzzy form of MOORA. The support and rejection degrees given to a judgement may sum to more than 1, provided the sum of their squares does not. The ratio system runs on this pair and comes down to a single net score.
Base method
MOORA →
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?
Cells. In crisp MOORA every cell is a single number. Here every cell is a pair: μ, the support degree, and ν, the rejection degree; it must satisfy μ² + ν² ≤ 1. Criterion weights come from outside as crisp numbers; uncertainty is carried only in the decision matrix's cells.
Scale equalisation. Crisp MOORA divides the cell value directly by the column's magnitude. PF-MOORA first reduces every pair to a single score. The score is support squared minus rejection squared (μ² − ν²); since this value can range from −1 to 1, 1 is added to shift it. The shifted score is normalised, as in crisp MOORA, by dividing it by the root of its own column's magnitude. On a cost criterion the pair is not reversed; the directional difference is instead carried by sign in the following addition-subtraction step, exactly as in crisp MOORA.
Score and the ratio system. The normalised, shifted scores are weighted; the sum over the "lower is better" criteria is subtracted from the sum over the "higher is better" criteria. This is exactly the same operation as crisp MOORA's ratio system; the only difference is that the input has already been reduced to a μ² − ν² score.
Result and defuzzification. The score-subtraction step is itself the defuzzification, and it happens at MOORA's first step, not at the end. The hesitancy margin, π = √(1 − μ² − ν²), never enters this score calculation at all. DecisionMind also lists the reference point approach as a step in this family, but this step simply copies the ratio system's score; it does not produce an independent calculation. The only approach that actually runs is the ratio system.
DecisionMind fixes, for classical PF-MOORA, μ² − ν² as the score function, and this score's calculation at the first step. Weights are taken from outside as crisp numbers; the method does not generate weights.
How to Read the Output
The output is a net score and a rank, as in crisp MOORA, and it is read the same way. The difference is this: this score in fact rests on the difference between the squares of a judgement's support and rejection degrees, and never sees the hesitancy margin, that is, the portion neither supported nor rejected. Two assessments with the same μ² − ν² difference but different hesitancy margins give the same result in PF-MOORA.
Thus instead of writing:
"PF-MOORA's result is more reliable because it accounts for uncertainty"
the report should read:
"PF-MOORA accounted only for the squared difference between support and rejection; criteria with a high hesitancy margin should be flagged separately in the report"
When to Prefer This over the Base Method
Use this extension where experts give a judgement both strong support and a marked reservation, and these pairs' sum exceeds the intuitionistic fuzzy constraint. Where the sum does not already exceed 1, intuitionistic fuzzy MOORA (if-moora) is sufficient; moving to Pythagorean adds no information, and only discrimination is lost. Where the sum of squares also exceeds 1, Pythagorean falls short, and q-Rung orthopair is required.
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 table must hold a single data type throughout. The exit condition is the same as for crisp MOORA: 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, and the hesitancy margin is zeroed. The calculation may look like PF-MOORA, but it actually reverts to intuitionistic fuzzy MOORA.
Changing the score function and expecting the same result. μ² − ν² is the canonical choice, but not the only one. A different score can give a different ranking; which score was used must be stated in the report.
Mistaking the reference point approach for a genuine second method. In this extension, the reference point step copies the ratio system's score; it does not perform an independent calculation.
The governing principle is this:
PF-MOORA exists to carry the expert's support and rejection degrees, without clipping them, into the ratio system. Writing ν as 1 − μ, or changing the score function without stating it, undoes this contribution.
Cases
The first case is DecisionMind's validation example. Yager (2014) and Zhang and Xu (2014) are the founding sources for the Pythagorean fuzzy set and its TOPSIS extension, but they do not contain a decision table specific to MOORA; DecisionMind has therefore built a small, hand-traceable table with the same 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 criteria are "higher is better," the third "lower is better."
| Alternative | C1 (higher is better) | C2 (higher is better) | 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 takes every cell's μ² − ν² score, shifts it and normalises it against the column's magnitude. It then weights the results and subtracts the sum over the "lower is better" criterion from the sum over the "higher is better" criteria.
| Alternative | MOORA score | Rank |
|---|---|---|
| A2 | 0.3534 | 1 |
| A3 | 0.2704 | 2 |
| A1 | 0.2357 | 3 |
The result reads as follows. A2 holds the highest support and lowest rejection degree on all three criteria; it carries the best share on the "higher is better" criteria and the lowest share on the "lower is better" criterion. For this reason A2 stays ahead under every weight distribution tested.
The board's hesitation lies not in the order between A1 and A3, but in how wide the gap ahead of A2 remains. If C1's weight is drawn down from 0.40 to 0.05 and C2's raised from 0.35 to 0.70 (C3 held at 0.25), A3 moves ahead of A2, at 0.3302 against 0.3248. This means A2's first place depends on C1's weight staying above a certain level.
In the report: "With the given weights, A2 has the highest net score (0.3534). Once C1's weight is markedly lowered and shifted to C2, A3 takes first place; this shows that A2's advantage rests on its strong position on C1."
Source: DecisionMind PF-MOORA manifest, validation example. The Pythagorean fuzzy score function follows the formulas defined by Yager (2014) and Zhang and Xu (2014); since the founding sources give no decision table specific to MOORA, the table has been built by DecisionMind faithfully to these formulas. The MOORA scores and the weight sensitivity were independently recalculated by this card's author with the same algorithm, matching the kernel code exactly.
2. Cybersecurity: An organisation's choice of daily monitoring software
An organisation's IT unit will choose among three security-monitoring software packages. Three criteria are used: threat-detection strength, alert noise (this one "lower is better"), and ease of integration. Experts score every package against a single judgement: "this software is fit for the organisation." The security team reports both strong support and marked reservation on threat-detection strength. The reason is that high detection strength often comes together with a high false-alarm rate; this duality pushes the support-rejection sum above 1.
The method scores and normalises the three packages, weights the results, and calculates the ratio system's score. Suppose the package with the highest threat-detection strength also has the highest alert noise; it still comes out first, because the weight on detection strength exceeds that on noise.
The IT unit's hesitation: if the weight on alert noise is raised, that is, if the team judges daily workload to matter more than detection strength, the ranking may change. This sensitivity should be reported not through a single weight scenario alone, but by showing at what point the order flips as the weight rises.
In the report: "With the given weights, the software with the highest threat-detection strength is first on net score; the point at which this ranking changes as the alert-noise weight is raised has also been shown."
3. What Not to Do
In the illustrative example, writing A2's C3 cell as μ=0.40, ν=0.60 by taking ν as 1 − μ instead of μ=0.40, ν=0.60 makes no difference here, since this pair's sum already comes to exactly 1; the actual mistake is shrinking a pair whose sum exceeds 1 (for example μ=0.80, ν=0.50) to ν = 1 − μ = 0.20. In that case the hesitancy margin is zeroed, and the Pythagorean structure's extra region of acceptance is never used. The second mistake is writing a pair whose squares sum to more than 1 (for example μ=0.90, ν=0.70) without checking μ² + ν² first; this cell should never enter PF-MOORA. The third mistake is presenting the reference point step's result as an independent second verification of the ratio system; in this extension that step simply copies the same score.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/pf-moora
Brauers, W. K. M., & Zavadskas, E. K. (2006). The MOORA method and its application to privatization in a transition economy. Control and Cybernetics, 35(2), 445–469. (no DOI)
Brauers, W. K. M., & Zavadskas, E. K. (2009). Robustness of the multi-objective MOORA method with a test for the facilities sector. Technological and Economic Development of Economy, 15(2), 352–375. DOI: 10.3846/1392-8619.2009.15.352-375
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
Yager, R. R. (2013). Pythagorean fuzzy subsets. 2013 Joint IFSA World Congress and NAFIPS Annual Meeting, 57–61. DOI: 10.1109/IFSA-NAFIPS.2013.6608375
Zhang, X., & Xu, Z. (2014). Extension of TOPSIS to multiple criteria decision making with Pythagorean fuzzy sets. International Journal of Intelligent Systems, 29(12), 1061–1078. DOI: 10.1002/int.21676