Knowledge (XXG)

:Articles for deletion/Evolutionary Algorithm for Landmark Detection - Knowledge (XXG)

Source 📝

522:
in this case one called "landmark detection", noting any unique features these algorithms have for this specific application, alongside other approaches and link to the general evolutionary algorithms page, is more appropriate - I just don't think the topic is wide enough to justify an article when the information is best presented as part of a more general one. I would argue for a rename or merge if there were anything of value in the article. Now I could be wrong about this, some topics such as
560:. But that is surely an argument for merge and expand rather than delete. Or at worst, rename and cut out the crap if no one can be bothered to work on it. As I've said at AFD before, it is totally perverse to our mission to delete the only information we have on a notable subject because it only covers part of it. We're here to build the encyclopaedia, not stamp on the bits that aren't yet perfect. 526:
deserve their own article because there are a lot of unique features when applying genetic algorithms to training neural nets, aside from the more general article on neural networks or evolutionary algorithm, even if they use standard algorithms like genetic algorithms as their base. Is the same true
466:
does it say that primary research papers don't add to notability. Of course they do. Lot's of people researching a topic is almost the definition of notability in a science subject. We must be cautious how we use primary sources, but they are not proscribed from being used at all, and even if they
576:
ok given an article for landmark detection doesn't yet exist, why don't we vote for this one to be renamed to "landmark detection", that way it still exists as a placeholder but is a more general article which will include the evolutionary algorithm approaches as part of it. If you agree with this I
521:
page or maybe a more general page on landmark detection, as it is just the application of standard algorithms such as partical swarm and genetic algorithms with maybe a few nuanced points. These algorithms have been applied to a wide range of fields and generally a mention in a more general article,
396:
I respect the effort here; I hadn't been able to dredge these up. Still, I am not convinced that a standalone article is warranted -- three papers with seventeen citations between them seems like it would make for one or two paragraphs at best. If I am wrong, and these end up being the bulwark of a
613:
page, also there is a lack of secondary sources covering this topic, suggesting it fails WP:NOTE (but even if there was I would argue it is best covered in the aforementioned article). There is nothing of value in the article in its current state so a merge is not necessary hence I vote delete.
475:
is "This paper provides an overview on evolutionary learning methods for the automated design and optimization of fuzzy logic controllers." It discusses landmark recognition. And it has 188 cites. So what additional requirement are you going to add to rule that one out as well?
443:
The sources linked are primary research papers and under Knowledge (XXG):Notability general notability guidelines notability is established through coverage of secondary sources. Even if a secondary source existed, I would argue that this topic is best handled within a section of
414:
I didn't pick the example papers for the number of cites. I picked them because they explicitly had both "landmark detection" and "evolutionary|genetic algorithm" in the titles which made them unarguably on topic. But if number of cites is your concern then
214: 371:. I agree the article is in a poor state but I don't see any purpose in draftifying unless someone is volunteering to work on it. The creator has not been here for twelve years. Sending it to draft would just be slow-motion deletion. 502:, as those provide the most objective evidence of notability. There is no fixed number of sources required since sources vary in quality and depth of coverage, but multiple sources are generally expected. Sources do 467:
were, that does not stop them adding to notability. Notability does not fail because the tabloid press has not run sensationalist stories about it. Overview papers are not primary sources and are pretty much
419:
has 41 cites and included in the text "Landmark detection is a fundamental task in autonomous...". The first paper I linked has 28 cites alone according to gscholar so I don't know how you got to 17 total.
144: 139: 148: 208: 131: 517:
Also again, even if we do establish evidence of lots of research covered by secondary sources such as review articles or certain textbooks, I still contest that this is best included within the
171: 680:: Per above, I think that this would address my notability concerns (obviously landmark detection is a thing which people do), so when I am back at the computer I will withdraw. 280: 135: 640:
I argue this article should be renamed to a more general "landmark detection" which will include the evolutionary approaches as well as other approaches as part of it.
257: 127: 79: 103: 541:
Sorry for the comment about moving goal posts, I thought it was the same user replying both times. You may be right that this is better covered in a general
462:
You are shifting the goalposts again. First you want sources, then sources with lots of cites. Now, so you say, primary research is ruled out. Nowhere in
229: 118: 196: 692: 672: 649: 623: 586: 571: 536: 487: 457: 431: 409: 382: 341: 310: 295: 272: 73: 514:. Multiple publications from the same author or organization are usually regarded as a single source for the purposes of establishing notability." 304:. The subject is notable, but the article is a mess which is why the article should be drafted so other editors can fix the issues wrong with it. 190: 253: 186: 236: 98: 91: 17: 497: 112: 108: 202: 321: 709: 248:
are real, but there's no indication here that this is a notable application, and the article is of very low quality. A
40: 175: 556: 507: 492:
Not sure how I can be shifting goalposts after my first comment. As for the part in WP:N it states as follows: "
667: 610: 566: 482: 426: 377: 397:
beautiful article on evolutionary algorithms for landmark detection, I will gladly withdraw my nomination.
548: 518: 445: 245: 52:. Good work everybody; per the arguments made here I am withdrawing my nomination and moving the page to 705: 36: 645: 619: 582: 532: 453: 222: 511: 356: 249: 662: 658: 635: 561: 542: 477: 438: 421: 391: 372: 336: 53: 546: 448:
and as I'd argue there is nothing of value currently in that article it is best just deleted.
364: 305: 87: 29:
The following discussion is an archived debate of the proposed deletion of the article below.
704:
Subsequent comments should be made on the appropriate discussion page (such as the article's
58: 35:
Subsequent comments should be made on the appropriate discussion page (such as the article's
554: 552: 416: 368: 360: 688: 641: 615: 578: 528: 523: 472: 449: 405: 291: 268: 69: 463: 331: 260:
on Google Scholar -- only one, and it's a list likely scraped from Knowledge (XXG).
369:"Research on genetic algorithm based on tabu search for landmark image recognition" 165: 550: 365:"Landmark-based music recognition system optimisation using genetic algorithms" 682: 399: 285: 262: 63: 558: 527:
here, or is it as I suspect, better covered by a more general article?
417:
Automatic Tuning of a Fuzzy Visual System Using Evolutionary Algorithms
545:
article. There are certainly numerous review papers on the topic
700:
The above discussion is preserved as an archive of the debate.
361:"A Novel Genetic Algorithm for 3D Facial Landmark Localization" 324:
to generate a more thorough discussion and clearer consensus.
473:"Evolutionary algorithms for fuzzy control system design" 161: 157: 153: 221: 330:Please add new comments below this notice. Thanks, 235: 43:). No further edits should be made to this page. 712:). No further edits should be made to this page. 279:Note: This discussion has been included in the 609:The topic is best covered by a section in the 281:list of Computing-related deletion discussions 56:. Hopefully some of these sources make it in! 128:Evolutionary Algorithm for Landmark Detection 80:Evolutionary Algorithm for Landmark Detection 8: 471:in medical articles. The first sentence of 119:Help, my article got nominated for deletion! 278: 577:will also change my vote to "rename" 18:Knowledge (XXG):Articles for deletion 7: 24: 104:Introduction to deletion process 1: 693:11:35, 21 December 2022 (UTC) 673:00:21, 21 December 2022 (UTC) 650:23:30, 20 December 2022 (UTC) 624:15:10, 19 December 2022 (UTC) 587:22:54, 20 December 2022 (UTC) 572:13:32, 20 December 2022 (UTC) 537:00:11, 20 December 2022 (UTC) 488:16:58, 19 December 2022 (UTC) 458:15:10, 19 December 2022 (UTC) 432:14:16, 16 December 2022 (UTC) 410:08:33, 16 December 2022 (UTC) 383:14:38, 14 December 2022 (UTC) 342:02:25, 14 December 2022 (UTC) 311:23:27, 12 December 2022 (UTC) 74:11:37, 21 December 2022 (UTC) 296:02:13, 7 December 2022 (UTC) 273:02:13, 7 December 2022 (UTC) 94:(AfD)? Read these primers! 729: 702:Please do not modify it. 32:Please do not modify it. 611:evolutionary algorithms 246:Evolutionary algorithms 632:After discussion with 519:Evolutionary algorithm 446:Evolutionary algorithm 176:edits since nomination 92:Articles for deletion 59:(non-admin closure) 659:Landmark detection 543:landmark detection 512:written in English 54:Landmark detection 499:secondary sources 344: 298: 109:Guide to deletion 99:How to contribute 61: 720: 639: 508:available online 442: 395: 339: 334: 329: 327: 325: 308: 307:`~HelpingWorld~` 240: 239: 225: 169: 151: 89: 57: 34: 728: 727: 723: 722: 721: 719: 718: 717: 716: 710:deletion review 661:and repurpose. 633: 626: 436: 389: 337: 332: 320: 318: 306: 182: 142: 126: 123: 86: 83: 48:The result was 41:deletion review 30: 22: 21: 20: 12: 11: 5: 726: 724: 715: 714: 696: 695: 675: 652: 627: 605: 602: 601: 600: 599: 598: 597: 596: 595: 594: 593: 592: 591: 590: 589: 524:Neuroevolution 515: 386: 385: 347: 346: 328: 314: 313: 299: 252:search yields 243: 242: 179: 122: 121: 116: 106: 101: 84: 82: 77: 46: 45: 25: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 725: 713: 711: 707: 703: 698: 697: 694: 691: 690: 685: 684: 679: 676: 674: 671: 670: 666: 665: 660: 656: 653: 651: 647: 643: 637: 636:Spinningspark 631: 628: 625: 621: 617: 612: 608: 604: 603: 588: 584: 580: 575: 574: 573: 570: 569: 565: 564: 559: 557: 555: 553: 551: 549: 547: 544: 540: 539: 538: 534: 530: 525: 520: 516: 513: 509: 505: 501: 500: 495: 491: 490: 489: 486: 485: 481: 480: 474: 470: 465: 461: 460: 459: 455: 451: 447: 440: 439:Spinningspark 435: 434: 433: 430: 429: 425: 424: 418: 413: 412: 411: 408: 407: 402: 401: 393: 392:SpinningSpark 388: 387: 384: 381: 380: 376: 375: 370: 366: 362: 358: 354: 353: 349: 348: 345: 343: 340: 335: 326: 323: 316: 315: 312: 309: 303: 300: 297: 294: 293: 288: 287: 282: 277: 276: 275: 274: 271: 270: 265: 264: 259: 255: 251: 247: 238: 234: 231: 228: 224: 220: 216: 213: 210: 207: 204: 201: 198: 195: 192: 188: 185: 184:Find sources: 180: 177: 173: 167: 163: 159: 155: 150: 146: 141: 137: 133: 129: 125: 124: 120: 117: 114: 110: 107: 105: 102: 100: 97: 96: 95: 93: 88: 81: 78: 76: 75: 72: 71: 66: 65: 60: 55: 51: 44: 42: 38: 33: 27: 26: 19: 701: 699: 687: 681: 677: 668: 663: 654: 629: 606: 567: 562: 503: 498: 496:" should be 493: 483: 478: 468: 427: 422: 404: 398: 378: 373: 351: 350: 319: 317: 301: 290: 284: 267: 261: 256:. Basically 244: 232: 226: 218: 211: 205: 199: 193: 183: 85: 68: 62: 49: 47: 31: 28: 506:have to be 209:free images 258:no results 706:talk page 642:EvilxFish 616:EvilxFish 579:EvilxFish 529:EvilxFish 469:de riguer 450:EvilxFish 357:WP:NEXIST 250:WP:BEFORE 37:talk page 708:or in a 664:Spinning 563:Spinning 479:Spinning 423:Spinning 374:Spinning 359:such as 322:Relisted 172:View log 113:glossary 39:or in a 494:Sources 215:WP refs 203:scholar 145:protect 140:history 90:New to 678:Rename 655:Rename 630:rename 607:delete 338:plicit 187:Google 149:delete 50:Rename 669:Spark 568:Spark 484:Spark 428:Spark 379:Spark 302:Draft 254:squat 230:JSTOR 191:books 166:views 158:watch 154:links 16:< 646:talk 620:talk 583:talk 533:talk 464:WP:N 454:talk 367:and 355:per 352:Keep 223:FENS 197:news 162:logs 136:talk 132:edit 657:to 510:or 504:not 237:TWL 170:– ( 683:jp 648:) 622:) 585:) 535:) 456:) 400:jp 363:, 286:jp 283:. 263:jp 217:) 174:| 164:| 160:| 156:| 152:| 147:| 143:| 138:| 134:| 64:jp 689:g 686:× 644:( 638:: 634:@ 618:( 581:( 531:( 452:( 441:: 437:@ 406:g 403:× 394:: 390:@ 333:✗ 292:g 289:× 269:g 266:× 241:) 233:· 227:· 219:· 212:· 206:· 200:· 194:· 189:( 181:( 178:) 168:) 130:( 115:) 111:( 70:g 67:×

Index

Knowledge (XXG):Articles for deletion
talk page
deletion review
Landmark detection
(non-admin closure)
jp
g
11:37, 21 December 2022 (UTC)
Evolutionary Algorithm for Landmark Detection

Articles for deletion
How to contribute
Introduction to deletion process
Guide to deletion
glossary
Help, my article got nominated for deletion!
Evolutionary Algorithm for Landmark Detection
edit
talk
history
protect
delete
links
watch
logs
views
View log
edits since nomination
Google
books

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