Extension card · q-Rung Orthopair
q-Rung orthopair TOPSIS (Pinar and Boran, 2020)
This is the form of TOPSIS for situations where an expert assigns a judgement both strong support and a strong reservation at once, and the sum of the two exceeds the intuitionistic or Pythagorean bound; it still ranks the result with a single closeness score.
Base method
TOPSIS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
q-Rung Orthopair →
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 decision logic stays the same.
Cells. In crisp TOPSIS every cell is a single number. Here every cell is a pair: support degree μ and rejection degree ν. The sum of the q-th powers of these two degrees cannot exceed 1. The user does not choose q; the method runs at q = 3 and this value is fixed in DecisionMind. Weights come from outside as a single number; the method does not generate weights.
Scale equalisation. In crisp TOPSIS columns are divided by the root of the sum of their squares. There is no such division here. For a cost criterion the method reverses the pair: the support and rejection degrees are swapped. Every criterion is thereby read in the benefit direction, and the remaining steps proceed in a single direction.
Distance. After weighting, the best pair and the worst pair are determined for every criterion. Every alternative's distance to these two pairs is measured taking all three components — support, rejection and hesitancy — into account together. In crisp TOPSIS this was a straight-line distance between single numbers. Here the distance has three components, and a hesitancy share also enters it.
Result and defuzzification. The closeness score carries the same definition: the ratio of the distance to the anti-ideal over the sum of the two distances. The result is again a single number between 0 and 1. The method does not discard uncertainty at the outset. Uncertainty is carried through to the distance calculation and descends to a single number there.
DecisionMind fixes the standard q-ROF Euclidean distance for this method. A different distance measure has also been proposed in the literature, and that measure can give a different magnitude, even a different order. Weights are taken from outside as a single number.
How to Read the Output
The closeness score is read as in crisp TOPSIS: it is not a percentage, it is not compared with another analysis, the ideal point shifts and the order can change once the alternative set changes. The difference lies here. Beneath the score there now also sits a tension between support and rejection, and the score does not say whether it reflects this tension.
The gap between two scores depends on how sharp the input pairs are. If an expert gave the same judgement both high support and high reservation, this duality enters the calculation but becomes invisible in the report. The report should therefore show not only the score but also on which criterion the gap between support and rejection is small.
Thus instead of writing:
"Because q-rung TOPSIS models uncertainty, the result is more accurate"
the report should read:
"The criteria on which the expert gave both strong support and strong reservation have been flagged separately; the closeness score has turned out sensitive to the weight of these criteria"
Carrying the uncertainty through does not make the result more certain, it only keeps it from staying hidden.
When to Prefer This over the Base Method
Use this extension when an expert gives a judgement both strong support and a strong reservation at once, and this pair exceeds both the intuitionistic and the Pythagorean bound. Which pair exceeds which bound is shown by the short decision rule on the q-Rung data-type card. If the pair already fits within the intuitionistic or Pythagorean bound there is no need to raise q; a large q reduces discriminating power, it does not raise accuracy.
Converting an already-measured criterion into this form is wrong. In DecisionMind the table must be of a single type throughout. If some criteria are measured and some are judgement-based, all of them are written into the same data type. A measured criterion is entered as a fixed pair, and that pair carries no uncertainty. The exit condition of the base TOPSIS holds here too: if no compromise is acceptable on one criterion, the TOPSIS family is not the right choice.
Mistakes Specific to This Extension
Entering data without checking the constraint. In every cell, the sum of the third powers of the support and rejection degrees cannot exceed 1. This check is made before the calculation, not after.
Changing the distance measure while expecting the same result. DecisionMind uses the standard q-ROF Euclidean distance. An alternative distance formula in the literature gives a different score, and in some tables a different order. Which distance was used must be stated in the report.
Reversing the cost direction twice. The method swaps the support and rejection degree for a cost criterion. Repeating this swap once more at the ideal-point selection reverses the direction entirely and turns the ranking on its head.
Defuzzifying first and then running crisp TOPSIS. In the illustrative example below, this path shows A1 and A2 as closer to each other than they really are; the real gap shrinks or grows, but in every case the resulting number is artificial.
The governing principle is this:
q-Rung orthopair TOPSIS exists to carry the tension between support and rejection through to the last step. Any application that disregards the rejection degree or fails to check the constraint erases this extension's own contribution.
Cases
The first case is DecisionMind's validation example. Because the three alternatives closely outrank one another on every criterion, the ranking comes out the same regardless of which measure is chosen. This example is not taken from a book or a paper page; it was produced by running the engine itself. The second case is an illustrative construction.
1. Illustrative example: Three candidates evaluated on three criteria (DecisionMind's validation example)
All three criteria face the benefit direction, and their weights are 0.40, 0.35 and 0.25 respectively. A1's support degree is higher than A2's on every criterion, and its rejection degree is lower than A2's. The same relationship holds between A2 and A3.
| Candidate | C1 (μ, ν) | C2 (μ, ν) | C3 (μ, ν) |
|---|---|---|---|
| A1 | 0.90 · 0.20 | 0.85 · 0.30 | 0.80 · 0.40 |
| A2 | 0.70 · 0.40 | 0.65 · 0.50 | 0.60 · 0.55 |
| A3 | 0.50 · 0.55 | 0.45 · 0.60 | 0.40 · 0.65 |
| Direction | more is better | more is better | more is better |
| Weight | 0.40 | 0.35 | 0.25 |
The method multiplies every column by its weight, then builds the ideal pair and the anti-ideal pair. A1 sits at the ideal point because it holds the highest support and lowest rejection degree on every criterion. Every candidate's distance to these two poles is then measured and the closeness score computed.
| Candidate | Closeness score | Rank |
|---|---|---|
| A1 | 1.000 | 1 |
| A2 | 0.360 | 2 |
| A3 | 0.000 | 3 |
The result reads as follows. A1 sits exactly at the ideal because it takes both higher support and lower rejection on every criterion, and its score is 1. A3 sits in exactly the opposite position, and its score is 0. A2 falls between the two, with a score of 0.360; this shows how far A2 sits from the ideal, not a percentage.
If the weights change places, that is, the heaviest criterion becomes the third, A2's score drops to 0.359 and the ranking does not change. In this example the ranking is resilient to a weight swap, because each candidate outranks its neighbour on every single criterion. This resilience comes from the dataset's own special design; it should not be expected in every table.
In the report: "Among the three candidates, A1 sits exactly at the ideal with both higher support and lower rejection degrees on every criterion. A2 is second with a score of 0.360, and the ranking does not change under a weight swap."
Source: DecisionMind's validation example for the QR-TOPSIS engine. The figures were calculated by independently rewriting the manifest's steps in Python and matched against the engine's own output.
2. Construction: Choosing among three main subcontractors
A contractor will choose among three main subcontractor candidates. Three criteria have been set: technical competence, safety record, and delay risk. Delay risk is a "less is better" criterion. Each subcontractor's suitability on each criterion has been turned into a pair from support and reservation scores given separately by the technical team and the audit team.
| Subcontractor | Technical competence | Safety | Delay risk |
|---|---|---|---|
| T1 | 0.85 · 0.35 | 0.75 · 0.30 | 0.30 · 0.80 |
| T2 | 0.70 · 0.50 | 0.65 · 0.45 | 0.45 · 0.65 |
| T3 | 0.55 · 0.65 | 0.50 · 0.60 | 0.60 · 0.45 |
| Direction | more is better | more is better | less is better |
| Weight | 0.45 | 0.30 | 0.25 |
The method first swaps the support and rejection degree in the delay-risk column, since this criterion is "less is better." The weights, the ideal pair and the anti-ideal pair are then built, and every subcontractor's distance is measured.
| Subcontractor | Closeness score | Rank |
|---|---|---|
| T1 | 1.000 | 1 |
| T2 | 0.476 | 2 |
| T3 | 0.000 | 3 |
The contractor's hesitation is this. If the weights change places, that is, delay risk becomes the heaviest criterion, T2's score rises to 0.489 but the ranking does not change. T1's advantage of both higher support and lower rejection on all three criteria makes the ranking independent of weight preferences. The contractor should still explain in the report where T1's 0.30 rejection degree on the safety score comes from; this is a reservation the audit team still holds.
In the report: "T1 is the subcontractor closest to the ideal, with both stronger support and lower rejection on the technical and safety criteria. The ranking does not change under a weight swap, but T1's reservation share of 0.30 on the safety criterion is separately noted in the report."
3. What Not to Do
In the illustrative example, disregarding the rejection degree and running classical TOPSIS on the support degrees alone gives A2 a score of 0.500 instead of 0.360. The ranking does not change, but the gap between A1 and A2 is shown at a different size than its true value. The second error is forgetting to swap the support and rejection degree on a cost criterion such as delay risk; in that case the subcontractor with the highest delay looks like the ideal option. The third error is adding a pair to the table that fails the q = 3 constraint. For instance a pair with support 0.95 and rejection 0.80 has cubes summing to more than 1, and the calculation starts from an invalid point.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/qr-topsis
Pinar, A., & Boran, F. E. (2020). A q-rung orthopair fuzzy multi-criteria group decision making method for supplier selection based on a novel distance measure. International Journal of Machine Learning and Cybernetics, 11(8), 1749–1780. DOI: 10.1007/s13042-020-01070-1
Yager, R. R. (2017). Generalized orthopair fuzzy sets. IEEE Transactions on Fuzzy Systems, 25(5), 1222–1230. DOI: 10.1109/TFUZZ.2016.2604005
Liu, P., & Wang, P. (2018). Some q-rung orthopair fuzzy aggregation operators and their applications to multiple-attribute decision making. International Journal of Intelligent Systems, 33(2), 259–280. DOI: 10.1002/int.21927
Hwang, C. L., & Yoon, K. (1981). Multiple Attribute Decision Making: Methods and Applications — A State-of-the-Art Survey. Lecture Notes in Economics and Mathematical Systems, Vol. 186. Springer-Verlag. DOI: 10.1007/978-3-642-48318-9
Kuvvetli, B. İ. (2023). Q-ROF TOPSIS ve Q-ROF CoCoSo Yöntemleriyle Petrol İstasyonu Yer Seçimi. Mühendislik Bilimleri ve Tasarım Dergisi, 11(4), 1294–1309. DOI: 10.21923/jesd.1245703