Extension card · Pythagorean
Pythagorean fuzzy WASPAS (DecisionMind derivation)
This is the form of WASPAS for situations where the support and rejection degrees given to a judgement can together exceed 1, provided only that the sum of their squares does not exceed 1. The weighted-sum and weighted-product components are calculated separately over these support-rejection pairs, and only descend to a single score at the very last step.
Base method
WASPAS →
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?
Four things change; the idea of blending a sum with a product does not.
Cells. In classical WASPAS 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, though their plain sum can exceed 1. Criterion weights remain crisp numbers taken from outside.
Scale equalisation. Classical WASPAS equalises every column by dividing it by its own best value. There is no such division step here, because support-rejection pairs already lie between 0 and 1. Instead, μ and ν swap places on a cost criterion. This operation does not equalise scale; it reverses direction.
Sum and product component. Classical WASPAS's weighted sum (WSM) is met here by the Pythagorean fuzzy weighted average (PFWA). Each alternative's support-rejection pairs across the criteria are first reduced to a single pair. This pair is then turned into a single number, Q1, by the score function (s = μ² − ν²). Classical WASPAS's weighted product (WPM) is met by the Pythagorean fuzzy weighted geometric mean (PFWG), which likewise returns Q2 through the same score. PFWA inflates support optimistically, while PFWG brings rejection to the fore; this mirrors the compensatory character of a sum and the penalising character of a product, respectively.
Result and combination. In classical WASPAS, λ is a parameter that can be changed in the interface, between 0 and 1, with a default of 0.5. In this extension, λ is fixed inside the engine at 0.5, and no input can change it; it is offered neither as an interface field, like the weights, nor as an extra input, as in Intuitionistic Fuzzy WASPAS. The combined score is always the equally weighted average of Q1 and Q2.
DecisionMind keeps this direction correction, the PFWA/PFWG combination, the score s = μ² − ν² and the λ = 0.5 constant unchangeable in PF-WASPAS; weights are taken from outside as crisp numbers, and the method does not generate weights.
How to Read the Output
The output is a combined score and a rank, as in classical WASPAS, and it is read the same way: it is not a percentage or a probability, and the ranking can shift when the alternative set changes.
The difference is this. The score blends an optimistic sum view (Q1) with a cautious product view (Q2) in equal weight, and this blend can never be altered. Beneath the score also lies a support-rejection pair, and under the constraint μ² + ν² ≤ 1 this pair covers a wider region than an intuitionistic fuzzy one. The score gap between two alternatives depends on how much support and rejection each received on which criterion.
Thus instead of writing:
"PF-WASPAS shows S2 to be the best alternative"
the report should read:
"This score results from combining the support-rejection pairs separately through PFWA and PFWG and blending them in equal weight; this advantage depends on how much support and rejection was given on which criterion, and it can shift if the weights change"
When to Prefer This over the Base Method
Use this extension when experts give a judgement both strong support and marked reservation at once, and the sum of these two degrees exceeds 1; the intuitionistic fuzzy constraint would force such pairs to shrink. If the sum never exceeds 1, Intuitionistic Fuzzy WASPAS is enough, and there is no need to move to Pythagorean. If the sum of squares also exceeds 1, Pythagorean falls short and a q-rung orthopair form is required. Classical WASPAS's exit condition still applies here: if no compromise is acceptable on one criterion, this extension too is fully compensatory.
If control over λ is wanted, that is, if the balance between WSM and WPM needs manual adjustment, this extension is not suitable; λ is fixed here. Such a need should turn instead to classical WASPAS, or to Intuitionistic Fuzzy WASPAS, which offers λ as an extra input.
Mistakes Specific to This Extension
Violating the value domain. Every cell must satisfy μ ∈ [0,1], ν ∈ [0,1] and μ² + ν² ≤ 1. Feeding the calculation without checking this invalidates the method.
Assuming λ can be changed. In classical WASPAS, and in some extensions of the family, λ varies as an input; in this extension λ is fixed inside the engine at 0.5. A statement in the report such as "tried with λ = 0.3" is wrong for this extension; λ never changes in this family.
Writing ν as 1 − μ. This makes the sum always exactly 1, and the extra space the Pythagorean structure provides over the intuitionistic one goes entirely unused.
Changing the score function and expecting the same result. s = μ² − ν² is the canonical choice but not the only one. A different score can produce a different Q1 or Q2; whichever score was used must be stated in the report.
The governing principle is this:
In PF-WASPAS, the support-rejection pair is combined and scored separately through PFWA and PFWG; the two scores are then blended in an unchangeable equal weight. Writing ν as 1 − μ, or using this extension for a pair that already fits within the intuitionistic constraint, wastes the extension's one contribution: its wider zone of acceptance.
Cases
The first case is DecisionMind's validation example: since the literature has no shared PF-WASPAS application example, a synthetic table of three alternatives and three criteria has been built, faithful to the formula chain. The second case is an illustrative construction.
1. Illustrative example (DecisionMind's validation example): Choosing an irrigation-system technology
A farming enterprise will choose one of three irrigation technologies for its land. Three criteria apply: water efficiency (higher is better), application reliability (higher is better), energy consumption (lower is better). The agricultural engineers reported strong points and serious reservations for every technology-criterion pair at once, so they recorded each assessment as a support-rejection pair; the two values often sum to more than 1.
| Technology | Water efficiency | Application reliability | Energy consumption (lower is better) |
|---|---|---|---|
| S1 | (0.70; 0.40) | (0.50; 0.50) | (0.60; 0.50) |
| S2 | (0.80; 0.30) | (0.60; 0.40) | (0.40; 0.60) |
| S3 | (0.60; 0.50) | (0.70; 0.40) | (0.50; 0.50) |
| Weight | 0.40 | 0.35 | 0.25 |
The method swaps μ and ν on energy consumption, combines the pairs across the three criteria separately with both PFWA and PFWG and scores them (s = μ² − ν²), then blends the two scores with the fixed λ = 0.5.
| Technology | Combined score | Rank |
|---|---|---|
| S2 | 0.3425 | 1 |
| S3 | 0.1588 | 2 |
| S1 | 0.1048 | 3 |
The result reads as follows. S2 holds the highest support and lowest rejection pair (0.80; 0.30) on the most heavily weighted criterion, water efficiency, and is also favoured on energy consumption once reversed. S3 holds the strongest pair on application reliability (0.70; 0.40), but this is not enough to offset S2's advantage on water efficiency.
The enterprise's hesitation: what happens if the water-efficiency weight is lowered from 0.40 to 0.05 and application reliability raised to 0.70 (energy consumption staying at 0.25)? Running the kernel directly and independently in Python, S3's score under these new weights falls to 0.2344 and S2's to 0.2183; first place passes to S3, because S3's advantage in application reliability now governs the heaviest criterion.
In the report: "With the given weights (0.40; 0.35; 0.25), S2 holds the highest combined score (0.3425). Once the weight is shifted markedly towards application reliability (0.05; 0.70; 0.25), first place passes to S3; which criterion should take priority therefore needs its own justification."
Source: DecisionMind's PF-WASPAS validation example; since the literature has no shared PF-WASPAS application table, it was built synthetically, and expected results were derived from the formula chain in the manifest (direction correction, PFWA/PFWG combination, score s = μ² − ν², fixed λ = 0.5). The value space rests on Yager's (2014) definition of the Pythagorean fuzzy set. The scores and weight-swap scenario were computed independently by this card's author by running the kernel directly.
2. Nursery: Choosing a corporate childcare service provider
A company will choose one of three providers to run a corporate childcare service for its staff. Three criteria apply: quality of the education programme (higher is better), physical safety standard (higher is better), monthly service fee (lower is better). The human resources committee reported, for every provider-criterion pair, both a strong positive impression and a serious reservation at once, as a support-rejection pair.
The method swaps μ and ν on the service fee, combines the pairs across the three criteria with PFWA and PFWG and scores them, then blends the two with the fixed λ = 0.5. Suppose the provider with the highest support on the education programme also came out with low rejection on the safety standard, and finished first.
The committee's hesitation: for a provider whose rejection degree on the service-fee criterion remains high, this reservation has dissolved into the single score. The committee should report this front-running provider's rejection degree on the service fee separately, and settle it before signing the contract.
In the report: "One provider stands out on account of the education programme's quality and the safety standard; this provider's rejection degree on the service-fee criterion is higher than the others' and should be addressed separately during contract negotiation."
3. What Not to Do
In the illustrative example, writing S2's water-efficiency pair as 0.80 and 0.20, deriving ν as 1 − μ instead of the reported 0.80 and 0.30, is wrong; it erases the genuine reservation the engineers reported and effectively turns the calculation back into intuitionistic fuzzy WASPAS. The second error is stating in the report that "λ was pulled to 0.7 to give more weight to the sum"; in this extension λ is fixed inside the engine and no input changes it, so no such operation ever took place. The third error is reporting S2's score of 0.3425 as "34 per cent suitability"; the score only ranks these three technologies relative to one another.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/pf-waspas
Zavadskas, E. K., Turskis, Z., Antuchevičienė, J., & Zakarevičius, A. (2012). Optimization of weighted aggregated sum product assessment. Elektronika ir Elektrotechnika, 122(6), 3–6. DOI: 10.5755/j01.eee.122.6.1810
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