Knowledge

Conflict resolution strategy

Source 📝

22: 106:
Specificity - If all of the conditions of two or more rules are satisfied, choose the rule according to how specific its conditions are. It is possible to favor either the more general or the more specific case. The most specific may be identified roughly as the one having the greatest number of
113:
Not previously used - If a rule's conditions are satisfied, but previously the same rule has been satisfied by the same facts, ignore the rule. This helps to prevent the system from entering infinite loops.
110:
Recency - When two or more rules could be chosen, favor the one that matches the most recently added facts, as these are most likely to describe the current situation.
272: 40: 309: 349: 87: 75: 102:
Conflict resolution strategies fall into several main categories. They each have advantages which form their rationales.
107:
preconditions. This usefully catches exceptions and other special cases before firing the more general (default) rules.
58: 335: 172: 120:
interpreters use by default, but any strategy may be implemented by building suitable rules in a Prolog system.
232: 286: 371: 36: 259:"Conflict Resolution Techniques for Expert Systems Used to Classify Remotely Sensed Satellite Images" 79: 339: 313: 376: 94:
arises when the conditions of two or more rules are satisfied by the currently known facts.
116:
Order - Pick the first applicable rule in order of presentation. This is the strategy that
8: 133: 123:
Arbitrary choice - Pick a rule at random. This has the merit of being simple to compute.
345: 266: 258: 83: 365: 168: 206: 256: 287:"KnowledgeWorks and Prolog User Guide. 3.1.5.3 Conflict Resolution" 91: 117: 138: 31:
may be too technical for most readers to understand
207:"IAI: Production Systems. 10. Conflict Resolution" 173:"Production System Conflict Resolution Strategies" 363: 341:Prolog Programming for Artificial Intelligence 257:Pakiarajah, V., Crowther, P. and Hartnett, J. 166: 271:: CS1 maint: multiple names: authors list ( 200: 198: 196: 194: 192: 190: 204: 328: 312:. University of Edinburgh. Archived from 187: 59:Learn how and when to remove this message 43:, without removing the technical details. 279: 224: 364: 334: 162: 160: 158: 156: 154: 41:make it understandable to non-experts 230: 15: 13: 250: 151: 14: 388: 310:"Prolog and Execution Strategies" 307: 20: 344:. Addison Wesley. p. 644. 233:"Chapter 6: Production Systems" 301: 72:Conflict resolution strategies 1: 289:. LispWorks. 22 December 2009 144: 97: 90:to fire. The need for such a 175:. Carnegie Mellon University 86:, to help in choosing which 7: 127: 10: 393: 212:. University of Birmingham 205:Bullinaria, John (2005). 82:, such as in rule-based 80:artificial intelligence 261:. GeoComputation 2000. 134:Cognitive modelling 76:production systems 372:Logic programming 351:978-0-201-40375-6 169:Forgy, Charles L. 69: 68: 61: 384: 356: 355: 332: 326: 325: 323: 321: 305: 299: 298: 296: 294: 283: 277: 276: 270: 262: 254: 248: 247: 245: 243: 237: 231:Fayyoumi, Ebaa. 228: 222: 221: 219: 217: 211: 202: 185: 184: 182: 180: 164: 64: 57: 53: 50: 44: 24: 23: 16: 392: 391: 387: 386: 385: 383: 382: 381: 362: 361: 360: 359: 352: 333: 329: 319: 317: 316:on 31 July 2016 306: 302: 292: 290: 285: 284: 280: 264: 263: 255: 251: 241: 239: 235: 229: 225: 215: 213: 209: 203: 188: 178: 176: 167:McDermott, J.; 165: 152: 147: 130: 100: 88:production rule 65: 54: 48: 45: 37:help improve it 34: 25: 21: 12: 11: 5: 390: 380: 379: 374: 358: 357: 350: 327: 300: 278: 249: 223: 186: 149: 148: 146: 143: 142: 141: 136: 129: 126: 125: 124: 121: 114: 111: 108: 99: 96: 84:expert systems 67: 66: 28: 26: 19: 9: 6: 4: 3: 2: 389: 378: 375: 373: 370: 369: 367: 353: 347: 343: 342: 337: 331: 315: 311: 304: 288: 282: 274: 268: 260: 253: 238:. EIS, Jordan 234: 227: 208: 201: 199: 197: 195: 193: 191: 174: 170: 163: 161: 159: 157: 155: 150: 140: 137: 135: 132: 131: 122: 119: 115: 112: 109: 105: 104: 103: 95: 93: 89: 85: 81: 77: 73: 63: 60: 52: 42: 38: 32: 29:This article 27: 18: 17: 377:Rule engines 340: 336:Bratko, Ivan 330: 318:. Retrieved 314:the original 308:Brna, Paul. 303: 291:. Retrieved 281: 252: 240:. Retrieved 226: 214:. Retrieved 177:. Retrieved 101: 74:are used in 71: 70: 55: 49:January 2022 46: 30: 366:Categories 320:18 January 293:18 January 242:18 January 216:18 January 179:18 January 145:References 98:Categories 338:(2021). 267:cite web 171:(1976). 128:See also 92:strategy 35:Please 348:  118:Prolog 236:(PDF) 210:(PDF) 139:CLIPS 346:ISBN 322:2016 295:2016 273:link 244:2016 218:2016 181:2016 78:in 39:to 368:: 269:}} 265:{{ 189:^ 153:^ 354:. 324:. 297:. 275:) 246:. 220:. 183:. 62:) 56:( 51:) 47:( 33:.

Index

help improve it
make it understandable to non-experts
Learn how and when to remove this message
production systems
artificial intelligence
expert systems
production rule
strategy
Prolog
Cognitive modelling
CLIPS





Forgy, Charles L.
"Production System Conflict Resolution Strategies"






"IAI: Production Systems. 10. Conflict Resolution"
"Chapter 6: Production Systems"
"Conflict Resolution Techniques for Expert Systems Used to Classify Remotely Sensed Satellite Images"
cite web
link
"KnowledgeWorks and Prolog User Guide. 3.1.5.3 Conflict Resolution"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.