Knowledge

:Bots/Requests for approval/Lightbot 13 - Knowledge

Source 📝

431:'gallon' is highly suitable for human-overseen-automation (either as Lightbot or Lightmouse). Note that there is also a time dimension: references to 'gallon' in the British Empire/Commonwealth outside North America have declined massively as the metric system has been adopted. It's easy to worry too much about the ambiguity, but in practice the naked gallon can almost always be specified beyond reasonable doubt. This is trivial to demonstrate. As you suggest, I'll certainly avoid making a decision where the time-frame or region makes the ambiguity difficult to resolve. 559: 778: 522: 48: 351:
convert template will have to come out. But the issues are usually trivial or esoteric for example the addition of 'US' to gallon and/or the use of upper and lower case. From time to time, new variations on these issues do crop up and I've started many discussions myself in the relevant guideline pages following feedback on a conversion.
354:
Mix of metric and non-metric. The bot isn't designed to resolve mixed units and has no provision for it in the code. Articles often contain primary metric alongside primary non-metric - sometimes it's for a good reason (such as mixing miles and metres on transport, as you suggest. I'm aware of this),
732:
Yes. The correct convert template isn't the issue. The issue is correctly detecting target text while avoiding false positives. Believe me, I'd prefer to have a static Knowledge and a single process and a single piece of code. My conservative approach is to do the easy stuff (e.g. unambiguous units,
668:
Ranges like '0-60 MPH' '0 to 60 MPH', 'between '0 and 60 MPH' are a big challenge. It's not just mph, it's all units. There are so many variations of how ranges are expressed that I spend a lot of effort trying to avoid false positives and changes that look odd. It's a lot more work to make a change
430:
Regional variation/overlap for gallon: Ironically, this is why work is required to eliminate the ambiguity for readers. The automation is required to simplify the work but it will be the human that makes the decision. It hasn't been my main focus but over the years I've done enough to know that the
346:
Ambiguous units. In many cases of 'ambiguous units', there is no ambiguity in the context. For example, it's almost always easy to see when the author write 'gallon' but means the US gallon because it's in a US article about a US topic using US sources. Ambiguity will be avoided where the ambiguity
350:
Reasons for format change. It's not possible to use the convert template *without* adopting a standard format in accordance with guidelines. Non-template and template conversions will be (as far as I know) consistent. If somebody disagrees with the format used by the convert template, then the
398:
I am in favor of determining the meaning of which gallon is meant. Ambiguity would be real in non-American articles. I'd stay away from (or at least be very, very aware and cautious of) any articles, like British Empire/Commonwealth related, where the imperial gallon is most likely meant.
355:
sometimes it's not. Over the years using automation and seeing lots of articles pass in front of me, I have noticed suboptimal unit sequences and responded with human edits in either the Lightbot or Lightmouse accounts. So the option is useful, but is a low priority for Lightbot.
528:
Task is a suitable expansion of Lightbot 5. Note that a successful trial will not necessarily result in however, since I still have some reading to do with the ARBCOM mess, and I'm also wondering if Lightbot 5 should have been approved at all... But let's trial it for now.
211:
The guideline is stable and has existed in various forms for a long time. Other editors and I have done many edits along these lines over a long period. Examples of such conversions exist in contributions list but it would be easier just to demonstrate with new edits.
323:; other articles about railway gauges will be similar as some are defined in imperial and others in metric. I understand it is standard practice on railways in Northern Ireland to measure distances in miles and metres - what will your bot do if it encounters this? 450:
The manual of style was written in part by many people and I know that outside of the United States the abbreviation US is more popular. I remember when we wrote that. People didn't want 'U.K.' and didn't want 'UK' with 'U.S.', therefore US was used (see
733:
non-ranges) together where possible. The scope of that expands with experience. Special issues like ranges, ambiguous units, grouped units are best done in special runs where code and human can be optimised to reduce risks.
318:
What will you do if you find an article that uses a mix of metric and imperial units. I've seen this, including ones that use the convert template with 'imperial (metric)' and 'metric (imperial)'? See for example
427:'U.S. gallon' versus 'US gallon': The Manual of style states 'US gallon' and the convert template complies. I'll do the same. I really don't care either way as long as it's unambiguous and consistent. 198:
Lightbot 5 is permitted to convert miles, but not miles per hour. It is permitted to convert cubic inches but not fluid ounces. This request seeks to correct that. A relevant guideline is at:
635:, but should be handled before approval nonetheless (this way, the bot doesn't have to run twice over the same articles). Could you add fixes such as km² → km per the last bullet of 838: 758: 685:
With respect to km² → km, I agree. It's tackled by default in the template. I'll update the code and that should address many of the non-template instances in text.
754: 192: 188: 180: 669:
that looks good. I don't think I can deliver high performance on ranges right now. Could I appeal to you and your colleagues to allow me to tackle ranges later?
202: 184: 403:, when someone says gallon without saying U.S., they mean imperial gallon. Something to think about... It will be interested to see the trial runs. — 339:
Precision: The 'convert template' will usually be used with default precision. If you want to know more details about how it works, feel free to ask at
737:
We're in the desirable position of discussing task priorities and permutations within the bot scope. In order to get started, can we move to approval?
761:(the addition of 'inch') are entirely contained within this application. If this application is approved, Lightbot5 and Lightbot10 will be withdrawn. 343:. In many cases, this is a match, or +/- 1 significant figures. With the template conversion in place, it's easy for an editor to adjust precision. 206:"Where English-speaking countries use different units for the same measurement, follow the "primary" unit with a conversion in parentheses." 21: 88: 166:
Source code for monobook or vector are available. Source code for AWB will vary but versions are often also kept as user pages.
139: 793: 649: 589: 539: 83: 172:
Janitorial edits to units that contain at least one unit of length, area, or volume e.g. 50 mph, 30 cubic feet per minute.
435:
As you say, a trial will demonstrate how it can be done. Please can we proceed to a trial without further delay? Regards
361: 389:(with dots). Therefore, if you are editing only American articles/topics, it should probably use the more common, U.S. 118: 526:
Approved for trial (50). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
720: 103: 315:
Why would you change the format of units, and what would you do if there was an objection to a change you make?
806: 770: 746: 724: 694: 678: 662: 622: 602: 573: 552: 514: 498: 471: 444: 418: 376: 332: 300: 452: 340: 320: 766: 742: 690: 674: 618: 569: 494: 469: 440: 416: 372: 296: 152: 133: 98: 93: 820: 328: 274: 40: 789: 645: 585: 535: 78: 636: 801: 657: 597: 547: 400: 762: 738: 686: 670: 614: 565: 490: 458: 436: 405: 368: 292: 129: 482:
Laws, like sausages, cease to inspire respect in proportion as we know how they are made.
797: 716: 653: 593: 543: 324: 279: 270: 17: 218:
Multiple runs. Often by batch based on preprocessed list of selected target articles.
832: 785: 641: 581: 531: 228: 59: 385:
Small point: In the United States, the 'United States' is most commonly abbreviated
508: 312:
Where the unit is ambiguous (e.g. "gallons") how will you determine which is meant?
161: 47: 477:
It doesn't surprise me. I think the following quote is apt for style guides:
455:). Convert complies with U.S. as well: {{convert|10|u.s.gal|impgal}}--: --> 708: 703:
When I come across the likes of "0 to 60 mph in 10 seconds" I do this
257:
For units that contain at least one unit of length, area, or volume:
813:
The above discussion is preserved as an archive of the debate.
613:. Edit summary is 'Fix units that include length, area, volume' 278:"50 miles per hour (80 km/h)". This will be in accordance with 819:
To request review of this BRFA, please start a new section at
484: 309:
How will you determine the precision of the conversion to use?
39:
To request review of this BRFA, please start a new section at
265:
Edits may edit the format or spelling e.g. "5 gal(US)" -: -->
183:. That BRFA was very similar to the two previous approvals: 179:
This request duplicates the 'units of measure' section of
629: 610: 261:
Edits may add conversions to units e.g. "50 mph" -: -->
113: 108: 73: 224:
Individual runs of tens, or hundreds, or thousands.
631:it missed a conversion for 0-60 MPH. Not really a 280:Knowledge:Link#What_generally_should_not_be_linked 176:Links to relevant discussions (where appropriate): 759:Knowledge:Bots/Requests for approval/Lightbot 10 191:. This is an extension of the existing approval 33:The following discussion is an archived debate. 755:Knowledge:Bots/Requests for approval/Lightbot 5 193:Knowledge:Bots/Requests for approval/Lightbot 5 189:Knowledge:Bots/Requests for approval/Lightbot 2 181:Knowledge:Bots/Requests for approval/Lightbot 3 705:{{convert|0|to-|60|mph|abbr=on}} in 10 seconds 456:10 U.S. gallons (8.3 imp gal). Good Luck. — 185:Knowledge:Bots/Requests for approval/Lightbot 8: 839:Approved Knowledge bot requests for approval 367:Please can we move to a 50 edit trial? 291:Please can we move to a 50 edit trial? 269:Edits may add or remove links e.g. "50 7: 222:Estimated number of pages affected: 628:Seems all in order. However, here 28: 45:The result of the discussion was 776: 557: 520: 46: 238:Yes, will comply with 'nobots' 146:Automatic or Manually assisted: 637:Knowledge:MOSUNIT#Unit_symbols 157:AWB, monobook, vector, manual 1: 262:"50 miles per hour (80 km/h)" 855: 401:Twelve miles from my house 377:09:52, 25 April 2011 (UTC) 333:12:14, 23 April 2011 (UTC) 301:10:28, 16 April 2011 (UTC) 807:16:24, 15 June 2011 (UTC) 771:10:14, 15 June 2011 (UTC) 747:16:09, 14 June 2011 (UTC) 725:22:55, 13 June 2011 (UTC) 816:Please do not modify it. 695:22:03, 20 May 2011 (UTC) 679:21:59, 20 May 2011 (UTC) 663:19:18, 20 May 2011 (UTC) 623:09:30, 10 May 2011 (UTC) 603:09:12, 10 May 2011 (UTC) 36:Please do not modify it. 757:(already approved) and 574:22:38, 5 May 2011 (UTC) 553:15:47, 4 May 2011 (UTC) 515:01:49, 4 May 2011 (UTC) 499:15:50, 1 May 2011 (UTC) 472:14:53, 1 May 2011 (UTC) 445:14:17, 1 May 2011 (UTC) 419:02:36, 1 May 2011 (UTC) 242:Already has a bot flag 148:Automatic supervised 341:Template talk:Convert 321:Minimum gauge railway 266:"5 US gallons (19 L)" 203:mosnum - Unit symbols 22:Requests for approval 153:Programming language 362:BAGAssistanceNeeded 229:Exclusion compliant 579:Links to results? 305:Some questions - 170:Function overview: 712: 254:Function details: 846: 818: 805: 780: 779: 710: 706: 661: 601: 561: 560: 551: 524: 523: 511: 468: 465: 462: 415: 412: 409: 366: 360: 50: 38: 854: 853: 849: 848: 847: 845: 844: 843: 829: 828: 827: 814: 784: 777: 723: 704: 640: 580: 563:Trial complete. 558: 530: 521: 509: 463: 460: 457: 410: 407: 404: 364: 358: 289: 216:Edit period(s): 124: 63: 34: 26: 25: 24: 12: 11: 5: 852: 850: 842: 841: 831: 830: 826: 825: 774: 773: 753:The scopes of 750: 749: 730: 729: 728: 727: 715: 698: 697: 682: 681: 626: 625: 606: 605: 518: 517: 487: 486: 475: 474: 433: 432: 428: 424: 423: 422: 421: 393: 392: 391: 390: 380: 379: 356: 352: 348: 344: 336: 335: 316: 313: 310: 288: 285: 284: 283: 271:miles per hour 267: 263: 256: 209: 208: 178: 123: 122: 116: 111: 106: 101: 96: 91: 86: 81: 76: 74:Approved BRFAs 71: 64: 62: 57: 56: 55: 29: 27: 18:Knowledge:Bots 15: 14: 13: 10: 9: 6: 4: 3: 2: 851: 840: 837: 836: 834: 824: 822: 817: 811: 810: 809: 808: 803: 799: 795: 791: 787: 783: 772: 768: 764: 760: 756: 752: 751: 748: 744: 740: 736: 735: 734: 726: 722: 718: 714: 702: 701: 700: 699: 696: 692: 688: 684: 683: 680: 676: 672: 667: 666: 665: 664: 659: 655: 651: 647: 643: 638: 634: 630: 624: 620: 616: 612: 608: 607: 604: 599: 595: 591: 587: 583: 578: 577: 576: 575: 571: 567: 564: 555: 554: 549: 545: 541: 537: 533: 527: 516: 513: 512: 506: 503: 502: 501: 500: 496: 492: 485: 483: 480: 479: 478: 473: 470: 467: 466: 454: 449: 448: 447: 446: 442: 438: 429: 426: 425: 420: 417: 414: 413: 402: 397: 396: 395: 394: 388: 384: 383: 382: 381: 378: 374: 370: 363: 357: 353: 349: 345: 342: 338: 337: 334: 330: 326: 322: 317: 314: 311: 308: 307: 306: 303: 302: 298: 294: 286: 281: 276: 272: 268: 264: 260: 259: 258: 255: 251: 249: 246: 243: 239: 237: 234: 231: 230: 225: 223: 219: 217: 213: 207: 204: 201: 200: 199: 196: 194: 190: 186: 182: 177: 173: 171: 167: 165: 163: 158: 156: 154: 149: 147: 143: 141: 138: 135: 131: 128: 120: 117: 115: 112: 110: 107: 105: 102: 100: 97: 95: 92: 90: 87: 85: 82: 80: 77: 75: 72: 70: 66: 65: 61: 58: 53: 49: 44: 42: 37: 31: 30: 23: 19: 815: 812: 781: 775: 731: 632: 627: 562: 556: 525: 519: 507: 504: 488: 481: 476: 459: 434: 406: 386: 304: 290: 253: 252: 247: 244: 241: 240: 235: 232: 227: 226: 221: 220: 215: 214: 210: 205: 197: 175: 174: 169: 168: 160: 159: 151: 150: 145: 144: 136: 126: 125: 68: 51: 35: 32: 611:Trial edits 162:Source code 60:Lightbot 13 763:Lightmouse 739:Lightmouse 687:Lightmouse 671:Lightmouse 615:Lightmouse 566:Lightmouse 491:Lightmouse 453:WT:MOSABBR 437:Lightmouse 369:Lightmouse 293:Lightmouse 287:Discussion 164:available: 130:Lightmouse 114:rights log 104:page moves 782:Approved. 609:Yes. See 325:Thryduulf 277:)" -: --> 127:Operator: 109:block log 833:Category 794:contribs 786:Headbomb 650:contribs 642:Headbomb 590:contribs 582:Headbomb 540:contribs 532:Headbomb 489:Regards 347:is real. 140:contribs 84:contribs 52:Approved 20:‎ | 821:WT:BRFA 798:physics 654:physics 633:problem 594:physics 544:physics 510:MBisanz 505:Recused 464:detroit 411:detroit 41:WT:BRFA 387:"U.S." 802:books 658:books 598:books 548:books 245:(Y/N) 233:(Y/N) 89:count 16:< 790:talk 767:talk 743:talk 721:cont 717:talk 691:talk 675:talk 646:talk 619:talk 586:talk 570:talk 536:talk 495:talk 441:talk 373:talk 329:talk 297:talk 275:km/h 273:(80 187:and 155:(s): 134:talk 119:flag 99:logs 79:talk 69:BRFA 707:. 461:MJC 408:MJC 250:No 94:SUL 835:: 800:/ 796:/ 792:/ 769:) 745:) 711:IM 693:) 677:) 656:/ 652:/ 648:/ 639:? 621:) 596:/ 592:/ 588:/ 572:) 546:/ 542:/ 538:/ 497:) 443:) 375:) 365:}} 359:{{ 331:) 299:) 195:. 142:) 823:. 804:} 788:{ 765:( 741:( 719:· 713:p 709:J 689:( 673:( 660:} 644:{ 617:( 600:} 584:{ 568:( 550:} 534:{ 493:( 439:( 371:( 327:( 295:( 282:. 248:: 236:: 137:· 132:( 121:) 67:( 54:. 43:.

Index

Knowledge:Bots
Requests for approval
WT:BRFA

Lightbot 13
BRFA
Approved BRFAs
talk
contribs
count
SUL
logs
page moves
block log
rights log
flag
Lightmouse
talk
contribs
Programming language
Source code
Knowledge:Bots/Requests for approval/Lightbot 3
Knowledge:Bots/Requests for approval/Lightbot
Knowledge:Bots/Requests for approval/Lightbot 2
Knowledge:Bots/Requests for approval/Lightbot 5
mosnum - Unit symbols
Exclusion compliant
miles per hour
km/h
Knowledge:Link#What_generally_should_not_be_linked

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