Extension card · q-Rung Orthopair
q-Rung Orthopair CoCoSo (Kuvvetli, 2023)
This is the form of CoCoSo for situations where an expert gives a judgement both strong support and a strong reservation, and the sum of the two exceeds the intuitionistic or Pythagorean boundary. Its output is again a combined compromise score and the ranking that score produces.
Base method
CoCoSo →
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 five-step skeleton and the decision logic do not.
Cells. In crisp CoCoSo every cell is a single number. Here every cell is a pair: support μ, rejection ν. The sum of these two degrees raised to the q-th power cannot exceed 1. The user does not choose q; DecisionMind works with q=3, just as in QR-TOPSIS. Criterion weights are supplied from outside as crisp numbers.
Score and scale equalisation. Every cell is reduced to a single number with Peng and Huang's (2020) hesitancy-penalised score function: r = μ^q − ν^q − ln(1 + π^q), where π = (1 − μ^q − ν^q)^(1/q) is the hesitancy margin. This score differs from Liu and Wang's (2018) simpler s = μ^q − ν^q score by additionally penalising hesitancy. Crisp CoCoSo scales columns to 0-1 against the raw value; here that scaling is applied on top of the score, through direction-sensitive (benefit/cost) min-max. The cost direction is handled directly at the normalisation step here, rather than by complementing the cell as other family members do.
Degeneracy. A weighted sum (S) and a weighted power-sum (P) are computed over the scaled scores. If an alternative is the worst in the column on at least one criterion, its scaled score on that criterion drops to exactly 0. This can push that alternative's S or P down to exactly zero as well. If S or P is zero, the second compromise strategy, k_b = S/min(S) + P/min(P), stays undefined, because the denominator is zero. In this case DecisionMind does not compute k_b (the published value is left blank) and builds the final K score from the sum of k_a and k_c alone; the normal formula, (k_a·k_b·k_c)^(1/3) + (k_a+k_b+k_c)/3, is not used here. This also occurs in the manifest's own validation example (see the illustrative example below).
Score instead of distance. DecisionMind holds the standard Peng-Huang (2020) score and q=3 fixed. Weights are taken from outside as single numbers.
How to Read the Output
As in crisp CoCoSo, the K score is only a ranking within this alternative set. Whether the three compromise strategies agree shows robustness; but when k_b stays undefined (see the "Degeneracy" paragraph above), only two strategies (k_a, k_c) remain, and the robustness comparison must be made on that basis.
The difference is here: beneath the score lies both the support-rejection tension and the hesitancy penalty. Two cells with the same μ−ν difference receive different scores if their hesitancy margin π differs; the Peng-Huang penalty additionally punishes a large π.
Thus instead of writing:
"Because q-Rung CoCoSo models the uncertainty, the result is automatically more accurate"
the report should read:
"The score has reduced the support-rejection difference to a single number together with the hesitancy penalty; if an alternative's S or P is zero, the third compromise strategy (k_b) cannot be computed and K is built from only two strategies, and this must be stated in the report"
When to Prefer This over the Base Method
Use this extension when an expert gives a judgement both strong support and a strong reservation, and this pair exceeds both the intuitionistic and the Pythagorean boundary. If the pair already fits one of these boundaries, there is no need to raise q; a larger q reduces discrimination. Converting a measured criterion into this form manufactures uncertainty that is not there; in DecisionMind the table must be of a single type throughout. The crisp method's exit condition applies here too.
Mistakes Specific to This Extension
Failing to notice that S or P is exactly zero. In the illustrative example below, the weakest alternative (A3) is the worst in the column on every criterion, so its scaled score is exactly 0 on all three criteria; this in turn pushes its weighted sum (S) down to exactly zero. In this case k_b cannot be computed. DecisionMind does not silently swallow this; it leaves k_b blank and builds K from k_a+k_c. Stating in the report that "all three compromise strategies were computed" is wrong in this case.
Ignoring the hesitancy penalty. The Peng-Huang score (r = μ^q−ν^q−ln(1+π^q)) is a fixed rule. Confusing it with Liu and Wang's (2018) simpler s = μ^q−ν^q score can give a different ranking; which score was used must be stated in the report.
Assuming q can be changed. DecisionMind works with q=3, and the user does not choose it. As q changes, the magnitude of the scores changes too (in the illustrative example, A2's K drops from 1.069 at q=2 to 0.882 at q=5), but this is a parameter DecisionMind holds fixed.
Entering data without checking the constraint. In every cell, the sum of μ^q + ν^q cannot exceed 1; this check is performed before the calculation.
The governing principle is this:
In q-Rung orthopair CoCoSo, an alternative being the exact worst in the column on one criterion can push its additive or multiplicative measure down to exactly zero; in that case the third compromise strategy cannot be computed, and K is built from only two strategies.
Cases
The first case is DecisionMind's validation example. QR-CoCoSo's only DOI-carrying application source (Kuvvetli, 2023) presents a case with 5 alternatives × 10 criteria and three decision-makers; because DecisionMind builds a single-decision-maker kernel, rather than carrying this large table over verbatim, it uses a small table, deliberately designed for "strict dominance," that follows the paper's own steps (Equations 9-16). The second case is an illustrative construction.
1. Illustrative example (DecisionMind's validation example): Assessment of three freight quotations on three criteria
All three criteria are in the benefit direction; their weights are 0.40, 0.35 and 0.25 respectively. A1's support degree on every criterion is higher than A2's, and its rejection degree lower than A2's; the same relationship holds between A2 and A3.
| Alternative | 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 |
| Weight | 0.40 | 0.35 | 0.25 |
The method reduces every pair to the Peng-Huang score (q=3), scales it with direction-sensitive min-max, and computes the weighted-sum (S) and weighted-power-sum (P) measures.
| Alternative | Combined score (K) | Rank |
|---|---|---|
| A1 | 1.616 | 1 |
| A2 | 1.008 | 2 |
| A3 | 0.0004 | 3 |
The result reads as follows. A1 fits the ideal exactly, since it receives both higher support and lower rejection on every criterion. A3, being the worst in the column on every criterion, has a scaled score of exactly zero on all three criteria; this leaves A3's weighted sum at S=0 and, in turn, its third compromise strategy (k_b) undefined. DecisionMind detects this and builds K from k_a and k_c alone (k_a=0.616, k_c=1.000, total K=1.616, for A1). A3's K (0.0004) is small enough to be treated, in practical terms, as zero among these three alternatives.
The board's hesitation: if A1's support on C1 (the most heavily weighted criterion) drops from 0.90 to 0.50 and its rejection rises to 0.55, A2 moves ahead (A2: K=1.542, A1: K=1.302). This shows that A1's first place rests on its clear superiority on C1, not on a fixed structural advantage. Even if the weights on C1 and C3 swap places (0.25 / 0.35 / 0.40), the ranking does not break down. Even as the q parameter changes (2, 3, 5), the ranking stays the same; only A2's K shrinks (1.069 → 1.008 → 0.882), which shows that the hesitancy penalty grows heavier as q increases.
In the report: "Among the three alternatives, A1 sits closest to the ideal, with higher support and lower rejection on every criterion (K=1.616); A3 being the worst in the column on every criterion has left the third compromise strategy undefined, so K has been built from only two strategies. If A1's support on C1 drops markedly, A2 moves ahead."
Source: DecisionMind's validation example for the QR-CoCoSo engine; since Kuvvetli's (2023) paper presents a large, multi-decision-maker case, DecisionMind built a small table, deliberately designed for "strict dominance," for its own single-decision-maker kernel. The K scores, the case where k_b stays undefined, and the sensitivity tests were computed by this card's author running the kernel directly.
2. Freight: A logistics firm's choice of last-mile delivery provider
An e-commerce logistics firm will renew its annual contract with one of three last-mile delivery providers (K1, K2, K3). Three criteria are used: on-time delivery performance, reliability based on the damage/loss rate, and capacity flexibility (meeting extra demand during peak periods). The operations team scored, separately, how much support and how much reservation it holds for the judgement "this provider meets the contract terms," for each provider; for some providers both support and reservation are high at the same time.
The method reduces every provider's pairs on the three criteria to the Peng-Huang score, scales them with direction-sensitive min-max, computes the weighted-sum and power-sum measures, and combines them through the compromise strategies. Suppose the provider strongest on on-time delivery is also the weakest on capacity flexibility, and still comes out first, because the weight on on-time delivery is higher.
The firm's hesitation: a provider being the exact worst in the column on any criterion can push its additive measure down to zero and disable the third compromise strategy. The firm should not treat the K score alone as sufficient, and should also see in the report which strategies were actually taken into account.
In the report: "With the weight given to on-time delivery performance, this provider ranks first; however, because of its weakness on capacity flexibility, the third compromise strategy may not have been computable, in which case K has been built from only two strategies."
3. What Not to Do
The first error is mistaking A3's near-zero K score (0.0004) for a calculation error; this is the natural, kernel-verified result of A3 being the worst in the column on every criterion. The second error is reporting that "all three compromise strategies were computed"; when S or P is zero, k_b is undefined, and K is built from k_a and k_c alone. The third error is presenting q=3 as a parameter the user chose; DecisionMind holds this value fixed.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/qr-cocoso
Yazdani, M., Zarate, P., Zavadskas, E. K., & Turskis, Z. (2019). A combined compromise solution (CoCoSo) method for multi-criteria decision-making problems. Management Decision, 57(9), 2501–2519. DOI: 10.1108/MD-05-2017-0458
Yager, R. R. (2017). Generalized orthopair fuzzy sets. IEEE Transactions on Fuzzy Systems, 25(5), 1222–1230. DOI: 10.1109/TFUZZ.2016.2604005
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
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