Wikipedia:Bots/Requests for approval/HawkEyeBot
- The following discussion is an archived debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA. The result of the discussion was Withdrawn by operator.
Operator: Sitongpeng (talk · contribs · SUL · edit count · logs · page moves · block log · rights log · ANI search)
Time filed: 18:38, Thursday October 11, 2012 (UTC)
Automatic, Supervised, Manual: Automatic
Programming language(s): Python
Source code available: https://github.com/stoneG/Slam_Tracker/blob/master/HawkEyeBot.py (uses pywikipedia)
Function overview: Update grand slam tennis statistics for professional male tennis players.
Links to relevant discussions (where appropriate): https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Tennis#HawkEyeBot Unfortunately I am the only one posting on this thread so far (as of 10/10/2012)
Edit period(s): Run four times a year, after grand slam tennis tournaments (Jan, Jun, Jul, Sept)
Estimated number of pages affected: 200 (first run through may be larger, like 500, as to check all players, but subsequent runs would only need to check those players who participated in the slam tournament)
Exclusion compliant (Yes/No): No
Already has a bot flag (Yes/No): No
Function details: Regarding exclusion compliance, this bot should never access other bot pages. This bot updates the statistics for professional male tennis players' grand slam performance, so it would only affect WikiProject Tennis. Specifically, it only affects one table on the page, called the Singles Performance Timeline. Essentially the bot uses the round performance specified in the table (so 2R or SF or W, etc) to determine the number of wins and losses that corresponds to. Then it calculates the statistics in the table (3 / 8, 32–5, 86.49) and edits the wiki article to update those statistics. The bot determines which pages to run based on a list it gets from it's own user page (or a list somewhere in its namespace). I have done some preliminary testing on wikia which you can view if you go to the user page for HawkEyeBot.
Discussion
editI looked through your code, it looked fine, though I don't think your edit summaries are appropriate (see WP:BOTREQUIRE). LegoKontribsTalkM 21:03, 11 October 2012 (UTC)[reply]
Also per WP:BOTACC, the bot account should identify the operator or bot function. — HELLKNOWZ ▎TALK 21:13, 11 October 2012 (UTC)[reply]
- Oh. Yes, I'm probably too eager with those edit summaries. I will tone them down. Also, I am identifying the bot operator on the bot tag of the bot user page and I describe the bot function in the ABOUT ME section but I will do my best to make those more apparent. Sitong 22:00, 11 October 2012 (UTC)[reply]
- Hellknowz is referring to the bot's username. LegoKontribsTalkM 06:56, 12 October 2012 (UTC)[reply]
- Yes, sorry, I meant "bot account's name should". — HELLKNOWZ ▎TALK 07:32, 12 October 2012 (UTC)[reply]
- I'd like to keep the bot username the same if possible. It is named after Hawk-Eye, the computer system that tracks ball trajectories in grand slam tennis tournaments. This system has the "final say" when players challenge line calls made by umpires. While I was writing the code, I fancied the idea that this statistics checking bot would act as the Hawk-Eye for those pages it ran on. Hopefully this is within the realm of naming the bot with regards to it's function. Also, I'm going to make the edit summaries more specific, I will let you know when I believe I have something that constitutes "good communication".Sitong 16:47, 12 October 2012 (UTC)[reply]
- The new edit summaries are: (if correction needed) Corrected statistics in the Singles Performance Timeline and updated timestamp for this run. Concerns/suggestions? See User talk:HawkEyeBot. (if no correction needed) Statistics in the Singles Performance Timeline are correct. Updated timestamp for this run. Concerns/suggestions? See User talk:HawkEyeBot. Sitong 01:00, 14 October 2012 (UTC)[reply]
- I'm ok with the new edit summary and I'm also willing to give leeway on the name (it at least include Bot). Will it be making a visible change when doing the "Statistics in the Singles Performance Timeline are correct. Updated timestamp for this run." edits? MBisanz talk 22:06, 15 October 2012 (UTC)[reply]
- No visible change, just a change in the timestamp comment. I can insert "so no changes have been made" at the end of that first sentence for clarity if that seems better? Sitong 01:49, 16 October 2012 (UTC)[reply]
- I'm ok with the new edit summary and I'm also willing to give leeway on the name (it at least include Bot). Will it be making a visible change when doing the "Statistics in the Singles Performance Timeline are correct. Updated timestamp for this run." edits? MBisanz talk 22:06, 15 October 2012 (UTC)[reply]
- The new edit summaries are: (if correction needed) Corrected statistics in the Singles Performance Timeline and updated timestamp for this run. Concerns/suggestions? See User talk:HawkEyeBot. (if no correction needed) Statistics in the Singles Performance Timeline are correct. Updated timestamp for this run. Concerns/suggestions? See User talk:HawkEyeBot. Sitong 01:00, 14 October 2012 (UTC)[reply]
- I'd like to keep the bot username the same if possible. It is named after Hawk-Eye, the computer system that tracks ball trajectories in grand slam tennis tournaments. This system has the "final say" when players challenge line calls made by umpires. While I was writing the code, I fancied the idea that this statistics checking bot would act as the Hawk-Eye for those pages it ran on. Hopefully this is within the realm of naming the bot with regards to it's function. Also, I'm going to make the edit summaries more specific, I will let you know when I believe I have something that constitutes "good communication".Sitong 16:47, 12 October 2012 (UTC)[reply]
- Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete. Let's do one run-through. MBisanz talk 03:25, 19 October 2012 (UTC)[reply]
- If I have understood the operation of the bot correctly then I think I have found a major problem with the process. Apologies if I am merely confused as to what information the bot is using. Please see the discussion I have raised on the bot's talkpage almost-instinct 18:53, 23 October 2012 (UTC)[reply]
- I currently have no process set forth to deal with walk-overs, nor do I have the time to implement it at this moment, so I am withdrawing this BRFA for now. I hope to come up with something in the future. Sitongpeng (talk) 22:38, 23 October 2012 (UTC)[reply]
- Okey, no worries, you can re-submit if you ever decide to pursue it in the future. MBisanz talk 16:04, 25 October 2012 (UTC)[reply]
- I currently have no process set forth to deal with walk-overs, nor do I have the time to implement it at this moment, so I am withdrawing this BRFA for now. I hope to come up with something in the future. Sitongpeng (talk) 22:38, 23 October 2012 (UTC)[reply]
- If I have understood the operation of the bot correctly then I think I have found a major problem with the process. Apologies if I am merely confused as to what information the bot is using. Please see the discussion I have raised on the bot's talkpage almost-instinct 18:53, 23 October 2012 (UTC)[reply]
- The above discussion is preserved as an archive of the debate. Please do not modify it. To request review of this BRFA, please start a new section at WT:BRFA.