Extension card · Linguistic
Linguistic Pythagorean fuzzy EDAS (CRITIC-weighted) (Akram, Ramzan and Deveci, 2023)
Linguistic Pythagorean fuzzy EDAS is the form of EDAS where criterion assessment is done with support and rejection degrees chosen from a term set, and criterion weights are derived not from an expert but from the data itself, by the CRITIC method.
Base method
EDAS →
Philosophy, mechanics, strengths and weaknesses are on the base method card; this card describes only the difference.
Data type (family)
Linguistic →
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?
Five things change; the logic of position relative to the average does not.
Cells. In crisp EDAS every cell is a single number. Here every cell is a linguistic Pythagorean fuzzy number: a support index and a rejection index chosen from the term set, whose squares must sum to no more than the square of the term set's highest level. Where more than one decision-maker is involved, each expert's pair is reduced to a single pair by a weighted aggregation rule (Hamacher sum).
Weights come from within, not from outside. Crisp EDAS does not generate weights, it takes them from outside. This extension does the opposite: criterion weights are computed from the aggregated linguistic Pythagorean matrix by the CRITIC method (Diakoulaki, Mavrotas and Papayannakis, 1995). CRITIC looks both at how widely a criterion's own values spread and at how much distinct information it carries relative to other criteria; it gives a higher weight to a criterion that is widely spread and only weakly related to the other criteria. Even if the user enters a weight, it is not used in this extension; the weight is recomputed from the data on every run.
Reduction to a score and the average solution. Before CRITIC is computed, every cell is reduced to a single number by a score function; CRITIC's spread and correlation calculations are carried out on these scores. The average solution, however, is built on the raw linguistic Pythagorean pairs themselves, using their own aggregation rule; the positive and negative deviation are measured against this average and against each cell's score.
Result and defuzzification. The weighted deviations are also summed as linguistic Pythagorean pairs and are reduced to a single number by the score function only at the final step. This is a different order from IV-EDAS's defuzzification at the very start, and closer to IV-ARAS: here defuzzification happens twice, once per cell for CRITIC, and once more for the weighted sums.
DecisionMind fixes, for this extension, the internal computation of CRITIC and the disregarding of any user-entered weight. This means the principle "weight is taken from outside," stated on the crisp EDAS card, does not apply to this extension.
How to Read the Output
The assessment score is read the same way as in crisp EDAS: it is a position relative to the set's own average, not a percentage or a probability. The difference is here: the weights are not a decision-maker's preference but a consequence of the data's own spread. A criterion coming out with a high weight does not mean "this criterion is important"; it means "this criterion is the one that most separates the alternatives from one another." Two different data sets can give the same criteria different CRITIC weights.
Thus instead of writing:
"According to LPF-EDAS, this criterion's weight came out high, so the organisation sees this criterion as the most important"
the report should read:
"This criterion's weight arises from the fact that its discriminating power among the alternatives is highest in this data set; it does not reflect the organisation's subjective priority"
When to Prefer This over the Base Method
This extension is suitable when criterion assessment is carried out with support-rejection pairs chosen from a term set, and when criterion weights need to be derived from the data's own spread rather than from expert judgement. If experts' own weight preferences need to be recorded, CRITIC is not a suitable choice; a linguistic EDAS extension where weight is set by subjective methods (AHP, BWM, SWARA) should be sought instead. If all alternatives take the same value on a criterion, CRITIC reduces that criterion's weight to zero; this is the weight-side counterpart of crisp EDAS's own principle that a criterion close to the average has weaker discriminating power.
Mistakes Specific to This Extension
Assuming the user-entered weight was used. In this extension, any weight entered is for reference only; the weight actually used in the calculation is CRITIC's own output. The report must state clearly which weight was actually used.
Leaving one criterion's column constant. If all alternatives take the same value on a criterion, CRITIC makes its standard deviation, and so its weight, zero. This is not an error; it indicates that the criterion is not discriminating within this data set.
Using a different τ (the term set's top level) for different assessors. All decision-makers and criteria must share the same term set; sets with different top levels cannot be compared directly.
Carrying over the manifest's recorded example figures without question. This extension's manifest example figures do not exactly match the engine's current output; the detail is in the sign-off note. The card therefore uses the figures the engine produces today.
The governing principle is this:
In LPF-EDAS, weight is a measurement, not a preference. Presenting CRITIC's output as if it were the user's own weight, or mistaking a criterion's zero weight for an error, misrepresents the method's data-driven nature.
Cases
This extension is on the engine's list of flagged methods for direction testing: whether it behaves in the expected direction when one alternative's data is improved on certain criteria needs separate examination. The manifest's own recorded example values also do not exactly match the engine's current output; the ranking is the same, the magnitudes differ. The first case therefore uses not the manifest's table but the figures the engine produces today; the detail is in the sign-off note. The second case is an illustrative construction.
1. Illustrative example: Assessing three alternatives on three criteria (the engine's current output)
Three alternatives are assessed on three criteria (C1, C3 "higher is better"; C2 "lower is better") with linguistic Pythagorean support-rejection pairs. The term set's top level is 8 (τ=8); two decision-makers (weighted 0.6 and 0.4) gave idempotent scores, that is, they agreed on the same term.
| Alternative | C1 (support, rejection) | C2, cost (support, rejection) | C3 (support, rejection) |
|---|---|---|---|
| A1 | 3, 6 | 3, 6 | 4, 4 |
| A2 | 5, 3 | 2, 7 | 3, 6 |
| A3 | 4, 4 | 4, 4 | 5, 3 |
The method swaps support and rejection on C2, reduces every pair to a score, computes the criterion weights from the data itself with CRITIC (yielding C1=0.265, C2=0.317, C3=0.418), builds the average solution and applies the remaining steps of crisp EDAS.
| Alternative | Assessment score | Rank |
|---|---|---|
| A2 | 0.500 | 1 |
| A3 | 0.342 | 2 |
| A1 | 0.273 | 3 |
The result reads as follows. A2 sits clearly above the average on C3, the criterion that comes out heaviest. Despite being weak on C2, its lead on C3 makes it first. A1 stays around or below the average on all three criteria and finishes last.
The decision's hesitation: if A1's term on the cost criterion C2 improves by one level, that is, if the support-rejection pair shifts from (3,6) to (2,7), both A1's score and the CRITIC weights are recomputed. When DecisionMind's engine is re-run with this change, the ranking returns as A2, A1, A3; A1 scores 0.546, A2 scores 0.597, A3 scores 0.149. A3 drops to third place.
In the report: "According to the engine's current output, A2 is in the most advantageous position relative to the set's average (0.500); the weights were computed from the data by CRITIC, not chosen by the user. If A1's value on the cost criterion improves by a single level, the ranking changes and A3 drops to last place; A1's cost data should therefore be separately verified."
Source: DecisionMind's LPF-EDAS engine's current (2026-09-13) output. The manifest's recorded example values (A1=0.371; A2=0.512; A3=0.441) do not exactly match the values the engine produces today (A1=0.273; A2=0.500; A3=0.342); the ranking is A2, A3, A1 in both cases. The difference and its likely cause are detailed in the sign-off note. The assessment scores and the weight-trade-off scenario were obtained by this card's author independently running DecisionMind's engine (scripts/method_runner.py LPF-EDAS).
2. Publishing: A publisher's choice of translated-book proposal
A publisher will publish one of three translated-book proposals received from three agencies. Criteria: expected reader interest in the subject, the cost of translation rights, and the editorial workload of the text; the last two are "lower is better." Editors have given each proposal a support and rejection degree, chosen from a pre-declared term set, on these criteria.
The method reduces the three proposals' pairs on the three criteria to scores, computes the criterion weights from the data itself with CRITIC, measures favourable and unfavourable deviation from the average, and combines these into a single assessment score. Say the editorial-workload criterion came out very close across all three proposals, and CRITIC assigned this criterion a weight close to zero; the ranking effectively came to be determined by reader interest and rights cost alone.
The publisher's hesitation is this: a low weight for editorial workload does not mean this criterion is unimportant; it only means it is not discriminating among these three proposals. If a new proposal is added, this criterion could become discriminating again and its weight could rise.
In the report: "The priority order has been shaped by the reader-interest and rights-cost criteria; the editorial-workload criterion was not found discriminating among these three proposals and so came out with a low weight. If a new proposal enters the assessment, the weights must be recomputed."
3. What Not to Do
The first error is entering a user-chosen weight set in the illustrative example (say C1=0.50, C2=0.30, C3=0.20) and assuming it fed into the calculation; in this extension the weight is recomputed by CRITIC on every run, and the entered value is not used. The second error is interpreting editorial workload's near-zero weight in the publishing example as "this criterion is unimportant, no need to collect data on it"; a low weight only shows that discriminating power is low within the current data set. The third error is copying the manifest's recorded example figures straight into a report without comparing them against the engine's current output; in this card the two sources give different figures, and which one was used must be stated clearly.
Sources
For the formulas behind each step, the intermediate tables and citation formats, see the DecisionMind method page: decisionmind.app/library/lpf-edas
Akram, M., Ramzan, N., & Deveci, M. (2023). Linguistic Pythagorean fuzzy CRITIC-EDAS method for multiple-attribute group decision analysis. Engineering Applications of Artificial Intelligence, 119, 105777. DOI: 10.1016/j.engappai.2022.105777
Garg, H. (2018). Linguistic Pythagorean fuzzy sets and its applications in multiattribute decision-making process. International Journal of Intelligent Systems, 33(6), 1234–1263. DOI: 10.1002/int.21979
Diakoulaki, D., Mavrotas, G., & Papayannakis, L. (1995). Determining objective weights in multiple criteria problems: The CRITIC method. Computers & Operations Research, 22(7), 763–770. DOI: 10.1016/0305-0548(94)00059-H
Keshavarz Ghorabaee, M., Zavadskas, E. K., Olfat, L., & Turskis, Z. (2015). Multi-criteria inventory classification using a new method of evaluation based on distance from average solution (EDAS). Informatica, 26(3), 435–451. DOI: 10.15388/Informatica.2015.57